<?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[Product Builder - Medium]]></title>
        <description><![CDATA[Thoughts about product leadership, software development, quality assurance and UX design - Medium]]></description>
        <link>https://medium.com/product-builder?source=rss----3da3a1ec5155---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Product Builder - Medium</title>
            <link>https://medium.com/product-builder?source=rss----3da3a1ec5155---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:47:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/product-builder" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Three takeaways from the SaaSiest 2023 conference]]></title>
            <link>https://medium.com/product-builder/three-takeaways-from-the-saasiest-2023-conference-ff2b202df8c5?source=rss----3da3a1ec5155---4</link>
            <guid isPermaLink="false">https://medium.com/p/ff2b202df8c5</guid>
            <category><![CDATA[product-metrics]]></category>
            <category><![CDATA[product-led-growth]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Kasper Sørensen]]></dc:creator>
            <pubDate>Thu, 20 Apr 2023 06:47:44 GMT</pubDate>
            <atom:updated>2023-04-20T06:47:44.491Z</atom:updated>
            <content:encoded><![CDATA[<p>I just got back from <a href="https://saasiest2023.com/">SaaSiest 2023</a> and want to capture my thoughts and insights while they’re still fresh! SaaSiest is a strongly community-led conference meaning that there is a wide array of speakers which is great because you’ll see a couple of really experienced speakers, but also test the incubation grounds for new speakers. Very enjoyable and not as <em>produced</em> as many other conferences.</p><p>I could probably write a blog about each topic of the conference, but I’m going to focus on <em>3 aha-moments for me</em> and statements that got me thinking during the conference. Let’s get started.</p><h4>1. Picking apart the all-is-connected positioning model</h4><p><a href="https://www.aprildunford.com/">April Dunford</a> was one of the high profile names to give a keynote at the conference. In addition to some great and relevant stories about product positioning, she did a thing that surprised me; offering an oppinionated model of how to go about positioning even though it is overall an activity that incorporates a lot of different perspectives. A sequence instead of a big bowl of ingredients.</p><figure><img alt="April Dunford presenting her sequenced positioning model" src="https://cdn-images-1.medium.com/max/1024/1*1C39_NAvKcnyz104GTmOcA.png" /></figure><p>The sequence starts with analyzing competitive alternatives, then unique attributes of your product and so on and so on. Why is this cool? Well because every other academic model will tell you that you have to do these things at the same time, making the end result some sort of magic blend of thoughts. I liked April Dunford’s model a lot because it was something you can actually approach in a practical fashion.</p><h4>2. Product Led Growth is not for everyone</h4><p>The headline here is a paraphrase that I think fits the topic of a few talks. <a href="https://www.linkedin.com/in/fredrikskantze/">Fredrik Skantze</a> provided a great overview of the challenges involved in moving between different go to market motions. His way of phrasing the problem was that it required <em>finding product-market fit again</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OcqmRxrp2od5-2oZz--TNA.png" /></figure><p>This really got me thinking as these transitions have been aspired to in now the last three places I’ve worked on product. Thinking that the grass is greener on the other side can easily lead you to desire this transition e.g. from Sales-led to Product-led, but that road isn’t easy.</p><p>This topic was further explored when <a href="https://www.linkedin.com/in/sunnaster/">Peter Sunna</a> talked us through building a funnel of Product Led Growth and the challenges of going from “Hipster developers” to enterprise customers. The aha moment for me was the idea of the Product Qualified Account (PQA). They would consider an account as product qualified when an account went from individual users of the product to an actual team (I think 3 or more people) would use the product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WH2p7aeC8QTyRmewreMeEw.png" /></figure><h4>3. Is MAU still the golden standard for product metrics?</h4><p>This one topic had my personal interest because of where I am in my current job with <a href="https://www.tricent.com/">Tricent</a> — trying to establish a few metrics that should guide the way we see success with the product.</p><p><a href="https://www.linkedin.com/in/matt-smith-9a313147/">Matt Smith</a> from Mixpanel had a great talk where he dived deep into product metrics. The two concepts that I learned was:</p><ol><li>Identify the one big <em>value moment</em> with your product. Write a list of things in your product that add value, identify the one thing that represents the point in time where a customer is most likely to receive this value — this is your <em>value moment</em>. Build metrics such as Monthly Active Users around this moment. This is what Matt calls your focus metric. Don’t obsess around logins or other non-valuable moments as they will change somewhat randomly without impacting value.</li><li>Break down activation, engagement and retention metrics based on this focus metric.</li></ol><figure><img alt="Matt Smith showing a breakdown of metric types. Activation metrics are about how quickly you get to value. Engagement metrics are about how many times you deliver value. Retention is about whether users come back for value." src="https://cdn-images-1.medium.com/max/1024/1*v1DqEMcmVGMSOqkHN3yWAQ.png" /></figure><h4>Aaaaand … Talking to a lot of great people</h4><p>As I said in the beginning, SaaSiest is a very community oriented conference. So I’m happy to say that I felt welcome and invited to join this community. A lot of great new connections made and interesting perspectives uncovered. Even learned of a few companies that I would not want to work for, haha. But all in all this is the sort of level playing field you would wish for in a conference where you’re there to learn, not just be entertained.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff2b202df8c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-builder/three-takeaways-from-the-saasiest-2023-conference-ff2b202df8c5">Three takeaways from the SaaSiest 2023 conference</a> was originally published in <a href="https://medium.com/product-builder">Product Builder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Walking in the Product Designer’s shoes]]></title>
            <link>https://medium.com/product-builder/walking-in-the-product-designers-shoes-ec8f4c0985f1?source=rss----3da3a1ec5155---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec8f4c0985f1</guid>
            <category><![CDATA[product-discovery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Kasper Sørensen]]></dc:creator>
            <pubDate>Wed, 12 Apr 2023 11:21:14 GMT</pubDate>
            <atom:updated>2023-04-12T11:21:14.419Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many paths to becoming a Product Manager. My own journey started in the early 2000s when I was a student building web applications for the fun of creating online communities around my hobbies*. This endeavour naturally tought me about the importance of UX, but more as a way to shine up the technology and underlying idea of the product.</p><p>Today UX is obviously one of the most critical aspects of modern product development, and in the past couple of months I have been busy infusing this design-driven mindset as I had been tasked with reestablishing the PM organization from the ground up at Tricent.</p><p>The journey eventually left me engaging with Product Design in a way that I had not tried before: <em>Being</em> the Product Designer. Not a design reviewer, product partner, manager or whatever. But actually doing all the design work for the teams (temporarily while the team was being established). The experience was <strong>fun</strong> and I <strong>learned a lot</strong> from it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TcIx9b79UE27ustXSwOFKA.png" /><figcaption>Here’s part of what has been keeping me busy as a PM lately</figcaption></figure><h4>The discovery is in the detail</h4><p>As a new Product Manager, you have to discover and learn a lot about the product and the customers you’re building it for. There are many ways to learn about the product, but stepping into the shoes of the designer appeared to me to be a sort of shortcut to get to many of the key product considerations. The level of detail and question-answering needed to produce a new design for even a small feature is exactly the instigator you need to be able to start asking questions to your customers that inform you about how they really think. At the same time, presenting designs to the engineering teams yields exactly the kind of to-the-point discussions that you need to figure out where the technical hotspots of the product are.</p><p>To give an example, when I was first engaging with Tricent “as a designer” I was looking at a table like this from our UI. It is presented to users who have shared files they need to review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8iJNirgbbahzF5meec5ACw.png" /></figure><p>The table is pretty clear, but as I was originally wanting to add another column to the table it also made me start to think about the existing columns and the detailed behaviour in it. The “Path” column in particular has outgoing links and part of the path is redundant with the File name. So what are users benefit of having both columns, and when do they need which? As a PM I imagine that I would have not gotten to this level of detail if it wasn’t because all these details had shined in my eyes as I started messing around with the structure in Figma.</p><p>Taking this to customers then led me to have better exploratory discussions with them about what they need from the product. Only rarely would they need the outgoing link, but what they did need was the file’s parent’s path in order to provide context. The updated UX is shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZsBsitT0fO3qUNlMp96-jw.png" /></figure><p>The point is not so much that we made changes to the UX though. The point is that the level of detailed thinking that you get exposed to as a designer can be a helpful (although also quite time consuming) tool to discover what your customers are really using your product for.</p><h4>A picture is worth a thousand words</h4><p>OK the next point is probably well-known, but what I learned from <em>being </em>the Product Designer was also that now that I had obtained the skills to make hi-fidelity mockups of our product, I could use this for other means. Like presenting an item on the product roadmap to the team — including to designers — and making sure that the concept is really clear for everyone. It takes some of the guesswork out of product requirements if you can accompany it with one or two really obvious mockups.</p><h4>A picture is a conversation starter</h4><p>We’ve used Figma and tools like Usabilityhub and Maze for validating early design ideas with both customers and external user panels. What I have found about these interactions is that they act like a conversation starter. As a PM you often times want to go talk to customers about a new feature that you haven’t at all started building yet. That’s fine, but just like how a picture can clarify requirements to the team, it can also get your customers talking about what you’re proposing. Be careful with this of course, you will want to start very open-ended in your conversations and then eventually end up with something like concrete pictures.</p><h4>Figma for your vanity</h4><p>The last bit that I just wanted to add here is that learning Figma in order to do UX design was not a one-off exercise. I’ve come to love the tool for creating other graphical assets too. I’ve always been vain about my slide decks, and it feels like I’ve now learned a superpower for when I have to make something really stand out. Whether this is really a need to have, or just my own nice-to-have pet peeve, I won’t say. But I do enjoy and find benefits to having learned a better tool for the job.</p><p>So in conclusion: Product Managers, go get into the weeds with product design. It’s a great experience that I learned a lot more from doing than I thought I would. We all have opinions on design, but actually doing it will increase your appreciation for the work and unlock several conversations and tools that you can use in your product management work going forward.</p><p>*Only available on things like WayBackMachine, my first “products” where communities like pumpkins.dk (a forum for Smashing Pumpkins fans in Denmark) and doom3.dk (a news site tracking the development of the Doom 3 shooter game).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec8f4c0985f1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-builder/walking-in-the-product-designers-shoes-ec8f4c0985f1">Walking in the Product Designer’s shoes</a> was originally published in <a href="https://medium.com/product-builder">Product Builder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The “Tech roadmap” problem]]></title>
            <link>https://medium.com/product-builder/the-tech-roadmap-problem-8c5454fd5ee6?source=rss----3da3a1ec5155---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c5454fd5ee6</guid>
            <category><![CDATA[tech-roadmap]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[Kasper Sørensen]]></dc:creator>
            <pubDate>Fri, 31 Mar 2023 06:47:18 GMT</pubDate>
            <atom:updated>2023-03-31T06:47:18.864Z</atom:updated>
            <content:encoded><![CDATA[<p>Product leadership is all about discovering opportunities, setting direction and helping teams get their priorities straight. That much I think most people will agree on. Yet, I find that the expectation from many engineering teams is that their product partners (PMs, POs, call it what you will) are there to just manage <strong>user-facing and functional features </strong>and the team itself should self-contain any concern regarding <strong>non-functional</strong> and <strong>internal</strong> workings of the product. As examples I could mention reliability improvements, architecture changes, adopting new technologies etc.</p><p>I believe that this creates a great divide and can severely impact the two disciplines to work well together. It eventually leads to the team working on two agendas. Marty Cagan coined the term “teams of missionaries, not mercenaries” to describe how an empowered and inspired team will contribute manyfold better to both tech and product considerations. I see that a separate tech roadmap will lead to a situation where engineers becomes missionaries <em>only</em> of the tech side of the product.</p><p>Coming back to my initial statement: Product leadership is all about […] helping teams get their priorities straight. As a product leader you cannot do this job well if you aren’t invited to the table when all the work is planned. Similarly, as a product leader you have to invite the whole team to the table so they can take part of the feature discovery, planning and scoping.</p><p>So let’s discuss how product leaders can engage in the tech roadmap. Is there even any merit for them to engage in prioritization of such work? Are there frameworks to employ as a non-technical or not-as-technical product leader in the company of engineers?</p><h4>But tech work just has to be done</h4><p>There is typically a considerable amount of work that the team <em>has</em> to do for technical reasons, and thus the priority is not really a point of debate. But what happens to the roadmap when we are unable to even account for these activities? It shatters and the result is loss of trust from the external stakeholders of the product team. See, a side effect of having a product leader do a good job is that the team is recognized not just for new features, but for the <em>work that they do</em>.</p><h4>Torque versus speed</h4><p>Technical work of software teams usually contributes to either stability of the way the software is built, or to the speed/performance of the application itself. As a product leader you have to ask yourself if your product needs both, and how much it needs them.</p><p>Some cars have amazing torque, some cars have enormous top speeds. It’s rare that a car has both, and they don’t necessarily make for great cars/products. This is hard because it’s not like you would ever say that these traits are ever <em>bad</em>. But are they important? It depends on the product. In B2B SaaS where I’ve done the majority of my business, I find that stability (torque) is way more important than performance because so much emphasis in the B2B world is put on trust, which is derived from quality, reliability, stability and transparency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*anx5zmG_rl63430GALJcZg.png" /><figcaption>Torque lets you overcome any obstacle, but not necesarily at high speeds</figcaption></figure><h4>A simple decision matrix</h4><p>All decisions are contextual, so the below may not apply to you. But when I work with products with a high quality expectation, I usually go about making judgements about whether to interfere in prioritization decision making like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PkOvop2F4tEKroEcg_6kIw.png" /></figure><p>As a product leader, the most contentious part of this model is clearly around <strong>Performance improvements</strong> or other non-functional+negotiable parts. On a tech roadmap you will usually find a lot of these, and with them a lot of engineers who take this work as given. They’re often times right about their priorities, but often times also not, because they’re treating it as a non-negotiable piece of work. Performance, just like new features, is indeed a very negotiable feature. There are huge benefits, including cost-reduction, to improved performance, but they don’t always outweigh other benefits in e.g. functional bug-fixes or new features.</p><p>Where I think that a product leader can really shine here is by emphasizing the kind of tech roadmap items that they find to be important to the product. In my work I have found almost all stability improvements to always be of high importance, and creating an alliance with engineers around the prioritization and promotion of these changes can lead to a better collaboration and will invite the team to start thinking really as missionaries about their product area.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c5454fd5ee6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-builder/the-tech-roadmap-problem-8c5454fd5ee6">The “Tech roadmap” problem</a> was originally published in <a href="https://medium.com/product-builder">Product Builder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>