<?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 Get Real with Leslie Neal on Medium]]></title>
        <description><![CDATA[Stories by Get Real with Leslie Neal on Medium]]></description>
        <link>https://medium.com/@leslieneal?source=rss-9393bef58026------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PCOmFIci-8fKI0rPPz99Ow.png</url>
            <title>Stories by Get Real with Leslie Neal on Medium</title>
            <link>https://medium.com/@leslieneal?source=rss-9393bef58026------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 09:29:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leslieneal/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[From Product Vision to Product Reality: How AI Coding Finally Closed My Creative Loop]]></title>
            <link>https://medium.com/@leslieneal/from-product-vision-to-product-reality-how-ai-coding-finally-closed-my-creative-loop-12ad4bc56236?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/12ad4bc56236</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Thu, 14 Aug 2025 20:26:48 GMT</pubDate>
            <atom:updated>2025-08-14T20:26:48.409Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>My Perpetual Gap</strong></h3><p>I’ve spent my career living in the space between <em>what could be</em> and <em>what is</em>. Every product manager knows this feeling: you can see exactly how something should work, feel it in your bones, articulate it with precision to engineers and designers. You can map the user journey, define the edge cases, and anticipate the delights and frustrations. But you can’t build it yourself.</p><p>Instead, you become a professional translator. You take the vision in your head and convert it into requirements, user stories, acceptance criteria, and wireframes. You sit in planning meetings explaining what needs to be built and why it matters, how users will interact with it, and what success looks like. You become fluent in the language of explanation, of justification, of bridging the gap between business needs and technical implementation.</p><p>And then you wait. You wait for someone else to interpret your words and translate your vision. It filters through their understanding, their constraints, their priorities. Sometimes they get it exactly right. Often, something gets lost in translation. The thing that gets built is recognizably yours, but it’s not quite what you saw in your mind.</p><p>This is the peculiar isolation of product work. Your job is fundamentally creative because you’re imagining new ways for people to interact with technology and solving problems that don’t yet have solutions. But the act of creation itself always happens at arm’s length, mediated through other people’s thoughts and manifested through their efforts.</p><p>Your work is often long-term, nebulous, and oh so very abstract. It rarely comes with that satisfying moment of completion that developers get when their build runs clean, or that designers get when they see their pixel-perfect mockup come to life. Instead, you get the slow satisfaction of seeing usage metrics climb, or user feedback improve, or business objectives met. The dopamine hits are delayed and diluted.</p><p>Until now.</p><figure><img alt="illustration of a woman in profile writing computer code with a humanoid robot looking over her shoulder" src="https://cdn-images-1.medium.com/max/1024/1*ACDXbo_JObJ006mDWIjtLg.png" /><figcaption>AI-assisted coding</figcaption></figure><h3><strong>The Language I Already Spoke</strong></h3><p>What people dismissively call “vibe coding” fundamentally misunderstands what’s happening here. This isn’t about vibes or intuition or magical thinking. It’s agent-assisted development, and if you’ve spent years explaining to engineers what to build and why we’re building it, how users will interact with it, and how different pieces should connect, then you already speak the language.</p><p>The skills that made me effective as a product manager translate almost directly to working with AI coding tools: understanding user needs, defining scope, articulating functionality and flow, and thinking through state management and data persistence. These aren’t separate skill sets. They’re the same conversations I’ve been having for years, just with a different audience.</p><p>I started with Base44, a prototyping tool that feels like having a conversation with a very patient developer. I built three apps: a productivity tool, a fantasy football side-game, and a DIY home improvement guide. Each time, I found myself naturally explaining not just what I wanted, but why it mattered, how users would flow through it, what data needed to persist, and how different features connected.</p><p>Tools like Base44 are great for making one’s first foray into AI coding because they are self-contained; you get the entire backbone of your application along with the front-end without having to implement multiple services and tools. But, for me, the prototypes weren’t enough. I wanted to go deeper and understand how to think about the underlying systems. So I downloaded my code, opened it up in VS Code, and with the help of GitHub Copilot, I was able to replace the “all-in-one” pieces of my prototype and rebuild it from scratch. I’ve learned a lot more than a bit of JavaScript. I had to dig into authentication flows, database schemas, deployment pipelines, component architectures, state management, and design systems.</p><p>Sometimes the AI gets it wrong. Sometimes I have to debug, research, and manually experiment. But here’s what surprised me: I figured it out. Not because I suddenly became a computer science expert, but because I already understood the logic of systems, the flow of data, the relationship between user actions and application responses. I’d been thinking about these things for years; I just hadn’t been implementing them myself.</p><p>The process revealed something I hadn’t fully appreciated: how technical I was all along. Most people who know me professionally today wouldn’t recognize this version of me. They see the PowerPoint presentations, the storytelling workshops, the strategy sessions, and the stakeholder management. They haven’t seen me build a product in at least seven years, not since I was a PM who made my engineers’ lives infinitely more difficult because I had opinions about every implementation detail. Now I can have those opinions and act on them directly.</p><p>If you’re skeptical about whether this works, I understand. I think there’s a narrative out there that says anyone can build an app thanks to AI. I’m going to disagree with that. If you haven’t at least tertiarily been involved in building technology, you won’t be able to build a quality app out of the gate. That’s not the game-changer of AI-assisted development; we’re not going to see the internet flooded with garbage apps built by everyone. Well, we might, but it won’t last. The game-changer is going to be in the way we think about creativity and specialization in the technology workplace.</p><h3><strong>The Real Revolution: Dissolving Boundaries</strong></h3><p>Here’s what’s revolutionary about AI-assisted development, and why we’re fundamentally misunderstanding its impact: it’s not making us better at our individual jobs. It’s allowing us to step into each other’s domains in ways that were previously impossible.</p><p>This isn’t technological — it’s philosophical. We’re moving from a world of specialized expertise to one of collaborative creation, where the best outcomes emerge from people who can contribute meaningfully to multiple aspects of the creative process.</p><p>This requires a fundamental mindset shift. Instead of improving efficiency within our existing roles, we need to think about how to become more effective across the entire creation process. Instead of asking “how can I become a better product manager,” we should be asking “how can I contribute more meaningfully to building great products.”</p><p>We’ve been thinking about AI tools through the lens of role-based optimization. AI coding tools for developers to code faster. AI writing tools for PMs to write PRDs. AI design tools for designers to iterate more quickly. This misses the point entirely.</p><p>The fundamental transformation happens when roles blur, when the boundaries between disciplines start to dissolve, when a product manager not only specifies requirements but builds working prototypes, and when an engineer not only implements features but articulates product strategy, and when a designer can create mockups <em>and</em> deploy working applications.</p><p>This isn’t about everyone becoming everything; it’s about expanding the range of what we can contribute to the creative process. It’s about removing the friction between vision and execution, between idea and implementation.</p><h3><strong>The New Roles in Technology</strong></h3><p>We’re heading toward a fundamental reshaping of how creative and technical work gets done. Not job displacement, but job evolution. As the boundaries between roles become more fluid, the most valuable people will be those who can operate effectively across multiple domains.</p><p>What I’m about to describe is, in my opinion, how it should have always been. Learning adjacent skills was always crucial to success. Novel ideas and new technology have this funny way of exposing us, of showing us where we’ve been masking. A non-technical PM can compensate with a well-articulated strategy and a knack for relationship building if their engineering partners are highly competent. Now, with AI, the expectation for that product manager to do more technical work will illuminate skills gaps that didn’t seem to matter before.</p><p>The Product Manager of the Future won’t just write requirements; they’ll build working prototypes that demonstrate precisely how features should work. They’ll be able to validate ideas quickly, test assumptions directly, and communicate vision through working software rather than documentation. They’ll spend less time translating between stakeholders and more time facilitating collaborative creation. Instead of being bottlenecks between business and engineering, they’ll become force multipliers. The PM who can say “here’s exactly how this should work” while showing a functioning prototype will be infinitely more valuable than one who can only describe it in words.</p><p>Engineers will increasingly need to think beyond implementation to user experience and business impact. The engineers who thrive will be those who can build what’s specified and contribute to what should be built. They’ll need to understand user needs, market dynamics, and business objectives, not just technical requirements. We’ll see the emergence of engineer-evangelists who can communicate technical decisions to non-technical stakeholders, who can translate business objectives into technical strategy, and who can advocate for architectural choices that support long-term product goals rather than just short-term feature delivery.</p><p>Designers will move from creating static representations to building interactive experiences. The distinction between design and front-end development will blur as designers gain the ability to implement their visions directly. They’ll be able to test interaction patterns, validate visual hierarchies, and iterate on user experiences without waiting for development cycles. We’ll see designer-developers who can take a user experience from concept to working implementation, who can conduct usability testing on actual software rather than clickable prototypes, and who can make real-time adjustments based on user feedback.</p><p>The rise of hybrid roles is inevitable. These aren’t new job categories — they’re evolved versions of existing roles, expanded by the ability to work fluidly across traditional boundaries. And the ones who were already able to bridge those gaps are going to be the ones who survive the longest.</p><h3><strong>Work Will Change</strong></h3><p>The death of hand-offs is coming. The traditional model of throwing work over the wall from product to design to engineering will give way to more collaborative, iterative processes. Teams will work together on shared artifacts, making changes in real-time based on immediate feedback.</p><p>Think about the traditional product development cycle. An idea emerges from user research or business needs. Product managers write requirements. Designers create mockups. Engineers estimate effort and build features. The cycle repeats, with feedback loops that span weeks or months. At each handoff, something gets lost or transformed. The final product is recognizable but different from the original vision. It’s sometimes better, sometimes worse, but always filtered through multiple interpretations.</p><p>Now imagine collapsing that cycle. Instead of describing what you want and waiting for others to interpret it, you can build working prototypes in real time. Instead of static mockups, you can create interactive experiences that stakeholders can use and provide meaningful feedback on. Instead of specification documents that try to capture every edge case, you can iterate on actual implementations.</p><p>Most importantly, I think we’ll see a resurgence of the things we tend to neglect in favor of speed and moving on to the next big thing. Leadership demands we deliver solutions, but often finds the slower parts of the cycle less palatable. Things like discovery, testing, validation, post-launch iteration, and acting on feedback tend to be deprioritized and neglected. But now, with the speed we can move with AI, there is absolutely no excuse for ignoring these vital aspects of our jobs. And now, these activities don’t belong to any one role; they belong to all of us.</p><h3><strong>The End of Creative Limbo</strong></h3><p>First, let’s be clear about what AI can and can’t do here. AI can translate human intent into implementation, suggest patterns and solutions based on existing knowledge, and help us iterate quickly on existing ideas. What it can’t do is generate the novel ideas themselves — the insights that come from deep user empathy, the connections between disparate market forces, the creative leaps that identify problems worth solving in the first place.</p><p>We still need the same fundamental human capabilities: the product managers who can identify unmet needs, the designers who can envision new ways of interacting with information, the engineers who can spot technical opportunities that others miss, the researchers who can uncover useful truths about human behavior. The difference is that these same people can now act on their insights more directly, with less dependency on others to translate their vision into reality.</p><p>The future belongs to full-stack creators: people who can take an idea from initial concept through user research, design, implementation, and iteration. Not because they’re experts in every area, but because they’re fluent enough in each area to contribute meaningfully and collaborate effectively.</p><p>This doesn’t mean everyone needs to become everything. But it does mean that artificial boundaries between roles are becoming less relevant, and the people who can work fluidly across those boundaries will create disproportionate value.</p><p>For me, for the first time in my career, my ideas don’t have to die in the space between conception and creation. They don’t have to be filtered through other people’s interpretations, delayed by development backlogs, or compromised by resource constraints. They can go directly from my mind to working software, limited only by my ability to communicate clearly with tools that are getting better at understanding intent every day.</p><p>The gap between vision and reality is closing. For people like me — people who have spent their careers living in that gap — this changes everything.</p><p>The future of product development isn’t about AI replacing human creativity. It’s about AI amplifying human creativity by removing the barriers between imagination and implementation. It’s about turning more people into creators, not just coordinators.</p><p>And for those of us who have been coordinators for so long, finally being able to create feels like coming home.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12ad4bc56236" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Shiny Object Parade: A 20-Year Tour of My Favorite Solutions in Search of a Problem]]></title>
            <link>https://medium.com/@leslieneal/the-shiny-object-parade-a-20-year-tour-of-my-favorite-solutions-in-search-of-a-problem-005b75ab6ce5?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/005b75ab6ce5</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology-trends]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 13:12:59 GMT</pubDate>
            <atom:updated>2025-07-24T13:12:59.048Z</atom:updated>
            <content:encoded><![CDATA[<p>I landed my first tech job a long time ago. I don’t even want to give my age away by sharing the year, but suffice to say, I’ve seen a lot of trends. I’m not old enough to have ever thought the internet itself was a fad, but I’ve been around long enough that by the time I was 25, the job I had in technology was something I couldn’t have imagined when I was choosing a college major.</p><p>Now, mid-career, I find myself in a similar moment of professional recalibration. AI is changing the way I work. And not in the abstract. It’s already reshaped how I write, research, brainstorm, plan, design, and build. The one thing I always wished for as a product manager was a way to execute what I could only describe, and it’s suddenly more plausible. I still don’t code, and I’m no designer, but AI closes the gap. At least, a little.</p><p>It’s easy to see AI as yet another technology trend. And in some ways, the early behaviors are familiar: many teams are scrambling to “add AI” to their products, whether or not it solves anything meaningful. But unlike a few of the waves we’ve seen before, this one won’t fade. AI will eventually become infrastructure. But we’re not there yet, and pretending we are leads to the same pattern we’ve repeated for years: solution-first thinking with no problem in sight.</p><p>The promise is productivity, creativity, and insight. The reality is disjointed tools, surface-level integrations, and a growing sense of pressure from leadership to be “doing AI” without a strategy for what that means.</p><figure><img alt="A roller-coaster: riding the hype cycle" src="https://cdn-images-1.medium.com/max/1024/1*bK1KsYDZ9eidSznCXc6TOg.jpeg" /></figure><p>What’s happening now isn’t new. It’s just the latest iteration of a pattern I’ve gotten to participate in more than a few times:</p><h3><strong>Blogs (2005–2010): Authenticity at scale</strong></h3><p>Blogs emerged in the post-Web 1.0 world, providing companies with a direct means to communicate with customers without relying on media gatekeepers. At a time when consumer trust in traditional advertising was declining, the idea that a brand could build credibility through consistent, human content felt both novel and necessary.</p><p>Platforms like Blogger and WordPress made publishing easy, and suddenly every company needed a blog. For a while, it worked. But over time, frequency replaced thoughtfulness, and content became a commodity. Strategy gave way to SEO, and volume outpaced value. What began as a channel for authentic voice turned into a treadmill. <strong>Still, the blog era left a lasting imprint: content marketing has become deeply embedded in how businesses grow.</strong></p><h3><strong>Mobile Apps (2009–2015): Presence as product</strong></h3><p>The rise of the smartphone changed user behavior faster than most organizations could adapt. As screens moved from desktops to pockets, the message was clear: you had to be mobile, or you were invisible. It didn’t matter if your business made sense on mobile; the expectation was presence.</p><p>App stores are now flooded with redundant or poorly scoped builds. Many apps were simply websites with a home screen icon. However, in some cases, apps enabled entirely new behaviors, such as on-demand services, mobile payments, and GPS-driven utilities. Mobile-first eventually became mobile-only for some industries, but the rush to mobile left a trail of disconnected experiences. <strong>It wasn’t just a shift from big screens to small ones. It was a shift in expectations.</strong></p><h3><strong>Social Media (2010–2018): Connection as currency</strong></h3><p>As a MySpace junkie, I’ll call this the second wave of social media. It didn’t begin with mobile, but it reached ubiquity because of it. As mobile usage peaked, social media transformed into a necessity, and one that lived in our pockets. The dominant logic became: if people are always online, brands need to be part of the conversation. Platforms like Facebook, Twitter, and Instagram offered immediacy, personality, and the potential for virality.</p><p>Marketing shifted from campaigns to presence. Community managers became brand voices. Engagement metrics started driving strategic decisions. But for many, the investment in social presence yielded little beyond visibility. Algorithms shifted. Organic reach shrank. Paid performance eclipsed participation. Still, the expectations around brand identity, responsiveness, and tone were permanently altered. Peddling your wares online wasn’t enough; you had to perform to get attention.</p><h3><strong>Daily Deals (2010–2012): Acquisition without cost</strong></h3><p>Daily deals boomed in the shadow of the Great Recession. Consumers were price-sensitive, and local businesses were desperate for foot traffic. And here we came (I was very involved in this space.) with the promise of high-volume acquisition: instant customers, minimal upfront cost. It felt like a win-win.</p><p>But retention rarely followed redemption. Margins collapsed. Merchants churned. The model didn’t scale sustainably. What it revealed, though, was a growing appetite for performance-based marketing. This wasn’t about brand awareness; it was about immediate, measurable results. The instinct to drive growth now, and fix loyalty later has shown up in many waves since.</p><h3><strong>Subscription Everything (2015–2020): Predictable revenue, permanent relationships</strong></h3><p>In the post-recession recovery, predictability became the holy grail. Recurring revenue made forecasting easier. Lifetime value became the dominant metric. Investors loved it, and startups sprang up everywhere and in every industry. From streaming to socks, everything became a subscription. And for a while, the math worked. But eventually, saturation kicked in.</p><p>Consumers hit subscription fatigue. Churn started to outpace acquisition. The fundamental question — <em>is this product worth a monthly relationship?</em> — hadn’t always been asked. In some categories, subscriptions stuck around. In others, they exposed the limits of business-model-first thinking.</p><h3><strong>Blockchain (2016–2022): Trust without intermediaries</strong></h3><p>Blockchain rose on a wave of institutional distrust following the 2008 financial crisis. The pitch was powerful: remove intermediaries, restore control, create transparency. For early adopters, it was an ideological choice. For investors, it was speculative. But real use cases struggled to emerge at the same pace as the hype.</p><p>Technical complexity, user confusion, and regulatory ambiguity clouded adoption. The core architecture may still prove valuable, especially in sectors such as logistics or identity management. But the hype cycle burned through trust before practical value could take hold. It offered a radical alternative to institutional systems, but most people didn’t understand the tech or trust the motives.</p><h3><strong>No-code/Low-code (2020–present): Everyone becomes a builder</strong></h3><p>As developer bandwidth became a constraint and pressure for speed intensified, no-code and low-code tools promised relief. They lowered the barrier to prototyping and shifted some power to business teams. But with that empowerment came a flood of shadow systems, fragmented data, and governance nightmares. The promise of “anyone can build” proved true, but not always helpful.</p><p>Today, those same promises are being absorbed and reframed by AI. Generative tools enable design, coding, and testing in a single step. The goal is no longer just enablement; it’s automation. But the risk is unchanged: <strong>fast isn’t better unless you’re pointed in the right direction.</strong></p><p>AI is different, but the organizational behaviors surrounding it are not. The question is not whether to adopt it; the question is how to embrace it. The challenge is how. And for whom?</p><p>If you’re in a large company, here’s what that means:</p><ul><li><strong>Do</strong> identify internal use cases with real friction that are ripe for augmentation with AI: Repetitive research, content drafting, documentation, planning, summarization.</li><li><strong>Do</strong> experiment at the edge: Enable small teams to test use cases before scaling. Use shadow usage to inform actual strategy.</li><li><strong>Do</strong> rethink workflows, not just interfaces: AI isn’t just an assistant. It changes what good looks like. Redesign accordingly.</li><li><strong>Don’t</strong> treat AI as a checklist item: Adding an “AI feature” won’t differentiate your product. What matters is whether it improves the experience.</li><li><strong>Don’t</strong> push usage without training: Most internal resistance comes from a lack of clarity, not a lack of willingness. Equip people. Show value early.</li><li><strong>Don’t</strong> assume strategy will emerge later: It won’t. Hype fills the vacuum left by unclear direction. If leaders say “do AI,” make them say what that means.</li></ul><blockquote>Every hype cycle leaves something behind. Not just the remnants of tech we don’t use anymore, but organizational patterns that quietly become habits: rushing to adopt without alignment, prioritizing visibility over value, mistaking novelty for progress.</blockquote><p>AI will stick. But not everything built in its name will matter.</p><p>The teams that get it right won’t be the ones with the most features, the most dashboards, or the loudest demos. They’ll be the ones who stop to ask better questions. They won’t work from a place of, <em>“How can we use AI?”</em> but from, <em>“What problem are we trying to solve, and is this the right way to solve it?”</em></p><p>Because that’s what strategy is. It’s not a backlog of ideas or a mandate from the C-suite. It’s the disciplined act of making a choice. Of deciding what not to do. Of recognizing when a tool is valuable, and when it’s just noise.</p><p>So if you’re leading teams in a moment like this — where everything feels urgent, possible, and undefined — the best thing you can do isn’t to go faster. It’s to pause. Name the real problem. And make sure whatever you build earns its place.</p><p>That’s not just how you survive a hype cycle. It’s how you build something that lasts beyond it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=005b75ab6ce5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buzzword Bingo: Transparency]]></title>
            <link>https://medium.com/@leslieneal/buzzword-bingo-transparency-fc5f0e9296aa?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc5f0e9296aa</guid>
            <category><![CDATA[buzzwords]]></category>
            <category><![CDATA[transparency]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Wed, 15 Jan 2025 15:34:27 GMT</pubDate>
            <atom:updated>2025-01-15T15:34:27.740Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="large single pane window half clean and half dirty looking into an office space" src="https://cdn-images-1.medium.com/max/504/1*pkB4ORaTogLOcvkLwnj6Tw.jpeg" /></figure><p>I spend my days helping good product teams <a href="http://www.workablestrategy.com/">transform</a> into excellent product teams, or helping non-product teams adopt a product mindset. I talk to a lot of stakeholders on behalf of these teams. I love interviewing stakeholders; they give me great insight into the perceived performance of a product team. Stakeholders do not particularly care about velocity, prioritization matrices, or discovery techniques. In fact, some of them have visceral reactions to even hearing the word discovery (a topic for another time). What they do care about, among other things, is what they call transparency.</p><p>Early on, I was a proponent of transparency among teams. It seems like a no-brainer. Transparency means sharing and being forthright, not gatekeeping information or techniques, and being open and honest. It should build trust and empathy and makes for a better working relationship. However, after hearing stakeholders request transparency even after receiving full access to everything a product team was doing, I changed my mind.</p><p>When I ask stakeholders how they feel about what their partner product teams are doing — things like what they are prioritizing or what they have on the roadmap — I’m met with a variety of responses. In all honesty, the responses tend to be more aligned with a person’s natural demeanor than with a professional evaluation of the question. But when I do get thoughtful answers, I hear a lot of <em>I don’t understand, I don’t know, it’s unclear</em>, and eventually the inevitable, <em>what we need is more transparency into the process</em>.</p><h3>Why does everyone want transparency?</h3><p>The obvious answer is that people are nosy know-it-alls. But if I just chalked it up to human nature, I’d be done with this article, and I’m trying to hit a nice 7-minute read time for you. But there are a few simple type-of-people-reasons that you get requests for transparency.</p><p>Some people think they know best, and if they just knew what was going on, they would be the ones to fix things. It’s a sort of corporate savior complex. <em>If I had just known, this wouldn’t have happened, I would have said something</em>. Potentially true, but sort of insulting to say that to another person, especially in a professional setting where there is expertise at play.</p><p>There’s <a href="https://www.forbes.com/sites/brycehoffman/2024/09/22/think-you-saw-it-coming-how-hindsight-bias-limits-your-ability-to-learn/">hindsight bias</a>, which is similar. This is the tendency to attach outcomes to decisions after the fact. It’s super easy to dissect a process or strategy after the outcome is known. This is Monday morning quarterbacking. Read <a href="https://www.amazon.com/Thinking-Bets-Making-Smarter-Decisions/dp/0735216355">Annie Duke’s Thinking in Bets</a> for more on this.</p><p>And of course, some people just want to be involved. Busy bodies, you might say, but it’s often more the desire to be included, for whatever reason, most of which aren’t nefarious. But that’s an issue with individual dynamics, not a systemic stakeholder group behavior, and we want to focus on the latter.</p><p>Here’s what stakeholders are actually saying when they ask for transparency: <em>I don’t like what you’re telling me, I disagree with your decision, I don’t trust you</em>. Ouch! Very rarely is a request for transparency in good faith, and if it is, what a lucky duck you are to have a stakeholder who has legitimate curiosity and interest in your field of expertise.</p><h3>If stakeholders are asking for transparency, use your product skills to find the root cause.</h3><p>What does “understand” mean? We have this way of exclaiming our dismay using the phrase, <em>I don’t understand how this could have happened</em>. You leave something in the oven too long, even though you’re pretty sure you set the timer. You do understand how this happened. You know overcooking that loaf of sourdough is going to turn it to charcoal. It’s not that you don’t understand the physics, it’s that you can’t puzzle together what led to the mistake. You’re surprised by the outcome when you feel like all the right pieces were in place for a different one. You’re not daft, you’re baffled.</p><p>When a stakeholder says <em>I don’t understand</em>, they aren’t saying, <em>I want the details of the process that led to this decision</em>, they are really saying, <em>I don’t agree with the decision</em>. They are saying, <em>I thought we were aligned, I expected something different, I feel misled, I feel frustrated that this isn’t what I wanted</em>. If they had full transparency, would it change the outcome? I suggest it wouldn’t. That’s how we know there’s something else lurking.</p><h3>Lack of trust and alignment.</h3><p>The root cause is usually a lack of trust. It’s the worst root cause, it’s the hardest to overcome, and unfortunately, it’s the most common. Why don’t stakeholders trust product teams? (This is any group of people and any other group of people at work, I just write about product teams, so substitute your own teams as needed.)</p><p>If a stakeholder group does not trust a product team, there has been a severe breakdown somewhere. At some point, the stakeholder group was probably burned by a bad experience. Previously there was a product manager in the role, and it was not a good fit. Or, the leader of the stakeholder group influenced a negative perception that has lingered. Or, historically, the product team hasn’t always delivered things that solved problems, delivered too slowly, or missed goals. It could be nearly anything. And thanks to <a href="https://thedecisionlab.com/biases/belief-perseverance">belief perseverance</a>, they’ll always believe it, even if the teams have completely turned over and it’s been years. (Seriously, I’ve seen it.)</p><h3>You can’t build trust with transparency.</h3><blockquote>Trust is built by delivering on promises, not by detailing process. Trust comes from partnership and meeting expectations. It’s inherent in good relationships, not in exposure to tactics.</blockquote><p>If your stakeholder group is frustrated, do not send them a link to your Confluence page outlining your discovery techniques or show them your prioritization scorecard. Do not set up an intake form for requests thinking that a paper trail means transparency. Do not spend weeks putting together a RACI matrix and then make everyone sign a working agreement. (Side note, if you’re doing any of these or seeing them at your company, please <a href="https://calendly.com/workablestrategy">hit me up</a>. I can help.)</p><h3>Stop worrying about explaining frameworks, processes, and methodology: spend your time creating partnerships.</h3><p>As an example, let’s use something with tons of well-documented techniques: prioritization. You might know how to use, and be able to explain, RICE, KANO, MoSCoW, 2x2, or any one of these <a href="https://foldingburritos.com/blog/product-prioritization-techniques/">20 methods</a>, and that’s amazing. But Mr. Smartypants with his cool Excel spreadsheet and weighted scores often wonders why his stakeholders are still pissed. <em>But the prioritization is so clear! We’re data-driven! </em>It doesn’t matter. All the math in the world will not save you if you can’t create a partnership in which everyone feels good about the decisions being made.</p><p>Remember, stakeholders aren’t saying, <em>I don’t understand your prioritization methodology</em>, they’re saying they don’t agree with the outcome, which means they think you made a bad decision.</p><h3>Want to stop people from disagreeing with your decisions?</h3><p>Here’s how: change them from <em>your</em> decisions to <em>our</em> decisions. Team up with your stakeholders as partners, and make decisions together. Prioritize together. Solution together. Don’t explain the process, share the process. It won’t matter at all which techniques or frameworks you choose — even the ones you use behind the scenes — if everyone feels included. Inclusion breeds trust. Trust mitigates the desire for transparency. Do this, and let the results become celebrations.</p><h3>Try clarity instead.</h3><p>Repairing eroded trust by building partnerships will go a long way to stop people from wanting to know “how the sausage is made,” but you still need to be prepared to defend decisions, explain trade-offs, frame problems and opportunities in a way that everyone understands, and deliver a clear and concise roadmap. These things don’t require transparency, but they do require clarity.</p><p>While transparency emphasizes access to information to prove there’s nothing hidden or obscured, clarity emphasizes understanding to facilitate action and <a href="https://medium.com/@leslieneal/buzzword-bingo-alignment-4e26bc41b55e">alignment</a> so that everyone has the same interpretation of the information. When stakeholders need transparency, give them access via partnership. Then focus your attention on whether your messaging is clear and understandable; spend your time simplifying complex ideas and communicating effectively. In fact, do it with your stakeholders, as partners.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc5f0e9296aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five systemic culture-based innovation killers to avoid]]></title>
            <link>https://medium.com/@leslieneal/five-systemic-culture-based-innovation-killers-to-avoid-e38b72ab35bf?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/e38b72ab35bf</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[measurement]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Tue, 15 Aug 2023 17:49:10 GMT</pubDate>
            <atom:updated>2023-10-19T16:13:43.856Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*ReY7VSPeuRLh0N70BceYBQ.jpeg" /></figure><p>It’s human nature to crave innovation. We aspire to explore and invent. We relish new ideas, novel concepts, and discovering the next hot trend. We seek to grow and evolve, to improve our lives. In a business context, innovation is needed for companies to succeed in competitive markets where customers have come to expect it. Failure to innovate can leave a business stagnant.</p><p>I’ve been lucky to observe many companies and identify what it means to create an environment that encourages and nurtures innovation. Some do it incredibly well, from idea generation to execution. They have open exchanges of ideas, communicate clearly, and have a shared understanding of strategy and goals; and they’re willing to fail. On the other end of the spectrum, you find organizations that suffer from problems like rampant territorialism, worker complacency, limited accountability, and unclear direction from leadership.</p><p>These failures are easier to see when they manifest as individual behaviors, but when the dysfunction is truly systemic, it speaks to a problem with the organization’s culture, and that can be harder to identify. Over the years, I’ve seen first-hand a few systemic innovation killers that you should try to avoid.</p><p><strong>When disagreement is a no-no…</strong></p><p>I’ve unfortunately not only seen disagreement treated as insubordination, I’ve experienced it personally. I was fed the old “it’s not what you said, it’s how you said it” line, and as a young professional, that shook me, so I worked hard to change how I said things. And it worked! Just kidding. It didn’t, because, at that company, it did not matter <em>how</em> I said anything. What mattered was that I disagreed, and disagreement was bad because it was “not my place.” (For those wondering, the company is long gone, and I’m still out here crushing it.)</p><p>Treating disagreement as bad behavior causes problematic team dynamics and a toxic experience for employees. A person discouraged from disagreeing with a peer or a leader will feel discouraged from expressing ideas, a requirement for innovation. And it cultivates a fear-based environment that can start to penetrate other areas of the culture. Silencing people is demoralizing and breaks the trust between employees and leadership; if people feel uncomfortable speaking up when the repercussions should be mild, they certainly won’t when the stakes are high. Additionally, silencing voices encourages a sameness that flies in the face of diversity.</p><p>Disagreement is one of the most powerful tools for quality innovation. Isn’t innovation inherently a disagreement with the status quo? True innovative thinking works best when many voices are heard, and when many ideas can be vetted and curated. As individuals — especially in leadership positions — the best thing we can do is create a safe space for disagreement. Even a heated debate can be healthy, as long as it’s well-established that the debate is in the spirit of being constructive. We need to practice <a href="https://www.inc.com/linda-naiman/how-to-transform-conflict-into-an-innovation-advantage.html">healthy methods of disagreement</a> like critique and inquiry. We need to shift our thinking and learn to use disagreement as a tool for sharpening ideas and creating a stronger sense of alignment and shared creation.</p><p><strong>When risk is considered reckless…</strong></p><p>Innovation is challenging. It’s hard work to think of something new, and even more difficult to say it out loud. What’s interesting to observe is that discouraging disagreement often overlaps with risk aversion. Those who don’t want to consider a disruptive concept because it’s a challenge to the status quo see that type of thinking as risky.</p><p>Business environments that treat risk as a danger to be avoided tend to view change as high risk but see the status quo as low risk, without evaluating each situation on its own merits. They also tend to measure risk only in terms of dollar value. While big swings don’t always pay off in terms of profitability, never taking the big swing will never pay off in any way. When risk is seen as reckless, innovation will not occur. It’s also unlikely to happen when leaders of companies require painfully long, drawn-out, repetitive processes to prove future value. The decision to go for it might happen, but burning out employees and burning through time might not be worth it.</p><p>A measured approach to big ideas or disruptions is reasonable, but on the extreme end is where we find the true innovation killer. Companies that go beyond cautiousness and create an environment where passionate change-makers are stifled and disappointed at every decision will inevitably have slower growth, watch competitors take innovation to market first, and eventually weed out the employees who tend to have the big ideas. To be innovators, leaders and companies must learn how to balance and mitigate risk, and thoughtfully decide if it’s riskier to do or not do by using more than a singular metric to identify risk.</p><p><strong>When the appearance of progress is valued over all else…</strong></p><p>One of the differences between companies that do innovation well and those that don’t is how they think about measurement. Companies that don’t do innovation well monitor ongoing KPIs and call milestone goals objectives. They watch lagging indicators forever, looking for a consistent and constantly moving needle. But companies that do it right monitor their KPIs while also setting measurable, achievable objectives for specific purposes, and measure those separately.</p><p>Tracking lagging indicators as the primary KPI causes two major problems. One, adjusting the trajectory based on a negative change to a lagging indicator is too late. The impact has already occurred; it’s way past time for innovation, and teams become responsible for fixing things instead of doing new things. Two, no negative change to a lagging indicator, while great, creates complacency with the status quo, because it’s working. And if objectives are set as things like “increase lagging indicator by X%” and it’s met, it seems like a success, and it technically is. But what’s the next objective? What caused that milestone to be achieved? More of the same is not innovation.</p><p><strong>When qualitative data doesn’t count…</strong></p><p>I love quantifiable results; I openly admit to being a little OKR obsessed. I do believe that measuring both progress and success is necessary. Avoiding measurement or measuring poorly is tantamount to blasphemy if you ask me. Here’s the catch: not all data is quantitative (and also, not all numbers are measurements).</p><p>Much like focusing on progress or the appearance of progress, using only quantitative metrics can obfuscate reality. Sorry mathematicians, numbers can lie, and they can lull us into a false sense of success. Companies that avoid qualitative data, like those that focus only on progress metrics, have one major thing in common: they don’t stop to ask why.</p><p>Organizations that require all measurements to be quantitative tend to have one of two results. One, the obsession with quantitative measurement drives people to spend an irrationally outsized amount of time and energy defining, implementing, tracking, and reporting on those measurements while neglecting other aspects of success. Two, quantitative data doesn’t explain why something is being done in the first place, so teams often get so lost in the minutiae of the measurement they miss nuance, sentiment, and context. This lack of thoughtful qualitative questioning can cause teams to not even understand what problem they are solving in the first place.</p><p><strong>When problems are defined with solutions included…</strong></p><p>“The problem is that we need a new house,” I shouted with exasperation to my husband in a moment of small-space frustration. “Yeah, you’re right,” he says to me, because, sure, that sounds right. Our number one problem was the lack of a bigger house, so we started house hunting. The flaw with this scenario is that we defined a solution within the problem. The problem was that we didn’t have enough space. Buying a house is one possible solution, but we settled on it before we even considered other options. I’ve seen this same logic over and over, especially when it comes to solving a technology issue. “The problem is that we don’t have a [name a piece of software].” Is that really the problem?</p><p>We fell into a trap, just like many companies do. The problem I exclaimed seemed logical and correct. We didn’t pause even for a second. In fact, the more acceptable and obvious a problem statement is, the harder it is to question.</p><p>When we accept a problem that’s actually a solution in disguise, it becomes immediately locked in. No one can see past it and no one will question it. It becomes the problem to be solved, but with the solution built-in there’s hardly anything to worry about it. You just go pick a new house.</p><p>Teams get formed, milestones get identified, the objective is to implement the solution, no one asks why, and success is measured by progress toward the solution. There is no innovation in that. This innovation killer also tends to drive people towards solving systemic problems with spot solutions, which creates a domino effect of implementing a series of spot solutions. Inevitably it becomes someone’s (or many someones’) job to untangle a mess, and fixing old problems burns the resources needed for fresh innovation.</p><p>My number one favorite tool from my product management days is the <a href="https://www.producttalk.org/opportunity-solution-tree/">Solution Opportunity Tree</a>. It’s a great way to prevent the solution-in-the-problem conundrum.</p><p>It’s also interesting to visualize the interconnectedness of these innovation killers. It’s never that a company has all or none of these problems, but it’s incredibly easy and common to suffer one that becomes a catalyst for others or see one manifest as another. It’s pretty easy to identify which of these 5 root causes exists by watching for a few key observable happenings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*E1tZ22RDGg2BZsKawyG_Vg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e38b72ab35bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buzzword Bingo: Alignment]]></title>
            <link>https://medium.com/@leslieneal/buzzword-bingo-alignment-4e26bc41b55e?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e26bc41b55e</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[alignment]]></category>
            <category><![CDATA[buzzwords]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 14:38:45 GMT</pubDate>
            <atom:updated>2023-10-19T16:39:42.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C40Qt5NZ90gFIe5l2UlFYw.jpeg" /></figure><p>When I first started to write about alignment, I assumed I’d find the same comfortable rhythm as when I expressed my love of semantics and my hatred of buzzwords in a post about <a href="https://medium.com/@leslieneal/buzzword-bingo-ambiguity-fd178dcb022e">ambiguity</a>. This Buzzword Bingo series exists because I find the lifecycle of everyday words moving from common vernacular into the business world fascinating. There’s a lovely irony to our attempts at specificity — and let’s be honest, sounding smart — that end up muddling the meaning of a word so badly that it’s almost like saying nothing at all.</p><p>But I don’t have the same issues with definitional misuse of alignment as I did with ambiguity. To be clear, if alignment isn’t on your buzzword bingo card, it still should be. I have flashbacks of hearing it said so many times in a meeting that I started to suffer from semantic satiation. But the challenge with it is something completely different.</p><p>The more I researched, the more I started to regard alignment in a negative way. I thought about all the “alignment meetings” I’ve been to, and I realize now that most of them were either status updates or “get with the program” meetings. At first I thought this was just a case of misuse, overuse, or being lazy, but could it be possible that it’s not quite as innocent? We all know that alignment literally means lining things up. It’s like ensuring the tires on your car point perfectly in the right direction individually so that the car propels forward smoothly.</p><p>So when meetings or emails have a subject line with the word alignment, the expectation seems very obvious and well-known. It conjures something participatory, a call for attendees to inquire and critique as though they have a say in the outcome. But the one-way communication of a status update or the description of an already-decided plan is most certainly not alignment.</p><h3><strong>Maybe alignment isn’t always good.</strong></h3><p>Forced alignment is a great example of <a href="https://en.wikipedia.org/wiki/Disagree_and_commit">disagree and commit</a>. (This is commonly seen as a good management principle, but if the culture of your organization tends to honor decisions based on the HiPPO, the disagreeing part becomes a waste of energy.) “Coercion dressed up like collaboration” is my new favorite way to describe it, as ranted about <a href="https://www.forrester.com/blogs/17-03-10-beware_the_word_alignment/">here</a>.</p><p>The example I’ll use is a really common experience for me. I have often worked somewhere between technology and “the business” (I’ll have to write something about <em>that</em> ridiculous delineation at a later date.) Everything including the pace of work, the way decisions are made, the level of empowerment and ownership individuals have, the way goals are set, the value of outcome and output, definitions of words, general knowledge, etc. are different. Basically, they rarely walk into a situation with a quality shared understanding.</p><p>When we try to align these groups — especially on strategy — we automatically presuppose that business and technology strategies are separate. We generally wait for the business strategy to exist before tackling technology plans as though one exists only to support the other. Any alignment meeting is going to be dictatorial, not collaborative. The teams need a shared strategy, something they agree on, not the “alignment” of two separate strategies.</p><h3><strong>Sometimes what you really need is agreement.</strong></h3><p>If alignment isn’t as collaborative as we’ve long believed it to be, I propose looking for situations in which we actually need agreement.</p><p>Two people — or maybe a small group — having the same viewpoint is an agreement, and it’s even more challenging and coveted than alignment. This <a href="https://www.huffpost.com/entry/how-aligned-is-your-organ_b_3881979">article</a> provides a great perspective on why agreement is more important than alignment. Basically, alignment isn’t enough. It’s like saying, “I don’t think I’d do the same thing myself, but I can get behind it.” Agreement is being on the same page as if you’d have come to the same conclusion on your own.</p><p>The level of trust required to create true agreement is a rarity, but it’s what we should strive for, and it starts with figuring out if you need agreement or alignment. It’s about deciding which one of these statements is how you want to describe a situation:</p><ul><li>“We agree this is the right direction.”</li><li>“We’re aligned that we’re going this direction.”</li></ul><p>The first statement with its hands together, heads nodding, confident affirmatives all around is much more empowering. It’s unbreakable. It means that everyone involved believes the same thing. It’s a shared understanding and alignment of values, not strategy.</p><p>The latter is committed participation. It sounds like a very business-appropriate way of passively expressing disagreement. I’m not discounting the value of alignment in many situations, but I am challenging the notion that it’s the ultimate status of harmony. Perhaps we should spend less energy trying to garner coerced alignment and put that effort into building the kind of trust that inspires agreement.</p><h3><strong>When to use agreement vs. alignment</strong></h3><p>As I mentioned, this isn’t about semantics as much as it is about practice. Alignment is necessary to keep a business moving forward, to create and accomplish goals, and to keep employees from losing their minds over ineffectual efforts. The problem is aligning the right things with the right people at the right level of responsibility. The most egregious mistake — in my opinion — and one I’ve seen a lot, is the tendency of organizations to align on day-to-day processes at the leadership level without the input of the people that do the actual processes. But that’s just one example. Ideally, good alignment — and agreement — might look more like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*Sy5uUKxJVqOEIGhJHuF4wA.png" /></figure><ul><li><strong>The macro-level agreement is focused on things like vision, strategy, and objectives</strong>. The entirety of the business’ mission needs to be a full agreement, not just an alignment. This agreement spans leadership across major functions. (Think of this pattern as repeating from the company level into each group.)</li><li><strong>Top-to-bottom/bottom-to-top alignment is built on a foundation of shared understanding</strong> that should be focused on expectations, with information delivered in both directions. This requires high-quality communication more than anything else. Working teams need to understand the strategy and business objectives, and leadership needs to understand progress and outcomes. But in a hierarchical organization, this doesn’t really need to be agreement. Sometimes someone just has to make the decision.</li><li><strong>Cross-team alignment needs to account for dependencies and milestones</strong>, where all the working groups have goals that are a mix of shared and independent. This is literally about aligning work to other groups’ work and ensuring that the goals of each group can be achieved in harmony.</li><li><strong>Within working groups</strong> — in addition to participating in and benefiting from the other alignments and agreements — is where people can agree on the kinds of processes and standards that will best help them achieve their goals.</li></ul><p>Because agreement is more challenging to achieve, it makes sense to strive for it within smaller groups with similar levels of responsibility. At the higher leadership levels, agreement — more than alignment — will be genuine and prevent deviation. Within working groups, the day-to-day activities of working together are everything. Feeling aligned is only temporarily satisfying. People feel and work better when they have a sense of ownership, and that’s accomplished with agreement. But alignment is enough across teams that may have only sporadic shared needs.</p><p>Overall, there’s less reason to be concerned with the use of the word <em>alignment</em> than there is to be concerned about how we actually align and why.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e26bc41b55e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buzzword Bingo: Ambiguity]]></title>
            <link>https://medium.com/@leslieneal/buzzword-bingo-ambiguity-fd178dcb022e?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd178dcb022e</guid>
            <category><![CDATA[ambiguity]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[buzzwords]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Wed, 28 Jun 2023 13:42:41 GMT</pubDate>
            <atom:updated>2023-06-28T15:23:37.112Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my favorite pedantic battles is debating the usage of words. It probably stems from my intense hatred of all things buzzwordy, and even though I find myself constantly having to use words I think have lost all meaning, I do spend time thinking about what they really mean and how they become so overused and problematic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bqGzkgCvtt-unR-M-4pYmw.png" /><figcaption>Person entering a complex maze with unclear paths and no end in sight</figcaption></figure><p>Today’s word is <em>ambiguity</em>. For clarification, I’m specifically referring to ambiguity as a descriptor for situations, not the semantic gymnastics people use for trickery.</p><p>There are three major problems with the overuse of the word ambiguity — or ambiguous — that overlap with each other:</p><h3><strong>Everything is ambiguous, so it’s not actually special.</strong></h3><p>If the most basic definition of ambiguity is having more than one interpretation or potential outcome, then unless you’re clairvoyant, everything is ambiguous. This means everyone is literally always functioning in ambiguous circumstances, which makes the word relatively moot. What happens instead is that an otherwise normal situation gets labeled as ambiguous, and since only certain people are good with ambiguity, it becomes this special circumstance that only certain people can deal with, but…</p><h3><strong>Comfort with ambiguity is not a skill, and most people couldn’t measure that skill anyway.</strong></h3><p>So many job descriptions want us to be “comfortable with ambiguous situations,” and recently, for the first time, I asked for clarification. The interviewer could not explain what it means beyond, “you know, accepting unknowns.” And so I asked: “How does one demonstrate that skill to you?” I did not receive an answer. The actual skill could be <em>mitigating</em> ambiguity with thorough contingency plans, using a last responsible moment decision-making strategy, or even having a pre-mortem to align on how to handle failure. The fact that my potential employer, in this case, didn’t know how to demonstrate the skill or evaluate it as a skill, means that it’s not really a skill, because…</p><h3><strong>Ambiguity is not a problem to be solved.</strong></h3><p>When a situation with obstacles is considered ambiguous, it indicates that one goal is to eliminate the ambiguity, which is impossible because, again, <em>everything is ambiguous</em>. And these mythical people who thrive in ambiguous situations have no incentive to solve ambiguity, because, by default, it’s where they are most comfortable. Ambiguity thus becomes a poorly used, catch-all proxy descriptor of an actual problem or set of problems that can be solved, but solving the problems does not eliminate the ambiguity.</p><p>Looking back, I realize I’ve also used ambiguity carelessly when I couldn’t take the time to dig deeper and describe something with more precision. It’s lazy, and it happens a lot. When we say a situation is ambiguous, we’re not actually saying what we mean or what we want to do about it. And especially when we throw it around nonchalantly as a blanket statement to describe an individual person’s abilities, it’s borderline insulting because we’re all functioning in ambiguous situations all the time.</p><p>Calling something ambiguous has become an excuse for not knowing what we’re doing, for describing rapidly changing circumstances, or for blaming someone else when they aren’t meeting poorly-defined expectations. And I think we should be more mindful. So, I propose we think about what we really mean and say it instead of using a buzzword as a crutch. Here are a few examples of times we could replace ambiguous with something more exact:</p><ol><li><strong>Your organizational structure is not quite right</strong>. Things are chaotic and difficult and it needs to change, but it hasn’t yet, so you call it ambiguous. It’s not <em>ambiguous</em> when an org structure doesn’t support the successful execution of strategy, goals, or good work; it’s just a bad org structure. It’s fixable. Even when it’s improved, you’re still going to have ambiguity per the rule that all things are ambiguous. <strong><em>You have a changing organization</em></strong>. Change is constant, which technically makes change not so ambiguous after all.</li><li><strong>You have no — or poorly — defined goals</strong>. For one, you have a much larger problem than ambiguity, but call it what it is. There is a lack of alignment, a lack of strategy, or no identified opportunities. If that’s the case, then ambiguity is not the circumstance nor the problem, and what you need isn’t a nebulous soft comfort with ambiguity, <strong><em>you need a real-deal tactical plan</em></strong>. Everyone in this situation should be uncomfortable enough to see the importance of fixing it.</li><li><strong>You are a leader and you don’t know exactly what you want</strong>, or it’s vague in your head, or you didn’t say what you want when you ask an employee to deliver something like a presentation, solution, perspective, or an idea. If ambiguity means the possibility of more than one interpretation, then you need to be prepared for something you weren’t thinking of. When it’s delivered, and you don’t like it because it’s not what you thought you wanted, then here’s the hard truth, friend: <strong><em>you’re the one who’s not good with ambiguity</em></strong>, not your employee.</li><li>Perhaps the most common, and seemingly correct — but still not quite right — use of ambiguous, is <strong>when we don’t know what’s going to happen at all</strong>, which is technically <em>all the time</em>. But, an unknown is just an unknown. For a thing to be ambiguous, it must have an interpretation or potentiality, therefore it must be somewhat known. We collectively went through one of the biggest disruptors in our lifetime, and adjusting to an <strong><em>unpredictable, uncontrollable unknown isn’t ambiguous, it’s just new</em></strong>. It’s a situation requiring the ability to be flexible and pivot quickly, which is what you should call it.</li><li><strong>You don’t know the solution to a problem yet</strong>. This one’s a trick! This is a perfect time to say ambiguous. It just means that you should be open to potentiality, that <strong><em>there are many ways to solve a single problem</em></strong>.</li></ol><p>When we use the word ambiguity, we should be mindful of what we’re really saying. Use it sparingly and when it makes the most sense. It’s about open-mindedness and acceptance of potentiality. If you’re cool with possibilities, then you’re great with ambiguity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd178dcb022e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Managing a 3rd Party Internal-use Tool]]></title>
            <link>https://medium.com/@leslieneal/product-managing-a-3rd-party-internal-use-tool-5c86e06eb488?source=rss-9393bef58026------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c86e06eb488</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Get Real with Leslie Neal]]></dc:creator>
            <pubDate>Wed, 10 Jul 2019 12:57:18 GMT</pubDate>
            <atom:updated>2023-07-21T19:33:32.564Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BP7Jy0-Om-9mgRxdNvf_cw.jpeg" /></figure><p>Product Managing a 3rd Party Internal-use Tool</p><p>What even is that? Managing a vendor-supplied piece of software for internal users, psh. I mean, seriously, is this a real thing that actually needs a product manager? (Yeah, I’ve been asked…repeatedly.) So I’m here to tell you that yes, it is a real thing, it does necessitate product management, and not to toot my own horn (toot!), it requires not only the well-documented, beloved core competencies of product management, but also an additional set of responsibilities and skills. Basically, you have to be pretty rad to pull this off.</p><p>I’m not going to focus on the differences between internal product management (users inside the company) and B2B/B2C (users/customers not inside the company). I’m differentiating between managing two kinds of internal products — built v. bought — and specifically writing about managing a product that my company purchased from another company. (There are nuances here as well, like the differences between buying an on-prem piece of software and customizing it completely v. using a SaaS solution, but I don’t dive into that either. For the record, my tool is SaaS.)</p><p>First, let’s get the basics out of the way. I own a roadmap and a strategy. I work with engineers and UX designers. I write and approve stories. We have agile ceremonies. I know my users’ pain points. We do deep discoveries, prototype solutions, test, and iterate. I prioritize a backlog. I find, calculate, and deliver value (in dollars most of the time). I align with stakeholders. I maintain scope. I do all the “standard” things any product manager would do, then some other stuff.</p><p>And here it is! All that other stuff, a.k.a., the ways that product management is different for me because I manage a 3rd party tool. (And I need to note that I work with a highly collaborative team of people, each of whom is involved in various capacities in all these things. In an effort to only tell my story, I say “I” when I could mean “we” or “the company” because this is my perspective, not because I’m acting alone — i.e. shout out to my awesome team!)</p><ol><li><strong>At the beginning, I was involved in whether we build or buy.</strong> In my specific situation, we did ultimately decide to buy, but that was after a full discovery and documentation of all our needs, pains, and use cases, after sitting through countless vendor demos, and after we looked at the LOE to build what we could buy. (Technically, if you’re an internal PM on a home-grown tool, you may have done this before too, but it’s a pretty big piece of how one even becomes the manager of a 3rd party tool.)</li><li><strong>Most of what I work on with our internal engineering team is integration.</strong> Of course, this can be the case with any product manager, but I’ve found that it’s much more of what I do percentage-wise than I have in the past. On this particular product, I’m less involved in traditional features that a user sees, and more involved in integrating my particular product with other internal tools. I would say it’s more technical, but really it’s just less feature-rich, as most people would understand it. That’s not to say we don’t build user-facing features that involve a UI; we do. When we do, though, we either utilize some preexisting functionality in the tool we have, or build an app separately and then, you guessed it, we integrate it!</li><li><strong>I have to maintain a relationship with a whole separate company.</strong> I deal with contracts; I spend time with an account rep; I talk to their product team, support team, engineering team, solutions team, project managers, sales people, and even sometimes a dev-ops person. I have semi-regular calls with their product team to get a heads up on what’s coming on their roadmap. I attend and speak at their user conference. We are partners for sure, but I’m also a paying customer. It takes some finesse to make this work.</li><li><strong>I think about cost differently.</strong> We have licenses. It has a hard cost, and it’s not the same as labor costs for engineers. In fact, in some cases, the money comes from different places. I thankfully don’t deal with that part, but I did work out some of the contract details. I have to think about the actual cost of the tool when I look at what value we deliver to the business.</li><li><strong>I have to consider two roadmaps simultaneously.</strong> I have a roadmap; I know what business value I will deliver to my internal users. The vendor of my tool also has a roadmap, and as much as I’d love to be, I’m not the only customer. I have to coordinate my roadmap with what they’ll be releasing, and I have to fully articulate someone else’s roadmap in terms of business value for my organization. Their roadmap dictates which users at my company get which features turned on; one small change they make in November means I have to be ready with a small change in one of my integrations in October; I have to build in time to test what they release before I tell my users it exists. I can’t force them to prioritize something differently, though I certainly make suggestions (see number 3).</li><li><strong>Support has another layer.</strong> A user clicks help, and sends a support request. It goes to an internal operations team (my primary users: the admins) for the first level of triage. If they can’t handle it, it comes to me. I have to figure out if it goes to our vendor, or if it goes to internal engineers. If it goes to the vendor, I enter a support request with them, and then I go back and forth until it’s resolved, or if it’s “working as designed” I enter it as a feature request in another system and then try to push the product team to make the change. Sometimes I have to decide if it’s something we want the vendor to do inside the tool, or if we should just build something ourselves. That starts a whole other conversation.</li><li><strong>Implementing a 3rd party tool initially (especially at a large corporation) is very different than building one. </strong>This is a two-part thing: First, I manage an established, fully-baked, “complete” platform. When we turn it on for users, that’s it, there’s no iteration, no solving one problem at a time. We have to do everything in one fell swoop, and it’s a completely different animal than implementing one new feature. I had to get as close to learning all of the platform’s capabilities at once as I could, and I didn’t have anything to do with building any of them. The change management alone is a nightmare. Second, our internal engineering teams have an established way of doing things, but when you mix in an outside piece of software, everything gets thrown off. Security is different. Data structure is different. The development environment is different. It’s like an organ transplant, and you’re worried about it being rejected.</li><li><strong>I don’t know everything. </strong>When I did work at a SaaS company myself, I was absolutely a product SME. I knew my product inside and out. I knew what every minute configuration change did. I knew where every setting was. I knew knowledge base articles by number; I even wrote some of them. I knew what column in what table needed to be checked when something looked weird. Now I have to search documentation or ask questions constantly. I know my particular domain extremely well, but with the tool itself, I just don’t know everything about it yet.</li><li><strong>I’m caught in the middle a lot.</strong> PdMs are pretty much always in the middle, but in addition to being caught between IT and stakeholders, or user pain vs. business goals, I also get stuck between my team and another company. Sometimes my engineers don’t like the documentation the vendor has. I don’t disagree, but I can’t get in a bitch session about it either, because I helped choose this tool and this vendor. Users sometimes don’t like the way something looks in the tool. I don’t disagree, and I can make a request, but I also can’t tell the user that I’ll get that on my backlog, because I really can’t, and I have to even prioritize what I push our vendor to change. Sometimes random people at my company think my tool should do something it doesn’t, and my vendor’s own mission, vision, and position in the market means it never will, and I can’t do anything about it. Sometimes I agree with what my vendor has done “as designed” and my users or engineers or someone else doesn’t. I can request a change from the vendor, or I can defend it to my own people. I have to constantly balance loyalty, partnership, and doing the right thing.</li><li><strong>Everything could completely fall apart</strong>. Sometimes software companies merge with other software companies, or holding companies sell them, or they go under, or they change direction completely, or their priorities change. I have zero control over another company’s business decisions, so all I can do is maintain a good relationship. Now, on the technical side of things, I do make sure my strategy includes some safeguards that will allow us to maintain parity no matter what, but I have to consider the fact, however unlikely, that one day my product could not exist as I know it.</li></ol><p>One of the really good things about managing a 3rd party tool is that because much of the required feature work is done (and being improved without my direct involvement), I do get to focus more on how my tool fits into a larger ecosystem. I consider the future in its entirety, not just a roadmap of feature sets for one product. It gives me the freedom to use integrations as the theme of my strategy, and in my opinion, it’s the in-between that matters most these days. Being tool agnostic with deep integrations; that’s my jam. (And maybe my next topic!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c86e06eb488" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>