← Back to News & Updates

NovaQTech Insights

The Emergent Strategy Model by NovaQTech: Strategy from Two Headwaters

November 1, 2026

Most strategy processes assume strategy is made in a planning cycle: analyse, decide, cascade, control. The document is approved, the budgets are attached, and the organization sets off to execute.

Then real life starts. A major customer collapses. A regulation changes the market. A local team finds a way of working that outperforms the official process. A decision that cannot wait until next year’s planning round is taken in a corridor, in a crisis meeting, in a week when events move faster than the calendar. Months later, if you list the strategies the organization is actually pursuing, a large share of them were never in the plan at all.

The Emergent Strategy Model by NovaQTech starts from that reality. It does not treat the plan as the strategy, and it does not treat what emerges as a failure of discipline. It runs both, openly, as one system — and it keeps the evidence to prove it is doing so.

Why plan-only strategy fails

The calendar model of strategy, in which an annual cycle of analysis produces the strategy, fails in recognizable ways:

• Expiry. The plan expires before it starts. A planning cycle takes months; the environment does not wait. By approval day, the document describes a world that has already moved, and the organization executes against the description instead of the world.
• Deferral. Analysis becomes a respectable way to defer. When the cycle owns the decision, every hard question can be answered with more study, scheduled for next year’s round. The issues that matter most rarely arrive on the calendar’s schedule.
• Escalation. A published plan defends itself. Once positions, budgets and reputations are attached to it, evidence against the plan is treated as disloyalty, and commitment escalates precisely when it should be re-examined.
• Ownership. The people who must carry the strategy did not make it. A specialist process produces a document that operating units receive as instructions. Compliance is the best outcome available; ownership is not.
• No route for surprise. The unexpected has no route in. Yet the unexpected — a customer’s collapse, a regulation, a local practice that outperforms the official one — is where real strategy most often comes from. A calendar system treats its richest source as an exception.

None of this is an argument against planning. It is an argument against the calendar as the only source of strategy.

The founding doctrine: two headwaters

The model’s founding claim is that strategy flows from two headwaters, and an organization running only one of them is working with half a strategy process.

The first is the lived stream: strategy arising continuously out of the organization’s real life — its intent and identity, the evidence about itself and its environment, the issues that force themselves onto its agenda, and the experiments and local successes inside its own operations.

The second is the planned stream: strategy set deliberately, in advance, on three horizons — a long-term direction, medium-term programmes, and short-term commitments.

The lived stream normally carries the larger share of an organization’s strategy, because most of what an organization must respond to, and most of what it can discover, arrives through its life rather than through its planning round.

The two streams do not outrank each other. They correct each other, through two standing movements:

• Re-opening. When evidence contradicts an assumption a plan entry rests on, the entry is re-opened and revised on the record, with its original text preserved.
• Graduation. When a lived strategy proves itself, it is written into the medium-term plan at the horizon review, gaining the plan’s protection, budget line and horizon.

Both streams flow into one portfolio, where every admitted strategy carries an origin tag: Lived, Planned, or Blended, for a strategy born in one stream and materially reshaped by the other before admission. One portfolio, one set of admission checks, one deployment route, whichever stream a strategy was born in.

The five functions of the lived stream

The lived stream is operated by five functions. Four of them produce strategy candidates; the fifth integrates them, together with the planned stream’s candidates, into the portfolio. They are not a sequence and they are not departments. They run continuously and in parallel, each on its own rhythm, and a strategy can be born in any of them: a reframed identity in Perspective, a failed assumption in Intelligence, a crisis on the Agenda, a pilot that works in Ventures.

Perspective holds what the organization intends and believes about itself. Two disciplines keep it honest. First, the distinction between the stated perspective and the revealed one: the function judges the perspective by what the organization’s decisions actually protect and fund, not by what the wall says, and records the divergence when the two part. Second, the assumption set: every element of the perspective rests on assumptions about the world, and Perspective names them explicitly and hands them to Intelligence to be tested. A perspective whose assumptions are unnamed cannot be evaluated; it can only be believed. Perspective also holds the key questions, the four to six questions the organization cannot yet answer but must keep answering, each with a named owner.

