Frequently Asked Questions About CodeLucky Agile Business Strategy Framework
21 answers covering everything from basics to advanced usage.
// Basics
What does 'maps to compasses' mean?
It's the foundational shift in agile strategy: replacing detailed predictive maps — rigid multi-year plans that assume a predictable landscape — with a compass, a directional tool that keeps you oriented toward your North Star Vision while allowing the path to change as terrain reveals itself. A map tells you every turn in advance; a compass just keeps you pointed right while you adapt to what you actually find.
Is agile strategy just an excuse to have no plan?
No — that's the most dangerous misreading. Agility without a fixed North Star Vision becomes chaos, not speed. Agile strategy is highly disciplined: it fixes the long-term destination as non-negotiable and adds structured feedback loops, predefined checkpoints, and evidence-based persevere-or-pivot decisions. The difference from traditional planning isn't less rigor — it's rigor applied to learning fast instead of predicting far.
What is the feedback loop engine in agile strategy?
The feedback loop engine is a compressed Plan → Do → Check cycle, shortened from years to months or weeks. It's the core mechanism that keeps you relevant: you plan a small experiment, execute it, then check real evidence before committing further. Compressing these cycles is the primary way to stay competitive, because it lets you learn and correct course before mistakes become expensive.
What inputs do I need before starting?
You need four essentials: a description of your current strategy and how decisions are made, a fixed North Star Vision, a list of your 2-5 biggest untested assumptions, and your market's VUCA context. Optionally, document your team structure — who approves what and how autonomous teams are — since that reveals whether alignment or permission-based bottlenecks are slowing you down.
// How To
How do I identify and rank my biggest assumptions?
List every belief your strategy depends on, then rank each on two axes: how much damage being wrong would cause, and how untested the belief currently is. The items scoring high on both become your immediate testing priorities. Focus your Minimum Viable Strategy on the top two or three. Never build elaborate plans on top of unvalidated assumptions.
How do I run a feedback loop checkpoint properly?
Bring actual market evidence to the table — not opinions. Frame one binary question: does the data support continuing this path, or does it show the path is wrong? Predefine what data you'll collect, who reviews it, and the checkpoint format before the cycle begins. Keep it short enough that the market can't materially shift before you review. End every checkpoint with an explicit persevere or pivot decision.
How do I embed alignment across teams?
Distill your North Star Vision into a single-sentence strategic intent and distribute it, then define clear decision boundaries — what can a team ship without approval? Test alignment by asking whether any team member could make a daily decision consistent with the intent without escalating. Audit whether decisions are still bottlenecked; if they are, your alignment is insufficient. A shared document alone is never enough.
How do I write a good North Star Vision?
Write a single, concrete long-term goal that stays fixed regardless of market turbulence. Validate it with one question: 'Would we still want this outcome even if the path to get there changed entirely?' If yes, it's a true North Star. Avoid making it a specific tactic or route — those must stay flexible. Keep it directional and enduring, not a quarterly target.
// Troubleshooting
My feedback loops keep slipping to annual reviews — how do I fix this?
Annual reviews are a classic pitfall: by the time you check, VUCA has already invalidated your assumptions. Fix it by choosing a cycle length matched to your market speed and enforcing it as a recurring rhythm, not a milestone. Predefine the checkpoint date, data set, and reviewers in advance. Treat the loop like a heartbeat — the next iteration begins immediately after each persevere-or-pivot decision.
My team treats every pivot as a failure — what should I do?
Reframe it. The framework explicitly treats pivoting as the feedback loop working correctly, not as failure. Stigmatizing pivots kills honest data review because people hide bad news to avoid blame. Publicly celebrate a clean, evidence-based pivot as a competitive superpower. When announcing one, restate the unchanged North Star Vision so the team sees the destination is intact and only the route changed.
My Minimum Viable Strategy took months to design — what went wrong?
If it took months, it isn't minimum viable — you over-engineered it. The whole point is lightweight and fast. You likely tried to predict too many variables instead of targeting one big assumption. Restart by asking: 'What is the smallest action that would tell us if our single biggest assumption is true?' Strip everything that doesn't directly generate that evidence.
We distributed the strategy document but decisions are still bottlenecked — why?
You achieved plan alignment without strategic-intent alignment. Distributing a document is not the same as ensuring every team member can make autonomous decisions consistent with the North Star Vision. Fix it by distilling the strategy into a memorable single-sentence intent, defining explicit decision boundaries, and testing whether people can explain why an action serves the North Star without escalating. Alignment is behavioral, not documentary.
// Comparisons
How does agile strategy compare to OKRs?
They're complementary, not competing. OKRs are a goal-setting and measurement structure; agile strategy is the surrounding operating rhythm that decides which goals to pursue and when to change them. Agile strategy's feedback loops can drive how often you revisit OKRs, and its persevere-or-pivot logic decides whether an objective survives. OKRs measure progress; agile strategy governs whether the direction itself is still right.
How is agile strategy different from lean startup?
They share DNA — the Minimum Viable Strategy borrows directly from lean's Minimum Viable Product, and both prioritize testing assumptions with evidence. The difference is scope: lean startup focuses on validating a product or business model, while agile strategy applies the same learn-fast logic to whole-organization direction, adding the North Star Vision, VUCA mapping, and cross-team alignment layer that lean doesn't formally address.
When is traditional waterfall planning actually better than agile strategy?
Waterfall wins in genuinely predictable, low-VUCA environments — building a bridge, executing a known regulatory compliance rollout, or projects where requirements are stable and the cost of change mid-execution is enormous. In those cases, exhaustive upfront planning reduces risk. Agile strategy's advantage only appears when volatility, uncertainty, complexity, or ambiguity make detailed long-range prediction unreliable, which describes most modern markets.
How does this framework compare to just 'being flexible'?
Vague flexibility has no fixed destination, no structured checkpoints, and no evidence standard — it drifts. This framework adds discipline: a non-negotiable North Star Vision anchors direction, feedback loops enforce regular review, ranked assumptions focus testing, and persevere-or-pivot decisions demand actual data. The result is fast adaptation with clear intent, not reactive improvisation that chases every new signal.
// Advanced
How do I choose the right feedback loop cycle length for my market?
Match the cycle to how fast your market materially shifts, and never exceed that window. Fast-moving consumer tech might warrant weekly or bi-weekly loops; a slower B2B enterprise segment might work at monthly or quarterly. When unsure, err shorter — a cycle that's too short costs some overhead, but one that's too long lets invalidated assumptions compound. Reassess cycle length itself as your market volatility changes.
How do I keep the North Star fixed without becoming rigid about tactics?
Draw a hard line between destination and route. The North Star Vision — the outcome — is non-negotiable; everything below it, including markets, products, and methods, is a flexible path. At each pivot, explicitly restate the unchanged North Star while changing the route. If you find yourself changing the destination at every pivot, that's drift, not agility. The separation is what prevents both rudderlessness and rigidity.
Can agile strategy work in a large, hierarchical organization?
Yes, but the alignment principle becomes the hardest and most critical part. Large hierarchies default to permission-based decision chains that kill speed. Success requires distilling strategic intent into language any employee can act on, explicitly defining decision boundaries at each level, and auditing for bottlenecks. Shorter feedback loops at the team level let learning propagate faster than a top-down approval structure allows.
What's the difference between a pivot and drift?
A pivot changes the route while keeping the North Star Vision fixed, and it's driven by evidence at a feedback loop checkpoint. Drift is changing the destination itself — abandoning the long-term outcome whenever new information appears. Pivots are disciplined and directional; drift is reactive and rudderless. The test: after the change, does your North Star still hold? If it moved too, you drifted.
How do I use VUCA mapping without overanalyzing?
For each VUCA factor — Volatility, Uncertainty, Complexity, Ambiguity — identify just the one or two most threatening current manifestations in your specific market. Don't catalog every possible risk; the goal is to make disruption feel expected, not to build an exhaustive threat register. This lightweight map feeds directly into which assumptions you prioritize testing, keeping the exercise practical rather than academic.