Knacklore

← All decks

Cover of Operations & Process Patterns

Operations & Process Patterns

Make recurring work run smoothly across teams.

Methods for making recurring work run smoothly in any team or function, for operations leads, managers and anyone who owns a process. The cards help you map the process as it really runs, find waste and bottlenecks, keep work flowing across handoffs, write procedures people use, run internal services with clear levels, choose what to automate and improve in small, steady cycles.

56 cards · 7 suits · 5 recipes · 2 missions

What's inside

A few cards

Illustration for Process Inventory
See The Work

Process Inventory

Write down every recurring process you run before you try to fix any of them.

Illustration for Eight Wastes
Find The Waste

Eight Wastes

Walk each step with eight kinds of waste in mind and name what you find.

Illustration for Write The SOP
Write It Down

Write The SOP

Write the best way you know as trigger, steps, owner and done, in words a newcomer can follow.

One card in full

Illustration for Automation Shortlist
Automate Wisely

Automation Shortlist

Score each manual task on a few factors and automate from the top of the list.

Teams usually automate whatever annoyed someone most recently, not what would save the most. A simple scoring sheet compares tasks on the same terms, so the first automation you build is one that pays back and keeps working.

How to use it

  1. List repetitive manual tasks, from your Process Inventory or a week of people noting what they repeat.
  2. Score each from 1 to 5 on four factors: how often it runs, how long it takes each time, how error-prone it is by hand, and how stable the steps are.
  3. Multiply or add the scores, and sort.
  4. Strike out any task whose steps change every month. Those are not ready.
  5. Take the top one or two into a closer look before building anything.

Example

A hypothetical school office scores twelve tasks. Weekly attendance letters score highest: frequent, slow, error-prone and the same every week. Timetable changes score high on time but low on stability, so they wait.

Watch out

  • Skipping the stability score. Automating a moving target means rebuilding it every month.
  • Counting only time. Error-prone tasks often matter more than slow ones.

Before building, simplify with Fix Before You Automate and test the sums with a Payback Check.

Recipes

Missions

Related decks

Security Awareness Patterns

Spot the scam and report it fast.

63 cards

Contingency Planning Patterns

Keep running when a person, site or system fails.

49 cards

Product & Roadmaps Patterns

Go from raw request to features people use.

56 cards

← All decks