<?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 Roger Norton on Medium]]></title>
        <description><![CDATA[Stories by Roger Norton on Medium]]></description>
        <link>https://medium.com/@rogernort?source=rss-554aae931057------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*87gdT0i9ptxtLYzHqAGDZQ.jpeg</url>
            <title>Stories by Roger Norton on Medium</title>
            <link>https://medium.com/@rogernort?source=rss-554aae931057------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:36:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rogernort/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[How to Level Up as a PM]]></title>
            <link>https://rogernort.medium.com/how-to-level-up-as-a-pm-5f88a7edc39d?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f88a7edc39d</guid>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 11:09:22 GMT</pubDate>
            <atom:updated>2026-04-23T11:09:22.837Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H_T960RIVWKYkW9In-BTzQ.png" /><figcaption>Photo by <a href="https://unsplash.com/@cagatayorhan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Cagatay Orhan</a> on <a href="https://unsplash.com/photos/landscape-photography-of-mountain-i_ivTcj8GFo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I get asked this at least once a week: how do you level up as a PM? The roles of junior, mid, senior, and exec-level PMs are fundamentally different. The easiest way to get a promotion is to already be delivering (at least partially) at the level of the promotion. So, the most direct way to level up is to start doing more of the work that belongs to the level above you.</p><h4><strong>Junior PM: the Who and When</strong></h4><p>At this level, your world is mostly project management. You’re coordinating delivery, writing docs, running QA, managing backlogs, and keeping scrum rituals on track.</p><p><strong>Hard skills:</strong> docs, user stories, QA, backlogs, scrum<br><strong>Soft skills:</strong> collaboration, project planning, research</p><p><em>In practice: volunteer to run a customer interview even if it’s not your job yet. Write a one-pager on a problem you’ve spotted. Shadow your PM in sprint planning and offer to own a small feature end-to-end.</em></p><h4><strong>Mid-level PM: the What and How</strong></h4><p>Now you’re focused on finding opportunities and defining what to build. You’re thinking about customer needs, current value, and how to prioritise effectively.</p><p><strong>Hard skills:</strong> customer interviews, PRDs, ICE scoring<br><strong>Soft skills:</strong> product sense, negotiation</p><p><em>In practice: ask to own a discovery sprint. Write your first proper PRD and get feedback on it. Start running ICE scoring on your backlog rather than just taking priorities from above.</em></p><h4><strong>Senior PM: the Why</strong></h4><p>Similar to mid-level, but more strategic. You’re looking beyond your product to wider stakeholders, adjacent markets, competitive differentiation, and where your product fits in the broader landscape.</p><p><strong>Hard skills:</strong> analytics, product strategy, business cases, cost-benefit forecasting<br><strong>Soft skills:</strong> customer discovery, internal sales, stakeholder management</p><p><em>In practice: put together a competitor analysis nobody asked for. Write a one-page product strategy for your area. Start presenting to senior stakeholders, not just your immediate team.</em></p><h4><strong>Exec level: the org and the team</strong></h4><p>At this level, your focus shifts entirely. You’re no longer deep in the product. You’re asking: is the product team in the right place in the org? Are we delivering real value to the business? Do we have the right people and resources? Are we actually effective?</p><p><strong>Hard skills:</strong> org design, hiring, roadmap communication, board-level reporting, OKRs<br><strong>Soft skills:</strong> executive presence, cross-functional influence, team development, strategic storytelling</p><p><em>In practice: run a retro on how the product team operates, not just what it ships. Propose a change to how your team is structured or resourced. Start thinking about hiring — what skills are missing?</em></p><p>Notice the pattern: as a junior, the world is black and white. As you level up, it becomes shades of grey. The answers get harder, the trade-offs more complex.</p><p>The upside: as you get better at the higher-level work, the lower-level stuff gets easier and more obvious.</p><h4><strong>So how do you actually level up?</strong></h4><p>Start doing more of the tasks and thinking that the next level requires. Identify waht that looks like in your current situation and define your growth path. Intentionally carve out time for it and start delivering and acting at the higher level. You’ll do your current job better, and be the most likely choice when a promotion is up for grabs.</p><p>Change the target, and the actions fall into place. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f88a7edc39d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product the WAY, not product the THING.]]></title>
            <link>https://rogernort.medium.com/product-the-way-not-product-the-thing-67739ee6e1e6?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/67739ee6e1e6</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Thu, 22 Jan 2026 18:34:17 GMT</pubDate>
            <atom:updated>2026-01-22T18:34:17.391Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the most common mantra I share with founders and product teams I’m coaching. Don’t just focus on delivering one piece of value. Rather, focus on how the team works in making decisions, communicating and collaborating; and if we can build good habits in how our team delivers value, we’re more likely to continue delivering value over time.</p><p>The greatest value a product brings is its ability to break down silos. It fosters increased communication, collaboration, and customer-centricity across various departments within an organisation. An important aspect of product management is organisational design, how teams work together, how we innovate, and what principles and habits the organisation needs to build to continually deliver value.</p><p>Many product managers are fixated on the ‘thing’ they’re building — be it launching a new feature or shipping an app. They are output-focused. I believe that ‘Product’ (as a discipline) is more about the way in which we build products, and that’s a much more effective thing to focus on. We’re not trying to build just one thing, we’re trying to design processes and structures that can enable our team or our organization continue to deliver great things. Again and again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uYBNBkEEJjQIfd_Pv7iLJQ.png" /><figcaption>When any great sports team trains, the coach first needs to get the foundations right. Things like trust, patterns, strategy, and team cohesiveness. Then they can focus on a few special moves, but they’ll always fall back onto and adjust around the foundations as a game unfolds. They start with the processes, not the scoring moves.</figcaption></figure><p>When thinking about “Product the way” not “product the thing” we don’t focus on the output of what we’re building. We focus on how the team works in making decisions, communicating and collaborating. And if we can build good habits in how our team delivers value, we’re more likely to continue to deliver value than if we focus on just shipping one good thing. (Actually focusing on the thing is less likely to make it good if you don’t have the org culture in place to ensure it.)</p><p>At the heart of this approach are key habits that signal a team’s focus on the ‘way’ they build a product.’ These habits are:</p><ol><li><strong>Customer-centric value creation.</strong> Are you speaking to customers regularly, at least on a weekly cadence?</li><li>Having <strong>a clear vision and mission</strong>. What is the goal? Where are we going? How do we get there?</li><li><strong>Data-driven decision making.</strong> Are we using data in order to inform our decisions or are we running purely on intuition without actually backing up intuition with data?</li></ol><blockquote>All entrepreneurs are a little bit <strong>delusional</strong>, because you have to be to build something that <strong>others can’t see</strong>. But data is how you <strong>don’t get lost in that delusion.</strong> And so if you’re not using data you’re very likely to just be the coyote running off the cliff without realizing that there’s no more cliff.</blockquote><p>4. Lastly, <strong>breaking down silos.</strong> The biggest value Product brings as a hybrid discipline is in breaking down silos and increasing communication, collaboration and customer-centricity across the various teams or departments of an organisation. The more you can break down those silos, the more you can actively drive better feedback loops, cross-pollinate ideas and build relationships between teams that don’t normally interact with each other. Which makes it more likely that you are able to continually innovate as an organisation.</p><p>With these four habits in place, you’ll focus more on Product the way and not product the thing.</p><p>So don’t just focus on the next thing that you’re delivering or the next task at hand. Rather, focus on the way in which your team thinks about building products. Focus on how they combine, collaborate, communicate and make decisions so that you can build many great products, not just one. Then, hopefully, continually iterate and continue improving those great products.</p><p><em>If you enjoyed this, you’ll likely enjoy the expanded 10 principles too. These cover far more areas on how to become Product-led organisation and create a framework on how to evaluate tools, methodologies and approaches to improve your team. Read on here:</em></p><p><a href="https://rogernort.medium.com/10-principles-behind-great-product-teams-21b77ab7b54b">10 Principles behind great Product teams</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67739ee6e1e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build software: Do it. Document it. Then Automate it.]]></title>
            <link>https://rogernort.medium.com/how-to-build-software-do-it-document-it-then-automate-d82c95af4455?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/d82c95af4455</guid>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Fri, 28 Jun 2024 07:14:43 GMT</pubDate>
            <atom:updated>2024-06-28T07:18:10.552Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TIzcua0xA_PlxLHI4Wg0xQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@halacious?utm_source=medium&amp;utm_medium=referral">Hal Gatewood</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I ran a startup studio which consulted by building tech for 50+ startups over 6 years. These 3 steps are the most common advice I gave to anyone* wanting to build software.</p><p>Once you think you have the solution to a potential customer’s problem, <strong>the wrong move</strong> is to run off to raise some money, hire a team build lots of software and try to launch it 6–18 months later… <strong>The right move</strong> is to solve that problem today. Ideally for money. Then you solve it again. And again.</p><p>The reason this is better is because you have solved a customers problem. Secondly, because in doing so you’ll invariably learn a lot of new things that you didn’t know you didn’t know before. And getting real money is the best indicator that a problem is worth solving.</p><blockquote>*The advice is most applicable to service based applications, but not exclusively.</blockquote><h3>Here’s how it works:</h3><h4>Step 1: Do it.</h4><p>Whatever it takes to solve the customers problem, with the funds, time and capacity that you have available to you right now. Then do it again, maybe for a different customer. The things you’ll learn will astound you.</p><h4>Step 2: Document it.</h4><p>While you are doing the thing, over and over, start to write down the process. Map the flows and decisions. Template out all the messaging and copy. Do this well enough and you should be able to hire an intern to also do it for come more customers. Interns are cheap.</p><h4>Step 3: Automate it.</h4><p>Interns are also not very smart, so you need to be quite explicit. You can now start using some low code tools and services to string it together for you. Documenting explicitly how to run a process repeatedly to solve customers problems also happens to be exactly what developers need in order to actually write some code for you. Ideally, you’ve now run this enough times to not need make too many big complicated, and costly, changes along the way.</p><h3>The benefits</h3><p>The reason this works is because <strong>you don’t know what you don’t know</strong>. Every idea is filled with assumptions and uncertainty. Only a solution that has repeatedly been delivered helps you know those things. “Get out of the building” as they say.</p><p>For example, if you’re manually doing the matching in excel and sending emails then you can make changes on the fly. Every customer can be charged differently when you email your pricing. Experiments can be rapid and improvements constant. Once something is coded it’s slow to change (unless you’re the developer) as you need to explain it, and scope it, and add it to the backend, add it to the frontend, and test it and fix it…</p><p>Software developers are expensive. It helps to know exactly what you need them to build.</p><p>Oh, and you could solve the customers problem today well enough that they’d actually pay you for it. Having real revenue from real customers is a great way to persuade developers that they should work for you — or to find investors that will give you money to pay them...</p><p>So next time you have a great idea for an app/service/website, stop. Rather be <a href="https://medium.com/playlogix/startups-need-a-problem-not-a-solution-c1fdfff6c95f">Problem, not Solution focussed</a> and go through the hard work of serving and learning — not the easy work of designing and speculating. You’ll save yourself a ton of time and money in the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d82c95af4455" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When good business advice is wrong for you.]]></title>
            <link>https://rogernort.medium.com/why-good-advice-is-wrong-for-you-4fb4c10ee562?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fb4c10ee562</guid>
            <category><![CDATA[startupş]]></category>
            <category><![CDATA[building-a-business]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[startup-advice]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Wed, 19 Jun 2024 06:36:48 GMT</pubDate>
            <atom:updated>2024-06-20T09:57:57.438Z</atom:updated>
            <content:encoded><![CDATA[<p>There is plenty of good advice for starting a business out there. However, “good advice” is relative. What makes sense for one situation might be wrong for another. This makes generally good advice,<em> wrong for you</em>.</p><p>“Entrepreneurship” encompasses such a wide spectrum of businesses — from a tuck shop to OpenAI. If you’re not discerning about what type of business you’re trying to build, you’ll find that most well-intentioned advice might lead you astray. But how do you know when it’s a fit?</p><h4>Startup vs Traditional (small) business</h4><p><em>Technically</em>, a ‘startup’ is a business which is small. And a ‘small business’ is starting up — but in reality they couldn’t be more different.</p><p>Add on another layer with ‘deep-tech’ or ‘tech-enabled’ businesses and the advice gets more inappropriate to your situation and things get messy.</p><p>Most advice out there only applies to a certain context with generally applicable advice so broad it’s not particularly useful. Knowing what type of business you are, goes a long way to filtering for good advice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*_e38h9-pQKnoIPJ9KZuCbQ.png" /><figcaption>Typical advice applies to only one of these quadrants but how you build a business in each varies wildly!</figcaption></figure><blockquote><strong>Side note:<br></strong><em>I generally find that the distinction of B2B vs B2C is also a relevant one that has a large impact. However, it is better understood and easier to spot. And although it changes most tactics and some areas of strategy (go to market, engineering, timelines, partnerships, risk) at the early stages of getting to PMF and fundraising it has an influence but less of an impact.</em></blockquote><blockquote><em>Note also that there are exceptions to every rule and while I focus on clear-cut examples, there’s a fair bit of grey area for you to apply a dose of common sense to.</em></blockquote><p>Lets dive into what these terms mean.</p><h4>A small business is…</h4><p>… the most common ‘traditional’ business worldwide. It starts small and can grow into a medium business, and then (hopefully) a big business. They do this sustainably by reinvesting some of their profits back into growth. If it stays small it’s called a lifestyle business. They are focused on <strong>sustainability</strong> and grow as fast as reinvesting the profits will allow.</p><h4>A startup is…</h4><p>…“a temporary organisation in search for a sustainable and repeatable business model,” according to the grandfather of the concept, <a href="https://steveblank.com/">Steve Blank</a>. It’s a bold experiment (gamble) to push the boundaries and create something novel. It’s designed to learn as quick as possible and optimises for <strong>rapid growth — </strong>or to fail fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pohftxvmo32aj4rpvl30Qg.png" /><figcaption>This sentiment by <a href="https://www.linkedin.com/in/earlystagesales?miniProfileUrn=urn%3Ali%3Afs_miniProfile%3AACoAAAO0q4QBt22QEspexaiyL09iKK90oINwzhY&amp;lipi=urn%3Ali%3Apage%3Ad_flagship3_search_srp_all%3BnlD4ThHLQmaeyQ7wlgLM9Q%3D%3D">Jen Abel</a> sums up the definition of a startup.</figcaption></figure><h4>Deep tech is…</h4><p>…A company where the <strong>core value that you deliver is the technology</strong>. Customers buy access to the technology and the technology is the value delivered. You can’t deliver an AI experience without the LLM or decentralised trust without something like a blockchain. If you remove the technology, you remove all the value. (These used to just be called “tech startups” until <a href="https://a16z.com/why-software-is-eating-the-world/">software ate the world</a>…)</p><h4>Tech-enabled is…</h4><p>… When you use software to deliver a product or service. (Think <a href="http://uber.com/">Uber</a> or <a href="http://takealot.com/">Takealot</a>) The customers aren’t actually buying the software or technology, they’re buying the car ride, shoes, advice, music, or access to a person to do the task. These tech-enabled businesses use tech to scale, but the <strong>customers are buying something else.</strong></p><blockquote>Small (traditional) businesses optimise for sustainability. <a href="https://www.paulgraham.com/growth.html">Startups optimise for growth</a>. It changes everything.</blockquote><h3>When good advice goes wrong: the advice mismatch</h3><p>These 4 quadrants help map out very different types of businesses. Each with completely different advice. Some are optimising for profit, others scale. Some need a technical co-founder, and some don’t. Far fewer than you think should raise venture capital.</p><p>There’s a lot of advice for entrepreneurs out there. But almost none of it applies to all situations except some very obvious things These nuances fundamentally change who you hire, how you spend, how quickly to grow, if you should patent, where to cut corners, etc.</p><p>Some obvious things might apply to all of these business types: e.g. hire well, be ethical, build team trust, have a clear vision, etc. But the nuances fundamentally change how you approach: who you hire, how you spend or raise money, how quickly you grow, how to protect IP, where (and if) to cut corners and a million other things that affect your business.</p><p>Knowing what type of business you are is a useful rubric to discern whether advice that sounds good actually applies to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*OfICcYHPfpzyvsyqjXkKVw.png" /><figcaption>Here’s that 2x2 again. This time with examples.</figcaption></figure><h4>Good types of advice for each quadrant</h4><p><strong>1/ Deep-Tech Startup.<br></strong>This is a tech-first business that needs to be able to scale fast. Some things to consider:</p><ul><li>You need to hire some very expensive engineers upfront to develop an initial version of the product. You need a superb technical co-founder since technology is <em>the </em>core value driver.</li><li>It has huge potential to scale with high margins (&gt;75%) and (hopefully) reach millions of users.</li><li>It will likely take longer to get your first customers due to longer product development and longer sales cycles. Having a co-founder who buys in and converts some of their pay into equity is super helpful. You need all the runway you can get.</li><li>It’s also high risk as if it ends up shutting down, there is usually no asset because very specific, half-baked software generally isn’t useful. There may be some patents, but they often aren’t worth much out of context and are better at defence while you’re alive.</li><li>It’s a great business profile for venture capital funding as it needs a lot of upfront R&amp;D to build the asset.</li><li>It can win VERY big. It’s an attractive acquisition for how it fits into an acquirer’s product suite or distribution engine - or simply to stop you from competing.</li></ul><p><strong><em>Example categories</em></strong><em>: AI, web3, product based SaaS</em></p><p><strong>2/ Tech-Enabled Startup.<br></strong>This is a business that sells a product and service and is able to scale fast due to tech. Things to consider:</p><ul><li>As above in its growth/exit potential and high margins.</li><li>These are typically asset-light (Uber doesn’t own cars, AirBnB has no properties) and the technical challenges come from scale, not the core service.</li><li>Distribution, marketing and sales make these work and they often rely heavily on network effects or product-led growth to do that. You’ll need a growth hacker or some marketing/branding savant as a founder.</li><li>Venture capital is a good fit for these but only later as growth capital and not upfront R&amp;D.</li><li>The asset of value, in the end, is the network and distribution channel.</li></ul><p><strong><em>Example categories</em></strong><em>: Gig marketplaces, sharing economy, e-commerce super stores, social networks</em></p><p><strong>3/ Deep Tech Small Biz</strong><br>This is where you’re developing something novel and patenting the heck out of it. It may be some hardware, medical or engineering breakthrough. Technology or a unique research insight is at the core of what you’re doing.</p><ul><li>To do this you need bucket loads of funding to cover the upfront R&amp;D and manufacturing. Early funding from universities, government, or NPOs is a good fit. Later, some VCs or Private Equity investors will back these businesses due to their potential and defensibility.</li><li>Even if they fail they’ll often have valuable technology or assets left over.</li><li>Taking venture funding early would be a disaster as the timelines take too long to make a VC return.</li><li>Your margins are usually thin, particularly at low manufacturing volumes, and you need to build up physical distribution and sales — likely through partners.</li><li>In the end your Intellectual Property or its licensing is what will be most valuable.</li></ul><p><strong><em>Example Categories:</em></strong><em> Inventions, medical devices, hardware, wearables, IT infrastructure</em></p><p><strong>4/ Tech-Enabled Small Biz.</strong> <br>This is a traditional business and most businesses fall into this category. Tech enables all businesses in some way nowadays — as admin software or a website. Most non-technical entrepreneurs are building this type of business. It’s the easiest to get off the ground but as such is the most competitive.</p><ul><li>It often starts as a consultancy for the founder’s skills and scales by productising their processes and methods. This could be through hiring more people to do what you do or to automate it through software.</li><li>While they can grow fast, they are hard to scale and need to evolve a lot as they do.</li><li>The asset of value over time is the current and future client relationships.</li><li>These are not a fit for venture capital funding as their margins are too low, and their scale is too slow.</li><li>There isn’t a real asset of value at the end of the day — other than the team to be <a href="https://en.wikipedia.org/wiki/Acqui-hiring">acqui-hired</a> or dividends paid out.</li></ul><p><strong><em>Example categories:</em></strong><em> Lifestyle businesses, consultancies, service businesses, niche e-commerce</em></p><blockquote>Advice out of context helps no one.</blockquote><p>Entrepreneurship is hard. Building new things is hard and most people want to help entrepreneurs. But don’t take on all the well-meaning advice on ‘how to build a business’ out there.</p><p>The next time someone shares some advice, consider where it is coming from, who it’s for and if it applies to you.</p><p>It’s likely good advice, but wrong for you.</p><p><em>A huge thanks to </em><a href="https://www.linkedin.com/in/sona-mahendra/"><em>Sona Mahendra,</em></a><em> </em><a href="https://medium.com/@olumideebigbola"><em>Olumide Ebigbola</em></a><em>, </em><a href="https://www.linkedin.com/in/renier-kriel/"><em>Renier Kriel</em></a><em> from </em><a href="https://www.theopenletter.io/"><em>The Open Letter</em></a><em>, and </em><a href="https://www.linkedin.com/in/ACoAAC5SQD4BY8TaQbjNRIVJXz48cG-04n4cWnU?lipi=urn%3Ali%3Apage%3Ad_flagship3_messaging_conversation_detail%3B0Ix%2Fy3z9SCKtxsY4Ykhm6w%3D%3D"><em>David Wright</em></a><em> for feedback on this piece.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fb4c10ee562" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Conversations that will immediately level-up a PM]]></title>
            <link>https://rogernort.medium.com/3-conversations-that-will-immediately-level-up-a-pm-591401171264?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/591401171264</guid>
            <category><![CDATA[conversations]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Fri, 05 Apr 2024 10:04:32 GMT</pubDate>
            <atom:updated>2024-04-05T10:04:32.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9Ry-pVK5KdYG-FXBmi0_A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Christina @ wocintechchat.com</a> on <a href="https://unsplash.com/photos/two-women-sitting-beside-table-and-talking-LQ1t-8Ms5PY?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>Information, understanding and insights are the currency of a good PM. Being in the know, knowing the facts, and being able to reference real customer feedback is the easiest way to stand out and nudge conversations towards value delivery and away from strong internal opinions.</p><p>Here are 3 conversations that you should have (or be part of) to help give you this edge:</p><ol><li><strong>Ask a developer to draw your stack. </strong><br>Knowing how your system works and how all the services, servers and apps connect at a systems level is critical. It helps you understand the technical constraints and limitations while also knowing when to pushback or how to propose solutions that actually work. You don’t need to know all the details of how they all work, but at least knowing how it all fits together will go a long way. It’s also a great way of getting more respect from your dev team and fostering tighter relationships with them as you can relate to their work. (<em>This is also one of my tips to become more technical without learning to code, </em><a href="https://medium.com/@rogernort/technical-pms-dont-need-to-code-3439278d28cd"><em>read more here.</em></a><em>)</em></li><li><strong>Ask someone in finance to talk you though how the company measures unit economics for your product. </strong><br>A PM’s job, according to <a href="https://www.svpg.com/value-and-viability/">Marty Cagan</a>, is to focus on Value and Viability. You quite simply can’t know viability if you don’t understand how your product captures value for the business — i.e. how you make money off it. That means you need to chat with someone in your finance team to run you thought how they allocate costs to calculate COGS, what revenue is actually generated, and what influences or discounts reduce that. You need to understand how the business thinks about the core unit economics for your product and how it fits into the the revenue across the org. Go to the source.</li><li><strong>Sit in on sales / customer support calls. </strong><br>The first part of ‘Value and Viability’ is how you’re delivering value to customers and how they perceive the way that you solve their problem. You have to get this directly from the mouth of the customer. You should get summary and quantitative data through personas, summaries or reports. But nothing replaces the richness of qualitative comments directly from a customer. Bonus is if you can pop in a few questions to dig deeper on key insights as sales and support are often discussing symptoms not causes.</li></ol><p>The best <a href="https://medium.com/founders-factory-africa/what-is-product-64e426500539">definition I have</a> for the role of a PM is: <strong>to deliver value to customers in a way that adds value to the business, while understanding technical constraints.</strong></p><p>If you’re not having these 3 conversations then I don’t know how you can claim to do that. So, what are you waiting for?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=591401171264" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What changes as PM levels up?]]></title>
            <link>https://medium.com/people-in-product/what-changes-as-pm-levels-up-69126c11ba93?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/69126c11ba93</guid>
            <category><![CDATA[product-management-career]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Tue, 12 Dec 2023 14:20:56 GMT</pubDate>
            <atom:updated>2023-12-12T14:20:58.529Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7woqLyXcBgaR78V69YvRRg.png" /></figure><p>If you’re wanting to know how to level up your career in Product, it helps to know what actually changes as you progress. A career in PM changes so much as it goes that often it looks completely daunting when you see others further along the path. <em>How do they context switch so much? How do they know all that stuff? How do they have all the answers???</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//twitter.com/BeauBlinder/status/1708840509387800874%3Fs%3D20&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fabs.twimg.com%252Ferrors%252Flogo46x38.png%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/3167b0a26af680105cecf19617ac0143/href">https://medium.com/media/3167b0a26af680105cecf19617ac0143/href</a></iframe><h3>Career levels</h3><p>More than most other careers, in Product Management the <em>timeline of</em> <em>impact</em>, <em>activities</em> and <em>focus</em> with regards to how your role adds value changes as you level. Here’s a breakdown of how I think about each and what you should probably master next if you want to move up.</p><h4>Junior (0–3 years experience)</h4><p>In the beginning you’re going to be pretty hands on in “getting the muck through the pipe.” You’re going to be running stand-ups, writing PRDs &amp; user stories, doing QA, interviewing customers, diving into data, and lots of project management type work. It’s very hands-on and delivery focussed.</p><p><em>The focus: delivery and execution.<br>Time horizon: 0–3 months</em></p><h4>Mid-level (3–6 years experience)</h4><p>At this point you’re probably doing similar activities as you were but are starting to work more on processes and templates. You’re thinking about creating structure and systems to make your ‘doing of the work’ easier. You’re starting to question prioritisation as you decide what is most important and you’re hopefully shifting to focus more on outcomes than outputs. You should be driving key insights and findings all the way from discovery through to delivery and measurement as you look at the whole delivery process not just the tasks and items — although there is still a lot of hands-on work involved.</p><p><em>The focus: Are we building the right thing, and are we building it right?<br>Time horizon: 3–9 months</em></p><h4>Senior (6–10 years experience)</h4><p>This is where you really start to take ownership of how what you’re building adds value to the company. How does the product fit into the larger offering to achieve business objectives? What are new opportunities should you be exploiting? At this point you should be the “mini CEO” of your domain and starting to think strategically about P&amp;L, customer trends and maximising value-add of your domain. (<em>A ‘domain’ could be specific product [Consumer App], a whole suite [Delivery apps] or area [Platform] depending on your company.</em>) You’ll also be doing a fair bit of team management, process improvement and monitoring delivery.</p><p><em>The focus: How do we add more value to the business? <br>Time horizon: 6–24 months</em></p><h4>Executive (+10yrs experience)</h4><p>At this point things start to get a lot fuzzier and very context dependant. Typically though, you’re going to be the overarching strategic leader in the organisation around value creation and capture. You’re thinking about the fundamentals that need to be true for this product to win in the long run, looking at how the product team interfaces with the rest of the organisation, and evaluating team impact and resource planning. I find at this level you’re typically focusing much further ahead outside the company as well as looking at how your team operates within the company. You’re pattern matching larger trends and diving into the details to course correct when you need to.</p><p><em>The focus: What do we need to win? <br>Time horizon: 18–36months</em></p><h3>Product the way, not Product the thing.</h3><p>The best way that I can articulate the shift as you level up is that you start to focus more on the <strong>way</strong> in which your teams <em>communicate, collaborate and make decisions</em> in how they create value; instead of focusing on the <strong>things</strong> that you’re building. I believe that if you can set up a team in the right <strong>way</strong> they can build many great <strong>things</strong>. (<em>Read my </em><a href="https://rogernort.medium.com/10-principles-behind-great-product-teams-21b77ab7b54b"><em>10 Principles of great product teams</em></a>)</p><p>I’m not saying more senior PMs won’t sometimes go deep — the best ones do regularly. But, as you level up you’re asking and answering higher-order questions that make the lower level questions either obvious or irrelevant. In the quoted tweet above, the Head of Product isn’t context switching all the time, they’re just fitting a wide array of problems into a larger mental model. It’s a different skill set and a different way of thinking that you develop over time — aka “experience”.</p><p><em>If you liked this, you’d like my other post on “🎄</em><a href="https://rogernort.medium.com/building-your-pm-career-48f58c126786"><em>Building a PM career</em></a><em>” that unpacks what opportunities to focus on as you level-up. But also check out my full list of Product related posts </em><a href="https://rogernort.medium.com/list/all-things-product-ad65f4db9177"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69126c11ba93" width="1" height="1" alt=""><hr><p><a href="https://medium.com/people-in-product/what-changes-as-pm-levels-up-69126c11ba93">What changes as PM levels up?</a> was originally published in <a href="https://medium.com/people-in-product">People In Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical PMs don’t need to code]]></title>
            <link>https://rogernort.medium.com/technical-pms-dont-need-to-code-3439278d28cd?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/3439278d28cd</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technical-product-manager]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Wed, 06 Dec 2023 09:46:32 GMT</pubDate>
            <atom:updated>2023-12-06T09:46:32.171Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many ways to become more technical as a Product Manager without learning how to code. Don’t get me wrong, having experience in shipping real code helps — it’s just not a requirement.</p><p>Here are 3 areas to improve technical proficiency without needing to learn how to code:</p><h4>1) SQL &amp; JSON</h4><p>Getting a solid understanding of how to write SQL queries to extract data from a database will go a long way to giving you solid building blocks for technical data manipulation. On top of that, being able to understand a JSON payload and its formatting helps a lot too.</p><h4>2) APIs and Auth</h4><p>Getting your head around using Postman to connect to APIs and make calls and get responses. Part of this will help you get your head around basic auth, jwt tokens, keys etc. You don’t need to write code to read the API docs and connect via tools, but understanding this will take you a long way to better testing and understanding what developers need to deal with.</p><h4>3) a modern Web stack</h4><p>The last area that I’d encourage PMs to understand is how software is architected and how all the parts connect together. You won’t need to build this from scratch, but being able to understand an app architecture map and know what the various services are and what they do goes miles. The easiest way to get this is to sit with a developer on you team and have them explain your current software. There are also plenty of examples online of popular companies and how their stack is constructed.</p><p>For all 3 of these areas, you don’t need to learn how to program. Ironically, most PM courses don’t cover these and the best learning resources will be found via Google or Youtube.</p><p>Getting an understanding of these will get you miles ahead of most PMs. It will also build great street cred with developers while you ask a lot less stupid questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3439278d28cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hold strong opinions tightly]]></title>
            <link>https://rogernort.medium.com/dont-hold-strong-opinions-lightly-6fb2d95ac09b?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fb2d95ac09b</guid>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Sun, 13 Aug 2023 12:37:50 GMT</pubDate>
            <atom:updated>2025-03-06T14:42:08.883Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*CYfWOgW_72lhDeFK5hl2oQ.png" /></figure><h4>I often hear people claim to have “strong opinions, loosely held,” as if it’s a good thing. But this is actually a toxic stance that undermines exactly what the speaker is trying to imply.</h4><p>When people use the phrase they want to imply they are decisive but not headstrong to the point of being unreasonable. That they’re willing to change their mind when presented with enough counter-evidence. Which sounds reasonable. But it’s actually an idiotic stance.</p><p>This piece from David Perell’s post on ‘<a href="https://perell.com/essay/how-philosophers-think/">How Philosophers think</a>’ highlights a core issue with how our brains work on this.</p><blockquote>The less time you give yourself to think, the more you’ll settle on <a href="https://perell.com/essay/narrative-market-fit/">socially rewarded points of view</a>. The early research on this idea goes back to a psychologist named Robert Trivers, who did most of his work in the 1970s. He argued that the human brain was designed to deceive itself. We distort information to make ourselves appear better than we actually are.</blockquote><blockquote>In his book <a href="https://amzn.to/3fZJtZW">The Folly of Fools</a>, Trivers argues that a contradiction lies at the heart of human intelligence. Our brains are simultaneously designed to seek out information and destroy that information after we acquire it. Specifically, our minds evolved to make sense of the world not in ways that are true, but in ways that help us survive. But once all that information enters our minds, we ignore critical information and believe self-serving falsehoods. Often, the more we distort information, the more rational we think we are. And so, we applaud ourselves for clear thinking even though we see the world through a tainted prism of self-serving beliefs. Summarizing his work, Trivers once said: “We deceive ourselves the better to deceive others.”</blockquote><h4>Strong opinions</h4><p>Having strong opinions implies that you believe that this opinion is most often correct. It’s formed through a lot of experience and reinforcement of facts that it is true. They’re incredibly useful because once we have them they can shortcut decision-making. You can rely on it instead of having to re-test a theory from the ground up. It helps to minimise the problem space by relying on a strong opinion to remove a lot of uncertainty.</p><p>The darker side of a strongly held opinion is that we’re more likely to defend it if challenged. If it was correctly formed, there should be enough evidence for us to know it’s most likely right. And hence, worth defending.</p><p>Here’s a quote by <a href="https://nicharry.medium.com/5-business-lessons-2015-taught-me-22d0c7a73ce3">Nic Harry</a> that I ‘strongly’ disagree with:</p><blockquote>Sometimes it’s good to hold strong opinions in the face of doubt and relentlessly defend them. Other times it pays to be nimble with your movements as well as the decisions you make when the facts around you change.</blockquote><blockquote>Hold strong opinions weakly or they might sink you.</blockquote><p>Maybe, the better strategy is to not hold them strongly in the first place.</p><h4>Loosely held.</h4><p>It’s not unusual for a person who says this to be comfortable with and embrace conflict. But not everyone is like that. Not everyone wants a conversation to be a robust debate. There are many forms of collaboration that don’t need conflict.</p><p>Holding strong opinions results in others tending to shy away from that area. People are actually less likely to challenge you on it. If you are holding it lightly and change your mind when they do, they’re going to see the conflict as even more pointless.</p><p>This makes it less likely to put yourself in situations that give you the information to correct a poorly formed opinion. Meaning you’re even more likely to stay wrong. It’s silly to hold an opinion strongly if by doing so you’ll prevent the necessary engagement to improve it.</p><h3>Strong opinions, strongly held.</h3><p>The best thing to do if you’re open to having your mind changed on something is to approach it with curiosity. To be humble about your knowledge and engage from a point of learning. It’s hard to do that with strongly held opinions.</p><p>If you need to be able to rely on an opinion, you should hold it strongly. But you should also ensure that it’s robustly formed. This likely means that you should hold fewer opinions strongly — and that’s a good thing. You shouldn’t be building sturdy houses on sand.</p><p>Stop holding strong opinions lightly. Either hold strong opinions (that you ensure are actually robust and where understand their limitations) or don’t hold them as strong opinions.</p><blockquote><em>Strong opinions should be strongly held. If you can’t do that, the answer is not to hold them lightly, but to not have the strong opinion in the first place.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fb2d95ac09b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Demystifying Product Market Fit]]></title>
            <link>https://rogernort.medium.com/demystifying-product-market-fit-e1f77c49533d?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1f77c49533d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-market-fit]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 08:38:01 GMT</pubDate>
            <atom:updated>2024-02-29T10:43:55.052Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qfMRbPCdAAGgQfk1qu_xZw.png" /></figure><p>Product Market Fit is the holy grail of early-stage startups, but it is so poorly understood. It’s why I’ve previously posted on <a href="https://medium.com/p/8bacdd67685">Why PMF is a bad target</a>. Since then, I’ve refined my thinking around how to make it more measurable, and, therefore a better target.</p><p>It needs to be much more specific and measurable than “<em>a feeling</em>” or “<em>if you have to ask you don’t have it</em>” nonsense. It’s also more than just a high NPS score or “a pull” that are completely unactionable. Or a willingness to pay that is obvious but hard to find signal in the noise. A good set of measures for PMF should be unambiguous and actionable.</p><p>Startups are all about building solid fundamentals. The way you define and measure PMF should be a measure of those fundamentals. Ultimately, you need to have 3 things: (1) growing demand from users who (2) regularly receive value and (3) stick around. What that means is…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yfHOa255jezJhxMbbh6dZw.png" /></figure><p>It’s worth noting that as the name suggests, product market fit is relevant to a specific product, in a specific market solving the needs of a specific customer segment. As one of those change, you’re going to need to optimise for another PMF and it’s not the case that once you have it you will always have it.</p><p>Aiming for PMF is also most relevant to early-stage, pre-Series A startups. That’s because it is the clearest indication of a startup having solid fundamentals at this stage. After Series A, revenue, margins, &amp; profit, etc become clearer to track and a more reliable indicator.</p><blockquote>ASIDE: Revenue in the early stage is often a very misleading measure to focus on (despite some investors loving it…) This is because some revenue can be generated from highly inefficient businesses that won’t scale well or falsely inflated by paid media where growth stops when you stop paying.</blockquote><h4>Definition of Product Market Fit</h4><p>The most useful and definitive description of PMF that we’ve found is based on the Trifecta from <a href="https://twitter.com/bbalfour">@bbalfour</a>:</p><p><strong>1) Double-digit user growth.</strong> (i.e. you are rapidly acquiring new users.) For different businesses, this may be over a week, month or quarter. You’ll know what is right for you</p><p><strong>2) Meaningful engagement</strong>. Once again, what is meaningful will differ per startup, but it’s useful to think of it as the frequency of core value delivery. What is the most valuable action that customers take on your platform? Can you get them to take it every day for a week? Forget the other fluff.</p><p><strong>3) Solid retention.</strong> Are people sticking around? If you have week on week engagement, do they do that each month? What is the customer’s lifetime for using your product? For B2C company 20–40% is good, for B2B good is 40–60% of users who sign up stay for an extended period (years). Have a look at <a href="https://www.lennysnewsletter.com/p/what-is-good-retention-issue-29">this post by Lenny</a> for a more detailed breakdown.</p><blockquote><strong>Only when you can show a (1) rapidly growing user base that are (2) actively engaged and (3) getting enough value so that they stick around for a long time can you claim to have </strong>Product Market Fit<strong>.</strong></blockquote><p>It’s also important to note that PMF depends on a specific combination of a <strong>Product</strong>, to a specific <strong>customer segment</strong>, in a specific <strong>market</strong>. When you change any of those, you are aiming for a different PMF. These “different PMFs” are the inflexion points in your <a href="https://medium.com/founders-factory-africa/creating-a-vision-mission-f0d1c1e3a813">Master Plan or Company strategy.</a></p><blockquote>Example of a Master Plan<br>(1) Build a high-end sports car for wealthy people in the US <br>(2) Build a mid-range family car for that same audience &amp; slightly lower in a small number of US &amp; EU markets. <br>(3) build a mass-market car and expand sales globally. <br>At each step of its <a href="https://www.tesla.com/blog/secret-tesla-motors-master-plan-just-between-you-and-me">Master Plan, Tesla</a> needed a new PMF target.</blockquote><p>So, although it can be quantified and clearly defined, PMF may change as your business grows. And that’s OK. That’s the point of strategy. But the most valuable thing for a startup to do in the early stages is to focus on getting to PMF in order to build solid fundamentals.</p><h4><strong>In Summary:</strong></h4><ol><li>Identify the inflection points in your Master Plan as a combination of <em>Product</em> to a <em>Customer segment</em> in a <em>Market</em>.</li><li>For the next inflection point define what rapid user growth, meaningful engagement and solid retention will look like.</li><li>Start with optimising for engagement, then acquisition, then retention.</li><li>Reach PMF and repeat for the next inflection point.</li><li>World Domination.</li></ol><blockquote>If you want to read further on this and the processes around how to deliver it, I highly recommend <a href="https://medium.com/founders-factory-africa/a-systematic-tool-to-help-african-startups-find-product-market-fit-5ed089f26fa8">A tool to help African Startups systematically find PMF.</a></blockquote><p>Huge hat tip to <a href="https://www.linkedin.com/in/steven-waidelich-1407386/">Steve Waidelich</a> and the wider Studio team at <a href="http://www.foundersfactory.africa/">Founders Factory Africa</a> that have been with me on this journey for clearer measurement and definitions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1f77c49533d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Principles behind great Product teams]]></title>
            <link>https://rogernort.medium.com/10-principles-behind-great-product-teams-21b77ab7b54b?source=rss-554aae931057------2</link>
            <guid isPermaLink="false">https://medium.com/p/21b77ab7b54b</guid>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-tools]]></category>
            <dc:creator><![CDATA[Roger Norton]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 09:02:05 GMT</pubDate>
            <atom:updated>2023-06-26T09:02:05.262Z</atom:updated>
            <content:encoded><![CDATA[<h4>“Should we use Scrum, Kanban, or SAFe?” is a version of a question I get asked all too often. I’ve found it’s more useful to answer these questions systemically by looking at what weakness the team has behind the question.</h4><figure><img alt="A collection of icons that Stable Diffusion thinks are product frameworks" src="https://cdn-images-1.medium.com/max/1024/1*mBUD7vn5ovbp7QmDR6jQVw.png" /><figcaption>“Product frameworks” image made by Stable Diffusion 1.5 via <a href="http://playgroundai.com/">playgroundai.com</a></figcaption></figure><p>As the ‘Product’ discipline is still developing, there are so many new ways of doing things. I often get asked what the best tool, methodology, or framework is to use for product roadmaps, creating a strategy, or running a backlog. The answer is always the same: <strong>It depends.</strong></p><p>It depends on your team culture, expertise, and personalities; it depends on your industry and clients, as well as your current systems and tools. Many variables make it impossible to know which tool will work best in each situation. But how do you know where to start?</p><p>I’ve realised that by taking a first-principles approach by assessing the strengths and weaknesses of the team, the problem becomes a lot simpler. Comparing a team to the fundamental principles that drive all great teams and then picking a tool/framework/methodology that will help to correct for where your team is lacking.</p><p>Here’s a summary of the <strong>10 Principles</strong> that I evaluate a team on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8GiIzuaTmv_PK2kUNYIaA.png" /></figure><h3>Breakdown of the principles:</h3><p>You’ve likely heard each of these principles before, and they’re relatively widely accepted. Effectively cliches that are so common they won’t go away. However trite they may be, I’ve found that they offer a valuable lens to be more intentional when choosing a tool or approach for a specific situation.</p><p>Below, I break down each principle in this context and explain what actions (⚡️) you can take to implement it and a list of tools, frameworks or methodologies (🛠) that could help. At the end, I’ll cover how I do the assessment and link to a <a href="https://coda.io/d/Tools-DB_dULT7z0JTEG/Product-Tools-DB_suPc7#Tools_tu5ms/r1">repository</a> that I’ve started building that can be filtered by principle. (These are still WIP, and I’d love some feedback.)</p><h4><strong>(1) Metrics &amp; measurement</strong></h4><p>The first foundational piece that every team needs (and that we too often see missing) is actually collecting data on what your users are doing. Specifically, this should be something where you can track actions by cohorts of users (per month, account type or source) and not just generic traffic. i.e. Mixpanel or Amplitude and <strong>not</strong> Google Analytics.</p><blockquote>⚡️ If you don’t have analytics set up, you’re flying blind and can’t do most of the other items on this list properly. Create a <a href="https://help.mixpanel.com/hc/en-us/articles/115004519886-Creating-a-Tracking-Plan">Tracking Plan</a>, implement it and <a href="https://info.amplitude.com/behavioral-data-event-tracking?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=Search_EMEA_EN_Topics_BOFU_Growth&amp;utm_content=143394307337&amp;utm_term=tracking%20plan&amp;gclid=Cj0KCQjwk7ugBhDIARIsAGuvgPbs0sfggj_9GOIWKnSdgE2qNfHowS4qrgXwQ0DYtVz2LJcKi4po9nMaAgXXEALw_wcB">learn how to use it</a>. Doing this right is table stakes nowadays.</blockquote><p>Once you have it in place, create a few reports of key engagement metrics, how you define activation for your product and a retention analysis chart. Try to avoid focussing on lagging metrics or ones that don’t actually mean much. e.g. instead of tracking the <em>number of sign-</em>ups, <em>track the % of people who signed up and took a key action in the last three days</em>. Ensure they’re action orientated and not just a pat on the back. (Hint: Revenue is nice, but it doesn’t tell you much if it’s not qualified.)</p><p>🛠 <a href="https://mixpanel.com/">Mixpanel</a>, <a href="http://amplitude.com/">Amplitude</a>, <a href="https://amplitude.com/blog/product-north-star-metric">North Star Metrics by John Cutler</a> at Amplitude</p><h4>(2) Customer Centricity</h4><p>While analytics will give you quantitative data, interacting with customers gives you qualitative data to balance it out. Having multiple team members engage with customers in the customers’ context is absolutely critical for hearing their issues and understanding their motivations directly. Too many teams operate in echo chambers where their picture of their customer is fraught with incorrect assumptions.</p><blockquote>⚡️ Take actions like setting up a weekly block for customer interviews and then having an automated opt-in for customers to be able to get added to a wait list where they get sent <a href="http://www.calendly.com/">Calendly</a> invites to join in the time slots to provide feedback. Another is to have developers spend a day a month working with the customer support team to resolve tickets or shadow the sales team for the day. It’s all about creating a routine to lower the barriers for your wider team to engage with customers directly.</blockquote><p>When you have multiple team members engaging the customers regularly, you don’t need intricate customer profiles, complex reports or a “<a href="https://firmbee.com/scrum-guide-6-who-is-a-product-owner">customer representative</a>” in the team. First-hand data backed up by analytics are far more effective. Remember that this is for qualitative data collection and creating a shared understanding — be careful <a href="https://rogernort.medium.com/customers-cant-innovate-for-you-f92efb792e37">not to let your customer innovate for you.</a></p><p>🛠 <a href="https://www.producttalk.org/2022/12/customer-interviews/">How to do customer Interviews</a> by Teresa Torres</p><h4><strong>(3) Learning Loops of Experimentation</strong></h4><p>With the data foundations in place, a necessary mindset is to think in learning loops. Life is hardly ever black and white. There are always other ways to achieve your exact goals — each with its trade-offs. And you’re going to get it wrong the first time, which is fine.</p><blockquote>If you respond quickly to change, it doesn’t matter where you start. Only that you do.</blockquote><p>The core lesson from The Lean Startup is to <strong>increase the rate of learning</strong>. To do that, you run through the build, measure and learn loop as quickly as possible. You often do that by spending less money, but sometimes you need to spend more to accelerate. The trick is to rapidly keep running experiments and learning from the results before deciding what to experiment with next.</p><blockquote>⚡️ To run any experiment, you need to have some key elements. Namely, a falsifiable<strong> hypothesis</strong> of what you believe, a <strong>method</strong> to describe what you’re going to do, something that you’re going to <strong>measure</strong> while you do it, and finally, <strong>success criteria</strong> for what the measurement needs to be for the hypothesis to be true or false. Strategyzer’s <a href="https://www.strategyzer.com/blog/posts/2015/3/5/validate-your-ideas-with-the-test-card">Test Cards</a> are a great template for this. This approach also implies a high shipping cadence to deliver new iterations of your product.</blockquote><p>This behaviour in a team will help you iterate through many solutions to find what works. It helps you get through what is an assumption and what is a fact — so that you’re not building your house on sand.</p><p>🛠 <a href="https://www.strategyzer.com/">Strategyzer</a>.com is a great starting point.</p><h4><strong>(4) Instinct informed, data validated.</strong></h4><p>Sifting through piles of raw data will sometimes help you discover a new insight, but usually, that’s not where new insights come from. It’s far more common for you to stumble across something interesting from qualitative customer data or an idea that sparks in a team conversation. It’s then up to you to find the qualitative data to back that up.</p><p>Similarly, identifying a data trend and blindly following it can also be risky. Both intuition and data are important counterweights.</p><blockquote>Startup founders are all a little delusional — you have to be to see something that others can’t.</blockquote><blockquote>Data is how you don’t get lost in the delusion.</blockquote><blockquote>⚡️ Asking: “how might we know for sure?” is a great question to bring some balance to your team. Bringing an emphasis on validating assumptions with a real number helps too — but remember to expect insights to come from the softer stuff.</blockquote><p>🛠 <a href="https://medium.com/thesis-of-uijun/hypothesis-testing-01-assumption-mapping-f4a918fc721f">Assumption Mapping</a> or <a href="https://heartofthecustomer.com/journey-mapping-to-hypothesis-mapping-creating-better-cx/">Customer Journey mapping</a> can be useful to make your assumptions explicit and easier to test.</p><h4><strong>(5) Outcomes over Outputs</strong></h4><p>This saying has become cliché for a reason. Far too many ‘road maps’ are feature release plans. Far too many “experiments” are specific functionality to be shipped and not hypotheses that can be tested in multiple ways. Too often, teams look at the data, decide on a solution and ship just that. They focus on the <strong>things</strong> that they are building, not the <strong>value</strong> they are adding.</p><blockquote>⚡️ Focussing on the value that you want to create for customers and phrasing your road map as the order of problems to solve is one of the easiest shifts that can have a profound impact on the way your team approaches what you build. Having a definition of done that measures value delivery helps too. One of the huge benefits of this is that Outcomes can be measured, whereas Outputs are shipped or not. Part of delivering value is continually measuring the impact instead of just moving onto the next thing.</blockquote><p>When you are P<a href="https://medium.com/playlogix/startups-need-a-problem-not-a-solution-c1fdfff6c95f">roblem-focused, not Solution-focused</a>, you are far more likely to see many possible solutions to any given problem. You’ll start working in trade-offs and compromises — how real life actually works. Remember that there is <a href="https://medium.com/founders-factory-africa/theres-no-right-way-to-build-a-product-bdca8db8c959">no ‘right’ way to build a product</a> but if you’re focussed on value delivery, then you’re far more likely to achieve it.</p><p>🛠 <a href="https://www.prodpad.com/blog/invented-now-next-later-roadmap/">Now, Next, Later</a> by Jana Bastow from ProdPad is a great tool to help you be more outcomes focussed.</p><h4><strong>(6) Clear vision</strong> to align actions towards</h4><p>I’m always surprised when founders can’t articulate their vision and mission clearly and compactly. Although often when they can, it still isn’t trickling down as a framework for decision-making throughout the organisation.</p><p>Your product strategy, product roadmap, financials and investment strategy are all just different representations of your core business strategy. They need to tell a coherent story of how everything fits together, each with its own angle and detail. If you’re struggling with prioritising backlog items, or evaluating what actions are more important, then you’re probably suffering from this. It would help if you had a better prioritisation framework that stems from your vision, mission, and business strategy.</p><blockquote>🛠 My personal preference is this <a href="https://medium.com/founders-factory-africa/creating-a-vision-mission-f0d1c1e3a813">Vision, Mission, and Master Plan</a> template. This typically feeds well into <a href="https://www.ravi-mehta.com/product-strategy-stack/">Ravi Mehta’s Product Strategy Stack</a>. Sometimes if a team needs more structure, then I’ll nudge them towards using <a href="http://flightlevels.org/">Flight levels</a> or something similar. Whatever your approach, you need a coherent strategy that ties it all together as it makes the 1000s of smaller decisions so much easier.</blockquote><h4><strong>(7) Acknowledging uncertainty</strong></h4><p>Traditional business loves certainty. Many executives that haven’t built software before — and a scary number who have, insist on committing to a plan of fixed items and release dates. Because of alignment and dependencies. But as anyone who’s tried to ship software before will tell you: there are always unknown unknowns. (And don’t get me started on <a href="https://www.reddit.com/r/programming/comments/7tm5l/hating_the_gantt_chart/">Gantt Charts!</a>)</p><h3>Eileen Wang on Twitter: &quot;Committing to a year&#39;s worth of roadmap is like saying &quot;I&#39;m not going to learn anything new that could change my mind&quot; and that&#39;s a self-fulfilling prophecy. / Twitter&quot;</h3><p>Committing to a year&#39;s worth of roadmap is like saying &quot;I&#39;m not going to learn anything new that could change my mind&quot; and that&#39;s a self-fulfilling prophecy.</p><p>Being <a href="https://agilemanifesto.org/">Agile</a> means, well, to be agile. It means things will change, and it means your systems need to adapt. Roadmaps should focus on sequencing what is most important, not timelines. If you spend the entire year only shipping and improving the most important thing on your roadmap, that’s the right thing to do. Yet I’m always surprised how often people just move to the next thing on their list.</p><blockquote>⚡️ Speaking in terms of “<em>bets</em>”, “<em>goals</em>”, “<em>hypothesis</em>”, and “<em>assumptions</em>” instead of “<em>features</em>”, “<em>releases</em>”, and “<em>deliverables</em>” goes a long way to shifting the way your team thinks about certainty. Always communicating dates as ranges is another way to make the uncertainty ‘visible’. Subtle shifts in language and structure can go a really long way to helping your team have the right conversations.</blockquote><h4>(8) Shared accountability &amp; ownership</h4><p>Great teams wake up every day thinking about how they improve the product for customers and the business. It’s not just one person’s ‘job’. In teams where everyone takes accountability to deliver value, they are engaged, interested and collaborative.</p><blockquote>⚡️ Is one person in your team making all of the decisions? Do you have the autonomy to try things that you think are worthwhile and have the platform to voice those? Does the rest of your team? Answering these questions and then reflecting on improving the status quo can help you achieve this. (It also plays very well with the next point on cross-functional teams…)</blockquote><p>🛠 Marty Cagan’s book <a href="https://www.amazon.com/gp/product/1119387507">Inspired</a> and <a href="https://www.svpg.com/empowered-product-teams/">this post</a> is a great start</p><h4><strong>(9) Cross-functional inputs &amp; decision making</strong></h4><p>Diverse teams aren’t “stronger”; they’re more resilient. They’re more adaptable, and the creativity from a broad range of backgrounds brings unique perspectives that will deliver more robust solutions. The evidence has been shown <a href="https://terem.tech/cross-functional-teams-research/">time and again</a>.</p><blockquote>We’re most blind to our own bias.</blockquote><p>It’s worth noting that diversity matters in gathering the inputs and collecting ideas as much as making decisions and commitments. The bias is different but has the same effect. I often find that teams may be diverse in creating inputs, but the decisions always get made by the same group of people. Being aware of and adjusting for your biases and blind spots are going to make you a better team.</p><blockquote>⚡️ Think of the last planning meeting or workshop that you had. What was the breakdown in gender, race, socio-economic background, seniority, and technical or functional skills? Now think of 1–2 people across your team that you could include next time to make it more diverse. If you can’t think of someone, then you probably need to hire for more diversity. It’s not about quotas or representation — it’s about better-performing teams and more holistic inputs.</blockquote><p>🛠 I’ve always found the <a href="https://www.insights.com/products/insights-discovery/">Insights Profiles</a> to be the most useful for personalities and ways of work.</p><h4>(10) Being adaptable &amp; Team empowerment</h4><p>When you have a clear vision (6) and acknowledge uncertainty (7) with a cross-functional team (9) that has shared accountability (8)… then it’s best to<strong> get out of their way.</strong> If you’re doing well on the other items but still micromanage them, then you’re missing most of the gold.</p><blockquote><strong>“Never doubt that a small group of thoughtful committed individuals can change the world.</strong> <strong>In fact, it’s the only thing that ever has.” — Margaret Mead</strong></blockquote><p>I’ve always loved these definitions: <strong>Responsible</strong>: has the ability to respond (without approval). <strong>Accountable</strong>: is held to account if it fails.</p><p>Giving a team responsibility and autonomy to respond in whatever way they see fit is incredibly empowering, particularly with the rest of the principles. It creates ownership and purpose and is great for motivation and job satisfaction. But making them fully accountable can backfire if they haven’t opted in. It takes a lot of trust to let the team run with something but you still be accountable. In my experience, doing this has been the most rewarding.</p><h3>How to evaluate your team</h3><p>I’ve explored more technical options with a series of weighted questions to evaluate how your team lives these values. But, honestly, they got overly complicated and didn’t add that much value — despite technically having more scientific rigour.</p><p>What I found more practical and faster is to evaluate how your team performs on each of these on a scale of 1 to 10. Each time I’ve done this, there are typically 2–3 areas that the team is weakest at. Those are the areas to focus on. You can then identify changes that can help improve these areas.</p><p>This process is not an exact science, but I have found this approach is a useful way to think about which tools compensate for where your team is weak. It also permits teams to adapt the tool/framework/methodology for their situation and empowers them to drop it and adopt something else as their situations change.</p><p>I am building out a <a href="https://coda.io/d/Tools-DB_dULT7z0JTEG/Product-Tools-DB_suPc7#Tools_tu5ms/r1"><strong>repository of tools</strong></a>, frameworks and methodologies that these principles can filter, so please let me know on <a href="http://www.twitter.com/rogernort">Twitter</a>, <a href="http://www.linkedin.com/in/rogernort">LinkedIn</a> or reply to this post with what you use or would like to add.</p><p><em>Thanks to Luke Naude and </em><a href="http://ww.twitter.com/paddycarmody"><em>Pat Carmody</em></a><em> for providing feedback on this post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21b77ab7b54b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>