Peak Command · Playbook · Delegation
Delegating with clear rights
without taking it back.
A playbook for delegating: an outcome instead of a task, a decision level, limits and a check-in. Put together the questions for your next handover here.
What do you want to hand over next, and how far?
2 questions in the plan. First question: How will you know the task is done well?
Four levels of decision rights
Inform. Recommend.
How will you know the task is done well?
Whoever hands over only tasks gets questions back.
Delegation rarely fails for lack of will; it fails on unclear rights: may I decide this? Up to which amount? When should I report? This playbook settles that beforehand. In Peak One, tasks are created in Peak Work, and permissions come from Peak One: each person sees in Peak Command only what they may see in the source product. Blockers from Peak Work appear on Today.
From reading to doing
Your handover questions. For the next task.
The next handover.
2 questions selected
- How will you know the task is done well?
An outcome with a number or a date, not a work step.
- Which decision level do you hand over: 1, 2, 3 or 4?
If in doubt, start at 2 and move to 3 after two good rounds.
What makes a handover
hold.
A clear outcome, an agreed decision level, limits within which nobody has to ask, and a date when you talk.
How will you know the task is done well?
An outcome with a number or a date, not a work step.
Outcome, not task“Delivery time under 10 days” instead of “call three suppliers”.
One level1 inform, 2 recommend, 3 decide and report, 4 decide.
LimitsE.g. up to €5,000 without asking. Above that: a recommendation.
The playbook
Hand over in three steps.
Outcome, frame,
trust.
Outcome → Level → Check-in
- 01
Describe the outcome.
Describe what should hold at the end, not how to get there. The path belongs to the person who takes over.
Example · Nordwind Travel Goods (fictional)
“New supplier by 30 Nov, delivery under 10 days, unit price at most €0.42.”“Take care of a new packaging supplier.” - 02
Agree level and limits.
Settle how far the decision is handed over and where the limits are. Write it down so nobody remembers it differently in three weeks.
Level and limitsLevel 3: decide and report.
Free up to €5,000 annual volume, above that a recommendation to management. - 03
Support, don't take it back.
Use the check-in for obstacles, not for control. When something goes above the limit, a recommendation comes and the decision is recorded. You see blockers in Peak Command on Today as soon as they are in Peak Work.
Check-in after two weeksTwo offers are in, one above the limit.
A recommendation comes, the decision is recorded in Command.
Your quality check
Is your handover clear?
Tick what you have checked. Your selection stays in this view only.
0 of 4 points checked
What this article is based on.
Editorial playbook with a fictional example and made-up numbers. The four levels are a common leadership model, not a Peak feature. Tasks in Peak Work, permissions inherited from Peak One and blockers on Today exist today.
- Evidence pending
Editorial guide with fictional companies and numbers. No customer data, no measured values, no customer results.
See how permissions work in Command.
The permissions and approvals page explains what Command takes over from Peak One.
Frequently asked questions
What should I delegate first?
Recurring decisions with clear criteria. The risk is low and the time saved is large.
How do I keep the overview?
Through fixed checkpoints. In Peak Command you see blockers from Peak Work and capacity from Peak Plan in one place.
Do team members see everything in Peak Command?
No. Peak Command inherits the permissions of the source apps; everyone sees only what they may see there.