Flowgrammer

90-Day Automation Operating Plan

A reusable backlog and review plan for automation opportunities, owners, baselines, human decisions, risks, and next actions.

Download the operating plan (PDF)

This template turns a collection of automation ideas into a short operating plan with owners, baselines, human-control points, and decisions.

How to use it

  1. Add one row for each workflow that is creating measurable friction.
  2. Name the business owner and the person who will own the system after launch.
  3. Record the baseline before choosing a tool.
  4. Write down what people must continue to decide.
  5. Review the backlog every 30 days and make one decision: expand, revise, stop, or investigate.

Opportunity backlog

Opportunity Business owner System owner Baseline metric Target metric Human decision or exception Risk Next decision

30-day discovery checklist

  • Current workflow mapped from trigger to outcome.
  • Inputs, systems, handoffs, and delays recorded.
  • Exceptions and sensitive decisions identified.
  • Baseline metric chosen and owner assigned.
  • Candidate first system ranked against impact and feasibility.

60-day design checklist

  • First release has a narrow scope.
  • Data and permissions are documented.
  • Human review and escalation paths are explicit.
  • Normal, incomplete, conflicting, and failure test cases exist.
  • Acceptance criteria are agreed with the business owner.

90-day launch checklist

  • Real cases tested before production use.
  • Users trained on the normal and exception paths.
  • Manual fallback or rollback path documented.
  • Baseline and post-launch measure compared.
  • Next decision recorded: expand, revise, stop, or investigate.

Review questions

  • Did the system change the metric we cared about?
  • Which cases still need a person?
  • What surprised the team?
  • What should we stop automating?
  • What is the next smallest useful improvement?

The plan supports the Fractional CAO engagement. If an opportunity is not clear enough to put into the table, record the missing information and book a fit call to discuss it.

Fill the first row from an actual operating decision

The three-page PDF includes a backlog with fields for opportunity, business owner, system owner, baseline metric, target metric, human decision or exception, risk and next decision. Start with one opportunity and give the two ownership fields real names or accountable roles. The person responsible for the business result may differ from the person maintaining the integration.

For a fictional enquiry-routing pilot, the baseline could be the proportion of valid enquiries without an owner after one business day. Write a target the team has agreed to test, then identify the exception that requires a person. Keep estimates labelled until measured; entering a target does not make it a forecast.

Review decisions at each planning interval

Use the next-decision field to say what evidence is needed and who will decide whether to continue, narrow or stop the work. Review access, unresolved exceptions and the baseline before scheduling another build. A 90-day plan is a sequence of decisions, not a promise that every listed system will launch within the period.

Keep the backlog as a working register and update it when evidence changes. If you need help comparing several opportunities first, use the portfolio workbook and roadmap course before committing capacity.

Book a fit call