When the goal is to explore strategy, test hypotheses, or navigate ambiguity, you need a different mindset—**Frame–Learn–Assess–Improve** (FLAI). Here’s why a small shift in language can reshape the way we lead.
Why Language Matters
Sometimes, a small change in language can significantly shift how something is perceived. You're not 'slow and steady'—you're 'deliberately paced.' You didn't 'change your mind'—you 'reassessed based on new data.' You're not 'multitasking,' you're 'operating asynchronously.' And in agile, saying 'we're learning in cycles' feels a lot more constructive than 'we're reworking our mistakes.'
Plan–Do–Inspect–Adapt: Built for Execution
The cycle of **Plan–Do–Inspect–Adapt (PDIA)** lies at the heart of agility. Modeled loosely on Lean’s Plan–Do–Check–Act, PDIA reflects the core of Scrum, which is grounded in transparency, inspection, and adaptation. Teams plan a short increment of work, execute it, inspect the outcome, and adapt based on what they learn. This approach is action-oriented and especially effective for **developing the right products** in complex environments. It promotes short feedback loops, continuous learning, and incremental delivery.
Frame–Learn–Assess–Improve: Designed for Exploration
But what if you're not building a product? What if you're exploring a strategy, shaping a policy, or testing the viability of an idea? In these cases, a slight shift in language—and therefore mindset—can make a big difference. Consider **Frame–Learn–Assess–Improve (FLAI)**. At first glance, it resembles PDIA, but each word invites a more exploratory and strategic type of work.
Breaking Down the FLAI Cycle
Instead of '**Plan**,' we say '**Frame**'—a term that feels less rigid. It allows us to define boundaries and assumptions without pretending we already have all the answers. '**Do**' becomes '**Learn**,' shifting the focus from execution to exploration, experimentation, and inquiry. Here, progress isn’t always a deliverable—it’s often a new insight. '**Inspect**' becomes '**Assess**,' inviting us to reflect not just on what was done, but on patterns, context, and emerging understanding. Finally, '**Adapt**' becomes '**Improve**,' emphasizing purposeful, directional change—not just reaction, but intentional progress.
Choosing the Right Cycle for the Work
These aren’t just word substitutions. Language shapes behavior, expectations, and mindset. The FLAI cycle reframes work for **idea development** rather than feature delivery. It's particularly suited for ambiguous or abstract work—like creating a data governance model, piloting AI use cases, or leading strategic transformation.
Guidance for Leaders
This isn’t about which cycle is better. It’s about understanding that **context matters**. **Plan–Do–Inspect–Adapt** helps you execute. **Frame–Learn–Assess–Improve** helps you explore. Agile organizations need both. The wisdom lies in knowing when to use which.
- Use **Plan–Do–Inspect–Adapt** when building, validating, and refining tangible outputs.
- Use **Frame–Learn–Assess–Improve** when exploring strategy, forming hypotheses, or navigating uncertainty.
By matching the feedback loop to the nature of the work, organizations can think more clearly, act more effectively, and scale agility well beyond delivery teams.