A baseline that hasn’t been stress-tested is just optimism in a spreadsheet.

I’ve seen it more times than I can count.

A team works hard to produce a baseline program.

Hours of effort. Hundreds of activities. Logic tied together.

And then it gets approved and no one asks the hard questions.

Not because they don’t care.

Because they’re busy being busy.

Here’s what gets skipped almost every time:

1. What is actually driving completion?

Not what looks like the critical path. What is the critical path and does the team truly understand it?

2. Where are the hotspots?

Every program has 2 or 3 areas that carry disproportionate risk. Most teams don’t name them out loud. So no one’s watching them.

3. What happens if this assumption fails?

Design ready by X. Approvals by Y. Resources available by Z.

Those aren’t facts. They’re assumptions. And assumptions need to be challenged, not buried in a footnote.

The baseline is the most important document on a project.

Not because it predicts the future.

Because it forces the team to think about the future and own their logic before reality tests it for them.

If your baseline hasn’t been challenged, it hasn’t been finished.