Intelligence is the evidence function. Its standing discipline is the awareness threshold: analysis continues while it is still capable of changing a decision, and stops at the point where more study would only delay one. Analysis that never ends in a decision, or in a recorded decision not to decide, has failed however thorough it is. Its main instrument is the strategy health check, described below.

Agenda turns what the organization notices into timely decisions. Its intake is open: any person in the organization can raise a strategic issue through a known route, and every issue raised is answered — decided, referred, or closed with a reason. Triage is fast by design: new issues are triaged within two working days against strategic weight, urgency, and evidence readiness. The function’s product is the decision record: the question, the evidence, the options considered, the decision, the conditions that would cause it to be revisited, and an owned review date. A decision without a revisit condition and a review date is a decision the organization has agreed never to reconsider, and in this model that is a defect, not a virtue. Agenda is measured by its latency: a function that decides brilliantly but late is failing at its one essential job.

Ventures works in two movements. The first is testing: strategic ideas are put into practice as bounded experiments whose outcome is honestly unknown. The function’s law is that verdicts are earned by criteria set before the experiment starts: every experiment records its hypothesis, its scope, and the measurable conditions for scale, for kill, and for one extension, before it spends anything. Criteria are never re-set mid-experiment. A killed experiment whose learning is recorded is a success of this function; an experiment that cannot be killed by its own criteria is not an experiment at all, but a project in costume. The second movement is finding: the organization’s own successful local practices are actively looked for, tested for whether they generalize beyond one person’s gift or one customer’s peculiarity, and promoted when they do.

Allocation is the integrator. It collects candidates continuously and unfiltered, from all four producing functions and from the planned stream, and every candidate carries its origin on the record. Before decision, each candidate passes three checks.

• Resources: what it needs, against what the organization can actually commit — a candidate that fails is staged, shrunk to fit, or held with the gap stated, but never admitted unfunded.
• Interests: whose interests the candidate serves and engages, because a strategy whose carriers gain nothing from it will be carried at half strength.
• Horizon: consistency with the perspective and the long-term picture.

Decisions are made on the record in one of five forms — admit (fund in full), stage (fund to a dated gate), hold (named reason, named review trigger), reject (reason recorded), or exit (for current items that have run their course) — and every decision carries its reasons in one or two sentences. A decision whose reasons cannot be written down has not been taken; it has been drifted into. Admitted strategies pass to deployment within days, not at the next planning round.

The planned stream, run as a living discipline

In this model, planning is not abolished. It is demoted from the whole river to one headwater of two, and held to a stricter standard than the calendar model ever applies. A plan direction must be capable of failing its own tests. Entries carry their assumptions by name. Standing triggers can convene the horizon review early, outside the recorded cycle. And when the health check contradicts an assumption beneath a plan entry, the entry returns to the portfolio with its original text and the contradicting evidence, and is revised, re-staged or exited on the record. A plan entry in this model is a living entry precisely because that bridge exists.

Keeping the system honest

Emergence without discipline is drift. The model’s discipline has three layers.

The strategy health check is run by Intelligence on a recorded rhythm, and immediately whenever an assumption fails. It combines three checks, and the order of the verdict matters:

• Assumptions. Are the assumptions the current strategy rests on still valid? Each named assumption is scored for validity. An assumption that is foundational, the strategy collapses without it, and scores at the bottom of the scale fails the strategy’s foundations, whatever the results say.
• Change. What has changed, inside and outside, and how much does it matter? Change is sensed across eight domains: laws and regulations, higher-level policies, stakeholders, economic conditions, political conditions, environmental conditions, social and cultural conditions, and internal capabilities. Every material change is routed — to a timely decision, to the portfolio review, or to the watch list. The discipline is the routing, not the scores.
• Results. Is the current strategy delivering what it promised? Before a gap is blamed on the strategy, it is diagnosed by working outward: execution first, then the objectives drawn from the strategy, then the actions designed, then target levels, then resourcing, then methods, and only then structure. Many strategies are condemned for failures of execution and resourcing that this order exposes first.

