A simple system to delegate projects without losing control

Executive overview

Delegation fails when leaders hand over work without transferring vision. The result: missed deadlines, missed budgets, frustrated owners who vow to do it themselves next time.

Two templates fix this. A project brief gets your vision out of your head and into a format your team can read, question, and act on. A project plan template gives the person running the project a repeatable structure so nothing gets skipped.

The core insight: your team can't execute your vision if they can't see it — templates replace blank pages with structured prompts that do the thinking for you.

The five sections of a project brief

1. Overview — current state, the transformation after the project, and the big-picture impact over 12+ months. Describes the "why" behind the project, not just the "what".
2. Key decisions — a running log of decisions made during the project, each with a date. If it isn't logged here, it isn't decided.
3. Prioritisation guidelines — ranks quality, speed, and budget so the team knows which constraint wins if trade-offs arise.
4. Deliverables and out-of-scope items — lists must-have outputs and explicitly names what the team should not touch. Out-of-scope items prevent overreach, not just scope creep.
5. Resources — time budget, financial budget, and any other constraints. Defines how tall the ladder needs to be.

How to use the project brief

• Fill in the brief before handing anything to the team — it forces you to articulate the future state in writing.
• Senior team members may need only the overview; junior or mid-level staff benefit from detailed deliverables and out-of-scope guardrails.
• The brief is a living document: key decisions get added throughout the project, not just at the start.
• The brief replaces the blank page — it prompts you to cover context you would otherwise forget.

The project plan template: before

• Create the project plan tasks — the assigned coordinator reads the brief and breaks it into specific tasks.
• Pre-kickoff prep — all team members review the brief and their assigned tasks independently before meeting.
• Kickoff call — a focused conversation covering four questions: Can you visualise the end result? What could go wrong? Is anything unclear? What happens next?
• Prep before the kickoff keeps the call short; questions are often already written in task descriptions, so the call becomes problem-solving, not information-sharing.

The project plan template: during

• Weekly status report — the project coordinator writes one sentence on where the project stands and sets a status: on track, at risk, behind with a plan, or behind without a plan.
• Weekly scrum call — 30 minutes or less: what happened, what's next, what's in the way. Fast-moving projects may run this twice a week.
• Running retrospective notes — every team member spends two to five minutes per week logging what they learned, what went wrong, and what they discovered. These notes feed the final retro.

The project plan template: after

• Retrospective call — held within one to two weeks of project completion. Reviews what went right and what went wrong across four structured questions.
• Retros are stored in a library; future project plans include a task to review relevant past retros before creating new tasks.
• The retro is required for every project — it is the mechanism that makes future briefs and plans progressively better.

Where this system fits in your business

• On average, small teams spend less than 10–20% of their time on projects; the remaining 80–90% is day-to-day routine work and fixing mistakes.
• These two templates systemise the project slice well, but the bigger time drain — daily operations — requires separate attention.
• Systemising projects is a starting point, not the complete picture.