Executives want it done in six months. Your PM is telling you it will take ten.
The “correct” answer is clear. Walk leadership through the scope, assumptions, and risks until everyone aligns on a realistic and defensible schedule. But in real life, those leaders have already circled the launch date, planned a party, and sent the invites.
So many PMO leaders fall back to the pragmatic thing.
They haggle for a compromise—maybe eight months—and hope the team can “find” the missing weeks. It’s simply easier to apologize for a concrete delay later than to debate an invisible risk now.
But over burritos not long ago, I listened to a project manager whose carefully reasoned timeline had been lopped by 30 percent with little explanation. After months of 55-hour weeks and several abrupt resignations (citing workload), she kept hearing the same directive: Make it work.
Translation: Your wellbeing is an expendable resource.
Maybe it’s my millennial sensibilities, but I keep coming back to a question I don’t hear asked nearly enough:
Is it ethical to baseline a schedule we know will demand chronic overwork?
What is an “aggressive” timeline, really?
Projects live on a probability curve—but few of us pull back the curtain on what those probabilities mean in human terms.
- A credible baseline usually reflects a 70–85% confidence level. You’ve validated assumptions, considered risks, and modeled resource constraints. If you simulated the project 100 times, about 8 in 10 would hit the target or beat it.
- A stretch date is more like a coin flip—50% or 60% chance of hitting the mark, given your planning assumptions. Beating the odds requires deliberate trade-offs: adding dedicated resources, reducing distractions, fast-tracking decisions, and funding risk mitigation plans.
- An aggressive date relies on both extraordinary luck and extraordinary effort. Your planning assumptions give this date low odds—sometimes just 20 or 30 percent. In most cases, the only way this target is achieved is for people to work considerable overtime. For long projects, the overtime this requires can last months—turning “temporary heroics” into the norm.
The Ethical PMO: What it Is, and Why It Matters
To me, an ethical PMO should honor (at least) three obligations:
- Shareholders – Deliver value through responsible, strategic use of time, money, and talent
- Employees – Protect well-being, especially when “our people” is a core value on the website.
- Public Interest – Safeguard public health, safety, and environmental sustainability.
Ignore one, and the others begin to wobble. Burn out your experts, and you lose throughput, institutional memory, and trust. Fail to create urgency, and shareholder value suffers from wasted resources and slow impact.
What I’ve seen is this: PMOs that don’t actively talk about ethics often sleepwalk into compromise.
Not because they don’t care—but because nobody named the trade-offs out loud.
Why Do We Normalize Unrealistic Schedules?
Ask around, and most project leaders can tell you when a schedule is unrealistic. So why do we go along with it anyway?
Sometimes it’s optimism bias—a sincere belief that this time will be different. Other times, it’s urgency theater: everyone knows the timeline is tight, but no one wants to be the one who slows momentum…including executives who want to make a splash by demonstrating tangible wins.
Then there’s good old-fashioned career management. If your bonus, visibility, or next promotion is tied to delivery—not realism—there’s pressure to say yes now and hope for the best later.
What makes this more dangerous is that overwork doesn’t look like failure—at first. It looks like dedication. Team spirit. “Leaning in.” Until the wheels come off.
We’ve made unrealistic schedules feel normal. And in the process, we’ve normalized the silent trade-off: deadlines at the expense of people.
The Hidden Costs of Aggressive Baselines
Aggressive schedules don’t just hurt morale. They carry hidden—and often compounding—costs:
- Burnout and attrition
Sustained overwork leads to health issues, absenteeism, and team churn. And when people leave mid-project, the timeline suffers anyway. - Lower quality, higher risk
Tired teams miss things. They make safe bets instead of creative ones. They cut corners—not because they’re careless, but because there’s no time to do otherwise. - Reputational damage
Leaders who habitually overpromise and underdeliver lose credibility. Stakeholders become skeptical, which makes it harder to get buy-in when it matters most. - Long-term velocity loss
Even if you “make the date,” teams often emerge depleted. Institutional knowledge leaves with burned-out employees. Momentum fizzles. And recovery takes longer than most roadmaps plan for.
When (If Ever) Aggressive Baselines Might Be Justified
There are moments when an aggressive date might be defensible. But it comes down to two things: informed consent and temporary scope.
An aggressive timeline might be worth pursuing if:
- The reward is significant and time-sensitive (e.g., regulatory shifts, competitive advantage).
- The team understands the odds—and what will be required to beat them.
- The organization is willing to fund the trade-offs (e.g., backfills, bonuses, extra staffing).
- There’s a clear off-ramp—an understanding that “the push” won’t become the plan.
If the team thinks they’re managing to a stretch target, but you’re actually baselining to an aggressive one, that’s not just risky. It’s a breach of trust.
What Ethical Planning Looks Like in Practice
Ethical planning doesn’t mean avoiding all discomfort. It means naming trade-offs out loud—so that deadlines aren’t silently subsidized by invisible overtime.
Here’s what that can look like in practice:
- Use Confidence Percentages (Informed by Your Team)
You don’t need a simulation tool to talk about probabilities. Try assigning confidence levels—like 80% or 60%—based on your team’s collective experience. One simple approach is to start with the PERT formula, a method for estimating task duration that considers three scenarios:
- O = Optimistic time (best case)
- M = Most likely time
- P = Pessimistic time (worst case)
The traditional formula looks like this:
(O + 4M + P) ÷ 6
It weights the “most likely” scenario most heavily, helping you avoid being too swayed by outliers. But if you’re aiming to reflect a more optimistic (or aggressive) estimate, you might experiment with a different weight—like:
(P + 3M + 2O) ÷ 6
- Once you’ve built a few versions, ask your team:
“What would have to go right to hit this faster timeline safely?”
“What are we assuming will break in our favor?”
That conversation alone can surface critical risks—and reset leadership’s expectations.
Want more on PERT? Here’s a solid primer: What is the PERT Formula?
- Forecast Ranges, Not Certainties
Instead of offering a single date, give a range—anchored in real constraints. For example: “With our current resources, we expect this to land between June 15 and July 20, with 80% confidence. To move it earlier, we’d to add more developers now, while there is still time for them to ramp up and operate at normal speed.”
Framing timelines this way resets expectations: it’s not about picking a number—it’s about understanding what higher certainty will cost, especially when that certainty hinges on sustained overwork.
- Monitor Team Happiness (Seriously)
Some overtime is inevitable, especially during peak delivery phases. But when “the push” becomes the pattern, you need a signal. Agile teams often use a simple tool: ask each team member to rate their weekly happiness or stress level on a scale of 1–5. (Bonus: ask why.)
Track the trend. A single low week might just reflect a crunch. A downward slope is a signal to pause and ask: What can we adjust? Can we redistribute work? Change scope? Adjust expectations?
Happiness might seem like a “soft” metric—but it’s often the earliest warning sign of burnout, disengagement, and turnover. And when people feel safe enough to answer honestly, you’ve already done something right.
Final Thought: What Gets Baselined Gets Believed
Baselines aren’t just numbers. They become signals—of what’s expected, what’s acceptable, and what’s worth sacrificing for.
When PMOs allow unrealistic schedules to become the official plan, even with quiet skepticism, they shift the burden to the team to “make it work.” And once it’s on the books, it’s treated as truth—even if it started as wishful thinking.
Ethical planning doesn’t mean shying away from urgency. It means naming the costs of speed—early, clearly, and often.
Because at the end of the day, it’s not just about whether you make the date.
It’s about how many people had to break themselves to get you there.