If the assumptions check fails the foundations, the verdict is rebuild: the strategy returns to the portfolio, and programmes resting on the failed assumptions are paused and rebuilt on the changed assumptions. Only when none of the failure routes applies is the verdict to continue.

Decision discipline applies five checks to every major decision before it is finalized: evidence named in the record; dissent actively invited and recorded; a revisit condition; an owned review date; and the rejected alternatives recorded with their reasons. Two scored instruments then measure what the checks protect. The Decision Quality Instrument scores major decisions across five areas, from strategic content and framing to follow-through and learning, and the model’s rule is that the lowest-scoring area becomes the improvement priority, with an action, an owner and a date recorded before the decision is filed. The Emergence Alignment Diagnostic scores the system itself, across the five functions and the model’s readiness conditions, with every score argued from evidence; an answer that cannot point to a record, a rhythm or an observed practice scores as not met. The diagnostic also places the system on a three-level maturity path: Level 1, ad hoc emergence, where strategy appears when events force it; Level 2, managed emergence, where all five functions run on recorded rhythms with named owners; and Level 3, compounding emergence, where the system’s outputs feed each other without prompting. Movement between levels is earned by fixing the diagnostic’s weakest group, not by adding process.

Emergence health metrics form the third layer: a small dashboard, reviewed at every portfolio review, that measures the system itself and not only its outputs. It tracks issue-to-decision latency (healthy at a median of ten days or fewer); experiments concluded (a cycle with none is a Ventures failure, whatever else the dashboard says); the experiment kill ratio (healthy between 30 and 70 percent — below it, criteria are too soft or verdicts are being avoided; above it, selection is too weak); the decision-quality trend; health-check completion; and the origin mix: the shares of active strategies by origin tag. The origin mix is the measure that keeps the founding doctrine honest. A portfolio near 100 percent Planned is telling you the emergence system is decorative. A portfolio near 100 percent Lived is telling you the planning discipline is absent. Healthy is a shape, not a fixed ratio: the lived stream carrying the larger share, the planned stream visibly present, and Blended entries appearing whenever the streams have genuinely corrected each other. The metrics are read together, never singly: latency falling while decision quality falls is haste, not health. What they make impossible is the quiet failure — a function that stops producing, a council that stops deciding — which in a calendar system stays invisible for a year and here is visible in one cycle.

Underneath the instruments sit the model’s readiness conditions, the social conditions the functions run on: leadership ownership of the strategy work; open information flow; protected dialogue, in which challenge is expected in the room where it can be answered and dissent is recorded as evidence; participation that creates ownership; and room to explore, a standing envelope of time and money that survives budget pressure. Each condition is observable, each has a recognizable symptom when absent (meetings agree; corridors disagree), and each is scored by the diagnostic. When the readiness group is weakest, as it often is, the strengthening actions belong to the senior team personally: conditions are set by what leaders do, and only marginally by what procedures say.

Disagreement between the functions, and between the streams, is settled by a stated contested-call protocol rather than by seniority, stamina or corridor influence: positions stated in writing with their evidence; the current evaluation tabled; the five decision checks applied; staging tested before a verdict, since a dated gate whose evidence will decide is often better than a winner; the Chair’s decision recorded together with the dissent; and the dissent revisited first when the item’s results are reviewed, and credited in the record if it proves right. The protocol ends contests; it does not require consensus.

One cycle, concretely

