A practical framework for structuring major events from master planning to implementation. Programmes, projects, task groups, tasks — one connected planning system instead of a pile of lists.
Step 8 of the 10-Step Major Event Strategy Roadmap.
Busy is not the same as structured.
Most organisers begin the same way. They open spreadsheets. They build schedules. They draft organograms. They start lists, open shared folders, create meeting routines, and ask every team to send actions.
All of that feels productive. Sometimes it is productive. But it does not automatically create a planning structure.
The organiser becomes busy, but not clear. People work hard, but not always in the same direction. Important work sits next to minor work with no real logic behind it. Leadership gets updates, but not a clear view of the whole.
That is not a people problem first. It is a structure problem first.
Each layer does a different job. Each layer depends on the one above it. And each layer makes the next one possible. Skip one and the work below it becomes harder to lead.
Strong event plans are not built from the bottom up by collecting thousands of tasks and hoping the structure appears later. They are built from the top down and then carried through to action.
A task is only truly useful when it belongs somewhere. If it does not sit inside a task group, project and programme, it is a floating action — and floating actions create confusion, duplication and missed dependencies.
155 pages. Each lesson takes one part of the planning problem and ends somewhere you can use the same week.
How to simplify 40,000 tasks into manageable layers without losing the big picture. The four connected levels, what each one does, and what breaks when a layer is missing.
Why strong event plans are built from the top down and then carried through to action — and why a task that does not sit inside a task group, project and programme becomes a floating action.
Purpose, audience, ownership and structure. The questions that decide whether a piece of work is properly defined before anyone starts building it.
Resources, outcomes, value, timing and measurement. The second half of the test, and the point where planning stops being a naming exercise.
Idea → Input → Output → Outcome → Value. The thinking model that runs through every layer and turns a planning structure into a working system.
How to decide what deserves time, money and effort when the list is longer than the organisation can carry — and how to make the no understandable.
Turning organisational subjects into planning containers with an objective, a lead, key components, milestones and a place on the timeline.
The benchmark. 37 programmes in five families, each with its objective, ownership, components and role in the wider structure. Use it to find what your event is missing.
How to move from the model on the page to a working planning sheet the organisation actually uses.
A framework can still become mechanical. A project can still be busy but weak. A team can still work hard on something that never connects to real value. This is the test that catches it.
A committee may have named the programme, defined the project, assigned an owner, opened the tracker and booked the meetings — and still not be clear on why the work exists or what value it should leave behind. That is the difference between a checklist and a blueprint.
A major event can look well planned and still be missing a whole programme area. The problem rarely shows early. It shows later as unclear ownership, hidden dependencies, missing budgets, weak stakeholder handling and reactive problem-solving close to delivery.
The First 100 Days builds the strategic core — vision, mission and values. Steps 1 to 3 of the roadmap. That is what the structure is supposed to serve.
The workshop and advisory routes are on the Programme & Project Planning Blueprint page. This page is the book.
The Blueprint page describes three levels of support: learning the method, running a one-day planning workshop, or building the framework together. This page is the book itself — 155 pages you can read and apply internally, without a workshop or an advisor.
Software tracks work well. It does not tell you what should become a programme, what belongs inside a project, or who owns each level. Those are structural decisions and they come first. Once the structure is right, Notion, Excel, a PMO system or the Bonacube App all become easier to use. The structure travels; the software is replaceable.
No. It is a benchmark list, not a fixed recipe. Some events combine several of the 37, large events split them further. The point is to test the completeness of your own event structure and find what is missing before it becomes a late surprise.
After. The First 100 Days builds the strategic core — vision, mission and values. The Blueprint is step 8 of the roadmap: how that strategy becomes an organised structure of programmes, projects, task groups and tasks.
Instant PDF download after checkout. The price is 99 € + VAT.
The earlier the structure exists, the less rework the organisation carries for the rest of the project.