<?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 Marc Fulner on Medium]]></title>
        <description><![CDATA[Stories by Marc Fulner on Medium]]></description>
        <link>https://medium.com/@marcfulner1?source=rss-4198531b44bc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*vUyh-Drr3SVysGQz.</url>
            <title>Stories by Marc Fulner on Medium</title>
            <link>https://medium.com/@marcfulner1?source=rss-4198531b44bc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:18:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marcfulner1/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[What sports performance can teach Product Leaders]]></title>
            <link>https://medium.com/@marcfulner1/what-sports-performance-can-teach-product-leaders-89930440ee61?source=rss-4198531b44bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/89930440ee61</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Marc Fulner]]></dc:creator>
            <pubDate>Wed, 29 Apr 2020 08:10:41 GMT</pubDate>
            <atom:updated>2020-04-29T08:10:41.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IbE8TCQJRNl4gXMPPfs-g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@justinng?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Justin Ng</a> on <a href="https://unsplash.com/s/photos/mma?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>As a huge sports fan, I am fascinated by high performance. What makes the top teams, top athletes more successful? It’s reasonable to think that in any sport the top teams have similar resources; outstanding coaches, training facilities, nutrition, sports psychology. So what strategies do the most successful teams use, and can these same strategies be used in creating high-performance Product Teams? Looking through some notable sports performances, I’ve pulled out some key coaching concepts and show how they can relate to Product Leadership.</p><h3>Process versus outcomes</h3><p>Dave Alred is an elite sports performance coach known for helping rugby players, golfers and footballers. Dave specialises in handling pressure. He has an excellent set of tools to do this, but one area that initially felt very counter-intuitive to me is Process vs Outcomes.</p><p>You are judged on your outcomes. If you release a new piece of functionality and it is unsuccessful, then you are rightly judged on it. But should you be? Dave would argue that if an International Rugby Fly Half, missed the first three kicks in a game, then the outcome is poor. When that player lines up kick number four if they were to dwell on the previous outcomes, they would be less likely to make the kick. Think of the process, the hundreds of hours of practice will allow the player to step up with confidence.</p><p>Returning to your product team and an unsuccessful release. The outcome is poor. However, it’s well-known lots of new features fail, but was the process good? Did you de-risk the project by having a robust discovery phase? Was this prototyped and tested throughout the project? Did you transition to users in the right way? Finally, was it a ‘lean’ enough that failure is just another way to learn, and you can move on quickly to a more successful project. Product leadership is ensuring that you have robust, consistent practices across your teams, open challenging conversations and mechanisms to learn and improve.</p><h3>Thinking correctly under pressure (T-CUP)</h3><p>Clive Woodward won England’s first (and only) Rugby World Cup. He deployed a range of techniques one of his most famous is TCUP, thinking correctly under pressure. During a game, unexpected things can happen, you could be winning then concede several points very quickly. This sudden change in score could be enough to unsettle a team and ultimately lose the game. TCUP is a way to help players in pressure situations. Intelligent decision making improves when you remove the pressure. By simulation scenarios during training, safe space, you can quickly adapt in the moment.</p><p>As a product leader, you will often have stressful scenarios. We tend to live and work in the moment, thinking what’s in front of us instead of putting time aside for deeper considerations. Situations that could affect any product leader include; an unsuccessful major release, your software goes entirely down, simultaneous resignations in your team, an aggressive/loud/opinionated member of the C-Suite who derails much of your work. You may not solve all these problems, but by considering what is likely and how you would manage it will significantly improve your decision making in the moment.</p><h3>Marginal Gains</h3><p>British Cycling was in a significant slump when David Brailsford took over. David is credited for a massive turnaround in British track cycling ensuring a huge haul of medals most notable in London 2012. David then moved to road cycling managing Team Sky who won four Tour de France.</p><p>David accepted that most top teams are broadly the same. Similar levels of funding, coaching, the effort by the athletes. So what makes the number one team, number one? David focussed on marginal gains. Merely a 1% improvement across all activities, in combination with a continuous improvement mindset. Marginal gains could be extreme, having a wind tunnel so that every cyclist could improve aerodynamics, or much more straightforward, such as each cyclist taking their pillow when travelling to ensure the best nights sleep.</p><p>A simple lesson, 1%, David splits this into Strategy, Human Performance and Continuous Improvement. Within Product Leadership, the model can be used as-is. Continuous small improvements to the process, product strategy and your team will, over time, contribute substantial gains.</p><h3>Will this make the boat go faster?</h3><p>Ben Hunt-Davis was part of the British Rowing 8 team who won gold in Sydney. However, before this, the team had been around 7th for the previous two Olympic cycles. They knew the teams around them didn’t train harder, so why did they always do better? They realised that they had to train smarter, with the one critical question, by doing X will this make the boat go faster?</p><p>By applying this simple question to everything they did, it gave real clarity to what was essential or not. There is, of course, more to consider. Again, process over results, teams need to set common goals and clear your mind of other peoples opinions to name the few that resonate with me.</p><p>Transferring this to Product Leadership seems relatively easy at first. However, the trick is knowing what makes your boat go faster? In rowing it is simple, you want to win races, to win your boat needs to cross the line first, simple! What does that mean to your product teams? There is no hard a fast answer, it will depend, if you are B2B, B2C, how you monetise, etc. I would avoid financial objectives they are primarily consequences of other activities. Growth is always a good starting point; user, customer, market share. ;0)</p><h3>Conclusion</h3><p>All the names sports performance coaches have an array of techniques, and this just scratches the surface. I would recommend reading each in detail for more significant insights. The advantage of sport is that it is so much more focussed on a single goal than many Product Teams. Success is clear cut, being the first to cross the line, or the team with the biggest score. Product, unfortunately, isn’t quite as clear. However, knowing what winning is to your company will undoubtedly help, and using these techniques, which has helped some the most notable teams have incredible success may help your boat go faster!</p><h3>References</h3><ul><li>Dave Alred — book — The Pressure Principle</li><li>Clive Woodward — book — Winning</li><li>David Brailsford — YouTube —<a href="https://www.youtube.com/watch?v=THNBIQenywc"> https://www.youtube.com/watch?v=THNBIQenywc</a> (6:34!)</li><li>Ben Hunt-Davis &amp; Harriet Beveridge — book — Will it make the boat go faster?</li><li>Don’t tell me the score — Podcast — Interviews with many leading sports performance coaches and players.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89930440ee61" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“What we’ve got here is… failure to communicate”]]></title>
            <link>https://medium.com/swlh/what-weve-got-here-is-failure-to-communicate-40e8c9496baf?source=rss-4198531b44bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/40e8c9496baf</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Marc Fulner]]></dc:creator>
            <pubDate>Wed, 03 Jul 2019 07:05:13 GMT</pubDate>
            <atom:updated>2019-07-04T06:52:01.242Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aAXkqX-3cNpp0EGaXCplFg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@ptrikutam?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Pavan Trikutam</a> on <a href="https://unsplash.com/search/photos/communication?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>“What we’ve got here… is failure to communicate” — a great line taken from the film ‘Cool Hand Luke’ in which Luke, played by Paul Newman, is part of a chain gang in a US prison. Unbendable to the will of the warden, he hears the famous quote regularly before being punished. Ironically in this case the communication is crystal clear however, the protagonist chooses not to accept it.</p><p>Unlike the warden in Cool Hand Luke, communication at work is often lacking. How many times have we heard “We should have communicated better” after something has gone wrong? Sprint retros regularly have communication as a discussion item; be it a badly written user story or a dev decision to implement differently that wasn’t shared with a Product Owner.</p><p>The great thing about communication is that we are already experts at doing it: we talk to our friends, colleagues, people in shops all the time. So why is it we commonly fall down when important information isn’t shared?</p><h3><strong>WHY COMMUNICATION FALLS DOWN</strong></h3><p>Below I’ve listed 4 of the most common failures I see commonly happening in workplaces and easy solutions to prevent them happening in the future.</p><p><strong>PEOPLE ASSUME OTHERS ALREADY KNOW</strong></p><p>I think possibly the biggest issue — the person who knows about the problem believes that everyone else will also know. Two examples: one extreme and the second more commonplace. In 1986 the Space Shuttle Challenger blew up during launch. This cost the lives of the 7 crew on board and needless to say was incredibly sad. Later investigation identified that the fault was a simple o-ring which was known by the engineers to have issues. This had been communicated to management. However, the engineers had communicated by putting the issue as just 1 part of a 200-page powerpoint presentation. Not surprising that it wasn’t ever picked up by the management teams*.</p><p>Fortunately most mistakes aren’t so devastating. Most of us don’t work in environments where lives depend on our decisions. A more mundane example of communication falling down could be that a replacement product has a different permission structure to the existing one. The engineers know, the Product Manager knows, but the Product Manager only communicated with Customer Success and Support teams via documentation. On release, chaos ensues because users aren’t correctly set up.</p><p><strong>SOLUTIONS</strong></p><p>The Agile manifesto says it really “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation”. Replace the development team with people and it feels like a pretty solid argument to me.</p><p><strong>SCARED OF CONFLICT</strong></p><p>No one wants to be that person. You know the person who is just about to tell the CEO the product doesn’t work, or there is a major flaw, or it’s going to overrun by 4 months. By being that person you instantly become responsible, therefore the person to blame.</p><p><strong>SOLUTION</strong></p><p>Sometimes bad stuff just emerges at the end and if that’s the case your choices are limited, don’t hide it away, address it, address it now. This is the time to own it, if you’ve not read the book Extreme Ownership I would recommend you do (see References).</p><p>In this situation take full ownership, avoid blame and avoid ego. Arm yourself with all the facts, if you have solutions great but if not, at least outline what you will do to get to a solution. Your CEO will respect you more if you say “The new mapping feature I’ve been responsible for is flawed. I missed the fact the our users will need to geotag so they can find their customers and geotagging isn’t currently supported. If we go live now, we will totally miss the mark and this will be very hard to recover from as customers will rightly lose faith. I propose a two-month delay, this will allow time to rectify the fault and give us a great opportunity for maximum uptake”.</p><p>Your CEO is still likely to be annoyed however, she will be grateful that you identified an issue before it was too late.</p><p>Note that the person used ‘I’ instead of ‘we’. It’s human to subconsciously share the blame, however it’s important to take full responsibility, even when mistakes have been made collaboratively. Basically that is a difference between being a Leader and a Manager.</p><p><strong>WE WILL SOLVE BEFORE ANYONE NOTICES</strong></p><p>Even worse than being scared of conflict is trying to fix something without telling anyone and hope they never find out, or as I like to think of it, the ‘Nick Leeson Effect’. Nick Leeson was a successful trader in the ’90s. However, things went south and Nick made several losses. Rather than ‘owning it’ he hid it away in a separate account and made bigger and bigger trades to try and cover the losses so he wouldn’t be found out. Like a gambler on a losing streak his losses mounted until eventually he fled the country. It is estimated that the total loses plus the damage to his employer, Barings Bank, totalled over $1bn and eventually let to the collapse of the bank and prison for Nick.</p><p>Most issues are not as big as Nick Leeson’s. Features being released with known caveats, that are known to the Agile team just not anyone else is a more familiar scenario.</p><p><strong>SOLUTION</strong></p><p>Firstly, issues are never hidden, they will always emerge and the later it is left the worse it will be.</p><p>Share issues at the earliest opportunity and ensure they have been understood. This may be during the early discovery phase where a known behaviour will change. Don’t leave this until release: connect with the people it will affect, share including the implications. Depending on how political your organisation is this may need to be backed up by audited communication (email, slack etc). Being transparent will buy you relationship credit with your colleagues and within your organisation. This is important stock to have in the bank, as you never know when you will need to spend some ;0)</p><p><strong>I DID TELL YOU….ON SLACK</strong></p><p>PM “What do you mean we failed sprint, I’ve checked every day in standup and everyone said it was good”</p><p>DEV “It is good, but you know like I told you this story is more complicated so we are good, but not for this sprint”</p><p>PM “ I don’t remember you telling me”</p><p>DEV “ Dude I slacked you on Thursday in the ‘whatever’ channel”</p><p>Communication tools are brilliant for many, many reasons. As with all good things there are downsides. We have so many different ways to communicate plus high frequency of interaction, it is hard to keep track of what’s important.</p><p>Digital communication is Snapchat. By that I mean, in the moment, quick to send, quicker to forget, basically transient. With this in mind, anything with a degree of importance needs to be at the very least acknowledged and preferable face to face. I know many teams have great use of tools like Slack, and they are brilliant most of the time. The danger is important information gets lost, tools like Slack encourage a fire and forget mentality. Unless acknowledged, the information hasn’t been successfully shared.</p><p><strong>SOLUTION</strong></p><p>If it is not urgent and not important your preferred way of internal comms is fine. E.g. “Do you want anything from the shop?” then Slack is fine. If it has a further impact then it needs to be direct 1–2–1 verbal communication, ideally face to face. If that is not possible a telephone call or an online meeting like a hangout.</p><h3><strong>CONCLUSION</strong></h3><p>As humans, we are a social species. Higher communication is a major differentiator we have from other mammals, so use it. Make sure that important information is communicated, as early as possible, as detailed as needed and with the right people. When in doubt, over communicate.</p><h3><strong>REFERENCE</strong></h3><p>‘What we’ve got here is failure to communicate’ — Cool Hand Luke (1967)</p><p>Extreme Ownership — by <a href="https://www.goodreads.com/author/show/10803973.Jocko_Willink">Jocko Willink</a> &amp; <a href="https://www.goodreads.com/author/show/10803974.Leif_Babin">Leif Babin</a></p><p>Nick Leeson — <a href="https://www.investopedia.com/ask/answers/08/nick-leeson-barings-bank.asp">https://www.investopedia.com/ask/answers/08/nick-leeson-barings-bank.asp</a></p><p>Challenger Disaster — <a href="https://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster">https://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster</a></p><p>*Should be noted it has been documented that NASA had a very ‘control and command management structure in the 80’s. Engineers felt that they weren’t listened to so therefore could only highlight problems and issues indirectly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40e8c9496baf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/what-weve-got-here-is-failure-to-communicate-40e8c9496baf">“What we’ve got here is… failure to communicate”</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX for Product Managers]]></title>
            <link>https://medium.com/swlh/ux-for-product-managers-12a33cf78475?source=rss-4198531b44bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/12a33cf78475</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Marc Fulner]]></dc:creator>
            <pubDate>Mon, 03 Jun 2019 08:29:03 GMT</pubDate>
            <atom:updated>2019-06-04T13:19:18.831Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMD9hDJJX-MG8HZU9CVxqA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@alecuffia?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">José Alejandro Cuffia</a> on <a href="https://unsplash.com/search/photos/prototype?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The Product Manager’s job is to work with cross-functional teams to create great experiences by solving well-defined user problems. To do this successfully they need to be proficient in the technology, the business, and the user experience, popularly described in the below Venn diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mX2VPHSzmrLiTDPn" /></figure><p>Product Managers often focus their time and energy on the business and technology elements. Managing features requests, backlogs, roadmaps and communicating across the business. However, I feel that many Product Managers overlook User Experience and are lacking in these skills. It’s possible that this is down to the fact that UX has grown into a strong specialism in its own right over the past 10 years. Companies are now bringing in UX specialists, who take full ownership of this role as a defined function, and that really is a good thing.</p><p>A Product Manager doesn’t need to be a Product Designer, however, to be a well-rounded Product Manager you really need to understand the underlying principles of UX. Having a greater appreciation of UX will enable you to make better and more informed product decisions.</p><p>User experience is more than the user interface which encompasses what you see on a screen such as the buttons, colours, and fonts. UX is the usability of a product and considers areas like interaction design and human-computer interaction. In human terms, this really means designing with real people at the core. Producing a product which considers the overall experience that the user will have. It is focused on the needs of the user and the jobs (JTBD) or objectives if you prefer, that they are trying to accomplish. I think it’s de-focusing on internal goals and aspirations and looking at the product through the lens of the user.</p><blockquote>“de-focusing on internal goals and aspirations and looking at the product through the lens of the user”</blockquote><p>UX can be the starting process however, it often comes in during product discovery phase. To unpack slightly, let’s say you have an existing product. An opportunity/problem has been identified by the business. Solving this will help to differentiate your product, sell more licences, make your proposition more sticky blah blah blah. The business is fully on board and in fact already coming up with solutions, a bunch of features, metrics and deliverable timelines.</p><p>Before you jump down the rabbit hole this is time to switch focus, unleash your product management expertise, and lead and execute a well structured process of learning and discovery. As with all things you have a variety of product discovery tools and each PM has their preferences, however, ensure that you also incorporate the UX mindset. This can largely be framed using design thinking skills and enables you to frame your questions with the user in mind;</p><ul><li>What is the problem?</li><li>What are the user’s needs and priorities?</li><li>What are the user’s pain points?</li><li>Data analysis — to test your assumptions and current user behaviours.</li><li>Reframe your challenges as opportunities (how might we)</li><li>Ideation — Come up with the ideas.</li><li>Prototype by utilising Interaction design &amp; UI principles</li><li>Test by observing if this solution solves the problem.</li></ul><h3>CONCLUSION</h3><p>User Experience is a skill in its own right. It’s one that every Product Manager would benefit from learning and understanding. You don’t have to be a UX specialist but knowing the underlying principles will enable you to make better; decisions, processes and ultimately better products.</p><h3>ADDITIONAL RESOURCES</h3><ul><li>Dom Norman — NN/g Group — grandfathers of design agency, loads of research that can be used.</li><li>AJ&amp;Smart — Product Design Agency provides a lot of thought leadership especially around design sprints.</li><li>IDEO — the front runners of design thinking.</li><li>Jason Fried — thought leader — great for challenging the status quo</li><li>Steve Krug — Usability Guru.</li><li>Luke Wroblewski — you definitely have used software designed by Luke.</li><li>Inside Design Blog — Great insight into the world of design and UX.</li><li>Interaction Design Foundation — awesome training if you want to invest some time and learn more.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12a33cf78475" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/ux-for-product-managers-12a33cf78475">UX for Product Managers</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t forget the user]]></title>
            <link>https://medium.com/@marcfulner1/dont-forget-the-user-f325dd4bbe6?source=rss-4198531b44bc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f325dd4bbe6</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[productmanagment]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Marc Fulner]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 12:56:00 GMT</pubDate>
            <atom:updated>2019-05-01T12:29:27.132Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DM6WTkQXXMrFPkX05My_Mg.jpeg" /></figure><p>People are at the heart of Agile, design thinking and lean practices, so it’s surprising that users are often left out of product development altogether and when users are included it is often at the wrong times — their involvement reduced to nothing more than a token effort.</p><p>In this post, I’m going to explore the journey of a product development lifecycle and when you should and shouldn’t involve your users in order to create the best possible outcomes. I won’t go into detail on specific techniques but happy to explore these at different times.</p><p>To appreciate why teams make mistakes it is important to understand the boundaries that you and users share. Users are great at highlighting the problems that they face, they are great at testing solutions you put in front of them but are famously bad at coming up with solutions to a problem. Let’s face it why should they? That’s not their job it’s your job — you and your team have the skills, experience and knowledge to do it.</p><p>A great analogy is the Simpsons episode, ‘Homer Designs a Car’ — Homer is designated the average American, therefore whatever he designs will suit all Americans. The outcome is a shambles as you would expect, with a massive car fully equipped with 3 horns, muzzle for quarrelling kids and a massive price tag. The point being, users need to be part of the process but not running the process. The skill of product teams is to look deeper into the underlying issues and working with a cross-functional team to come up with amazing solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*dFZTNOBwqjXO22f8dVPEWA.gif" /></figure><h3>We have a problem… awesome</h3><p>The start of any project is when you have discovered a pain point, a problem that you believe can be solved through your amazing software. Nothing gets a Product Manager happier than a well-defined problem, especially if you think this isn’t being addressed in the marketplace. Some of the best ideas, however, turn into the worst products, so your first test is to see if your problem truly is a problem. Regardless of how this idea was conceived be it stakeholder, user research, internal feature request and so on, it needs to be tested with your users.</p><p>It’s important to remember that the actual building of the software is usually the most expensive part of your process. If your new product/feature fails then it’s likely you haven’t tested with users during the early part of the product development lifecycle . You should be doing as much as possible to de-risk any product development. Being able to qualify in or out new ideas at a very early stage is paramount to success.</p><p>Note: I’ve moved away from the term validation and think more about testing, perhaps just a semantic point, to me validation feels like we have already agreed to something and we are just checking the box to say it is ok. Testing means we have an idea and we are going to see what people think and most importantly we are prepared to learn from that.</p><h3>Research</h3><p>Now we have a well-qualified problem it is tempting to jump straight into a Product Design Workshop. However, before we even schedule a workshop, we need to establish customer needs, this utilises both qualitative and quantitative research.</p><p>The quantitative side typically has little direct user involvement and instead relies on analytics, market trends and surveys. Some established products have mechanisms to poll existing users which can be very powerful.</p><p>On the qualitative side however this will involve some in-depth user involvement, Great techniques include 1 to 1 interviews with experts and potential users. Many product teams like small group sessions although I’m not a fan of these, as you end up with group think, HIPPOS or dominant personalities stealing the show. These sessions are not about solutions more about better understanding the needs. What this does is to pick out the underlying issues, challenges and opportunities.</p><p>Example, you have identified that users want to take data out of your product. Through the research, you discover that users would be happy to export data from your product and put it into a spreadsheet. Involve users in your workshop and this is what you may end up with and it would be fine.</p><p>However, what are they doing with the data? Producing reports that they share with their leadership team as part of their monthly reporting. Therefore by understanding the type of information they produce for their leadership team we could build the reports within on our product. This would a) save the user time as they wouldn’t need to do it in a spreadsheet themselves, b) increase the number of time users spends in our product looking at analytics, c) increase licences, if the leadership team can access this from our system themselves they can access up-to-date reports whenever they want and d) increase stickiness of our product by adding more value for the user.</p><blockquote><em>“</em>People don’t know what they want until you show it to them. That’s why I never rely on market research. Our task is to read things that are not yet on the page.”</blockquote><p>This quote from Steve Jobs really capsulated it for me. You need to understand the underlying need (user research), come up with solutions (your team) and then test your assumptions back to the users.</p><h3>Product design workshop</h3><p>Stakeholders often assume that this is the time to get your users fully involved in the process, ‘if we are making a product for our customers surely we need them to be involved in the solution’</p><p>The most successful workshops I’ve had, the ones that have built the best products, haven’t involved users, not until the very very end when you are playing back your solution to them (testing). In my experience users fixate on their own use case and find it very difficult to think more broadly and to be fair why should they. They want the best product for themselves, whereas a product design workshop is about making the best solution for a wider breadth of users.</p><p>It’s worth reiterating the point here. During a Product Workshop users are not actively present or involved in this ideation phase. Any solution conceived however, MUST be tested back to users BEFORE you move onto development. This does not necessarily need to be during the workshop and most commonly isn’t. Remember, it‘s often not the first idea out of your Product Design Workshop that you end up taking through to Development. This is why user testing is so important at this stage.</p><h3>Construction/development</h3><p>We’ve identified a problem, came up with a solution and user tested. As we enter into the Development stage it’s important to continually get feedback so you can incrementally maximise the value your product offers your users . Hopefully, you are shipping your product in short iterations . This enables you to fulfil the build-measure-learn loop and will give you every chance of success. Build a bit, test the results, improve it for your users.</p><p>As your run through the development cycle you will likely have to compromise some features, let’s face it we never have time to build everything you will likely get to a point where you have to increase time, resource or reduce features. Again this should be a decision based on research, what is the core jobs of your product, what is the real value of your proposition? Asking users what the priority is and they will likely fixate on features that they want rather than the core jobs that need to be done.</p><h3>The Product Owner is not the User</h3><p>During your development, especially with Scrum Teams, you will have a Product Owner. Most commonly the Product Owner role is fulfilled by the Product Manager on the project. The Product Owner is a proxy for your user, the users representative on the team, able to answer questions during development around how the users would like to achieve a goal. This is based on in-depth knowledge of both the users and the product. The Product Owner should speak for your users when making decisions, however, they are NOT the user. A common mistake is Product Owners who haven’t had deep interaction with users and instead rely only on previous conversations, domain knowledge or just gut feeling, what they believe is best.</p><h3>It’s (a) live</h3><p>The only real way to judge the success of your initial idea is after you have shipped and measured against any objectives you had set at the beginning. Many great products and to be fair some not so great products get through all the above and then completely fail to gain traction in the market, ahem Segway, Nike Fuel Band and countless others. Having the right type of users, enough users and having them engage at the with times will help minimise risk and give the best chance of success. Once live you actually have the best volume of testing so don’t waste it, you may be surprised at which elements add the most value. Youtube, Slack and Groupon all started out as very different products, all were failing until they realised that just a small element of their product really held all the value to their users and they all pivoted around this core job — look up their stories they are great reads.</p><h3>Conclusion</h3><p>Keeping your users close to you as you run through a development cycle is really important. Ensure though that you are engaging at the right times to launch a successful product. Users are great at identifying problems and testing solutions and providing feedback. You and your team should be absorbing all the feedback and looking at the core jobs that the users are trying to achieve and build solutions that meet these jobs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f325dd4bbe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>