<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Fatih Güler on Medium]]></title>
        <description><![CDATA[Stories by Fatih Güler on Medium]]></description>
        <link>https://medium.com/@FatihhGuler?source=rss-ed1e953cea1a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cnaXpQ8cujVHsgtSBL8Jug@2x.jpeg</url>
            <title>Stories by Fatih Güler on Medium</title>
            <link>https://medium.com/@FatihhGuler?source=rss-ed1e953cea1a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 10:05:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@FatihhGuler/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Iteration Makes Perfect but How? Cont.]]></title>
            <link>https://medium.com/@FatihhGuler/iteration-makes-perfect-but-how-cont-9740063996b2?source=rss-ed1e953cea1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9740063996b2</guid>
            <category><![CDATA[iteration-planning]]></category>
            <category><![CDATA[kata]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[goals]]></category>
            <category><![CDATA[product-improvements]]></category>
            <dc:creator><![CDATA[Fatih Güler]]></dc:creator>
            <pubDate>Sun, 25 Feb 2024 11:32:18 GMT</pubDate>
            <atom:updated>2024-02-25T11:32:18.050Z</atom:updated>
            <content:encoded><![CDATA[<p>In my previous article, I wrote about the “product kata” approach. We discussed that product improvement framework should proceed in 4 main steps and that iteration can be used to achieve perfection by following these steps. In this article, I will try to examine the Kata approach using an example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MITQKt97xHtEoM1Io-6zmg.png" /><figcaption><strong>Product Kata</strong></figcaption></figure><h3>Case Study:</h3><p>Product: Fitness App</p><p>Case: Simplifying Signup Flow</p><h3>Lets understand background first:</h3><p>We were developing a fitness app targeting busy professionals seeking convenient workout routines. Our initial signup flow, however, was lengthy and complex, leading to high drop-off rates before completion. We wanted to improve the signup experience and increase user acquisition.</p><h3>Understanding the Directions:</h3><p><strong>Beyond KPIs:</strong></p><p>While increasing sign ups was crucial, user engagement and retention were equally important. Especially for the CRM department.</p><p>We need to analyze user feedback and usage data, revealing that users found the existing signup process cumbersome and time-consuming.</p><p><strong>Align with strategic goals:</strong></p><p>The company aimed to become a leading player in the on-demand fitness app market. It has become clear that increasing the number of known users which the CRM department can communicate with is a business necessity, especially for improving conversion rates. We need more sign up counts.</p><p>Moreover a signup flow that catered to users seeking quick and efficient workout solutions should be implemented.</p><h3>Analyzing the Current State:</h3><p><strong>Get diverse data:</strong></p><p>We need to collect data from various sources, including <em>user interviews, app store reviews, app analytic datas, and support tickets</em>.</p><p><strong>Identify root causes:</strong></p><p>Data revealed several pain points such as: excessive form fields, unclear value propositions, and lack of a progress indicator. Assume the lengthy process discouraged users and led to high abandonment rates.</p><h3>Setting the Next Goal:</h3><p><strong>Start with setting a “Why”:</strong></p><p>“Increase signup completion rate by 30% to acquire more users and achieve market leadership.” This “why” will clarify the goal and motivate the team.</p><p><strong>Check for SMART:</strong></p><p>Prior to establishing objectives in product management, it is crucial to evaluate their alignment with the SMART criteria.</p><p><strong>Specificity</strong> and measurability of the objective must be ensured. Event definitions necessary for <strong>measurement</strong> should also be planned separately. While all product managers strive for high levels of success, unrealistic goals can lead to decreased motivation and inefficiency. Therefore, it is essential to ensure that a <strong>achievable</strong> goal is set.</p><p>To prevent incorrect measurement and inconclusiveness, the objective must be related to underlying factors, <strong>relavant</strong>. Furthermore, measurement can continue indefinitely without yielding results. Therefore, it is crucial to ensure that the objective is pursued within a specific <strong>timeframe</strong>.</p><p>The goal is:</p><ul><li>Specific (30% increase),</li><li>Measurable (onboarding completion and sign up rate),</li><li>Achievable (increase by about a third),</li><li>Relevant (addressed root causes),</li><li>Time-bound (within 3 months).</li></ul><h3>Choosing the Next Step:</h3><p><strong>Prioritize experiments:</strong></p><p>We need to design an A/B test with two variations:</p><p>Original flow (Control Group): The existing signup process with multiple form fields.</p><p>Simplified flow (A Variant): Reduced form fields, clearer value proposition, and a progress indicator.</p><p><strong>Focus on learning:</strong></p><p>You need to measure success rate then conclude uplift rate. We claimed to increase onboarding completion rate and get more sign up. Thus we assign some events with some related parameters to some points such as “<em>onboarding_page_one_view</em>” to understand if the user sees the page and “<em>onboarding_page_one_button_click</em>” to understand if the user tends to go for the second step. By events, the experiment measured signup completion rate, time to complete signup, and user feedback.</p><h3>Results and Iteration:</h3><p>Based on our analytics data the simplified flow led to a 32% increase in signup completion rate, surpassing our initial target.</p><p>According to NPSs and review results, users found the new flow quicker and easier to navigate.</p><p><strong>Next Goal:</strong></p><p>Based on user feedback we see that onboarding flow needs to be optimized by adding social login options and streamlining the account creation process.</p><h3>Lessons Learned:</h3><p>The Product Kata provided a structured approach to identify and address user pain points.</p><p>Small, focused experiments allowed for rapid learning and iteration.</p><p>Continuous improvement based on user feedback is crucial for product success.</p><p>Remember, this is just one example. You can adapt the Product Kata to your specific context and goals to drive successful product iteration.</p><p>“Iteration makes perfect!”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9740063996b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Iteration Makes Perfect but How?]]></title>
            <link>https://medium.com/@FatihhGuler/iteration-makes-perfect-but-how-a197429c40f0?source=rss-ed1e953cea1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a197429c40f0</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[production]]></category>
            <dc:creator><![CDATA[Fatih Güler]]></dc:creator>
            <pubDate>Wed, 31 Aug 2022 20:17:22 GMT</pubDate>
            <atom:updated>2022-08-31T20:17:22.050Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>According to the Product Kata, there are 4 main steps we should follow while trying to iterate our product processes.</strong> These are,</p><p>1. Understand the directions <br>2. Analyze the current state<br>3. Set the next Goal <br>4. Choose step of product process</p><p>These steps will help you to understand and analyze your product’s current state then create small solutions to make it better. Let’s imagine togetger</p><ul><li><strong>**Understanding business KPIs provides to know direction of your company or the point it should reach.</strong></li><li><strong>*Next looking for the current state provides us to see the product’s position and wrong sittings.</strong></li><li><strong>**Then we will be able to set the next goal easily ‘fix the wrong sitting to reach KPI X’</strong></li><li><strong>**Last and the beginning of new iteration, look for user footprint in the app and experiment analytically.</strong></li></ul><p>Iteration is the collection of steps that the infinite loop enters. We know that a line consists of a set of points, and we can draw the line with small solutions in the productization process. It would be unwise to worry that the line was not formed during the point-building phase. Awareness of the Product Kata steps will help to prevent imposter and to ensure healthy productization iterations.</p><p>I will share my experiences comparing by Product Kata steps in my next post.</p><p>Thank you for reading…<br>Fatih</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a197429c40f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>