<?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 The Cranky PM on Medium]]></title>
        <description><![CDATA[Stories by The Cranky PM on Medium]]></description>
        <link>https://medium.com/@thecrankypm?source=rss-3f9339c0d527------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EPnWF6oxbGOPm9UYJKRHaw.png</url>
            <title>Stories by The Cranky PM on Medium</title>
            <link>https://medium.com/@thecrankypm?source=rss-3f9339c0d527------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:38:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thecrankypm/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Set Project Goals That Don’t Suck]]></title>
            <link>https://medium.com/@thecrankypm/how-to-set-project-goals-that-dont-suck-4e9e0d631193?source=rss-3f9339c0d527------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e9e0d631193</guid>
            <category><![CDATA[effectiveness]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[The Cranky PM]]></dc:creator>
            <pubDate>Mon, 18 Aug 2025 09:56:54 GMT</pubDate>
            <atom:updated>2025-08-18T09:59:18.933Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jCW9xzOcdKY2LRBZaPnmQ.png" /></figure><h3>Why 90% of Project Goals Fail (And How to Fix Yours)</h3><p><em>Originally published on </em><a href="https://www.thecrankypm.com/p/how-to-set-project-goals-that-dont-suck"><em>The Cranky PM</em></a></p><p>Most project goals are corporate word soup designed to sound important while committing to absolutely nothing.</p><p>“Enhance user experience through innovative solutions.” “Optimize operational efficiency via strategic improvements.” “Drive engagement through platform modernization.”</p><p>What does any of that even mean? How would you know if you succeeded? These aren’t goals. They’re Mad Libs for middle managers, actively sabotaging projects before teams write a single line of code.</p><h3>Your Goals Are Meaningless Corporate Speak</h3><p>Here’s what bad goals look like:</p><p><strong>They’re unmeasurable.</strong> “Increase user satisfaction” sounds important until you realize you don’t measure satisfaction, have no baseline, and wouldn’t know what to do if it tanked tomorrow.</p><p><strong>They’re uselessly vague.</strong> “Build a better checkout flow” could mean fixing a typo or rebuilding the entire payment system. Your team will spend weeks arguing about what “better” means.</p><p><strong>They’re disconnected from reality.</strong> Your goal is to “modernize the tech stack” but you can’t explain why that matters to a single human using your product.</p><h3>How Bad Goals Kill Projects</h3><p>Poor goals don’t just waste time — they metastasize through your entire project:</p><p><strong>They create chaos instead of clarity.</strong> When everyone interprets the goal differently, you’re building a Frankenstein monster of incompatible features.</p><p><strong>They make decisions impossible.</strong> Every tradeoff becomes a nightmare when your goal is to “enhance the platform.” You can’t prioritize because you don’t know what you’re actually trying to accomplish.</p><p><strong>They turn scope creep into scope avalanche.</strong> When your goal is meaningless, you can’t say no to anything. Every stakeholder request becomes part of your “strategic vision.”</p><h3>What Good Goals Actually Look Like</h3><p>Good goals are boring. They don’t generate executive applause or make you sound visionary on LinkedIn. They just tell you exactly what you’re building and how you’ll know if you got there.</p><p><strong>Instead of:</strong> “Improve user engagement”<br> <strong>Try:</strong> “Increase weekly active users from 10,000 to 15,000 by fixing the three most common onboarding failures”</p><p><strong>Instead of:</strong> “Modernize the platform”<br> <strong>Try:</strong> “Reduce page load times from 3 seconds to under 1 second because 40% of users bounce after 2 seconds”</p><p><strong>Instead of:</strong> “Enhance customer experience”<br> <strong>Try:</strong> “Reduce checkout abandonment from 60% to 40% by fixing the broken payment flow”</p><p>See the difference? Good goals solve specific problems, use numbers that matter, and connect to outcomes people actually care about.</p><h3>The Simple Goal-Setting Framework</h3><p>Stop overthinking this. Here’s how to set goals that don’t suck:</p><h3>1. Start with a Real Problem</h3><p>What’s broken? What’s costing money? What’s preventing growth? Be brutally specific about the actual problem, not the solution you’re in love with.</p><h3>2. Define What “Fixed” Looks Like</h3><p>How will you know the problem is solved? What will be different? If you can’t answer this clearly, you don’t understand the problem.</p><h3>3. Put Numbers on It</h3><p>How much better? By when? If you can’t quantify success, you’re working on unmeasurable wishful thinking.</p><h3>4. Connect It to Business Value</h3><p>Why does this matter? How does solving this problem help real people or make real money? If you can’t answer this, you’re working on internal pet projects.</p><h3>5. Set a Real Deadline</h3><p>When will you know if you succeeded or failed? Set a date that prevents endless scope creep and forces you to ship something.</p><h3>Three Goal Templates That Work</h3><p><strong>Problem-Solution Format:</strong><br> “[User group] can’t [accomplish task] because [obstacle]. We will [solution] so that [outcome] by [date].”</p><p><strong>Metric-Improvement Format:</strong><br> “Increase [metric] from [current] to [target] by [date] because [business reason].”</p><p><strong>Cost-Reduction Format:</strong><br> “Reduce [cost/inefficiency] from [current] to [target] by [date] to [benefit].”</p><h3>Stop Trying to Sound Smart</h3><p>The reason most goals are garbage isn’t because teams don’t know how to set good goals. It’s because they’re optimizing for PowerPoint presentations instead of project success.</p><p>Good goals are tools, not trophies. They exist to help your team build the right thing, not to make you sound strategic in meetings.</p><p><strong>Make them specific</strong> enough that a stranger could pick up your project and know exactly what to do.</p><p><strong>Make them measurable</strong> enough that anyone could tell if you’re winning.</p><p><strong>Make them valuable</strong> enough that your CEO would actually care if you failed.</p><h3>The Uncomfortable Truth</h3><p>The perfect goal statement matters way less than having any clear, specific goal that everyone understands and cares about.</p><p>A decent goal that gives your team focus will produce infinitely better results than a beautifully crafted goal that confuses everyone.</p><p>Stop wordsmithing your way to perfection while competitors ship actual products. Pick a real problem hurting real people, define what solving it looks like, and start building.</p><p><strong>Your users don’t care how poetic your goal statement is. They care whether you actually solve their problems.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e9e0d631193" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Set Project Timelines When Your Stakeholders Live in Fantasy Land]]></title>
            <link>https://medium.com/@thecrankypm/how-to-set-project-timelines-when-your-stakeholders-live-in-fantasy-land-81370c7a9feb?source=rss-3f9339c0d527------2</link>
            <guid isPermaLink="false">https://medium.com/p/81370c7a9feb</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[The Cranky PM]]></dc:creator>
            <pubDate>Wed, 16 Jul 2025 08:13:02 GMT</pubDate>
            <atom:updated>2025-07-16T08:14:53.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JURNqwIMesUsEbKrmxaCjg.png" /></figure><p><em>Originally published on </em><a href="https://www.thecrankypm.com/p/how-to-set-project-timelines-when-your-stakeholders-live-in-fantasy-land"><em>The Cranky PM</em></a></p><p>You’re sitting across from a stakeholder who thinks project timeline creation is like ordering pizza.</p><p>They lean forward with that predatory smile and ask the soul-crushing question: <em>“So when can we launch this?”</em></p><p>And there you are, about to commit <strong>the cardinal sin of project management:</strong> giving them a realistic estimate based on the foolish assumption that they understand how software development actually works.</p><p>Here’s the uncomfortable truth: your stakeholders don’t want accurate project timeline estimates.</p><p>They want magical dates that make their business dreams come true, regardless of technical reality.</p><p>When those dates inevitably slip, guess who gets blamed?</p><p>Not the person who demanded the impossible timeline.</p><p><strong>You.</strong></p><p>It’s time to stop being the fall guy for other people’s delusions about deadline management.</p><h3>Why Your Timeline Estimates Always Become Your Problem</h3><h3>Your Stakeholders Are Timeline Terrorists</h3><p><strong>They’ve weaponized optimism against you.</strong></p><p>Every project timeline discussion follows the same script: they propose an insane deadline, you explain why it’s impossible, they guilt-trip you about “finding solutions”, and you eventually cave because you’re a professional who wants to be helpful.</p><p><strong>Type 1: The Wishful Thinker</strong><br> <em>“Can’t we just make it simpler?”</em><br> Translation: “I don’t understand what you’re building, but I need it by Tuesday for a presentation I forgot about.”</p><p><strong>Type 2: The False Urgency Creator</strong><br> <em>“This is absolutely critical for Q3.”</em><br> Translation: “I promised something to my boss without checking if it was possible, and now you need to save my career.”</p><p><strong>Type 3: The Scope Denier</strong><br> <em>“It’s just a few small changes.”</em><br> Translation: “I’m going to fundamentally alter the requirements but pretend it doesn’t affect the project timeline.” This is classic <a href="https://www.thecrankypm.com/p/scope-creep-isn-t-the-problem-your-boundaries-are">scope creep</a>.</p><h3>You’re Trapped in the Optimism-Reality Death Spiral</h3><p>Here’s your predictable cycle:</p><p><strong>You give an honest estimate.</strong></p><p>They push back.</p><p><strong>You reduce the timeline to keep them happy.</strong></p><p>The project inevitably runs late.</p><p><strong>You get blamed for poor deadline management.</strong></p><p><strong>You promise to “do better” next time.</strong></p><p>Repeat until burnout.</p><p>This isn’t a deadline management problem. It’s a <a href="https://www.thecrankypm.com/p/stakeholder-management-survival-strategy-project-managers">stakeholder boundary management</a> problem.</p><h3>The Reality-Based Timeline Framework</h3><h3>Step 1: The Three-Timeline Strategy</h3><p>Never give stakeholders a single date. Give them three options that force them to understand the tradeoffs:</p><p><strong>Timeline Option 1: The Bare Minimum (6 weeks)</strong><br>Core functionality only. No bells, whistles, or scope changes. Works for basic use cases.</p><p><strong>Timeline Option 2: The Full Vision (12 weeks)</strong><br>Everything they actually want, built properly, with time for testing and refinement.</p><p><strong>Timeline Option 3: The Fantasy Timeline (4 weeks)</strong><br>What they’re asking for, delivered through pure magic and developer tears. Include a disclaimer about quality expectations.</p><p><strong>Force them to choose.</strong></p><p>No middle ground, no “let’s shoot for somewhere in between.”</p><p><strong>Make them own the decision about what matters most.</strong></p><p>Make them own the decision about what matters most. This forces <a href="https://www.thecrankypm.com/p/how-to-prioritize-when-everything-is-a-priority">real prioritization</a> instead of wishful thinking.</p><h3>Step 2: The Assumption Warfare Document</h3><p>Create a project timeline contract that explicitly states every assumption you’re making. This isn’t just CYA documentation. It’s stakeholder education disguised as project planning.</p><p><strong>Sample Assumptions:</strong></p><ul><li>Final requirements will be provided by [specific date]</li><li>No scope changes once development begins</li><li>All stakeholder approvals within 2 business days</li><li>Third-party integrations will work as documented</li><li>Content and assets provided on schedule</li><li>No emergency “quick fixes” during development</li></ul><p>End with:</p><blockquote><em>“This project timeline is based on these assumptions. Each assumption that proves incorrect will impact the delivery date proportionally.”</em></blockquote><h3>Step 3: The Scope Change Hostage Strategy</h3><p>Build scope change consequences directly into your timeline presentation:</p><blockquote><em>“This timeline assumes zero scope changes. Each scope change, regardless of size, adds a minimum of one week to the schedule for requirements analysis, impact assessment, and timeline adjustment.”</em></blockquote><p><strong>Make scope changes expensive in time, not just money.</strong></p><p>When stakeholders understand that their “quick addition” costs them two weeks, they become more thoughtful about what they really need.</p><h3>Defending Your Timeline Against Common Attacks</h3><h3>“Can’t You Just Work Nights and Weekends?”</h3><blockquote><em>“I can work additional hours for short periods during genuine emergencies. A poor project timeline that was unrealistic from day one isn’t an emergency. It’s a planning failure. Working excessive hours reduces quality and creates more problems than it solves.”</em></blockquote><h3>“The Last Developer Did It Faster”</h3><blockquote><em>“Great! Let’s bring them back to handle this project. If they’re not available, then we’re working with the team we have, using realistic estimates based on current capabilities and requirements.”</em></blockquote><h3>“Can’t We Launch Something Basic and Add Features Later?”</h3><blockquote><em>“Absolutely. Here’s what ‘basic’ actually means: [list specific feature cuts]. We can launch this reduced version by [date]. Adding the missing features later will require [additional timeline] because we’ll need to modify working code instead of building from scratch.”</em></blockquote><h3>“This Should Be Simple to Build”</h3><blockquote><em>“Simple for whom? The user experience may seem simple, but creating that simplicity requires complex backend systems, integrations, and error handling. Every ‘simple’ feature is an iceberg. What you see represents about 20% of the actual work required.”</em></blockquote><h3>The Hidden Psychology of Deadline Management</h3><h3>Why Stakeholders Keep Pushing for Impossible Timelines</h3><p>They’re not trying to torture you (usually). They’re responding to their own pressures:</p><ul><li>Their boss demanded an unrealistic delivery date</li><li>They promised something without understanding the complexity</li><li>They’re measuring success by speed rather than quality</li><li>They don’t understand the technical work involved</li></ul><h3>Why You Keep Accepting Impossible Deadlines</h3><p>You want to be helpful.</p><p>You don’t want to seem difficult.</p><p>You think maybe this time will be different.</p><p>You’d rather be optimistic than disappoint people.</p><p><strong>This people-pleasing approach to deadline management destroys your credibility.</strong></p><p>When you consistently miss deadlines because you agreed to unrealistic expectations, stakeholders learn to distrust your estimates and add their own “safety buffer.”</p><h3>Advanced Timeline Defense Techniques</h3><h3>The Milestone Commitment Strategy</h3><p>Instead of committing to final delivery dates months in advance, commit to shorter milestone dates with regular reassessment:</p><blockquote><em>“I can commit to having user authentication working by March 15th. Based on what we learn during that milestone, we’ll reassess the timeline for the remaining features.”</em></blockquote><h3>The External Dependency Buffer</h3><p>When your project timeline depends on external factors, build massive buffers:</p><blockquote><em>“This assumes your content team delivers final copy by February 1st. If content is late, the entire project timeline shifts accordingly. I recommend building a two-week buffer into your content schedule.”</em></blockquote><h3>The Quality Tradeoff Presentation</h3><p>When pressured to cut timelines, present specific quality tradeoffs:</p><blockquote><em>“To deliver two weeks early, we’ll skip the user testing phase and launch with minimal error handling. Are you comfortable explaining to users why the application crashes when they upload large files?”</em></blockquote><h3>The Uncomfortable Truth</h3><p>Here’s what nobody tells you: the fight over project timelines isn’t really about schedules.</p><p><strong>It’s about who takes responsibility when things go wrong.</strong></p><p>Stakeholders want you to own the timeline risk so they can blame you for delays.</p><p><strong>Your job is to make them own the decisions that create timeline risk: scope, resources, and quality expectations.</strong></p><p>When you stop accepting responsibility for timeline outcomes that depend on factors outside your control, you force stakeholders to become partners in realistic planning instead of critics of inevitable delays.</p><h3>Stop Enabling Timeline Fantasy</h3><p>Your job isn’t to make stakeholders feel good about unrealistic expectations.</p><p><strong>Your job is to deliver working software that solves real problems.</strong></p><p>When you accept impossible timelines to avoid difficult conversations, you’re enabling a dysfunctional system that burns out teams and delivers poor results.</p><p><strong>The solution isn’t better estimation techniques. It’s better </strong><a href="https://www.thecrankypm.com/p/stakeholder-management-survival-strategy-project-managers"><strong>stakeholder boundary management</strong></a><strong>.</strong></p><p>Start treating project timeline discussions as negotiations between equals, not performance reviews where you’re graded on your willingness to promise the impossible.</p><p><strong>Stop being the fall guy for other people’s poor planning. Start being the professional who insists on realistic expectations and delivers on their commitments.</strong></p><p><em>What’s your experience with stakeholder timeline pressure?</em></p><p><em>How do you handle unrealistic deadline demands?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81370c7a9feb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>