Break it down, then break it down again

Break it down, then break it down again.

It's the key to building confident project plans.

When someone tells me "but I don't know how long it will take" or "I don't know how much it will cost" that's a good sign we haven't gone granular enough.

After all, it's called a work breakdown structure for a reason. 😉

One of my favorite frameworks for getting clear about what needs to be done is the GOST method.

It goes like this:

GOALS:

where we want to end up

⏬

OBJECTIVES:

specific milestones

⏬

STRATEGY:

roadmap to how we will get there

⏬

TACTICS:

activities to get things done

My rule of thumb for the type of projects I'm working on is that if you can't confidently say that an activity will take 8 hours of work or less, then it's not broken down far enough (work packages...)

The language and the rules matter to your team, so make sure you are in alignment.

👉 Share your favorite framework or method below!