Abstractions persuade nobody, so the model is published with a complete worked example: one full cycle at Kestrel Engineering, a fictional manufacturer of industrial pumps and valves with about 350 people. Its recorded strategy, win and hold large water-utility framework contracts, has worked for a decade. In a single quarter, three things land: the regulator publishes a new pump-efficiency standard the core range must meet within 24 months; input costs break their planning band (castings 27 percent above it, energy 31 percent); and the largest customer, 34 percent of revenue, enters administration. None of the three waits for an annual planning cycle. That is the point of the model: the calendar is not when strategy happens.

Agenda fires first. Both signals are raised the week they land and triaged within two working days. One decision cannot wait for the full evaluation, the compliance route, and it is taken within the fortnight on the evidence available: certify the core range model by model, because the test laboratory that route requires is needed under either route and takes nine months to build. The record states what would change the decision.

Perspective reframes the question. Stating the perspective as actually held, the senior team surprises itself: Kestrel sells uptime, not pumps. The challenge log then turns on the assumptions: the input-cost assumption is marked weakened on the spot, and the customer-renewal assumption is challenged by the administrator’s notice itself. Both are handed to Intelligence the same week.

Intelligence runs the health check. The assumptions check is decisive: of five named assumptions, the two that fail outright, input costs and customer renewal, are both load-bearing, and two more score near the bottom. The verdict, by the model’s rule, is foundations failed: stop and rebuild. The change check routes the regulation to the timely decision already taken and the stakeholder and economic changes to the portfolio. The results check finds the high-efficiency range at 30 percent of its target, and diagnoses the gap as design, not effort: the range was launched without certified test evidence, so framework buyers could not specify it. The laboratory is the correction.

Ventures contributes what no analysis could. The uptime-contract pilot reaches its review date: both pilot customers signed 24-month terms, and pilot margin beats the scale criterion fixed at launch, so the verdict is scale, ruled from the criteria and not from the room’s enthusiasm. A residential smart-pump experiment reaches its review in the same week and is killed on its own criteria, its learning recorded without blame. A service team’s 48-hour failure-analysis report passes the generalizability test and is adopted as the standard for all framework customers.

Allocation integrates. Five items are decided on the record: the laboratory admitted and funded in full; the lifecycle service platform admitted with staged funding; a customer-concentration programme admitted, to bring the largest customer from 34 percent of revenue to at most 15 percent by month 24; the smart-pump launch rejected, because the experiment was killed on its own criteria; and the legacy low-efficiency range exited at the compliance deadline. One call is contested: whether the laboratory or the platform should carry the staging. The protocol runs, the health check is tabled, and the laboratory’s nine-month build against a 24-month deadline settles it: the laboratory is funded in full, the platform is staged, and the Finance Director’s dissent is recorded in full and marked to be revisited first at the gate. The decision is then scored with the Decision Quality Instrument: 3.96 overall, with participation and dialogue the lowest area at 3.40. The improvement priority is therefore not a better analysis but a communication discipline, owned and dated before the decision is filed.

The cycle closes with the diagnostic and the dashboard. The diagnostic scores 45 of 60, the readiness conditions are the weakest group, and the placement is Level 2, managed emergence. The dashboard shows a median issue-to-decision latency of nine days and a kill ratio of 50 percent, inside the healthy band. And the origin mix carries the cycle’s most uncomfortable finding: every active strategy is lived-born, 100 percent Lived. It is recorded as a finding, not as purity: the planning discipline is absent, and the horizon review is already in the diary.

In September, the second headwater runs. The horizon review refreshes the three-year direction, and one strategy at the review is born in the plan itself: a remanufacturing line for returned pumps, which no experiment proposed and no crisis forced. It passes the same three checks and is admitted, staged, with the portfolio’s first Planned tag. The same review re-opens a standing commitment of the previous plan, entering two export markets in year 2, and finds that its assumptions do not survive February’s health check. The revised commitment, one market, after certification, is admitted tagged Blended: planned in origin, lived in its present form. The origin mix is computed again: 60 percent Lived, 20 percent Planned, 20 percent Blended. Read against February’s 100 percent Lived, that is the founding doctrine working as designed: the lived stream carries the larger share, the planned stream is visibly present, and the two have already corrected each other once.

