Strategic Delivery AI workflow kit: From a quarterly goal to shipped phases.

The ConvOps Strategic Delivery kit gives your AI one chain from strategy to execution: Goal sets a measurable target, Feature turns it into initiatives with plans, Plan writes phases, and Phase executes them. Each level waits for the level below, and you approve the target, every breakdown and every verification.

4 templates · 25 steps · 8 approvals · 5 loops back

kit · 4 workflowsreal steps
  1. 01Goal4 steps · 2 approvals
  2. 02Feature7 steps · 2 approvals
  3. 03Plan10 steps · 3 approvals
  4. 04Phase4 steps · 1 approval

one chip per stored step · square chips wait for an explicit approval

the set

What's in the Strategic Delivery kit?

Four Strategic Delivery templates, installed together, each received by your AI one step at a time.

One tree from a measurable goal through initiatives and plans to executed phases, where nothing above closes before the work below it.

01 · 4 steps · 2 approvals

Goal

The top of the Strategic Delivery tree: a measurable target with a date, active while initiatives run under it.

  1. Capture
  2. Active
  3. Review
  4. Complete
  • Set Q1 revenue targets and track progress to the milestone
  • Define a product-market-fit goal with explicit sign-off on the target
every step of Goal →

02 · 7 steps · 2 approvals

Feature

In Strategic Delivery, each initiative under the goal runs Feature to propose its plans and wait for them.

  1. Capture
  2. Define Plans
  3. Create Plans
  4. Execute Plans
  5. Verify
  6. Capture Learnings
  7. Complete
  • Ship a dark-mode toggle from spec to verified release
  • Add CSV export end to end: capture, build phases, review, verify
every step of Feature →

03 · 10 steps · 3 approvals

Plan

Plan turns one Strategic Delivery initiative item into phase files and one child task per phase.

  1. Analyze
  2. Draft
  3. Prepare Review
  4. Apply Fixes
  5. Review
  6. Create Phases
  7. Ready to Execute
  8. Execute Phases
  9. Verify
  10. Complete
  • Plan a Q2 roadmap from analysis to executed, verified phases
  • Break a database migration into reviewable phases before any run
every step of Plan →

04 · 4 steps · 1 approval

Phase

The bottom of the Strategic Delivery tree, where the work is done and verified one phase at a time.

  1. Ready
  2. Implement
  3. Verify
  4. Complete
  • Implement phase 3 of an auth refactor with verification before close
  • Execute a migration-testing phase from ready state to verified
every step of Phase →

reach for it when

  • For leaders who set quarterly or yearly targets and want each one tied to the work that moves it.
  • Initiatives should be judged by the metric they serve, not only by being finished.
  • Progress is reviewed at the goal level, and the close needs your approval.

something else fits when

  • Kit vs kit: when no goal sits above the work, Project Planning is the lighter set and adds Task for small items.
  • Your goals are tracked elsewhere, and ConvOps only runs the delivery.
  • You run a handful of tasks, not a portfolio of initiatives.
example · healthcare administrationenterprise

Cutting claim processing time across regions

A Goal records the target: median days to process a claim, from twelve to eight by year end. Each region runs a Feature under it, its plans break into phases, and Goal Review reports the number before the close is approved.

Capture and Review gates, Active waits for child work

how it fits

How do the Strategic Delivery workflows connect?

Four levels, one tree. A goal stays active while initiatives sit under it. Each initiative runs the Feature workflow and creates child plans. Each plan creates child phases. Nothing above closes until everything below is completed or cancelled, so a goal marked done means its work is actually done.

FromToHow the work moves
GoalFeatureActive holds the goal while initiatives are linked under it; the step waits for child work and allows an empty start.
FeaturePlanCreate Plans makes one child plan per approved item; Execute Plans waits for all of them.
PlanPhaseEach phase file becomes its own child task in Create Phases, and Execute Phases waits for all of them.

