<?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 Erin N on Medium]]></title>
        <description><![CDATA[Stories by Erin N on Medium]]></description>
        <link>https://medium.com/@ErinNardo?source=rss-c7ccb33ff8f4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*B8m8pH4qhezPEPe0iqmJJA.jpeg</url>
            <title>Stories by Erin N on Medium</title>
            <link>https://medium.com/@ErinNardo?source=rss-c7ccb33ff8f4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:17:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ErinNardo/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[The Real Cost of Return-to-Office Mandates: Why Flexibility Wins the Talent Wars]]></title>
            <link>https://medium.com/@ErinNardo/the-real-cost-of-return-to-office-mandates-why-flexibility-wins-the-talent-wars-63d159452161?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/63d159452161</guid>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Wed, 20 May 2026 19:32:32 GMT</pubDate>
            <atom:updated>2026-05-20T19:32:32.216Z</atom:updated>
            <content:encoded><![CDATA[<p>The organizations I joined in recent years, their flexible work policy was a major factor in my decision. Not the only one, but definitely in my top three. I’ve seen organizations struggle to compete for talent while simultaneously insisting everyone return to physical offices. It doesn’t add up.</p><h3>Remote work isn’t a perk anymore</h3><p>Here’s what many executives miss: remote and hybrid work options have fundamentally shifted from nice-to-have perks to standard expectations. Talented professionals now filter job opportunities based on work location flexibility before even looking at the role itself.</p><p>I’ve watched this play out in real time. Colleagues receive recruiting messages and the first question isn’t about compensation or growth opportunities. It’s “What’s your remote work policy?”</p><p>Organizations implementing rigid RTO mandates are essentially removing themselves from consideration by a significant portion of the talent pool. That’s not a strategic workforce decision. That’s self-sabotage.</p><h3>The productivity argument falls apart</h3><p>The claim that office presence equals productivity has been thoroughly debunked by the past few years. My teams have consistently delivered strong results regardless of their physical location. What matters is clear goals, regular communication, and accountability for outcomes.</p><p>When I manage teams, I focus on what they produce, not where they sit while producing it. If someone delivers exceptional work from their home office, a coffee shop, or a co-working space, why would I care which one?</p><p>The data supports this approach. Organizations tracking actual output metrics rather than office attendance often find remote workers match or exceed their in-office counterparts in productivity.</p><h3>What we’re actually measuring</h3><p>RTO mandates often reveal what leadership is really measuring: visibility over value. If you can only assess performance by seeing someone at their desk, you’re not evaluating the right things.</p><p>Effective management requires defining clear objectives and measuring progress toward them. That works regardless of location. If your management approach breaks down when people work remotely, the problem isn’t where people work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mTnLXNGJhZf3_ExM.png" /></figure><h3>The retention risk nobody talks about</h3><p>Beyond attracting new talent, there’s a retention crisis brewing. People who relocated during remote work periods, those with caregiving responsibilities, and professionals who’ve proven they can excel from anywhere are updating their resumes when RTO mandates come down.</p><p>I’ve had conversations with talented professionals who are actively looking specifically because their organization demanded full-time office presence. These aren’t people who were underperforming. They’re often top contributors who simply refuse to accept an arbitrary reduction in their quality of life.</p><h3>A competitive advantage hiding in plain sight</h3><p>Organizations that embrace flexible work arrangements have a genuine competitive advantage right now. They can recruit from anywhere, retain talent that might otherwise leave, and often reduce real estate costs simultaneously.</p><p>This is one of those rare situations where doing right by employees also makes solid business sense. The organizations that recognize this early will build stronger teams while their competitors wonder why they can’t fill positions.</p><p>The choice is clear: adapt to how talented people want to work, or watch them choose organizations that will.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63d159452161" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Logic Matters More than You Think]]></title>
            <link>https://medium.com/@ErinNardo/why-logic-matters-more-than-you-think-76b39170da5a?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/76b39170da5a</guid>
            <category><![CDATA[logic]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Wed, 20 May 2026 19:06:06 GMT</pubDate>
            <atom:updated>2026-05-20T19:06:06.141Z</atom:updated>
            <content:encoded><![CDATA[<p>When I was in college, I took a logic course that fundamentally changed how I approach problems. At the time, I didn’t realize how much that class would shape my career. We learned to construct valid arguments, identify fallacies, and reach sound conclusions based on evidence rather than intuition alone.</p><p>Years later, I find myself using those principles almost daily. Whether I’m evaluating investment opportunities, navigating tradeoffs, or building business cases for new initiatives, the framework I learned in that classroom continues to serve me well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nvIgUy-8Fl4J0LKl.png" /></figure><h3>Building a Case That Stands Up</h3><p>Making business decisions requires more than gut feeling or enthusiasm. You need to construct an argument that holds up under scrutiny. This means identifying your premises, testing your assumptions, and ensuring your conclusions actually follow from the evidence you’ve gathered.</p><p>I’ve seen too many proposals fail because they skipped this crucial step. Someone becomes passionate about an idea and builds a case backward, cherry-picking data to support a predetermined conclusion. When stakeholders start asking questions, the whole argument falls apart.</p><p>Logic forces you to work forward instead. Start with what you actually know, acknowledge what you don’t, and see where the evidence genuinely leads you. Sometimes that means abandoning ideas you were excited about, but better to realize that in the conference room than after you’ve committed resources.</p><h3>Making Tradeoffs Without the Drama</h3><p>Every business decision involves tradeoffs. You can’t have unlimited resources, infinite time, or all possible features. Logic helps you evaluate these tradeoffs systematically rather than emotionally.</p><p>When facing competing priorities, I lay out the explicit criteria that matter for the decision at hand. What are we optimizing for? What constraints are we operating under? What are the actual consequences of each option?</p><p>This approach removes a lot of the politics and personal attachment from difficult choices. It’s not about whose idea sounds better or who argued more passionately in the meeting. It’s about which option best satisfies our stated criteria given our current constraints.</p><h3>Spotting the Gaps</h3><p>One of the most valuable skills from studying logic is recognizing when an argument has holes in it. What assumptions are we making? Where are we jumping to conclusions? What evidence would we need to actually support this claim?</p><p>These questions save time and money. They help you identify risks before they become problems and spot opportunities that less rigorous thinking might miss.</p><p>I’ve watched teams spend months pursuing strategies based on faulty reasoning. Someone made an assumption that seemed obvious at the time, and nobody stopped to question whether it was actually true. A little logical rigor upfront would have revealed the flaw immediately.</p><h3>The Real Skill</h3><p>Learning to think logically isn’t about being cold or removing human judgment from decisions. It’s about ensuring that your judgment rests on solid ground. It’s about knowing the difference between a valid conclusion and wishful thinking.</p><p>That college course gave me a toolkit I use constantly. Understanding how to construct and evaluate arguments has proven more practically useful than almost anything else I studied.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76b39170da5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Big Picture Thinking Makes AI Projects Succeed Where Agile Alone Falls Short]]></title>
            <link>https://medium.com/@ErinNardo/why-big-picture-thinking-makes-ai-projects-succeed-where-agile-alone-falls-short-3516b6cc9af2?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3516b6cc9af2</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 21:00:28 GMT</pubDate>
            <atom:updated>2026-04-12T21:00:28.764Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been managed technology teams through several methodology shifts, and I’m watching many organizations struggle with an interesting challenge right now. They’re trying to apply traditional Agile practices to AI implementation and it’s creating friction.</p><p>Here’s what I’m seeing: Agile was designed to help teams move fast by breaking work into small increments — plan a little, build a little, check results, repeat. This approach worked well when human capacity was the limiting factor. But AI changes the equation entirely.</p><p>The Planning Paradox</p><p>With AI, your constraint isn’t human output anymore. You can generate code, create content, analyze data, and build prototypes at unprecedented speed. The bottleneck has shifted to something else entirely: the quality of your upfront thinking.</p><p>AI delivers results proportional to the clarity of your instructions and context. Feed it vague requirements or incomplete information, and you’ll iterate endlessly. Provide comprehensive context, clear boundaries, and well-defined success criteria, and you can move from concept to working solution remarkably fast.</p><p>This creates tension with Agile’s preference for minimal upfront planning. When you’re doing small bits of planning and thinking, you’re not setting yourself up for AI’s strengths.</p><p>What Works Instead</p><p>I’ve found that successful AI projects require a different balance. You need to invest more time defining:</p><p>Your complete vision. Not just the next sprint’s worth of features, but where you’re ultimately headed. AI can help you get there faster, but only if you know where “there” is.</p><p>Clear outcomes and boundaries. What does success look like? What constraints matter? What trade-offs are you willing to make? These decisions inform every prompt and every iteration.</p><p>Comprehensive context. The more background information you can provide, the better your results. This means understanding your users, your technical environment, and your business requirements deeply before you start building.</p><p>The Hybrid Approach</p><p>This doesn’t mean abandoning Agile principles entirely. The iterative mindset still matters. But the iterations look different.</p><p>Instead of planning one small piece at a time, invest in thorough upfront discovery and definition. Then use AI to iterate rapidly within that well-defined space. You can test multiple approaches, explore alternatives, and refine solutions much faster than traditional development allowed.</p><p>The checking and adjusting happens more frequently, but it’s informed by a consistent vision rather than discovering requirements piece by piece.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*57jCQdk52pruVpvw.png" /></figure><p>Leading Through The Shift</p><p>As a leader, this requires helping your team develop new skills. Strategic thinking becomes more valuable. The ability to articulate requirements clearly matters more than ever. Understanding how to evaluate AI-generated output critically is essential.</p><p>Team discussions about architecture, user needs, and technical strategy need to happen earlier and more thoroughly. You need to front-load the collaborative thinking that used to happen gradually throughout a project.</p><p>The teams adapting best to this approach are those willing to question their assumptions about when planning happens and how much is enough. Speed matters, but strategic speed beats rushed execution every time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3516b6cc9af2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Your Strategy Needs a Map Before the Journey]]></title>
            <link>https://medium.com/@ErinNardo/why-your-strategy-needs-a-map-before-the-journey-b437f38a27ed?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b437f38a27ed</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 20:27:01 GMT</pubDate>
            <atom:updated>2026-04-12T20:27:01.294Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been thinking about how we approach building products and managing teams. Recently, an article challenged the current state of agile development, arguing that without proper context and planning, we’re essentially taking a road trip with random stops and no destination in mind.</p><p>That resonated with me.</p><p>Nobody would pack for a trip without knowing if they’re heading to the beach or the mountains. Nobody would start driving without understanding the distance, the terrain, or what vehicle they need. Yet in product development and team management, we sometimes do exactly that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ub1EXl3wF88_YBPQ.png" /></figure><p><strong>Context Matters More Than Speed</strong></p><p>Agile methodologies have given us tremendous flexibility, but flexibility without direction creates chaos. I’ve watched teams sprint efficiently toward goals that turned out to be irrelevant. They moved fast, but they moved nowhere meaningful.</p><p>Understanding the full scope of what we’re building — and why — isn’t about abandoning adaptability. It’s about ensuring our adaptability serves a purpose. When my teams understand how their work connects to broader organizational objectives, they make better decisions at every level. They know what to prioritize when trade-offs emerge. They recognize which details matter and which don’t.</p><p><strong>Planning Isn’t the Enemy of Progress</strong></p><p>There’s a false dichotomy that suggests planning and execution are opposing forces. In reality, thoughtful planning accelerates execution.</p><p>Before launching any initiative, I ask my teams to map out three things: where we’re starting, where we’re going, and what we’ll need along the way. This isn’t about creating rigid documentation that becomes obsolete. It’s about building shared understanding.</p><p>When everyone on the team can articulate the destination and the reasoning behind our route, they can navigate obstacles independently. They don’t need constant direction because they understand the broader context. That’s when real ownership emerges.</p><p><strong>Building Teams That Think Beyond Tasks</strong></p><p>The managers I admire most build teams that operate with strategic awareness, not just tactical precision. Their team members understand how their individual contributions create collective impact.</p><p>This requires investing time upfront to establish that context. It means explaining not just what we’re building, but why it matters to customers, to the business, and to the market. It means connecting daily decisions to long-term vision.</p><p>When I hire, I look for people who ask about the destination, not just the next turn. People who want to understand the vehicle they’re driving and the conditions they’ll face. Those are the team members who become force multipliers.</p><p><strong>The Return of Strategic Thinking</strong></p><p>Perhaps the pendulum is swinging back toward valuing comprehensive understanding alongside rapid iteration. Not because one approach is inherently superior, but because the best results come from combining strategic clarity with tactical flexibility.</p><p>My role as a manager is to ensure my teams have both the map and the freedom to adjust their route when they encounter unexpected terrain. That balance — between knowing where we’re headed and remaining responsive to what we learn — creates the conditions for meaningful innovation.</p><p>Understanding context and seeing how pieces fit together isn’t about slowing down. It’s about moving with intention.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b437f38a27ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Grace We Give Others vs. The Grace We Expect]]></title>
            <link>https://medium.com/@ErinNardo/the-grace-we-give-others-vs-the-grace-we-expect-cebee783a042?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/cebee783a042</guid>
            <category><![CDATA[people]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 15:48:03 GMT</pubDate>
            <atom:updated>2026-03-18T15:48:03.777Z</atom:updated>
            <content:encoded><![CDATA[<p>I watched a team meeting derail last week. Not because of a bad idea or a technical problem, but because two talented people were talking past each other. One assumed the other was being deliberately difficult. The other assumed their good intentions were obvious. Both were wrong.</p><p>This happens constantly in organizations, and it’s one of the biggest sources of dysfunction I see. We expect people to understand our positive intent, but when we see negative impact from someone else’s actions, we rarely extend that same grace back to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vFV9CL9oJm9pC4g-.png" /></figure><h3>Intent and Impact Are Not the Same Thing</h3><p>We all know our own intentions. When I reorganize a workflow or push back on a timeline, I know I’m doing it to improve outcomes. When someone does the same to me? My first instinct is often to wonder why they’re creating obstacles.</p><p>This asymmetry is natural but destructive. We give ourselves credit for good intentions while judging others purely on the impact we experience. We want grace for our missteps but struggle to offer it when we’re on the receiving end of someone else’s.</p><p>The solution isn’t to ignore impact. Impact matters enormously. But before jumping to conclusions about someone’s motivations, ask yourself: am I giving them the same benefit of the doubt I’d want for myself?</p><h3>Start With Why, Not How</h3><p>Most organizational conflict stems from making assumptions based on what we observe people doing rather than understanding why they’re doing it.</p><p>You see someone pushing for a specific technical approach and assume they’re being inflexible. But if you understood their why, you’d learn they’re concerned about scalability based on a painful experience from their last company.</p><p>You watch a colleague decline to attend certain meetings and think they’re disengaged. Their why? They’re trying to protect focused time for their team after feedback that they were becoming a bottleneck.</p><p>When you start from the how or the what, you’re almost always wrong about the intent. Actions divorced from context are easy to misinterpret.</p><p>The framework that’s helped me most: understand the why first, then the what, then the how. Why is this person’s priority? What outcome are they trying to achieve? How are they going about it?</p><p>This sequence matters. Jump straight to critiquing the how and you’ll miss that you might share the same why but simply disagree on approach. That’s a completely different conversation than assuming someone has poor judgment or bad intentions.</p><h3>Stop Making Assumptions</h3><p>The fastest way to create dysfunction is to fill gaps in your understanding with assumptions. Someone doesn’t respond to your message quickly? You assume they don’t care. A colleague questions your proposal? You assume they don’t trust you.</p><p>Most of the time, you’re inventing a narrative that isn’t true.</p><p>Before concluding someone is difficult, uncommitted, or working against you, seek to understand. Ask questions. Get curious about their constraints, their concerns, their context.</p><p>You’ll be wrong less often. You’ll build better relationships. And you’ll solve the actual problems instead of the ones you imagined.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cebee783a042" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Fear Trap: Why Being Scared of Your Customers Is Bad Business]]></title>
            <link>https://medium.com/@ErinNardo/the-fear-trap-why-being-scared-of-your-customers-is-bad-business-9fb7678d0ac5?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fb7678d0ac5</guid>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 16:00:31 GMT</pubDate>
            <atom:updated>2026-01-07T16:05:32.144Z</atom:updated>
            <content:encoded><![CDATA[<p>I had a fascinating conversation with a leader yesterday that made me reflect on something I’ve observed repeatedly throughout my career. Too many businesses operate from a place of fear when it comes to customer interactions.</p><p><strong>The Customer Happiness Myth</strong></p><p>We’ve all been there. That moment when you need to deliver information your customer won’t like. The anxiety builds as you contemplate their reaction, and suddenly you find yourself sugarcoating or avoiding the truth altogether.</p><p>But here’s the reality: Operating in fear of an unhappy customer instead of giving an answer that they don’t like sets you up for failure. When we prioritize momentary happiness over honesty, we damage the foundation of the relationship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLxEqmXi9JVCYJ3_fQHJrQ.png" /></figure><p><strong>Building Trust Through Truth</strong></p><p>Successful customer relationships aren’t built exclusively on positive interactions. Think about your strongest personal relationships — they’ve likely weathered disagreements and difficult conversations.</p><p>Professional relationships follow the same pattern. What truly matters is how we handle those challenging moments. Are we:</p><ul><li>Consistent in our approach?</li><li>Transparent with information?</li><li>Trustworthy in our commitments?</li></ul><p>Sometimes providing what I call a “comfort answer” actually diminishes trust in the long run. When you promise what you can’t deliver just to avoid temporary discomfort, you’re setting up a much larger disappointment later.</p><p><strong>Success Over Satisfaction</strong></p><p>Your primary job isn’t making customers happy — it’s making them successful. Sometimes these align perfectly, but often they don’t.</p><p>A customer recently asked me for a nice to have feature that didn’t have broad value to our customer base. While saying no wasn’t pleasant, it prevented a situation where we’d spend roadmap capacity on a feature that isn’t valuable to the majority of our customers. The temporary disappointment was worth the superior outcome.</p><p><strong>Governing Your Responses</strong></p><p>We should expect to govern our answers carefully. This doesn’t mean being harsh or inflexible, but rather thoughtfully considering what information serves the customer’s ultimate goals.</p><p>We receive information we don’t particularly like both personally and professionally all the time. What I value isn’t whether the news makes me happy, but whether it’s delivered with care and helps me make better decisions.</p><p><strong>The Courage to Be Honest</strong></p><p>Building authentic customer relationships requires courage. The courage to say no when necessary. The courage to deliver disappointing news promptly. The courage to prioritize long-term success over momentary comfort.</p><p>When you operate from this place of honesty rather than fear, you’ll find your customer relationships become more productive, more trusting, and ultimately more successful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fb7678d0ac5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Art of Saying No: A Product Manager's Secret Superpower]]></title>
            <link>https://medium.com/@ErinNardo/the-art-of-saying-no-a-product-managers-secret-superpower-6fded2ade056?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fded2ade056</guid>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 15:28:46 GMT</pubDate>
            <atom:updated>2026-01-07T15:31:15.498Z</atom:updated>
            <content:encoded><![CDATA[<p>As a Product Manager, I’ve learned that one of my most valuable skills isn’t what I say yes to — it’s what I say no to. The reality? In product, you say no a lot. And I mean A LOT. If you’re doing your job well, saying no becomes part of your daily vocabulary. We’re investing here, not those 10 other places. We’re building this feature, not those. It’ll be ready in 3 months, not tomorrow. And no, it’s not free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oHofvj9OOStkhgj-" /></figure><p><strong>Why Saying No Matters</strong></p><p>Saying no is about focus. Without it, your product becomes a jumble of half-baked ideas and features that don’t serve a coherent purpose.</p><p>But here’s the thing — just saying no isn’t enough. The art is in how you say it and what comes after.</p><p><strong>Other ways to say No</strong></p><p>Sometimes the ideas are good, the timing may not be. It’s perfectly okay to tell a stakeholder, later. The important thing, is only do this if you truly think you will do this later. This can be interpreted as a yes or a maybe and should be used in that context and not to avoid having to say no.</p><p>If an idea may have merit, but you aren’t sure the value, now is a great time to enlist the help of the stakeholder to build a business case. Have them help track how often this is requested, go speak to other customers and users to understand the impact and the potential value. Often it becomes evident that the capability has value or that it doesn’t. The work of doing the research can justify why this should get roadmap capacity or it provides the data to justify the no.</p><p><strong>Beyond the No: Bringing Others Along</strong></p><p>When I say no to a stakeholder’s request, I don’t just leave them hanging. I bring them along on the journey:</p><ol><li><strong>Paint the vision</strong> — Show them where we’re headed and how their request fits (or doesn’t) into the bigger picture</li><li><strong>Explain the strategy</strong> — Share why we chose this path and what benefits we expect</li><li><strong>Break down prioritization</strong> — Be transparent about how decisions were made</li><li><strong>Offer alternatives</strong> — Suggest how they might get value from what is coming</li></ol><p><strong>Real Examples That Work</strong></p><p>Instead of: “No, we can’t build that.”<br>Try: “That’s an interesting idea that aligns with our long-term vision. For now, we’re focusing on X because it addresses our most critical user needs.”</p><p>Instead of: “No, it won’t be ready tomorrow.”<br>Try: “We’ve mapped out our delivery timeline based on engineering capacity and quality standards. I can walk you through what’s coming when, and we can discuss if there are interim solutions.”</p><p><strong>The Payoff of Principled No’s</strong></p><p>When you say no thoughtfully and bring people along with you, something magical happens: you build trust. Your team and stakeholders start to see you’re not arbitrarily rejecting ideas — you’re protecting the product’s integrity and their time.</p><p>And here’s the secret benefit: the more confidently you say no to the wrong things, the more enthusiastically you can say yes to the right ones.</p><p>Remember, every no is actually saying yes to something else — focus, quality, or sustainability. Master this skill, and you’ll become not just a better product manager, but a more respected one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fded2ade056" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Postcard Strategy: Ditch the Deck, Define Your Destiny]]></title>
            <link>https://medium.com/@ErinNardo/postcard-strategy-ditch-the-deck-define-your-destiny-0428e7b103fe?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/0428e7b103fe</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[planning]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 16:36:10 GMT</pubDate>
            <atom:updated>2025-10-13T16:36:10.575Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s that time of year again: strategic planning. And with it often comes the dread of creating massive, complex documents — fifty-slide decks or hundred-page reports that few people will ever truly internalize. These exhaustive documents can sometimes obscure the very clarity they’re meant to provide.</p><p>This year, let’s start differently. Let’s embrace a constraint that forces crystal-clear thinking: the postcard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HrzBnJz3iITtaPWi" /></figure><p>Forget the corporate jargon and endless bullet points for a moment. Instead, imagine you are writing an old-fashioned postcard to your future self, three years from now. You only have a few lines of space, so you must distill your team’s three-year vision into the most impactful, undeniable markers of success.</p><p>Ask yourselves: “In three years, what are the three to five biggest, most tangible accomplishments we could fit on this postcard?”</p><p>These can’t be abstract goals. They need to be specific achievements, like “Our user base grew by 5X in the targeted segments and we became the #1-rated app in our category,” or “We successfully launched Product X and captured 25% of the target market.”</p><p>Once those non-negotiable accomplishments are written down, you’ve established your North Star. Now, and only now, can you work backward. That small, powerful postcard becomes the foundation for your detailed execution plan. You can then build a brief, focused strategy document or deck that outlines only what’s necessary to achieve those powerful postcard goals.</p><p>Stop planning for the binder and start planning for the headline. This simple exercise will ensure your entire team shares a concise, memorable vision and a clear path to get there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0428e7b103fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Tough Truth of Customer Success: Why “No” Is Your Most Valuable Word]]></title>
            <link>https://medium.com/@ErinNardo/the-tough-truth-of-customer-success-why-no-is-your-most-valuable-word-389c7a272bf9?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/389c7a272bf9</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 16:22:09 GMT</pubDate>
            <atom:updated>2025-10-13T16:22:09.800Z</atom:updated>
            <content:encoded><![CDATA[<p>Delivering good news is easy. The customer loves the new feature, the project hit its deadline, and everyone is happy. Here’s the spoiler: managing a customer relationship is not about only delivering good news.</p><p>The true depth of your professional skill, and the real strength of your relationship, is only revealed when you have to deliver the bad news and present alternatives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tccOHthUlE8LwBr4" /></figure><h3>When “No” Is the Definitive Path to Success</h3><p>No one wants to be the bearer of bad news. It’s natural to want to appease customers, especially in a competitive market. However, constantly saying “yes” to immediate demands — particularly unvetted feature enhancements — is a direct path to a blown-up roadmap and an unsustainable business.</p><p>It’s tempting for teams (yes, I’m looking at you, Sales) to offer easy “yeses” to keep the customer happy in the moment. But executing your strategy is everyone’s responsibility, not just Product’s. Saying “no” isn’t being unhelpful; it’s being protective of your execution and the long-term viability of your product.</p><p>A firm “no” is a positive, definitive answer. It ends speculation, confirms the boundaries of the current offering, and immediately pivots the conversation toward the available path forward. You are not there simply to make customers happy; you are there to help them succeed.</p><h3>The Puppy Problem: Setting Boundaries</h3><p>Think about any strong relationship, personal or professional: they are built on clear boundaries.</p><p>Failing to establish what is acceptable behavior is akin to treating every customer like an adorable German Shepherd puppy without setting boundaries or teaching manners. You’ll be left wondering why you have a 100-plus-pound liability on your hands later.</p><p>In business, this means:</p><ol><li>Don’t hide behind a ticket: Your job isn’t done by asking someone else to take the brunt of customer displeasure. Take ownership of the difficult conversation.</li><li>Affirm the process: When an answer is final (e.g., a feature is off the roadmap, or a technical limitation exists), you must firmly anchor the discussion to the existing strategy.</li><li>Offer the viable alternative: The key is to pivot away from the disappointment and toward the solution. Your skill is in explaining <em>why</em> the bad news is true and then expertly presenting a viable alternative that allows the customer to move forward.</li></ol><h3>Armor Up: Creating Space for Frustration</h3><p>Once you deliver the difficult news, you must be prepared to have your armor on.</p><p>Show genuine empathy, but expect that you may get an unreasonable response. That response is almost always rooted in frustration, and people are rarely at their best when they feel stuck or blocked.</p><p>Your job is to create space for that frustration without letting it derail the professionalism of the relationship. Listen, acknowledge the difficulty of their situation, and then gently steer the discussion back to the path forward — the alternative you presented.</p><p>Dealing with these difficult situations is what truly hones your professional skills. It enables you to diffuse current tension and, more importantly, prevent similar boundary issues in the future. Strong customer relationships are built not just on the wins, but on how you handle the tough conversations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=389c7a272bf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Coffee Pot Leadership Effect: Small Acts, Big Impact]]></title>
            <link>https://medium.com/@ErinNardo/the-coffee-pot-leadership-effect-small-acts-big-impact-0017fa6ca4b0?source=rss-c7ccb33ff8f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/0017fa6ca4b0</guid>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Erin N]]></dc:creator>
            <pubDate>Tue, 07 Oct 2025 12:47:11 GMT</pubDate>
            <atom:updated>2025-10-07T12:47:11.290Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever wondered what truly makes a great leader? It’s not always the grand gestures or inspirational speeches. Sometimes, it’s as simple as filling the coffee pot when it’s empty.</p><p>I recently came across Bette A. Ludwig’s article on <a href="https://medium.com/psychology-of-workplaces/coffee-pot-leadership-what-the-greatest-leaders-already-know-db12295d76ed">Coffee Pot Leadership</a>, and it perfectly crystallizes what exceptional managers already understand intuitively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OrMLbjgWd11KZPwe" /></figure><p><strong>Everyday Acts of Respect</strong></p><p>The most effective leaders demonstrate their values through consistent, small actions. They show up. They listen. They remember your kid’s soccer game.</p><p>These seemingly minor behaviors speak volumes about how they view their responsibility to others. They signal “I see you as a whole person” without ever needing to say those words.</p><p><strong>Connection Before Direction</strong></p><p>If you’re guiding others, you must genuinely care about their well-being. Understanding what helps your colleagues succeed isn’t just nice — it’s necessary.</p><p>Sometimes this means providing technical guidance. Other times, it’s offering support when life happens. Most often, it’s simply listening to their ideas.</p><p><strong>The Multiplier Effect</strong></p><p>The beauty of coffee pot leadership is its compounding return. Small, consistent actions build trust over time. When people feel valued, they bring their best ideas forward, take meaningful risks, and invest deeply in shared outcomes.</p><p>Remember: Your impact as a guide for others comes not from occasional grand gestures but from the everyday choices that show what you truly value.</p><p>What small action might you take today that demonstrates care for those around you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0017fa6ca4b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>