Every Schedule Tells a Story

Every schedule tells a story.

After 35 years of building and reviewing CPM schedules, that's the one thing I keep coming back to.

The WBS is your table of contents. It tells the reader what this project is about, how it's organized, and where to find what matters.

The activity groupings under each WBS node are your chapters. The logic ties between them are the narrative thread — they explain how one chapter leads to the next, what depends on what, and why the sequence matters.

But here's what I see over and over again.

The intent is there. The scheduler knows the WBS matters. They build one out because the project requires it.

But it gets thrown together under time pressure. The structure isn't thought through. Nodes get created to check a box, not to tell the story of how the project actually gets built.

And then the schedule is harder to navigate than it needs to be. The review takes longer. The narrative doesn't flow. The project story gets lost in the noise.

I've seen schedules with hundreds of WBS nodes that are so overly complex they make the schedule harder to read, not easier. And I've seen schedules with a clean hierarchy from mobilization through closeout that practically review themselves.

The difference isn't the number of activities. It's the structure.

If you're reviewing contractor schedules, try something next time — before you look at the critical path, spend five minutes with the WBS. You might be surprised how much it changes the way you read everything else.