From decision to deployment

A formation model that stops at the decision leaves its hardest step, turning decisions into the organization’s working instruments, to a different system with a different logic. In this model the deployment cascade sits inside the same model, recorded on the same chain: each admitted strategy is clarified (what will be different when it succeeds, what it explicitly is not, and which existing work it displaces, since a strategy that displaces nothing only adds load); chartered as a programme, with resources confirmed against the budget before approval; reflected in the policy statement where it changes what the organization promises; and cascaded into objectives that each unit restates as the part it can actually move, with its own measure and date. A unit objective that merely repeats the organization’s number divided by headcount is returned: the cascade is a translation, not an arithmetic. Deployment does not ask which stream a strategy was born in; it asks whether the strategy is clear, resourced and owned.

The model also names the ways systems running it fail, because each pattern has a built-in antidote: the annual ritual, in which the functions are run once a year as a planning season and emergence dies between seasons; expert capture, in which Intelligence becomes a priesthood and the other functions stop arguing with it; the silent function, which generates nothing for a year while nobody notices; experiments without verdicts; the unfunded mandate; dialogue theatre, consultation performed after decisions are taken; the sacred document, a portfolio record defended rather than updated; and the two silos, in which the streams keep separate documents and meet only in budget fights. All eight are failures of the system’s discipline rather than of intelligence or effort, which is why the antidotes are records, rhythms and metrics rather than exhortations.

What this model adds

Five elements of this model are NovaQTech’s own contributions, built in rather than bolted on. First, the founding doctrine itself: emergence and deliberate planning run as two headwaters of one model, integrated in one portfolio, where the emergence tradition treats planning as the opposing camp and the planning tradition treats emergence as indiscipline. Second, the deployment cascade sits inside the same model, so admitted strategies are carried into programmes, policy and objectives on the same record instead of being handed to a separate planning system. Third, the emergence health metrics layer measures the system itself, and its origin mix keeps the founding doctrine honest. Fourth, the emergence maturity path gives the system development levels of its own, so an organization can see what better means for its strategy process and not only for its strategy. Fifth, disagreement is settled by the contested-call protocol, with the dissent preserved on the record as evidence for later reviews. Underpinning all five, the model’s two instruments are scored instruments designed for this model, so decision quality and system alignment are measured, not asserted.

Honest limits

This model does not forecast: its horizon pictures and change sensing prepare the organization to respond; they do not predict, and they should never be quoted as predictions. It does not choose between strategies by formula: no scoring matrix in the toolkit ranks candidates, because the model treats integration as judgement, disciplined by the checks, the evaluation and the protocol, and recorded with its reasons, not as computation. It does not manage execution day to day: programmes run under the organization’s own management once chartered. And every scale in the toolkit, the health check’s scores, the instruments’ scales, the metrics’ healthy bands, is a recording convention of this model, labelled as such on its artifacts: the scores discipline the organization’s own conversation about itself; they are not a measurement against any external benchmark, and they certify nothing.

Running the model

The Emergent Strategy Model by NovaQTech is operated through the Emergent Strategy Toolkit: a system guide; a procedure and a record for each of the five functions; the horizon planning procedure and record; the strategy evaluation workbook carrying the health check and both instruments; a training deck; a traceability matrix for the model itself; and the complete Kestrel worked example, in which every score, figure and verdict in this article can be followed and checked. A free sample, the complete worked example together with the strategy health check workbook that evaluates it, is available on the toolkit’s product page.

Most organizations discover, the first time they tag their portfolio, that their origin mix is not what their planning system claims it is. That discovery is where this model starts working.