<?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 Ohad Kedar on Medium]]></title>
        <description><![CDATA[Stories by Ohad Kedar on Medium]]></description>
        <link>https://medium.com/@ohadkedar?source=rss-5562fb914b70------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*m8Kde18s6sIROZMOevpxVQ.png</url>
            <title>Stories by Ohad Kedar on Medium</title>
            <link>https://medium.com/@ohadkedar?source=rss-5562fb914b70------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:44:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ohadkedar/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[Move fast while breaking as little things as you can]]></title>
            <link>https://medium.com/@ohadkedar/move-fast-while-breaking-as-little-things-as-you-can-9fe8edc42d03?source=rss-5562fb914b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fe8edc42d03</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ohad Kedar]]></dc:creator>
            <pubDate>Mon, 17 Oct 2016 05:26:08 GMT</pubDate>
            <atom:updated>2016-10-17T05:26:08.300Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3T-43FgcfdKukw2GM6sLfw.jpeg" /></figure><p>Agile has become a buzzword. Many companies claim they work in an agile methodology, however, in reality most companies do not follow on all agile methodology principles. I actually do not see it as a bad thing. While the concepts behind agile development are imperative for a software company’s ability to advance itself, I believe each company should tailor their working methodology around their DNA, thus, there could not be a ‘one fits all’ methodology.</p><p>Having said that, the <a href="http://agilemanifesto.org/">agile manifesto</a> highlights four main values which are probably relevant for any variation of the methodology you’d encounter.<br>One of those values can act as an Achilles heel for product managers — <strong>‘working software over comprehensive documentation’</strong>.</p><p>The goal of releasing software soon and often is super important, especially at early stage. Product managers, therefore, often do not ‘spec’ out each feature in a heavily spec documentation, and rely on personal interaction and collaboration in order to make sure things are built correctly. However, documentation goes beyond a couple of comments in the code in order to make the code clearer for future developers to come or a couple of sentences in the feature release notes. In fact, the hard product work starts only after a feature has been shipped.</p><p>Failing to properly ‘document’ a feature could have a negative impact on two main objectives which are crucial in order for the business to move in the right direction.</p><ol><li><strong>The company’s ability to measure progress over time</strong></li></ol><p>Most features companies work on are optimization features, even for early stage companies.</p><p>Of course there are ‘blue ocean’ features, usually in the form of early experiments or MVPs of new products, which we cannot really expect the impact they would create. However, most of the stuff we work on, even if not explicitly defined as a V2 of an existing feature, are usually features that are tied to existing metrics. Let it be registration rate, activation rate, average transaction value, etc. Eventually, most features we build are designed to move the needle of one of those metrics. Thus, it is imperative that we measure the ongoing progress of each metric, and to be able to tie it to specific changes / improvements we had in our product. This is not always an easy task, especially if you move fast and favor ‘working software over comprehensive documentation’.</p><p><strong>2. Feature adoption across different teams within the company</strong></p><p>Whether a feature you worked on is customer facing or not, most chances are that other teams in your company should be highly acquainted with it.</p><p>The customer success team should be familiar with it in order to onboard existing customers.<br>The customer support team should know how to respond to potential issues customers may face.<br>Marketing teams should know how to ‘sell’ this feature to new leads, and occasionally also configure it differently for different marketing channels.<br>You get the idea.. If your own team is not fully acquainted with your product — how can you expect your customers to be?</p><p>Getting acquainted with a new feature is not always straightforward.. sometimes even for the feature requestor. Original vision of a feature might change during the product design or development phases, there might be configurations which control the appearance / behavior of the feature — Those are just some of the stuff that might stand in the way of feature adoption within your company. Lacking proper documentation makes it an even harder challenge.</p><h4><strong>Agile documentation — Making up for the absence of full documentation</strong></h4><p>The potential negative effects above should not send us back to the ‘spec-ing’ board.. Instead, we should find alternative ways to help us make up for the absence of a full spec.</p><p>The tactics below are just some of the ways I found to be very useful for that purpose:</p><ol><li><strong>Not company demos — working teams hands-on demo</strong></li></ol><p>Teams who work in <a href="http://scrummethodology.com/">Scrum methodology</a> usually have a company demo at the end of each sprint, where the new deployed version is presented for the entire company / team. While this demo is more effective than no-demo-at-all — it is almost impossible to craft this demo in an efficient way. Since the demo is intended for the entire company / team — have it too detailed and go over all the bits and bytes — you will have a demo meeting of several hours, where you will lose the attention of all members at some point. Have it too broad — you might get a lot of appreciation from the team, but probably a low feature adoption among the team.</p><p>In order to make this process more effective, limit the all-company demos you have just for big releases where it is important that all team members are familiar with the ongoing company effort and execution. For the rest — have a hands-on session with team members who this feature is relevant for. Go over the bits and bytes, see possible configurations, go over happy scenarios and end cases, but most importantly — see it in real action and make sure the feature will be utilized properly.</p><p><strong>2. Tracking product changes</strong></p><p>Keeping up with feature releases’ scope and dates can get messy. Sure, you can look in your Git changelog and see the capacity of each version deployed to your production environment. Beyond the fact that this process is too messy, this means relying on your developers to edit all the changes that got into the version. Even more so, it will not include any changes you performed in your product not by deploying a version — for instance: starting an AB test or changing a configuration. It is, therefore, critical that you document all changes that go into your product into (at least one) centralized place.</p><p>We maintain a ‘product versions and changes’ sheet which we document every change we perform in the product. In addition, we create annotations in each of our analytics tools for each new version deployed, making it easier to track changes in product performance over time.</p><p>Even if you know the date the feature was released on, as time passes, it is not that easy to remember what was the exact scope of V1 / V2 / … of a feature. It was Tomer’s, our CTO, idea to maintain a centralized UX presentation with ALL product flows under the same place. I admit that I was skeptical at first about how much this would be useful, but once we crafted some structure around this presentation by aggregating similar flows together and indicating release dates for each feature, this has turned into one of the most useful tools we have in the product development cycle, including our designers, developers and data people.</p><p><strong>3. Tracking product performance</strong></p><p>Being able to tell the date a feature was deployed on, covers the ‘When’ dimension. But there is another, more important, dimension — the ‘How’. As your product evolves it is harder to track the product performance and attribute the effect for a specific feature. We often revisit hypotheses which we already tackled in previous iterations. Failing to record the effects of new features and experiments in our product is likely to throw us off course, and perform redundant experiments without implementing the lessons we learned in the past.</p><p>In order to aggregate the lessons we have learned from every product change we performed, we created a new Trello board for ’Product analysis’, where we track all the effects each product change had. The board is comprised of lists of different areas within our product — registration, conversion, retention and other important flows and metrics in our business. Each card in the list is a summary of the performance of a feature or an experiment that contributed to the general metric it is nested under.</p><p>This is not a dashboard where you can see the performance of the feature, but we often attach the cards some charts we created in the feature dashboard we created in our analytics tools, in order to visualize the effect that product change had. Having such a centralized place where you can see the effect of related features, really helps you focus when you try to see the big picture.</p><p>Working software or Comprehensive documentation?<br>Like in any trade-off — there is no ‘win it all’ solution.<br>I will choose ‘working software’ over ‘comprehensive documentation’ every day.. But implementing the tactics above has really helped us keep our focus while also improving our product development cycle.</p><p>What about you?<br>Do you have any other tactics that helps your product development cycle?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fe8edc42d03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your product is not your customer’s product]]></title>
            <link>https://medium.com/@ohadkedar/your-product-is-not-your-customers-product-d13a120b43a0?source=rss-5562fb914b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/d13a120b43a0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-vision]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Ohad Kedar]]></dc:creator>
            <pubDate>Sat, 10 Sep 2016 06:23:17 GMT</pubDate>
            <atom:updated>2016-09-10T06:23:17.196Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K_IRMvR77iShjnMj09k8wg.png" /></figure><p>My daily routine usually starts with looking over a set of dashboards and reports, while drinking my morning coffee. Feeling the pulse of your product on a daily, better yet — hourly, basis is perhaps one of the most important traits a product manager must posses.</p><p>Like it or not, after a while sticking to this routine, you eventually get to the point where you grasp your own product as a set of funnels, conversion rates and cohort analysis reports.</p><p>Attend any product meetup, or mingle with other product managers in a conference, you’d usually hear a lot of discussions about average conversion rates, AB testing, registration flows and so on. While these rather technical objectives are crucial in order for you to <em>feel the pulse of your product</em>, they could easily take your focus out of the actual value the customer is getting out of your product, and that’s dangerous.</p><h3><strong>Value metrics over KPIs</strong></h3><p>While every (successful) business has those <em>technical</em> KPIs, each product generates a different value for the customer.</p><p>This is especially true for e-commerce and online-services businesses, where the mobile app or website, is usually only the discovery gateway for the actual product or service.</p><p>I’ll share a couple of examples from recent products I have worked on.</p><p>In <a href="http://www.myfanzone.com/?utm_source=ohad-blog&amp;utm_medium=medium&amp;utm_campaign=your-product-is-not-the-customer-product">Fanzone</a>, where we operate transportation solutions for live events, we were seeing pretty solid average conversion rates for our direct coach buses in many of the events we operated. However, as we started segmenting our customers, we saw very different conversion rates for customers in different cities. When we analyzed the data, we saw that the main difference between higher conversion cohorts to lower conversion cohorts, was the average distance from the customer’s home address to the nearest boarding point to the bus.</p><p>Put simply — the service which we marketed as a ‘door to door’ solution, failed to act as such in reality for many of those customers, yielded less value to the customer, which eventually translated into numbers and we saw lower conversion rates.</p><p>In order to leverage this opportunity, we crafted a procedure to optimize the boarding points’ location, aiming to maximize the reach of each boarding point to nearby customers. In recent events where this procedure was utilized we were able to double the amount of customers using our services.</p><p>During my time at LivePerson, where we operated a marketplace of professional experts, one could get an online professional advice in different fields (i.e. from a psychological therapist, a tutor, a lawyer, etc.), we were seeing very different retention rates for customers coming from different channels.</p><p>When we analyzed the differences between the different marketing channels, we were seeing that this pattern is kept across different channels which were sending customers to specific professionals on our platform. Meaning — the average retention rate of the customer was derived as a result of the professional from whom they received the service. While this makes a lot of sense, it is not always this easy to recognize these differences among your ‘merchandise’. This is even more true for early stage companies, which do not have a lot of traffic to be able to measure this statistically.</p><p>We continued slicing the data and isolated the dimensions which had high correlation with existing clients’ lifetime value, eventually baking those factors in the ranking algorithm in our product. This change was key in the overall onboarding experience of customers, as it meant that they were engaging with was a top tier professional, for whom they are more likely to return for a recurring advice.</p><h3><strong>Putting it to practice</strong></h3><p>In both of the cases I illustrated, we saw significant changes in customers’ behavior, which resulted as a difference in the actual ‘product’ or ‘service’ the customer was looking for.</p><p>It is often easier to look and solve pains for ‘top of the funnel’ issues. Go ahead and add a guest checkout flow, and you’ll see your <em>upper</em> funnel steps improve by 20–50%. Most likely, the effect on the overall conversion will not be as strong (if at all).</p><p>’Meeting the actual product’, however, is the last step in the funnel. Many times, the real value of the product is only grasped at this stage. I’ll argue that it is the most important step to look into.</p><p>While ‘top of the funnel’ steps will determine if customers are exposed to your product, this ‘last step of the funnel’ will determine whether the customer will use your product, return to your product and eventually will refer their friends to your product (as emphasized in Dave McClure’s <a href="http://www.slideshare.net/dmc500hats/startup-metrics-for-pirates-long-version">AARRR framework</a>).</p><p>In order to be able to measure this ‘last step of the funnel’, you must identify and isolate the key dimensions / characteristics of the <em>customer’s</em> product.</p><p>Since every product is different at its core, there is no one trick magic here.<br>There are two tactics I found to be working well in order to identify those dimensions.</p><p><strong><em>The qualitative approach</em></strong> — step in your customer’s shoes.</p><p>Use your product often — whatever your business is — talk to a therapist, join a group-chat, get a logo designed from a freelancer, etc.</p><p>Sometimes it is not that easy to use your product, especially not on a frequent basis — so go ahead and look in your <a href="https://fullstory.com/">Fullstory</a> user recordings (a great tool if you’re yet to be using it). Create segments of customers that ended up purchasing similar products (or dropping out of the funnel of similar products), and try to identify differences in the experience the customer is going through.</p><p>Did you experience friction while getting the service? Did the quality of the service met your initial expectations (your marketing messages)? If not, here is your chance to identify <em>failure points </em>and think what you can do in order to improve the service.</p><p><strong><em>The quantitative approach</em></strong> — slice your data, and then slice it again.</p><p>Most businesses already segment a lot of their data. But in many of these cases — this is a one-sided segmentation. For instance, segmenting acquisition channels, landing pages, customer demographics and even different product categories.</p><p>While we can learn a lot just from this data, there are are super important insights we can learn by segmenting the customer’s product usage or product selection. Looking on usage metrics, and then look back on the customers segments tied to those metrics can teach us a lot.</p><p>To illustrate this point, let’s think of a hypothetical example — Let’s say that <em>Uber</em> discovered it is seeing different retention rates for their customers based on the length of the first trip of the customer. While long trips have higher fees, thus may indicate on a big spender, most customers don’t have a lot of those. Hence, a customer with a relatively high final fee for his first transaction, might be less likely to return for a second ride. If Uber were only looking on the ‘revenue per user’ it would have been much harder to recognize this pattern, as the trip price is not tipped by the distance alone.</p><p>Having earned this insight, now Uber can act by identify riding patters of similar customers and think of ways to entice them to use their service for other trip categories (i.e. commute), which is more likely to turn them to a returning customer.</p><p>Combining the two approaches should give you a better picture of what your customer is really experiencing when using your product, or at least get you to ask those important questions regarding what really matters in your product.</p><p>It may seem like a complexed process. Well, it is…</p><p>While low hanging fruits may yield nice improvements in your product, the real gains are not likely to be lying there. Tackling the big issues I described above is what can take an average product to a great product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d13a120b43a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hi]]></title>
            <link>https://medium.com/@ohadkedar/hi-103e746b5e42?source=rss-5562fb914b70------2</link>
            <guid isPermaLink="false">https://medium.com/p/103e746b5e42</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Ohad Kedar]]></dc:creator>
            <pubDate>Sat, 10 Sep 2016 05:41:57 GMT</pubDate>
            <atom:updated>2016-09-10T05:41:57.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SoUhGxYC5C31J7PMJOPGTQ.png" /></figure><p>I love building stuff.</p><p>I got to build a lot of things during my lifetime.</p><p>Starting with Lego as a child, building websites as a teenager, crafting secret operations in my military service, developing mobile apps as an entrepreneur, eventually leading product teams building world class online products and services.</p><p>However, as for writing — This is the first blog post I have ever posted.<br>I have decided to give it a go for a couple of reasons.</p><p>Reading other people’s opinions and learning from their experience has taught me a lot throughout the years. Now it’s my turn to share some of the insights I gained to help others.</p><p>I also realized that one of the best ways to reflect on your own progress and really challenge yourself in order to bring you to the next level, can be achieved by sincerely sharing your opinions, thoughts and even more importantly — your second thoughts, with others (whom you trust).</p><p>I hope that by sharing some of my thoughts here, I would be able to do just that — challenge myself while sharing my experience with others, contributing to a better product community. <br>And hopefully receive feedback from you!</p><p>I currently serve as head of product at Fanzone, delivering a transportation platform for live events around the world, having previously led the product team of LivePerson’s B2C business. I also founded a couple of startups, which I, unfortunately, had to shut down, but the lessons I learned while building them were priceless.</p><p>When I’m not crafting user-experience stuff, I enjoy living in Tel Aviv with my wife, Gal, and occasionally take my bike out for a spin in the forest.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=103e746b5e42" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>