<?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 Katerina Goyeau on Medium]]></title>
        <description><![CDATA[Stories by Katerina Goyeau on Medium]]></description>
        <link>https://medium.com/@katerina.goyeau?source=rss-9ed651b5bd12------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IFYJdDff02FdQWIUitzq1w.png</url>
            <title>Stories by Katerina Goyeau on Medium</title>
            <link>https://medium.com/@katerina.goyeau?source=rss-9ed651b5bd12------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:34:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@katerina.goyeau/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[Why Tech is Obsessed with Customer Obsession — and How to Win Hearts]]></title>
            <link>https://medium.com/@katerina.goyeau/why-tech-is-obsessed-with-customer-obsession-and-how-it-builds-winning-products-feffac8e2607?source=rss-9ed651b5bd12------2</link>
            <guid isPermaLink="false">https://medium.com/p/feffac8e2607</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[enterpreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Katerina Goyeau]]></dc:creator>
            <pubDate>Mon, 23 Mar 2026 03:37:21 GMT</pubDate>
            <atom:updated>2026-03-26T02:22:49.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4IVbbIzGAXxBVYOvB2CPhw.jpeg" /></figure><p>Jeff Bezos built Amazon on a single, unwavering principle: <strong>Customer Obsession</strong>. The most influential movement in UX and UI today is <strong>User-Centered Design</strong>. The <strong>Agile and Lean</strong> methodologies that power modern product teams are fundamentally built around seeking user feedback and building iteratively around it.</p><p>Tech companies that clung to traditional product-centric models have been — and continue to be — pushed out by user-centric competitors. So why is the user experience so critically important? And why does it work so reliably?</p><h3>Money Talks. Here Are the Facts.</h3><p>Amazon disrupted and replaced entire industries by offering faster and more convenient alternatives. Major casualties include bookstore chains (Barnes &amp; Noble), traditional retail giants (Sears, Toys “R” Us), and specialty retailers like Sports Authority — each of which saw widespread store closures and a painful, often fatal shift from physical to digital commerce.</p><p>Chewy, the online disruptor of pet supplies, projects approximately <strong>$12.6 billion in revenue for 2025</strong> — while industry veterans PetSmart and Petco are closing the year at roughly $10 billion and $6 billion respectively. A once-small startup from Florida now outsells each of the largest legacy pet retailers individually.</p><p>Wayfair grew from an idea in a founder’s spare bedroom into the leading online home goods retailer in the U.S., capturing approximately <strong>14–15% market share</strong> in the home goods sector as of 2022–2026.</p><p>Each of these companies made user experience their core value — not a feature, not a department, but a fundamental business philosophy.</p><p>After spending a long time asking myself why user experience is so powerful, I went back through my own memories — the best and worst customer experiences I’ve had. And that’s when I had my “aha” moment.</p><h3>Customer Experience Is Personal.</h3><p>It doesn’t speak to your logic. <strong>It speaks directly to your emotions.</strong> And that is the most powerful trigger there is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nRLaEDhwgntuKQ_VoH7xbA.jpeg" /></figure><p>Let me show you why, through my own experiences.</p><p><strong>Chewy.</strong> I have two cats, so naturally I started buying supplies at my local PetSmart. It was convenient, but I never loved the experience — the chain sells live animals that aren’t always properly cared for, and many die during transportation. I’d heard of Chewy but was hesitant because my cats constantly change their dietary preferences, and I dreaded dealing with returns. Then I tried Chewy — and they completely changed my expectations. Returns turned out to be extremely easy and they even ask how my pet is doing by name, and suggest I donate the returned items to a local shelter rather than shipping them back. Convenience — check. Ethics — check. Genuine care — check.</p><p><strong>Macy’s vs. Delta Airlines.</strong> In my twenties, I was a devoted Macy’s shopper — Platinum status, year after year. Then I bought a pair of flip flops that were extremely uncomfortable. When I asked about returning them (having worn them outside once), a customer service rep said to bring them in. When I did, the manager met me with rude dismissal and sent me away. I reported my feedback, but received no follow up. I closed my store card and never looked back.</p><p>Contrast that with Delta. I once booked a flight with a third-party carrier listed on Delta’s website. During that flight I had a few very unpleasant experiences. Delta, despite only being the ticket reseller, personally called me to apologize. They followed up by email and issued a flight credit. I carry this memory to this day.</p><p><strong>Care matters.</strong> And it is remembered far longer than any price discount or loyalty program.</p><h3>The Four Pillars of Building Products Customers Love</h3><p>Here are actionable steps you can take to build products that not only serve your customers — but make them loyal for life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ad6YGSYkDlQxkW0R6JgphQ.png" /></figure><h3>Pillar One: Build User-Centric Products</h3><h4>Start With a Deep Understanding of Your User</h4><p>Before you write a single line of code or sketch a single wireframe, you need to intimately understand the person you’re building for. Start by defining your <strong>user persona</strong> — not as a demographic checkbox, but as a real human being.</p><p>Ask yourself:</p><ul><li>Who are they? What do they do for work, for fun?</li><li>What are their goals and motivations?</li><li>What frustrations, pain points, or problems do they encounter repeatedly?</li><li>What tools or solutions have they tried, and why have those fallen short?</li></ul><p>The goal is to develop genuine empathy for your user. The best product teams don’t just know their personas — they think like them.</p><h4>Problem Discovery Before Solution Design</h4><p>One of the most common mistakes in product development is falling in love with a solution before you’ve truly validated the problem. User-centric development flips this — it demands that you deeply understand the problem space first.</p><p>Conduct <strong>user interviews</strong> early and often. Ask open-ended questions. Listen more than you speak. You’ll be surprised how often users reveal problems they can’t articulate directly but demonstrate through behavior. Complement qualitative interviews with <strong>behavioral data</strong>: session recordings, heatmaps, funnel analysis, and support ticket trends can reveal friction points that users never think to mention.</p><h4>Ideation: Quantity Before Quality</h4><p>Once you’ve defined the problem clearly, open the floor to ideas — no matter how unconventional. <strong>Design Thinking</strong> methodology is particularly powerful here. Run structured ideation sessions (sometimes called “How Might We” workshops) where your team generates as many solutions as possible without judgment. The goal is divergent thinking first, convergent thinking second.</p><p>Some of the best product ideas start as throwaway thoughts in a brainstorm. Don’t filter too early.</p><h4>Validate Before You Build</h4><p>This is perhaps the most important — and most ignored — step in product development: <strong>do not go straight to engineering</strong>.</p><p>Mock up a quick <strong>MVP (Minimum Viable Product)</strong> or even a low-fidelity prototype using tools like Figma, Sketch, or even paper. Then put it in front of real users. Watch how they interact with it. Where do they hesitate? Where do they get confused? What delights them unexpectedly?</p><p>Use a combination of:</p><ul><li><strong>Usability testing sessions</strong> (moderated or unmoderated) to observe behavior in real time</li><li><strong>Analytics platforms</strong> (Mixpanel, Amplitude, Google Analytics) to track user flows and drop-off points</li><li><strong>A/B testing</strong> to compare variations on existing features and make data-driven decisions</li></ul><p>If the prototype doesn’t resonate, that’s not a failure — it’s information. Mock up another version. Test again. Iterate. The cost of a failed prototype is a fraction of the cost of a failed product launch.</p><h4>The Double Diamond Framework</h4><p>A useful mental model for this entire process is the <strong>Double Diamond</strong>, a design framework developed by the British Design Council. The first diamond covers <em>discovering</em> the problem and <em>defining</em> it precisely. The second diamond covers <em>developing</em> potential solutions and <em>delivering</em> a tested, refined version. The key insight: you should be expanding your thinking (diverging) before narrowing it (converging) — twice. Most teams skip the first diamond entirely, jumping straight to solutions. Don’t be most teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUT6pDsNUdcz3KhkxP0k9A.png" /></figure><h4>Stay Anchored to Your Persona</h4><p>Every design decision, every feature prioritization discussion, every sprint planning session — ask yourself: <em>does this serve our core user persona and their problem?</em> Feature bloat is one of the leading causes of product failure, and it almost always stems from losing sight of the user. Build what they need. Cut what they don’t.</p><h3>Pillar Two: Build Customer-Centric Teams</h3><p>Products are built by people. And the way people feel about their work shows up directly in how customers feel about your product.</p><p>Think about it — your customers are ultimately the ones paying your bills. They deserve genuine respect and care, not scripted responses. I work with customers every day in SaaS, and I can say with confidence: I genuinely care about their experience. Not because I was told to, but because I love the company I work for, I trust its leadership, and I believe in what we’re building together.</p><p><strong>Happy employees produce happy customers.</strong> That relationship is not a coincidence — it’s causal.</p><p>Building a customer-centric team starts with leadership. Company values aren’t posters on a wall — they’re demonstrated through behavior at every level. When a leader makes a decision that prioritizes the customer, even at short-term cost, it sends a message to the entire organization. When leaders hold themselves accountable and express genuine care for their people, that energy flows outward.</p><p>A simple, sincere “thank you” from a manager can do more for employee morale than a bonus check. And high morale translates directly to better customer interactions.</p><p><strong>Team morale equals customer morale.</strong> If you want one, invest in the other.</p><h3>Pillar Three: Design With Intention</h3><p>Great design is invisible. The user should never have to think about how to use your product — the experience should feel intuitive, even obvious, in hindsight.</p><p>Look at <strong>Duolingo</strong>: they get people to willingly learn languages they would never study in a classroom — because you’re not studying, you’re playing a game. Funny characters, satisfying sounds, streaks, trophies, and haptic feedback make the experience intrinsically rewarding. The friction of learning a language is absorbed by a beautifully designed loop of small wins.</p><p>Now look at <strong>Google Search</strong> in its early days: a single empty bar. Nothing else on the page. At a time when portals like Yahoo were cluttered with news feeds, weather widgets, and directory links, Google’s radical simplicity was a competitive advantage. The complexity was all handled on the backend; the user experienced only ease.</p><p>These are two very different products with one shared philosophy: <strong>do the hard work so your user doesn’t have to.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RAU_WsTa2Jbb3087jEYMRw.png" /></figure><p>Here are a few key principles to keep in mind:</p><p><strong>Reduce cognitive load.</strong> Every element you add to a screen competes for the user’s attention. Every decision you ask them to make costs them mental energy. Design for clarity first, delight second. Progressive disclosure — revealing complexity only as the user needs it — is a powerful pattern here.</p><p><strong>Design for emotion, not just function.</strong> Shopify’s seamless checkout, Spotify’s personalized weekly playlists, Airbnb’s beautiful photography — these products all trigger a positive emotional response. Users don’t just find them <em>useful</em>, they find them <em>enjoyable</em>. That emotional connection drives retention more reliably than any feature roadmap.</p><p><strong>Respect user-established mental models.</strong> Users come to your product with expectations formed by every other product they’ve used. Drag-and-drop interactions, swipe gestures, the shopping cart metaphor — these conventions exist because they match how users already think. Break them only when you have a genuinely better alternative, and test rigorously when you do.</p><p><strong>Validate demand before building.</strong> The Metaverse is the most expensive recent example of what happens when technical ambition outpaces user desire. Impressive technology. No product-market fit. Build what users actually want, not what impresses engineers.</p><h3>Pillar Four: Treat Feedback as a Strategic Asset</h3><p>People have an innate need to be heard. Give your users ample opportunities to share their experience — and, most importantly, act on what they tell you.</p><p>Negative feedback about a new feature isn’t a setback. It’s free product consultation. Not only might you be discovering a gap in your product, you may be getting direct input on what to build next to drive growth. Customers who feel heard become advocates. Customers who feel ignored become churned users who leave negative reviews.</p><p>Take every piece of feedback seriously. Build feedback loops into your product: in-app surveys, NPS tracking, customer advisory boards, regular user interviews. Read your support tickets — they are a direct window into user pain.</p><p>When something goes wrong, use the <strong>“5 Whys”</strong> root-cause analysis technique: ask “why?” five times in succession, drilling from the symptom down to the fundamental cause. This prevents your team from treating symptoms while the underlying problem continues to fester. It’s a staple of post-mortem culture at high-performing engineering and product teams for good reason.</p><h3>Bottom Line</h3><p>Being user-centric is no longer a strategic choice — it’s a survival requirement.</p><p>The modern competitive landscape will push you out of existence if you fail to win your users’ hearts. Not their click-through rates. Not their downloads. Their <em>hearts</em>. Because when you lose a customer’s emotional trust — no offer, no discount, and no rebranding campaign will ever win it back.</p><p>Build with empathy. Design with intention. Listen without defensiveness. And never, ever stop asking: <em>what does my user actually need?</em></p><p>The companies that answer that question best — consistently, obsessively — are the ones that define industries. The ones that don’t become cautionary tales in someone else’s Medium article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=feffac8e2607" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Transformation Story. How To Stop Your Business From Failing?]]></title>
            <link>https://medium.com/@katerina.goyeau/agile-transformation-story-how-to-stop-your-business-from-failing-806cd2b92329?source=rss-9ed651b5bd12------2</link>
            <guid isPermaLink="false">https://medium.com/p/806cd2b92329</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Katerina Goyeau]]></dc:creator>
            <pubDate>Thu, 01 Feb 2024 18:11:26 GMT</pubDate>
            <atom:updated>2024-02-01T18:11:26.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*6WWdQp5PjHLY87EyQVfMEw.png" /><figcaption>Source: <a href="https://www.inventorsdigest.com/articles/be-end-user-friendly/">InvestorsDigest</a></figcaption></figure><p>Once I attended a PMI (Project Management Institute) annual symposium with the topic of the “Digital Transformation.” One speaker in particular took my breath away with her presentation. She shared a staggering statistic that about <a href="https://www.inc.com/ilan-mochari/innosight-sp-500-new-companies.html#:~:text=About%2050%20percent%20of%20the,Innosight&#39;s%20forecasted%20churn%20rate%20holds.">50% of the S&amp;P 500 will be replaced over the next 10 years. In 1965, the average tenure of companies on the S&amp;P 500 was 33 years and it will shrink to 14 years by 2026</a>. While there are many factors contributing to this trend, one stands out the most — <strong>failure to keep up with the modern technology</strong>. Old giants are being pushed out by tiny innovative startups. A perfect example of that is Blockbuster. Those of you who have been around for a while may remember going to a Blockbuster store and picking out a VHS tape or a DVD to watch on a player. At its peak in 2004, Blockbuster had <a href="https://www.sec.gov/Archives/edgar/data/1085734/000119312505063510/d10k.htm">more than 9,000 stores worldwide</a> and 6.1 million dollars in revenue as you see in the chart below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EYztYZ8hh7ARTy4ImjA9PQ.jpeg" /></figure><p>Where is Blockbuster now? The company reached 1 billon dollar debt in 2010 and filed for bankruptcy and got delisted from NYSE. A startup called Netflix came into the market and revolutionized how we watch movies. It made Blockbuster completely obsolete. In retrospective, what could they have done differently? It’s a loaded question. At a first glance one may think of all the resources large companies have at their disposal (financial, human, legal, etc). But what do startups have that large companies usually don’t? <strong>It’s Agility</strong>. When you’re a small startup things move quickly — there is a small number of stakeholders involved, minimum to none approvals required, no processes to follow, low stakes, low risks. When a company becomes an international corporation, there is a complex hierarchy, processes upon processes, multi level approvals, and every step in the wrong direction may have severe consequences for the business. The company becomes a slow moving monstrosity, but it doesn’t mean that once you make it big you’re doomed to face failure because of a new young competitor with it’s fresh revolutionary technology. There is way out and it’s name correlates with the missing ingredient — Agile, a methodology for delivering projects incrementally.</p><p><strong>How to Implement Agile Transformation?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*RBu42XOSkBQ73R6gz36g_g.png" /><figcaption>Source: <a href="https://www.nrspp.org.au/2019/04/30/all-that-matters-is-my-journey-from-a-to-b/">NRSPP</a></figcaption></figure><p>First we need to understand what Agile framework is good for. Unlike Waterfall, Agile frameworks are good for the projects that don’t have a clearly defined outcome. For instance, in the software development, sometimes you start developing an application for human heart beat monitoring and end up with a dog fitness app. Happens all the time. And it’s a good thing. It means that the company is agile, it’s listening to its user, as well as the market trends, and making adjustments accordingly. Now you might think — I develop a heart monitoring device, I know exactly how it needs to be in the end, so Agile is not right for me. Wrong. Agile methodology also requires a change of the mindset. Te mindset that promotes positive changes is <strong>user-centric</strong>. Every step we take is targeted towards the user. A common mistake I see especially in the world of software development is that engineers get caught up in what they think is the best solution. And they may be right, engineers are generally brilliant people and they do tend to come up with brilliant solutions. But would the customer pay for them?</p><p><strong>Transformation Journey Guide</strong></p><p>Now that we have the right mindset, let’s begin our transformation journey. Let’s pretend we are a software as a service (SaaS) company that allows construction workers to take pictures on site and upload them into the project folder for a future review with their team. Our revenue is steadily declining because of the new competitors that joined the market. In an attempt to save our business we decided to go through the Agile Transformation. In this guide we will be following <strong>Scrum</strong> framework, which is the most basic and commonly used form of Agile methodology. A good representation of the Scrum workflow is in the picture below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_0fXk4pSkuMZXkJbax4hQ.png" /><figcaption>Source: <a href="https://intetics.com/blog/the-main-phases-of-the-scrum-project/">Intetics</a></figcaption></figure><p><strong>Step 1:</strong></p><p>Define your <strong>epic</strong>. Epic — a large body of work that can be broken down into a number of smaller tasks or as Agile calls them, <strong>user stories</strong>. Epic in Waterfall terms would be called a milestone. Our epic is massive, we want to redesign our product to improve user experience.</p><p><strong>Step 2:</strong></p><p>Write your <strong>user stories</strong>. A user story is an end goal, not a feature, expressed from the software user’s perspective. Let’s say we conduct a market research and find out that around 67.7% of the construction workforce are 25–54 years old, with a median age of 42 — this is our end user.</p><p>To keep a user-centric mindset, a suggested format for writing a user story is the following:</p><p>“As a [user persona], I [want to], [so that].”</p><p>Writing user stories could be a cross-functional group exercise or it could be handled by the Product Manager/Owner. There should be a considerable number of user stories developed by the team, but for the sake of an example, our team developed the following three:</p><p>“As a 42 year old construction worker, I want to be able to have pictures upload automatically, so that I don’t click on too many buttons.”</p><p>“As a 42 year old construction worker, I want my pictures to be saved to the right project folder, so I don’t spend time organizing them myself.”</p><p>“As a 42 year old construction worker, I want to easily share my pictures with my coworkers, so that we can collaborate on our construction plans.”</p><p><strong>Step 3:</strong></p><p>Now that all the user stories are outlined, we estimate their weight and adding a number of <strong>story points </strong>to each of them. Story points will represent the amount effort required to complete each user story. It is recommended to have the whole team get involved in estimating the effort. You can decide what is the range that is more appropriate for your team, but 1–5 should be sufficient for most projects.</p><p><strong>Step 4:</strong></p><p>Congratulations! You have now defined the scope of the project. Now we need to get ready for <strong>sprints</strong>. Sprints are short endeavors for completing a part of the work, that will result in some kind of a shippable product. Obviously it will not be a completed product overall, but it will be something usable. For example, we may want to focus on adding geolocation for an automatic detection of a construction site, so that the photos automatically get s saved in the project folder of that location. It is a fraction of the final product, but it can be shippable as a product on its own. The standard length of a sprint is 2 weeks, but it can vary from 1 to 4 weeks.</p><p>To begin, we need to prioritize all our user stories as a team and evaluate which user stories will be included in the Sprint #1. All others will go to the s<strong>print backlog</strong>, which will get reevaluated during the panning of subsequent sprints.</p><p><strong>Step 5:</strong></p><p>At this point we good to go and have begun our sprint. We will be meeting with the team every day for 15 mins for daily scrums. During the daily scrum 3 questions get answered:</p><ul><li>What did you do yesterday?</li><li>What will you do today?</li><li>What is blocking your progress?</li></ul><p>Each project team member will take turn answering this question. And this points out another <strong>major benefit</strong> of Agile. It gives voice to every team member and reduces the time for “fluff” since meetings are short and demand efficiency. Once sprint is coming to an end, there will be a sprint review meeting, where the following questions get asked:</p><ul><li>What went well?</li><li>What didn’t go well?</li><li>What adjustments are we making?</li></ul><p>The idea is the same — each person answers. Sometimes the best ideas are held by employees that are not vocal by nature, so following Agile allows companies to not miss out on these opportunities. To avoid unnecessary chatter, Project Manager or Scrum Master must keep everyone’s time boxes in check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Do3mbuDdW--UfJZ8Ryttsg.png" /><figcaption>Source: <a href="https://www.flexjobs.com/employer-blog/what-drives-diversity-inclusion-initiatives-leadership-support/">FlexJobs</a></figcaption></figure><p>Based on the outcome of the meeting, we will be making adjustments to the following Sprint.</p><p>Upon completion of Sprint #1 we push the upgrade to all our customers. We can begin gathering data on the user feedback. Based on these data we will adjust product development strategy in subsequent sprints. Unlike with Waterfall, we are not locked in to a specific product at the end of the project.</p><p><strong>Conclusion</strong></p><p>While there is a wealth of information and courses available online on the topic of Agile, the intent of this article is to give an idea on what tools can be used within organizations to drive the culture of innovation. Agile is not a magic pill that will solve all problems, transformation journey will consist of other strategies that need to be implemented. However, just switching to Agile project delivery alone is enough to yield the results. It is recommended to have a solid Change Management program as Agile gets introduced to teams. Changing the mindset of teams requires implementation of structured tools and processes. Just inspirational speeches by themselves will not cause change. Sure, may be a good all hands meeting will get everyone pumped for a week, but then employees will get back to their old ways. Applying Agile framework is an effective mechanism that will guide people into the world of innovation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=806cd2b92329" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Are the Technical Program Managers?]]></title>
            <link>https://medium.com/@katerina.goyeau/who-are-the-technical-program-managers-53a29f1ef5e0?source=rss-9ed651b5bd12------2</link>
            <guid isPermaLink="false">https://medium.com/p/53a29f1ef5e0</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Katerina Goyeau]]></dc:creator>
            <pubDate>Mon, 22 Jan 2024 06:00:04 GMT</pubDate>
            <atom:updated>2024-01-22T06:00:04.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*nVSd1B0NTytL4qGsg8zV7g.jpeg" /></figure><p>If you ask a random person, chances are they won’t know the answer to this question. In fact, even if they work in a technical industry, they won’t have a good idea either. Most common guesses would be that Technical Program Managers (or TPMs) are Product Managers or Project Managers. Despite the lack of popularity, the specialty continues to grow every year with hundreds of thousands of Technical Program Managers employed in the United States. Some sources cite over 300K TPMs currently in the workforce. There is no surprise why — the position comes with an attractive salary. According to Glassdoor, the median pay of TPMs is $150K to $227K. Although some tech giants, such as Google, Meta, Apple, Amazon, and Netflix, pay upwards of $200,000 for this title, going up to approximately $600,000.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPPowaGG7GytIO4rh3m4Gw.png" /><figcaption>Source: <a href="https://www.glassdoor.com/Salaries/technical-program-manager-salary-SRCH_KO0,25.htm">Glassdoor</a></figcaption></figure><p>And here is the twist — you can get into this job from a wide variety of backgrounds. Most commonly, Technical Program Managers have a bachelor’s degree in computer science, mechanical engineering, business administration, management or a like-field. Sometimes, expertise in a field is prioritized over technical skills. For example, if you have a rare expertise in primate behavior and there is a startup developing a software for decoding primate behavior, you actually have a shot at working for that company as a TPM and beginning to earn the “big bucks.”</p><p>Now that we are clear on the benefits of this job, let’s discuss what being Technical Program Manager actually entails. In order to understand that, we need to break the title apart, starting with understanding of the Program Management (leaving the “Technical” part out for now).</p><p>There are three interrelated concepts in the field:</p><ul><li>Portfolio</li><li>Program</li><li>Project</li></ul><p>The most clear definitions (in my opinion) are outlined in <a href="https://graduate.northeastern.edu/resources/project-management-vs-portfolio-management-vs-program-management/#:~:text=A%20program%20is%20a%20group,or%20unrelated%20to%20one%20another">the article by the Northeastern University</a>:</p><ul><li>“A <strong>project</strong> is a temporary endeavor undertaken by a company or organization (such as the creation of a new product, service, or result)</li><li>A <strong>program</strong> is a group of projects that are similar or related to one another, and which are often managed and coordinated as a group instead of independently</li><li>A <strong>portfolio</strong> is a group of different programs and/or projects within the same organization, which may be related or unrelated to one another”</li></ul><p>The diagram below is a good visual for understanding this concept — there are multiple programs under a portfolio and there are multiple projects under a program.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5d6K5sijmuhsio5TYcwVfA.jpeg" /><figcaption>Source: <a href="https://www.modernanalyst.com/Careers/InterviewQuestions/tabid/128/ID/860/Portfolios-Programs-and-Projectswhats-the-difference.aspx">ModernAnalyst</a></figcaption></figure><p>We don’t often hear about Portfolio Managers as the actual job titles and there is a reason for it. While there are Portfolio Managers out there, most companies choose to have this part be handled by an executive team of the function. Portfolio entails setting business goals and objectives, which often falls under the realm of the leadership.</p><p>Given that projects make up a program, all of the specifications of a project cascade down to a program. Just like a project, a program must have a beginning and an end date, otherwise it becomes an operational initiative. When a Program Manager is “Technical,” it generally means they have an expertise in a technical field, such as software engineering, hardware engineering, mechanical engineering, aerospace engineering, etc. These fields tend to have small agile projects running under the same umbrella or initiative or… a program. There is no need to have just one person running a development of one feature, such as a button on an app. Instead, there can be a person that would run a development of a feedback page, for example, and there will be projects to design a user interface with form submissions and buttons, back end with data storage and processing, analytics tools for data interpretations, etc. Unlike the construction industry, where we see the most Project Managers, the building of a bridge would keep a person occupied for a good period of time.</p><p>That was a long, but much necessary breakdown of how the title of a Technical Program Manager came about.</p><p>Now what do Technical Program Managers do?</p><p>Given that any Program starts with a Project, TPMs perform Project Management duties on the day to day basis.</p><ol><li>Define <strong>scope</strong>. When handed a new project, it is important to understand very clearly what is included and what is not included. For example, if a Project Manager is told to build a vase, it would not be enough information. What color does that vase need to be? What size? Will it include flowers? Will there be a design painted on it? What kind? All details must be defined. This is where the “Technical” part becomes more important. Project scoping requires deep technical expertise. It is important to understand the scope from within, otherwise scope creep is unavoidable. In some cases, such as with software development, project scope is hard to define. In many cases the project may change by the time it is closed, based on the user feedback. However, there is generally an objective and high level scope still defined. Those projects are delivered using Agile or it’s subtype — Scrum methodology.</li><li>Establish <strong>stakeholders</strong> and RACI. Each project will have different types of stakeholders, such as leadership, department managers, engineers, lawyers, clients - it is a mix of people. “Stakeholder” is essentially anyone holding a stake in a project. Every project needs to have those stakeholders clearly identified and they need to be involved and informed about their role in a project. That leads us to a concept of RACI, which stands for “Responsible, Accountable, Consulted, Informed.” An example of a RACI chart is below. Not every stakeholder will be expected to actually do something within a project, some may want to be only informed. RACI becomes handy not only for people’s understanding of their and others role within a project, but it also helps TPM properly structure Program communication. <strong>If I had to pinpoint one factor that will determine the outcome — success or failure of your project or program, I’d say it is communication.</strong> More about communication planning in the section 5.</li><li>Determine the <strong>timeline</strong>. Timeline may be set by the leadership or it can be calculated by a TPM. Sometimes the leadership team may come up with a project, such as migration of certain data from one place to another and say that it needs to happen within 1 year, for example. In that case, TPM would have to structure resources and allocations accordingly. If it is a short timeline, it means more people and funds may be needed. In cases where timeline needs to be determined by TPM, a planning process is initiated. TPM needs to understand the resources necessary, meet with the applicable stakeholders and understand timelines involved for executions of all parts of the project. Following this bottom up process would lead to the main all encompassing timeline.</li><li>Set the <strong>budget</strong>. Just as the timeline can be given or determined, the same happens with the budget. It may be dictated, in which case some compromise may need to be made. For example, choosing an offshore team of engineers as opposed to the local one. Or the budget can be calculated based on the resources available and the project needs as determined by the stakeholders.</li><li>Create a <strong>communication plan</strong>. As mentioned above, communication is a crucial part of a project or a program. It cannot be done ad hoc. A good TMP will define their format and frequency of communication with each stakeholder and a team. For example, a CTO will not care how many software bugs were resolved this week, but she will care that the feature has been released. In this case a quick monthly summary in a form of an email or a slide will be the best. On the other hand, a software engineer will need all details of those bugs and will want to participate in the daily or weekly calls to discuss the latest progress updates.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O8D6eI9ri8oSd0V709r46Q.png" /><figcaption>Source: <a href="https://www.wrike.com/blog/what-is-a-raci-chart/">Wrike</a></figcaption></figure><p>Another part involving a technical skill set is the risk identification. Technical Program Manager should be able to foresee risks and create mitigation strategies ahead of time. This also requires technical skills. For example, the fact that a server may go down, causing major data loss , and therefore increasing project timeline and budget, requires an understanding of the software architecture. A potential mitigation strategy in this case would be having another server with data replicated and consistently synced. TPM are not necessarily expected to identify risks and create mitigation strategies themselves, but they are expected to know who are the right stakeholders for developing these strategies and be able to work with them productively.</p><p>The tasks described so far are mainly relevant to the project initiation and planning phases, but there are other project phases as pictured in the diagram below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*MsSF4riufbk_uiZzYk1Ttg.png" /><figcaption>Source: <a href="https://resourceguruapp.com/blog/project-life-cycle">ResourceGuruApp</a></figcaption></figure><p>We covered technical and project management skills, but having those is not enough to be a successful Technical Program Manager. <strong>Building relationships</strong> and <strong>influencing people</strong> is an essential part of TPMs job responsibilities. One time I had an experience that struck me and it really stayed with me until this day. I was attending a seminar with a topic of using Agile methodology to deliver projects and the presenter was talking about being a manager without having a management authority. It is definitely a big aspect of the job — TPMs assign tasks to people that do not report to them directly and TPMs are ultimately responsible for the delivery of those tasks. So, back to the seminar presenter. I was very intrigued by this topic, as it is so relevant in the field. I asked the presenter what are the tools they use to influence people, to get them to do what is needed for the project. Surprisingly, the presenter said that when he needs engineers to do something for the project, he usually says something along the lines of “I really need this, man. I swear. I will owe you one.” Obviously, it doesn’t take a seasoned professional to understand that this is not a good strategy, nor is it sustainable long term. What actually needs to happen is a meticulous building of relationships with people. Your project stakeholders need to trust you. They need to trust that your requests are reasonable and that they are the right tasks for the project, they need to know that you have their best interest and that you have their back. Then they will do what you ask and they will do it well. This takes time, as trust must be earned.</p><p>There are many more aspects of a Technical Program Management job, but these are good high level indicators of it.</p><p>If I had to summarize, Technical Program Managers are the orchestrators of a number of company initiatives that possess technical expertise. They are communicators and trusted advisors. They are advocates of their team and right hands of the executive team. Being an orchestrator gives a satisfying visibility into the big picture, but it can also feel like a thankless task, as the results are not tangible. In fact, work of a successful TPM is the least noticeable as everything would be running smoothly. Nevertheless, it is a job that is based on relationships and communication with people. It is the joy of seeing the results come through and it is the joy of building things together that makes the job of TPM so rewarding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53a29f1ef5e0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>