<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Abexperiments on Michal Zygar</title>
    <link>https://www.mzygar.com/tags/abexperiments/</link>
    <description>Recent content in Abexperiments on Michal Zygar</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>All rights reserved - 2019</copyright>
    <lastBuildDate>Wed, 10 Apr 2019 22:49:50 +0100</lastBuildDate>
    
	<atom:link href="https://www.mzygar.com/tags/abexperiments/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>AB Experiments strategy</title>
      <link>https://www.mzygar.com/post/ab-experiments-strategy/</link>
      <pubDate>Wed, 10 Apr 2019 22:49:50 +0100</pubDate>
      
      <guid>https://www.mzygar.com/post/ab-experiments-strategy/</guid>
      <description>Sometime ago I&amp;rsquo;ve had a great discussion with Danny Ruchtie about the AB Experimenting on features.
Iterative design It uses grand design as a direction we’d like the project to go. However, the changes are introduced iteratively. Each change introduced is atomic. You get a clear picture whether it is improving KPIs or not. If not, you tweak it until you get a positive result. Then test next atomic feature on top of it.</description>
    </item>
    
  </channel>
</rss>