The THRIVE Loop is a six-step continuous growth and evolution engine for navigating meaningful objectives under uncertainty. It helps individuals, teams, and organizations choose where effort matters, make expectations explicit, engage reality, learn from evidence, and continually improve both their results and their capacity.
T.H.R.I.V.E. is not simply a goal-setting method, execution process, learning loop, forecasting technique, or resilience practice. It brings those dimensions together. At its core, T.H.R.I.V.E. recognizes a simple problem: we routinely make choices before we can know their outcomes. We choose an objective, select an approach, and implicitly forecast what we believe will happen. Reality then gives us evidence about the quality of those choices.
The question is whether we learn from that evidence thoughtfully enough to improve what comes next.
T.H.R.I.V.E. (pronounced “Thrive” as in thriving instead of just surviving) provides a structure for doing so:
T – Target: Choose a meaningful, achievable objective and approach.
H – Hypothesize: Predict a measurable outcome from the approach.
R – Reach: Stretch to take on the targeted challenge using the chosen approach.
I – Investigate: Deeply explore what happened and why.
V – Validate: Did we achieve the predicted outcome, validate the approach, and understand any gaps?
E – Evolve: Apply what we learned to improve the approach and take the next step toward the larger objective.
The letters describe a sequence, but T.H.R.I.V.E. is a loop rather than a checklist. Each cycle should change the starting conditions of the next. A better Target can improve what we choose to pursue. A better Hypothesis can improve what we expect and measure. Reach puts those assumptions into reality. Investigation expands what we see. Validation sharpens judgment. Evolve carries the learning forward.
Repeated well, the loop can progressively improve the objective, the approach, the system, the people involved, and the way future challenges are understood.
We’ll also explore:
- 5-Whys as the Connective Tissue of T.H.R.I.V.E.
- After Action Reviews: From Experience to the Next T.H.R.I.V.E. Loop
- T.H.R.I.V.E. Operates at More Than One Scale
The T.H.R.I.V.E. was developed in the context of other iterative processes decided in Talent Code Applied, specifically targeted as developing Learned Resilience, and later adjusted in The Tao of Forecasting
T – Target: Choose a Meaningful, Achievable Objective and Approach
T.H.R.I.V.E. begins before action. The first challenge is deciding what deserves our attention.
Most people and organizations have more possible goals, problems, opportunities, and demands than they can thoughtfully pursue. Activity alone therefore tells us very little about progress. We can become extremely efficient at work that does not meaningfully matter.
Target begins with triage. We ask where focused effort can create the greatest worthwhile movement. What is already sufficiently under control? What is presently outside our meaningful influence? Where is there a constraint, opportunity, unmet need, or challenge where attention could produce meaningful leverage?
This resembles finding a Goldilocks zone. The Target should matter enough to justify the effort, be tractable enough to influence, and be sufficiently challenging to produce meaningful progress.
Destination and Approach
A Target contains two distinct choices. The Destination is the objective we hope to reach. The approach is how we currently believe can best move us toward it.
For example, “improve customer retention” is not the same choice as “introduce a new onboarding process.” The first describes where we hope to go. The second describes one possible way of getting there. Keeping those separate prevents an approach from becoming confused with the objective itself.
If an approach fails, we may still believe deeply in the Destination. We can choose another approach. Conversely, repeated cycles may intentionally keep the same approach while changing another variable. Holding one element stable can help reveal whether an observed improvement was real and what may have caused it.
T.H.R.I.V.E. therefore encourages commitment to purpose without requiring premature attachment to a particular path.
Target the Constraint, Not Merely the Activity
Systems rarely improve equally everywhere at once. A large improvement in one area can produce little meaningful value if another constraint continues to limit the overall system. Worse, local optimization can sometimes damage the larger whole.
Target therefore asks where the limiting factor really sits. For a company, it might be product adoption rather than engineering speed. For an athlete, it might be recovery rather than training volume. In a relationship, it might be trust rather than communication frequency.
This shifts the question from “What can we improve?” to “What improvement would matter most now?”
Connect the Near-Term Target to the Deeper Why
A high-leverage Target can still point in the wrong direction. This is where 5-Whys curiosity begins to function as connective tissue within T.H.R.I.V.E.
Before committing to a Target, we can ask: Why does this objective matter? Why does that outcome matter? What larger objective does it serve? What need, mission, value, or purpose sits beneath it?
The point is not to mechanically ask “why?” five times. It is to trace the immediate objective far enough forward that we understand what it is ultimately intended to serve. This is a guard against strategic drift.
A sequence of individually reasonable decisions can still carry a person or organization somewhere it never intended to go. Forward-looking inquiry helps connect the immediate Target with the larger direction.
Target therefore combines leverage, tractability, challenge sizing, Destination, approoch, and purpose.
Its governing question is:
- What meaningful and achievable objective is most worth pursuing now, why does it matter, and what approach appears most promising?
H – Hypothesize: Predict a Measurable Outcome From the Approach
After choosing a Target, T.H.R.I.V.E. does not immediately rush into execution. We first make the forecast visible.
A useful hypothesis can be expressed simply:
If we do X using this approach, we expect it to move us toward Y, our Destination, as measured by Z.
That structure matters because the hypothesis is not merely a metric. It is a causal claim. We are saying that a particular approach is expected to contribute to a particular result. This gives reality something meaningful to test.
Make the Forecast Before Knowing the Answer
Without an explicit hypothesis, hindsight can become remarkably forgiving. If the outcome is good, we may convince ourselves that we expected it. If it is poor, we may redefine what success supposedly meant. Both reactions weaken learning.
Defining the expected outcome before acting creates a cleaner comparison later. What did we actually predict? What happened? What does the difference teach us?
That distinction turns experience into better evidence.
Begin With the Outside View
Human judgment naturally gravitates toward the details of the situation directly in front of us. That is the Inside View. It matters, but it can make the current situation feel more unique than it really is.
Before concentrating on our special circumstances, Hypothesize asks us to consider the Outside View. What usually happens in situations like this? What do previous attempts, historical data, comparable projects, or relevant experience suggest?
These baseline expectations help ground the forecast in reality. Only then do we adjust for the Inside View. What is genuinely different about this case? Are our resources stronger? Is timing worse? Do we have an unusual advantage? Is the constraint different?
The combination helps balance historical evidence with contextual judgment.
Make Uncertainty Visible
A forecast does not become more rigorous by pretending certainty. If appropriate, T.H.R.I.V.E. encourages expressing confidence explicitly. We might believe an outcome has a 65 percent likelihood rather than saying it “probably” will happen.
The exact number is less important than the discipline. Over repeated loops, we can ask whether our confidence itself is calibrated. When we feel 80 percent confident, are we right approximately that often? Are we chronically overconfident? Are we too cautious?
This transforms forecasting into a learning process about our own judgment.
Hypothesize therefore makes the approach, predicted outcome, measurement, assumptions, historical baseline, unique conditions, and uncertainty explicit.
Its governing question is:
- What measurable outcome do we predict from this approach, why do we expect it, and how confident should we be?
R – Reach: Stretch to Take On the Targeted Challenge Using the Chosen Approach
Reach is where the forecast leaves our heads and enters reality. We act.
But the word Reach is intentional. The step is not merely called Execute because T.H.R.I.V.E. is interested in more than completing work. A meaningful Reach often asks something beyond what is already certain or comfortable.
Full Engagement Meets Perpetual Beta
Reach calls for committed engagement with the chosen approach. We do not make a tentative half-effort that makes the hypothesis impossible to evaluate. We give the approach a meaningful opportunity to work.
At the same time, commitment does not require rigidity. A perpetual-beta mindset allows us to act seriously while remaining open to evidence that the plan needs to change.
That balance matters. Weak commitment produces ambiguous evidence. Blind commitment ignores evidence. Reach aims for purposeful engagement without attachment.
Why the Stretch Matters
The challenge within Reach has a second purpose. A Target that is already comfortably within our capability may produce a result, but it reveals relatively little about what we could learn or become capable of doing next.
A genuine Reach contains some uncertainty. That can increase the probability of missing the predicted outcome. It can also increase the opportunity for learning, skill development, resilience, ingenuity, and expanded capacity.
There is an important limit. If the challenge is too small, adaptation may be minimal. If it is wildly beyond present capacity, the experience can become destructive or defeating rather than developmental.
The productive zone lies between those extremes. Learning theory describes a related concept as the zone of proximal development. Physical training uses progressive overload. Learned Resilience describes right-sized challenges that stretch without unnecessarily snapping the person or system.
The insight is broader than any of those labels. Difficulty is not automatically evidence that something has gone wrong. Sometimes difficulty is the environment in which new capability is being created.
Reach Creates Evidence
This is what connects Reach to the rest of T.H.R.I.V.E. Before Reach, the approach remains a hypothesis. During Reach, reality begins producing evidence.
The approach encounters customers, competitors, physics, emotions, constraints, teammates, changing circumstances, and unforeseen events. The Reach is therefore simultaneously execution, challenge, evidence generation, and potential capacity building.
Success after a meaningful stretch can create satisfaction and earned confidence. A recoverable miss can also create enormous value when the evidence is thoughtfully investigated.
The purpose is not to glorify failure. Nor is it to maximize difficulty. It is to create enough meaningful contact with reality that progress and learning both become possible.
Reach asks:
- What happens when we fully engage this meaningful challenge using the approach we chose?
I – Investigate: Deeply Explore What Happened and Why
Reach creates evidence. Investigation seeks to understand it.
Investigation begins while the action is unfolding, not only after it ends. We watch what reality is telling us in real time. What is moving? What is not? What changed unexpectedly? Where is resistance appearing? Has the constraint moved? Has new information altered our original assumptions?
If the evidence warrants it, we update.
Investigate With Dragonfly Eyes
One perspective is rarely enough in a complex system. A dragonfly sees through many visual facets at once. The metaphor is useful because good investigation similarly seeks multiple partial views.
Quantitative measures may show one thing. Customer experience may reveal another. Front-line employees may see a constraint leadership misses. A dissenting colleague may notice an assumption everyone else has accepted.
Investigation actively seeks these different signals. We should be especially curious about evidence that contradicts our preferred explanation. This is one of the protections against confirmation bias.
The goal is not to defend the original hypothesis. The goal is to become less wrong.
Update Without Erasing the Starting Point
Investigation can change our forecast while a Reach is still underway. New evidence may justify changing our confidence, adapting execution, or even changing the approach.
That does not mean pretending the original forecast never existed. The original hypothesis remains valuable precisely because it gives us a baseline against which to observe how our understanding changed.
A disciplined investigator can therefore say: We began at 70 percent confidence. New evidence reduced that to 50 percent. We adapted the approach. Here is why.
That record improves future judgment.
Move From Surface Symptom Toward Root Cause and Meaning
This is another place where 5-Whys curiosity becomes powerful. What happened is only the beginning.
Why did it happen? What condition made it likely? What constraint shaped the result? What assumption led us to choose this approach? What deeper need or value were we attempting to serve?
The inquiry can move from symptom, to condition, to pattern, to belief, and sometimes to meaning. That makes 5-Whys more than a failure-analysis technique. It becomes a way of moving beneath appearances.
Investigation therefore combines real-time observation, multiple perspectives, updating, disconfirming evidence, systems awareness, and root inquiry.
Its governing question is:
- What actually happened, what might we be missing, and why did reality unfold this way?
V – Validate: Did We Achieve the Predicted Outcome, Validate the Approach, and Understand Any Gaps?
Validation brings the original Target and Hypothesis back into view. Investigation asks what happened and why. Validation asks what that evidence allows us to conclude.
This is not a binary pass-fail audit. It is a multi-layer evaluation across tactical, strategic and systemic, and human dimensions.
Tactical Validation: Did the Predicted Outcome Occur?
First, return to the measurable prediction. Did we achieve Z? Did it occur to the degree expected? Were our timing and magnitude predictions accurate? How well calibrated was our confidence?
This is where the hypothesis meets the most direct evidence. A prediction that did not occur is not rescued by a good story. Likewise, an unexpected success deserves investigation rather than automatic self-congratulation.
Validate the Approach
Next, did the chosen approach actually contribute to the result?
Correlation is not causation. An outcome may have improved because of timing, luck, another intervention, market conditions, or an unrelated change elsewhere in the system.
We therefore ask what evidence supports the approach itself. A single cycle may validate that an approach appears effective. It rarely proves that it is globally optimal.
That distinction preserves curiosity. An approach can work and still be improved.
Strategic and Systemic Validation: Did the Result Actually Matter?
This is where T.H.R.I.V.E. protects against local optimization.
Suppose the predicted metric moved exactly as hoped. Did that actually advance the Destination? Did it relieve the meaningful constraint? Did throughput increase across the larger system? Or did the improvement simply move the bottleneck elsewhere?
A company can ship features faster while making customers less happy. A team can increase output while exhausting its people. An athlete can improve one metric while increasing injury risk.
A tactical win can therefore coexist with a strategic loss. Validation asks both.
Human Validation: How Did We Get There?
The method matters as well as the result. Did we act consistently with our values? Did fear cause us to conceal evidence, protect status, blame others, or take shortcuts? Did the process strengthen capability and trust, or damage the human system that must continue operating afterward?
Psychological safety is not separate from rigorous learning. It is one of its conditions.
If challenging a hypothesis threatens the person who proposed it, people begin protecting ideas rather than investigating them. Bad news arrives late. Dissent disappears. Forecasts become political.
T.H.R.I.V.E. therefore distinguishes an invalidated hypothesis from an invalidated person. The data may tell us our assumption was wrong. That can still validate the value of the experiment and the learning it produced.
A miss can become evidence rather than identity.
Validate Our Understanding of the Gap
Finally, if the predicted outcome was missed, do we understand why well enough to improve the next cycle? A plausible explanation is not necessarily understanding.
This is where retrospective 5-Whys inquiry can connect the visible gap to system conditions, assumptions, beliefs, incentives, or values. We might ask: Why did this outcome occur? Why did the system make it likely? Why did the approach fail to navigate that condition? Why did we believe this approach was appropriate? What were we ultimately trying to create or protect?
Validation therefore tests the measurable result, causal effectiveness of the approach, strategic value, systemic consequences, human integrity, predictive calibration, and our understanding of any gaps.
Its concise question remains:
- Did we achieve the predicted outcome, validate the approach, and understand any gaps?
E – Evolve: Carry the Learning Into a Higher-Order Next Cycle
A great deal of improvement work ends with a sensible question: What should we standardize or embed?
T.H.R.I.V.E. asks something larger:
What should now evolve?
The distinction is deliberate. Embedding can preserve a useful improvement. It can also lock a local solution into place after the conditions that made it useful have changed.
T.H.R.I.V.E. treats what worked as evidence, not doctrine.
Evolve the Approach
The Destination may remain valid while the approach changes. Perhaps the Reach revealed a more effective method. Perhaps the original approach worked but can now be improved. Perhaps the next cycle should compare two approaches deliberately.
Learning should alter execution.
Evolve the System
Removing one constraint often reveals another. The next bottleneck may exist somewhere entirely different from the one we just addressed.
Evolve therefore looks beyond the immediate fix. What changed in the larger system? What workflow, structure, incentive, tool, dependency, or relationship now needs attention?
The purpose is not merely to improve one component. It is to improve the capacity of the whole.
Evolve the Strategy
Evidence can challenge the objective itself. Perhaps the problem we believed mattered most is not actually the core problem. Perhaps a customer need is different from what we assumed. Perhaps the environment has changed.
Evolution sometimes means changing course rather than executing the old course better. This is another defense against strategic drift and local optimization.
Evolve the Human Capability
A completed cycle can also change the people who moved through it. Knowledge increases. Skills improve. Judgment becomes more calibrated. Confidence may become more earned. Teams may become better at disagreement, inquiry, recovery, and adaptation.
A challenge that once required a significant Reach can eventually become ordinary capability. That shifts the baseline. The next challenge can now begin from a higher place.
Evolve How We Learn
This may be the deepest dimension of Evolve. T.H.R.I.V.E. should not only improve what we do. Over time, it should improve how we arrive at what to do.
We may learn to choose more meaningful Targets. We may improve how we form hypotheses. We may become better calibrated about uncertainty. We may recognize which sources of evidence deserve more weight. We may discover better ways to investigate.
We may become more skillful at separating people from hypotheses. We may learn how large a Reach creates the richest learning without producing unnecessary damage. In this sense, even the way we use T.H.R.I.V.E. can evolve.
Evolve Beyond the Individual
The learning can also move outward. A useful insight discovered by one person can improve a team. A team can change an organization. An organizational learning can improve the wider ecosystem it touches.
Sharing better approaches can expand collective capacity rather than leaving learning trapped within one person or one project. This is the human-continuum dimension of Evolve.
The loop can strengthen not only the person who encountered the challenge, but others who inherit the learning.
Evolve therefore means more than taking another step. It means allowing validated learning to change the approach, system, strategy, capabilities, people, relationships, judgment, and the way future learning happens.
Its governing question is:
Given what we now know, what should evolve before we choose the next Target?
5-Whys as the Connective Tissue of T.H.R.I.V.E.
Although 5-Whys inquiry becomes especially visible in Investigation and Validation, its deeper role can run through the entire loop.
In Target, it can be forward-looking:
- Why this objective?
- Why now?
- Why does it matter?
- What larger purpose does it serve?
In Hypothesize, it can expose assumptions: Why do we believe this approach will produce that result?
In Reach, difficulty can trigger curiosity rather than immediate judgment: Why is this harder than expected?
In Investigate, it can move from symptom toward cause: Why did reality behave this way?
In Validate, it can test meaning and systemic value: Why did this result matter, and what does the gap reveal?
In Evolve, it can help determine what deserves to change: What deeper cause, belief, structure, or purpose should now inform the next cycle?
This is why 5-Whys can function as something like the nervous system of T.H.R.I.V.E. The six letters provide the structure. Curiosity helps meaning move through it.
After Action Reviews: From Experience to the Next T.H.R.I.V.E. Loop
The U.S. Army’s After Action Review (AAR) offers a useful example of an established practice that aligns naturally with several parts of T.H.R.I.V.E. Rather than simply asking whether something succeeded or failed, an AAR compares intention with reality, investigates why the difference occurred, and carries the learning forward.
Its four core questions are remarkably simple:
- What did we intend to happen?
- What actually happened?
- Why did it happen that way?
- What should we change or repeat next time?
Seen through T.H.R.I.V.E., those questions span several parts of the loop.
What did we intend to happen? returns us to Hypothesize. What outcome did we predict from the chosen approach? Making that expectation explicit before acting gives us a meaningful baseline rather than allowing hindsight to rewrite what we supposedly expected.
What actually happened? begins Investigate. Before explaining the outcome, we first establish reality as clearly as possible. What did we observe? What changed? What did not? What surprised us?
Why did it happen that way? takes Investigation deeper. This is where multiple perspectives, disconfirming evidence, constraints, assumptions, and 5-Whys inquiry become particularly valuable. The purpose is not merely to describe the result, but to understand the conditions and causes that produced it.
What should we change or repeat next time? crosses from Validate into Evolve. Before deciding what to repeat, we need to validate whether the predicted outcome was achieved, whether the approach actually contributed to it, and whether we understand any gaps. Only then can the learning responsibly inform what comes next.
Learn From Successes as Well as Misses
AARs are especially valuable when they are used after successes as well as failures.
Success can be dangerously easy to misunderstand. A positive outcome does not automatically validate the approach that preceded it. Luck, timing, changing conditions, or another part of the system may have contributed. Conversely, something may have worked exactly as predicted, but at an unacceptable cost elsewhere.
A successful outcome therefore deserves many of the same questions as a miss:
Why did this work? Which parts of our approach actually mattered? What should we repeat? What should we not assume will work again? Did the result advance the larger objective, or merely improve a local measure?
This is one reason T.H.R.I.V.E. treats both wins and misses as sources of evidence.
Blameless Does Not Mean Causeless
A strong AAR also depends on the willingness to examine our own contribution to what happened.
If a leader uses reflection primarily to evaluate everyone else, people quickly learn to protect themselves. Information becomes filtered, inconvenient observations disappear, and the review becomes an exercise in attribution rather than learning.
T.H.R.I.V.E. requires something different. We want rigorous causal inquiry without turning causality into personal indictment.
A leader might therefore ask: What did I assume? What signals did I overlook? What conditions did my decisions create? What might I have communicated poorly? How did the system we created shape the outcome?
This connects directly to the Human dimension of Validate and to psychological safety. An invalidated hypothesis does not require an invalidated person. A blameless review can still be exacting about causes, choices, systems, and consequences.
AAR as a T.H.R.I.V.E. Practice
An After Action Review does not replace T.H.R.I.V.E. It fits naturally within it.
T.H.R.I.V.E. begins earlier by helping us choose a meaningful Target and make the expected outcome explicit before action. Reach then puts that hypothesis into contact with reality. An AAR provides a disciplined way to examine what that contact revealed. Validate determines what the evidence supports. Evolve converts that understanding into a better next cycle.
In that sense, AAR provides a concise practical bridge:
Intention → Reality → Why → What Changes Next
T.H.R.I.V.E. embeds that bridge inside a larger continuous growth and evolution engine, so the lesson is not merely recorded after the fact. It changes the next Target, the next approach, and potentially the capability of the person, team, or system that enters the next loop.
T.H.R.I.V.E. Operates at More Than One Scale
The same underlying loop can appear in very different domains because uncertainty, action, evidence, and adaptation are not limited to business.
A product team can Target a customer problem, Hypothesize how a feature will change behavior, Reach by releasing an experiment, Investigate usage, Validate value and systemic effects, and Evolve the product and strategy.
An athlete can Target a performance constraint, Hypothesize that a training change will improve a measurable result, Reach through a challenging training cycle, Investigate performance and recovery, Validate the approach, and Evolve the next training block.
A person working on a relationship can Target a meaningful change, choose an approach, predict what healthier interaction might look like, Reach by behaving differently, investigate the response, validate what helped, and evolve how the relationship is approached.
A forecaster can Target a question worth answering, establish a probability, gather evidence, update as reality changes, validate calibration against the result, and evolve the forecasting model.
A leader can use the same architecture for organizational change. An engineer can use it for system improvement. A learner can use it to develop a skill.
The content changes. The underlying discipline remains recognizable:
- Choose thoughtfully. Forecast explicitly. Engage reality. Investigate deeply. Validate honestly. Evolve deliberately.
The Loop Does Not Return to the Same Place
A circle returns to its starting point. T.H.R.I.V.E. ideally does not.
If the loop has worked well, Evolve changes the baseline from which the next Target is chosen. The system knows something it did not know before. The approach may be better. A constraint may have shifted. Confidence may be better calibrated. A team may have greater capability. An individual may be able to take on a challenge that previously would have been too large.
The next loop therefore begins on an elevated horizon.
This is where repeated cycles can compound. Small loops can be particularly powerful because they reduce the time between assumption and evidence. They allow us to learn before committing everything to one enormous bet.
Small does not mean unambitious. A large objective can be pursued through a sequence of meaningful, increasingly capable reaches.
Over time, Targets can become more ambitious. approaches can become more effective. Forecasts can become better calibrated. Investigation can become more discerning. Validation can become more honest and systemic. People and systems can become capable of challenges that once exceeded them.
That is continuous evolution.
What T.H.R.I.V.E. Ultimately Seeks to Improve
The immediate success of a T.H.R.I.V.E. loop may be a measurable outcome. Its larger value is what happens to the system that produced that outcome.
Did we become better at deciding what deserves attention? Did we become more thoughtful about cause and effect? Did we become more honest about uncertainty? Did we learn to expose our assumptions before reality exposes them for us?
Did we become more curious about evidence that challenges us? Did we distinguish a tactical win from real strategic progress? Did we preserve the psychological safety required for people to tell the truth? Did we convert both successes and misses into useful understanding?
Did we change the next cycle because of what we learned? And did our growing capability allow us to engage more meaningful challenges than before?
That is why T.H.R.I.V.E. is more than an execution checklist and more than a learning loop.
It is a continuous growth and evolution engine for engaging uncertainty with purpose, disciplined judgment, action, curiosity, humanity, and the willingness to keep evolving what we do and how we learn.
See Also
See Also: Talent Whisperers
Talent Code Applied
Other systems/processes that informed the THRIVE Loop including Build-Measure-Learn, the OODA-Loop, Talent-Code-REPS, Kaizen, Agile-Sprints, Lean-Startup, Toyota-Production-Systems (TPS), Bosch-Innovation, Design-Thinking, Jobs-To-Be-Done, …
Describes an iterative process for individuals and organizations to become increasingly reslient and the birth place of T.H.I.R.V.E.
Tao of Forecasting
Applies T.H.R.I.V.E. to forecasting in business and everyday life.
See Also: After Action Reviews and Organizational Learning
After Action Reviews — Wharton Executive Education
Wharton presents the U.S. Army’s After Action Review as a practical method for continuous performance improvement and adaptive learning. It lays out the four core questions and explicitly emphasizes learning from successes as well as failures. Particularly relevant to T.H.R.I.V.E., it stresses spending substantial attention on why events unfolded as they did and creating a climate where leaders examine their own contribution rather than evaluating everyone else. This makes it an excellent deeper exploration of how Hypothesize, Investigate, Validate, and Evolve can connect in practice.
After Action Reviews — U.S. Army TC 7-0.1
This current U.S. Army training circular provides the authoritative military foundation for After Action Reviews. The Army describes an AAR as a guided analysis intended to improve future performance through candid, standards-based examination of strengths and weaknesses from multiple perspectives. That emphasis aligns closely with T.H.R.I.V.E.’s distinction between merely observing a result and deeply Investigating what happened before Validating what the evidence actually supports. It also demonstrates that structured reflection is not simply retrospective documentation; its purpose is to improve the next engagement.
A Better Approach to After-Action Reviews — Harvard Business Review
This Harvard Business Review article examines what organizations have learned from decades of trying to transplant the Army’s AAR into business. Its central warning is particularly relevant to T.H.R.I.V.E.: a powerful learning discipline can become little more than a pro forma exercise when the underlying philosophy is reduced to a checklist. The authors revisit the original purpose of the AAR and explore how organizations can make the practice more effective rather than merely performing its mechanics. It provides useful depth for understanding why T.H.R.I.V.E. likewise depends on curiosity, candor, interpretation, and adaptation rather than simply moving mechanically through six letters.
Why Leaders Don’t Learn from Success — Harvard Business Review
Francesca Gino and Gary Pisano explore why success can actually impede learning when leaders assume a positive outcome proves that their judgment or strategy was correct. They identify tendencies such as overconfidence, attributing success too readily to our own actions, and simply failing to ask why something worked. Their recommendation to examine successes with the same rigor applied to failures strongly reinforces T.H.R.I.V.E.’s Investigate and Validate phases. It also helps explain why achieving the predicted outcome should not automatically end the inquiry: we still need to understand whether the approach caused the result, what else contributed, and what is truly worth carrying into Evolve.