What Is the FLOW Framework?
Four moves that turn a contested AI decision into a written outcome with a walkaway condition attached.
The FLOW framework is a four-step decision sequence (Facts over feelings, Listen to understand, Open to new ideas, Walkaway when necessary) for resolving contested AI governance questions when evidence is partial and pressure to commit is high.
FLOW is one of four named frameworks in Jacqueline V. Twillie's body of work, alongside L.A.T.T.E., A.H.A., and R4. Where A.H.A. addresses individual career pressure and L.A.T.T.E. prepares a negotiation, FLOW governs the decision itself: which AI initiative gets funded, which gets a pilot, and which ends this quarter.
What does each step do?
Facts over feelings. Every proposed initiative arrives with three things before discussion: what it replaces, who currently does that work, and what result would prove it worked. If the initiative can't answer the first two, it's a capability someone wants, not a workflow anyone runs.
Listen to understand. State the strongest objection in the objector's own words before answering it. The operations lead describing an exception rate, the compliance officer asking about reversibility, the quiet question about headcount: each carries a fact the roadmap needs and does not have.
Open to new ideas. Re-examine build-versus-buy at every planning cycle rather than inheriting last year's answer. Let the people doing the work propose the initiatives. Openness governs how the work gets done. The operating rules stay fixed.
Walkaway when necessary. Set the end condition before the pilot starts, in writing: a result that must appear by a named date, a cost ceiling where upkeep exceeds the manual process, or a rule condition that ends any initiative requiring suspension of an operating rule. A decision framework without a walkaway is a justification framework.
How BNEDai defines this differently
Most AI decision frameworks score maturity, telling a team where it currently sits on a continuum. FLOW produces a decision instead: one page per initiative, with a stated reason for being on the roadmap and a stated condition for leaving it.
A maturity score can be presented without action. A FLOW outcome has a walkaway condition with a date and an owner attached. Someone is accountable for checking whether the condition was met.
The full application of FLOW to an AI technology roadmap is covered in AI leadership frameworks. FLOW sits within the broader discipline of AI governance, which covers the operating rules a team writes before deploying any agent.
Frequently asked questions
What does FLOW stand for?
Facts over feelings, Listen to understand, Open to new ideas, Walkaway when necessary. It is a four-step decision sequence from Jacqueline V. Twillie, one of four named frameworks in her leadership and governance work.
How is FLOW different from an AI maturity model?
A maturity model tells a team where it currently sits. FLOW decides what to do next: a written outcome per initiative with a walkaway condition and a named owner.
When should a team use FLOW?
When the decision is contested, the evidence is incomplete, and the pressure to commit is high. Most AI roadmap decisions fit that description. FLOW runs in a single session on one initiative at a time.
What is a walkaway condition?
A written rule for when the initiative ends, set before the pilot starts. Three forms: a result condition naming a specific outcome by a date, a cost condition marking where upkeep exceeds the manual process, or a rule condition ending anything that requires suspending an operating rule.
Build something that actually runs your workflow.
A focused, free 60-minute live session with Jacqueline. You build alongside her, on your own real task, and leave with an agent that is already running.