Writing a plan is the part most teams enjoy most, and also the part where they make the biggest mistake. They think the plan is finished when the boxes are full.

You know the plan is finished when the team has excluded something. That is exactly where a facilitator earns their fee, and where no tool is going to help you.

What you do

You make sure a choice gets made. In practice: you separate the ambition from the wish list, you insist that a goal gets a number and a date, and you hold on when the team writes a strategy that excludes nothing.

That last one is the real work. “We are investing in customer focus” is not a choice, because nobody is against it. You are the one who asks: so what are we going to stop doing?

You also guard the process. Whoever runs the session cannot also push their own view on the content. That is why a team with an outspoken director cannot run a good session itself, and why they call you.

What the platform does

It records what was decided while you are working.

The brainstorm space is shared, so you can use it during the session rather than afterwards. Nobody is taking notes in a separate document that has to be merged later. The familiar management models are in there (Business Model Canvas, SWOT, lean canvas, stakeholder analysis), so the analysis and the plan sit in the same place.

After that, every element carries what it needs to steer on: an owner with a name rather than a department, a deadline, a target value with a unit. An empty block asks the question it exists for, which is a better prompt than an empty field on a flip chart.

The checklist and the OGSM score are your quiet ally. They show where the plan is still vague: a goal without a target, a strategy without an owner, an action without a date. You no longer have to ask for it as the facilitator, because it is on the screen. That takes the nagging out of your role and lets you stay on the content.

Where it usually goes wrong

The plan is too full. The first version of the action list is rarely realistic. Count on having to cut in the second session, and say so in advance so it is not a surprise.

The team wants to halve the process. “We will do the brainstorm in an hour.” Then you get a plan that does not survive the first setback, and three months later that gets called a software problem.

The plan does not feel like the team’s. Ownership matters more here than speed. The team has to feel this is their plan and that they are accountable for the results. A plan that is handed over rather than made does not get opened in month two.

What else the platform does here

Everything around writing a plan is set out on the product site: the brainstorm, the management models, the detail view per element, the AI generator and the OGSM score.

The full description of this phase, with screenshots.

Create on ogsm.online

Once the plan exists, execute begins.