Business focus with retrospective knowledge

Focus drifts, and no one decides it

Focus rarely disappears in one big decision. It leaks away in small ones: a customer who needs “just one more thing”, a tool to try out, a channel to test. Three months later the calendar is full, but no one can say what it actually built.

The remedy is not more discipline. It is a fixed point where facts about what worked correct course before the leak becomes permanent.

What retrospective knowledge actually is

Retrospective knowledge is not a gut feeling about last quarter. It is written, checkable answers to three questions:

• —What produced a measurable result — revenue, hours saved, fewer errors — and what only produced activity?
• —What cost more than it was worth, and how was that actually decided?
• —What do we know now that we should have known when we chose what we chose?

The answers must be written down. Knowledge that only lives in the meeting disappears with the meeting — and returns as the same discussion next time.

The simplest possible retrospective

One year, one hour, three columns: keep, stop, start. Everything in “keep” must point to a concrete result from the list of what worked. Everything in “stop” must have a cost that can be stated in numbers or hours. Everything in “start” must be tied to something observed, not something someone read about.

For small businesses this is sufficient. The formats of larger companies — longer templates, external facilitators, scoring systems — are designed for organisations with different problems.

From knowledge to focus

The retrospective only becomes business focus when it decides one thing: where the next period's weight goes. Choose the single work area the retrospective shows gave the most effect per hour spent, and let it decide what gets calendar space first. What doesn't fit isn't rejected — it is deliberately postponed.

Then focus is no longer an intention, but a conclusion — drawn from what the business itself has documented works.