Operating Cadence
Part of Startup planning and execution
Writing an owner and outcome for each initiative
Write a compact initiative record that names its owner, intended outcome, evidence, dependencies and decision boundary.
For each initiative, name one person responsible for moving it towards a stated result. The owner coordinates the work and raises decisions.
Write the outcome as a change someone could observe, then say how and when the team will check it. The outcome tells the team why the work matters.
Write the outcome before the task list
Begin with the problem the initiative is meant to address. Describe who or what should be better off if it succeeds. “Create a new intake form” is a deliverable. “Delivery staff have the agreed customer requirements before starting work” describes the intended change; the form may be one way to pursue it.
Add an observation the team can obtain. It might be a count from an existing work record, a check of a sample of completed handovers, or feedback from the people receiving the work. State the source and the period.
If there is no reliable starting figure, record that gap and gather a baseline before claiming improvement. A completed deliverable can be checked sooner than a business outcome, so keep both milestones visible.
Avoid promising that the initiative alone will cause a result affected by sales mix, staffing or other changes. The outcome is what the team is trying to influence. At review, consider whether the work appears to help and whether another explanation needs attention.
Key Metrics for Tracking Initiative Success
- Evidence source
- Internal delivery logs and sample handover reviews
- Review frequency
- Bi-weekly until target achieved
Give the owner a usable mandate
The initiative owner should know what they can decide, whose contribution they need and what must come back for approval. One person can own progress even when several people do the work. Name a specific person or role rather than “the team”. Check that the owner has time to coordinate the work and access to the information needed to report progress.
This is an initiative assignment, not a rewrite of everyone’s standing responsibilities. For example, a delivery lead may own the intake improvement while a sales colleague supplies information and an authorised founder approves any change to customer promises. If the owner cannot secure an essential decision, state who can make it and when the question should be raised.
Use a compact initiative record
A workable record can fit on one page:
Field / Write this
- Intended outcome
- The observable change sought and who benefits
- Evidence
- Source, current position if known, and the next check
- Owner
- Person accountable for moving the initiative and raising decisions
- First deliverable
- The next tangible piece of work, with its reviewer
- Dependencies
- People, approvals or inputs needed before progress is possible
- Decision boundary
- What the owner may change and what needs approval
- Review point
- When the team will continue, adjust, pause or stop
For a hypothetical customer handover initiative, the first deliverable might be a draft intake record reviewed by sales and delivery. The outcome would be that the delivery team receives the agreed scope before work begins. The team would inspect actual handovers before saying whether the change occurred; producing the draft alone would not establish it.
Check whether the wording can guide work
Ask the owner and one contributor to read the record. Can they identify the next action? Do they agree on what would count as progress? Would they know when to ask for a decision?
If the answer is unclear, revise the outcome or boundary before adding more tasks.
At review time, separate three statements: what was delivered, what changed, and what is still uncertain. If the deliverable is complete but the intended change is absent, the owner can propose a different approach. If the evidence cannot yet show a change, record what will be checked next rather than marking the initiative successful by default.
