A workflow is one of the eight business functions that a change has to work through: Sales, Marketing, Product, Engineering, Strategy, Operations, Finance and Legal. A workflow record describes how one of those functions will work differently because of a bet. Workflows is the second block in Lead, and a function can also hold internal hunches, read with its own KPI.
For example, the team bets that the points progress bar will drive rewards adoption. For that to land, Marketing has to add the progress bar to onboarding emails. That change in how Marketing works is a workflow record.
Why it matters
A design change rarely stays inside design. When nobody maps which functions it touches, the launch stalls: Marketing wasn't told, Finance didn't budget for it, Legal sees it a week before release. The change is good, but the business isn't ready to carry it.
Naming each affected workflow makes the real cost of a bet visible. It shows who holds influence in each function, how that function sets budgets and priorities, and how it measures its own performance. That is what lets a design decision earn support across the business.
For every bet, name each function that has to change, describe the change in plain words, and confirm it with someone who leads that function.
How we write one
Every workflow record is written as one sentence that names the function and how it changes:
A function changes how it works.
Marketing adds the progress bar to onboarding emails.
Writing it this way keeps each record to one function and one concrete change, so the owner of that function can see exactly what is being asked of them.
How it differs from similar ideas
-
A bet is the commitment to a change. A workflow record describes how one function changes because of that bet, and one bet can affect several workflows.
-
An audience is who the evidence comes from, such as Stakeholders. A workflow is a function of the business that has to act differently.
-
A business goal is what the change is weighed against. A workflow is part of how the business gets there.
-
A constraint is a fixed limit on concepts. A workflow may impose constraints, but the record itself describes a change in how a function works.
A good workflow record
-
Names one of the eight functions
-
Describes one concrete change in how it works
-
Links to the bet that causes the change
-
Names who holds influence in that function
-
Says how that function will measure the change
-
Is confirmed by someone who leads the function
What happens to it
-
Identified. A bet names the function, or Ray infers it from a launch plan or memo.
-
Confirmed. Someone who leads that function agrees to the change and its cost.
-
Changing. The function is adopting the new way of working.
-
Delivered. The change is in place and flows through Mapping into Results.
-
Reverted or retired. If the bet is reversed, the function goes back, and the record is kept for history.
For Ray
This part tells Ray how to find a workflow change in an input, such as a launch plan, a RACI chart, a budget request, a cross-team email or an operating review, and how to store it.
How to find one
-
Mark statements about functions changing. Read the input and mark every statement where a team or department has to do something differently because of a change.
-
Name the function. Match it to one of the eight workflows: Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal. If it fits none, flag it.
-
Find the change. Pull out what the function will do differently, in one concrete action.
-
Find the bet. Identify the bet that causes the change. If none exists yet, leave it blank and flag it.
-
Find influence and priorities. Note who holds influence in that function and how it sets budgets and priorities, if stated.
-
Find how it's measured. Note how that function judges its own performance, such as conversion, cost or cycle time.
-
Write the sentence. Use the format: [Function] [changes how it works].
-
Fill the record, score it, link it and store it using the rules below.
Cues to look for
-
Ownership language: "Marketing will", "Finance needs to", "Legal has to sign off", "Ops owns"
-
RACI charts and launch checklists that assign tasks to teams
-
Budget requests or headcount changes tied to a launch
-
Changes to a team's own measures: "email open rate now includes rewards clicks"
What doesn't count
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>If the statement...</p></th><th colspan="1" rowspan="1"><p>Store it as</p></th></tr><tr><td colspan="1" rowspan="1"><p>Commits to the overall change, with a goal and metric</p></td><td colspan="1" rowspan="1"><p>Bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Describes who evidence came from</p></td><td colspan="1" rowspan="1"><p>Audience</p></td></tr><tr><td colspan="1" rowspan="1"><p>Sets a fixed limit on what concepts can do</p></td><td colspan="1" rowspan="1"><p>Constraint</p></td></tr><tr><td colspan="1" rowspan="1"><p>Is a task inside one team that doesn't change how it works</p></td><td colspan="1" rowspan="1"><p>Leave it out, or note it on the existing workflow record</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reports a measured change after launch</p></td><td colspan="1" rowspan="1"><p>Business Outcome or Result</p></td></tr></tbody></table>
The record
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What to fill in</p></th><th colspan="1" rowspan="1"><p>Values</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>The one-sentence workflow change</p></td><td colspan="1" rowspan="1"><p>[Function] [changes how it works].</p></td></tr><tr><td colspan="1" rowspan="1"><p>Function</p></td><td colspan="1" rowspan="1"><p>Which of the eight it is</p></td><td colspan="1" rowspan="1"><p>Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal</p></td></tr><tr><td colspan="1" rowspan="1"><p>Change</p></td><td colspan="1" rowspan="1"><p>What the function will do differently</p></td><td colspan="1" rowspan="1"><p>Short text</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bet</p></td><td colspan="1" rowspan="1"><p>The bet that causes the change</p></td><td colspan="1" rowspan="1"><p>Link to Bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Influence</p></td><td colspan="1" rowspan="1"><p>Who holds sway in this function</p></td><td colspan="1" rowspan="1"><p>Names or roles</p></td></tr><tr><td colspan="1" rowspan="1"><p>Budget and priorities</p></td><td colspan="1" rowspan="1"><p>How this function sets them, and what the change costs</p></td><td colspan="1" rowspan="1"><p>Short text, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Performance measure</p></td><td colspan="1" rowspan="1"><p>How this function judges its own work</p></td><td colspan="1" rowspan="1"><p>Short text, with link to KPI if known</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confirmed by</p></td><td colspan="1" rowspan="1"><p>The function leader who agreed to it</p></td><td colspan="1" rowspan="1"><p>Name or role, or blank</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>The input and exact passage, row or message</p></td><td colspan="1" rowspan="1"><p>Link to Input</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Where it stands</p></td><td colspan="1" rowspan="1"><p>Identified, Confirmed, Changing, Delivered, Reverted, Retired</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>How clearly it was stated</p></td><td colspan="1" rowspan="1"><p>High, medium, low</p></td></tr></tbody></table>
New records start as Identified. Only someone who leads that function can move one to Confirmed.
Scoring confidence
Confidence measures how clearly the change was stated and by whom, not how big the change is.
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Level</p></th><th colspan="1" rowspan="1"><p>When to use it</p></th></tr><tr><td colspan="1" rowspan="1"><p>High</p></td><td colspan="1" rowspan="1"><p>Stated in writing by someone in that function, with a concrete change tied to a bet</p></td></tr><tr><td colspan="1" rowspan="1"><p>Medium</p></td><td colspan="1" rowspan="1"><p>The function and change are clear, but the bet, influence or measure is missing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Low</p></td><td colspan="1" rowspan="1"><p>Inferred from a bet or plan without anyone from the function saying so</p></td></tr></tbody></table>
If any part of the record can't be filled from the source, leave it blank and lower confidence by one level.
Linking
-
Check for duplicates first. If an existing record describes the same change in the same function for the same bet, add the new source to it instead of creating another.
-
Link to the bet that causes it and its source input.
-
Link to the business goal the bet serves, since the goal is weighed through workflows.
-
Link to results once the change is delivered through Mapping.
-
Note conflicts. If two bets ask the same function for changes that compete for budget or people, link the records as conflicting.
When to store and when to ask
-
Store automatically when confidence is high.
-
Add to the review digest when confidence is medium or low, when it has no bet, when the function doesn't match the eight, or when it conflicts with another workflow change.
When to flag
-
A workflow change has no bet behind it
-
A bet is Live but an affected workflow is still Identified, not Confirmed
-
Two workflow changes compete for the same budget or people
-
A workflow change has no performance measure for that function
-
A function is named that doesn't fit any of the eight workflows
Worked example
Input: an email from the Marketing lead to the product team after the steering committee.
"We'll add the progress bar to the day 3 and day 10 onboarding emails starting in Q2. I'll need to move budget from the travel campaign to cover design time. We'll track it through rewards click-through on those emails."
What Ray finds:
-
The writer leads Marketing, so the function is Marketing and the record can be confirmed.
-
"Add the progress bar to the day 3 and day 10 onboarding emails" is the change.
-
"Move budget from the travel campaign" shows how priorities and budget shift.
-
"Rewards click-through on those emails" is how Marketing will measure it.
Stored record:
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>Value</p></th></tr><tr><td colspan="1" rowspan="1"><p>Statement</p></td><td colspan="1" rowspan="1"><p>Marketing adds the progress bar to onboarding emails.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Function</p></td><td colspan="1" rowspan="1"><p>Marketing</p></td></tr><tr><td colspan="1" rowspan="1"><p>Change</p></td><td colspan="1" rowspan="1"><p>Progress bar added to day 3 and day 10 onboarding emails from Q2</p></td></tr><tr><td colspan="1" rowspan="1"><p>Bet</p></td><td colspan="1" rowspan="1"><p>We bet the progress bar will move Drive adoption, affecting Product and Marketing; measured by rewards redemptions.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Influence</p></td><td colspan="1" rowspan="1"><p>Marketing lead</p></td></tr><tr><td colspan="1" rowspan="1"><p>Budget and priorities</p></td><td colspan="1" rowspan="1"><p>Budget moved from the travel campaign to cover design time</p></td></tr><tr><td colspan="1" rowspan="1"><p>Performance measure</p></td><td colspan="1" rowspan="1"><p>Rewards click-through on onboarding emails</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confirmed by</p></td><td colspan="1" rowspan="1"><p>Marketing lead</p></td></tr><tr><td colspan="1" rowspan="1"><p>Source</p></td><td colspan="1" rowspan="1"><p>Email to product team, December 2026</p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p>Confirmed</p></td></tr><tr><td colspan="1" rowspan="1"><p>Confidence</p></td><td colspan="1" rowspan="1"><p>High: written by the function leader with a concrete change tied to a bet</p></td></tr></tbody></table>
Next step: stored automatically and linked to the bet; the travel campaign budget shift is noted for Finance.
Edge cases
-
One team, many functions. A growth team may span Product and Marketing. Store one record per function, so each leader can confirm their part.
-
Function outside the eight. "Customer service" usually fits Operations. Map it to the closest of the eight and note the original name.
-
No bet yet. A team plans a change before a bet exists. Store the record with Bet blank, lower confidence, and flag it.
-
Bet reversed. Mark each linked workflow Reverted and prompt the function leader to confirm they have rolled back.