In Strategic Delivery, a parent step that waits on children holds until every child task is completed or cancelled.

where approval is required

Where does the Strategic Delivery kit wait for approval?

The eight Strategic Delivery approval gates, read from the stored workflows; each holds until an explicit approval is given.

TemplateStep with an approval gateIf you reject
GoalCapture step 1no rejection path; approve to continue
Review step 3back to Active
FeatureDefine Plans step 2no rejection path; approve to continue
Verify step 5back to Execute Plans
PlanReview step 5back to Apply Fixes
Ready to Execute step 7no rejection path; approve to continue
Verify step 9back to Execute Phases
PhaseVerify step 3back to Implement
example

What does a week with the Strategic Delivery kit look like?

An illustrative Strategic Delivery run, labelled as an example, using the real Strategic Delivery step names.

  1. 01

    You set a Q1 goal

    Goal Capture records the metric, the timeline and how success is measured. You approve the target.

  2. 02

    Initiatives go under it

    Two Feature runs start under the active goal. Each proposes its plans, and you approve each breakdown.

  3. 03

    Plans run their phases

    Each plan writes phase files, you review, and phase tasks run and verify one by one.

  4. 04

    The quarter review

    Goal Review reports linked work and progress on the metric. You approve the close, or reject to keep it active.

what you need

What do you need to run the Strategic Delivery kit?

make it yours

How do you customize the Strategic Delivery kit?

Once installed, each Strategic Delivery template is a workflow in your workspace; ask your AI to change it in plain words.

Claude Codeexample

new chat

In Goal Review, compare progress with last quarter.
workflow_step_update · Strategic Delivery
Done. Strategic Delivery in your workspace now has the change, and every new run follows it.

more example prompts

  • "In Goal Review, compare progress with last quarter."
  • "Add a Goal Capture rule: every goal names one owner."
  • "In Feature, link each initiative to the goal metric it moves."
questions

Strategic Delivery kit FAQ

What is the ConvOps Strategic Delivery kit?

The ConvOps Strategic Delivery kit gives your AI one chain from strategy to execution: Goal sets a measurable target, Feature turns it into initiatives with plans, Plan writes phases, and Phase executes them. Each level waits for the level below, and you approve the target, every breakdown and every verification.

Can a goal hold work that is not a feature?

Yes. In ConvOps, the Goal template's Active step accepts initiatives for committed bodies of work, which run the Feature workflow, and direct tasks or bugs for standalone items. Types are semantic, so you pick what matches the work. Active waits for that child work and allows an empty start, so you can activate the goal before anything is linked.

How many approvals does a strategic delivery run have, from goal to phases?

In ConvOps, Goal has two approvals (Capture and Review), Feature two (Define Plans and Verify), Plan three (Review, Ready to Execute and Verify) and Phase one per phase at Verify. Each holds its step until an explicit approval is given, recorded with the account that gave it. You can remove any of them as the process matures.

Can I install Strategic Delivery on the Free plan?

Not all of it. The ConvOps Free plan includes 3 workflow templates and Strategic Delivery holds 4 (Goal, Feature, Plan and Phase), so the whole tree from Goal to Phase needs Pro or above. The catalog lists Feature as Goal's dependency and Plan and Phase as Feature's, so every level relies on the one below it.

How does the goal know its work is done?

In ConvOps, each level waits for the level below. Goal Active waits for its child work, Feature's Execute Plans waits until every child plan, task or bug is completed or cancelled, and Plan's Execute Phases does the same for phases. Goal Review then reports linked work and progress toward the measurable outcome before you approve the close.

What happens when a Strategic Delivery goal is not met?

In ConvOps, Goal Review reports the linked work and progress toward the measurable outcome. If the target is not met, a rejected review sends the goal back to Active, where more initiatives or tasks can be linked under it. The goal closes only when its review is approved, so a missed target stays open and visible instead of being marked done.