Reviewing Outcomes and Learning from Decisions

Introduction

Every decision a leader makes is, in one sense, a small experiment. The leader gathered facts, evaluated options, considered trade-offs, chose a path, built a plan, executed it, and stood behind the choice. And then reality responded. Sometimes reality confirmed the leader's thinking. Sometimes reality contradicted it. Sometimes reality produced outcomes the leader had not anticipated, either better or worse than expected. And in every case, reality offered something more valuable than the decision itself ever could. Reality offered information. Information about how the decision actually worked. Information about what was missed in the analysis. Information about what the leader did well and what they did poorly. Information that, if examined honestly and integrated into the leader's understanding, would make the next decision better than this one was.

But most of this information is never collected. Most decisions are made, executed, and then forgotten by the leader who made them. The leader moves on to the next decision, then the next, then the next. They never look back. They never review what actually happened. They never compare the outcome to what they expected. They never examine why the decision produced what it produced. And so they never extract the learning that the decision was offering them. They make hundreds of decisions a year, each one carrying potential lessons about their own judgment, their own blind spots, their own patterns, their own growth as a decision-maker. And almost none of those lessons get captured. They are lost in the busyness of moving on to whatever comes next.

This is one of the most quietly damaging patterns in leadership development. Leaders who do not review their decisions cannot learn from them. And leaders who cannot learn from their decisions are condemned to repeat the same patterns of judgment, the same patterns of error, the same patterns of strength and weakness, for the entire span of their careers. They may become more experienced. They may not become more capable. Experience without reflection produces patterns. Reflection turns experience into capability. The discipline of reviewing outcomes and learning from decisions is what turns the raw material of leadership experience into the actual growth of leadership judgment over time.

For a leader, developing this discipline is one of the most important investments you can make. It does not require special talent. It does not require new skills. It requires the willingness to slow down, after a decision has played out, and look honestly at what actually happened, what you expected, what you missed, what you got right, and what you would do differently. This work takes very little time. It produces enormous returns. And it compounds over many decisions across many years into a kind of judgment that no amount of unreflected experience can match.

This article explores reviewing outcomes and learning from decisions in depth. What it really means. Why it matters so much for the long-term development of a leader. The different kinds of reviews you can do, from quick individual reflections to structured retrospectives with your team. The components of a useful review. How to separate the quality of a decision from the quality of an outcome. How to extract lessons that are actually transferable to future decisions rather than overlearning from a single instance. How to build the habit so that reviewing decisions becomes a regular part of your leadership rhythm rather than a sporadic activity that happens only when something goes spectacularly right or wrong. And the deeper craft of becoming the kind of leader whose judgment improves continuously across the long arc of their career, because they have made the discipline of reflection a permanent part of their practice. By the end, you should be ready to bring this discipline into your real leadership in ways that will compound, over months and years, into the kind of judgment that distinguishes leaders whose decisions improve over time from leaders whose decisions stay the same.

Simple Meaning: What Is Reviewing Outcomes and Learning from Decisions?

Reviewing outcomes and learning from decisions is the deliberate practice of looking back at decisions you have made, examining what actually happened compared to what you expected, identifying what worked and what did not, separating the quality of the decision from the quality of the outcome, and extracting transferable lessons that you can apply to future decisions. It is the discipline that turns the raw experience of decision-making into the growing capability of better decision-making. It is the practice that distinguishes leaders who develop continuously throughout their careers from leaders whose judgment plateaus after a few years and stays largely the same for decades. And it is one of the most underused and most powerful capabilities a leader can develop.

Reviewing outcomes and learning from decisions is the practice of treating your own decisions as data. Each decision you make produces an outcome. Each outcome contains information. Information about how reality responded to your judgment. Information about what you understood correctly and what you understood imperfectly. Information about the assumptions that turned out to be valid and the assumptions that turned out to be wrong. Information about your own patterns of thinking, your own blind spots, your own areas of strength. This information is one of the most valuable things a leader can have. But it is only available to leaders who pause to collect it. Most leaders do not. They make a decision, move on to the next decision, and never look back at the first one. The outcome happens, the consequences play out, and the leader has moved on to other things long before the data has even fully arrived. They might know, in a general way, whether the decision worked. They might remember whether it produced what they hoped. But they never sit with it. They never examine why it worked or did not work. They never compare what they expected to what actually happened. They never extract the patterns that would inform their next decision. And so their next decision is made with essentially the same judgment as their previous one. Over months and years and careers, this produces leaders whose decision-making capability does not really grow. They become more confident, often. They become more experienced, certainly. But the actual quality of their judgment does not develop because they are not using the data that their own decisions are generating. The leader who reviews their decisions deliberately produces something different. Each decision becomes a learning opportunity. Each outcome becomes a source of information. Each review becomes a small but powerful contribution to the leader's growing judgment. Over months and years, this practice compounds. The leader becomes someone whose decisions are visibly better than they used to be, in ways the leader can name and that their peers can observe. They become someone who can articulate why they make the decisions they make, including the lessons they learned from past decisions that shaped their current thinking. They become someone whose judgment can be trusted because they have done the work of refining it through honest reflection over many years. This is the kind of leader whose career trajectory bends upward not because of luck or talent or charisma but because of the slow, patient accumulation of better judgment through the discipline of learning from their own decisions. Most leaders never develop this discipline. Those who do become some of the most quietly capable leaders in any organization. They are the people whose decisions tend to work out more often than chance would predict, not because they are smarter, but because they have spent years refining their judgment through the deliberate review of what worked, what did not, and why.

Reviewing outcomes and learning from decisions can be understood through four essential elements:

The Difference Between a Good Decision and a Good Outcome

One of the most important capabilities in reviewing decisions is the ability to distinguish between the quality of the decision and the quality of the outcome. These are not the same thing. Confusing them is one of the most common reasons leaders fail to learn from their decisions.

Good Decisions Can Produce Bad Outcomes

You can gather the facts well, evaluate the options thoughtfully, weigh the trade-offs honestly, choose the best path available given what you knew, and still produce a bad outcome. The world is uncertain. Random events happen. Other people make choices that affect your decision's outcome. Information that was not available at the time of the decision becomes relevant after the decision is made. A bad outcome from a good decision is not a sign that you decided poorly. It is a sign that uncertainty produced a result that did not favor your choice this time. If you treat every bad outcome as evidence of a bad decision, you will learn the wrong lessons. You may stop making the kinds of decisions that, on average, produce better outcomes. You may become more cautious in ways that are not warranted. You may second-guess yourself in situations where your original thinking was sound.

Bad Decisions Can Produce Good Outcomes

You can skip the fact-gathering, ignore the trade-offs, make the decision on impulse, and still get lucky. The world's uncertainty cuts both ways. Sometimes bad decisions produce good outcomes because circumstances favor you despite the quality of your thinking. If you treat every good outcome as evidence of a good decision, you will also learn the wrong lessons. You will reinforce sloppy decision-making. You will overweight your confidence in patterns that were not actually causing your good results. You will be unprepared when uncertainty stops favoring you.

The Discipline of Separating the Two

The leader who learns from decisions effectively asks two questions about every significant decision they review.

• Was the decision sound given what was known at the time? This evaluates the quality of the decision-making process.
• What was the outcome? This evaluates what actually happened.

These two questions can produce four combinations.

Reviewing decisions effectively requires asking both questions and being honest about both answers. Most leaders ask only about the outcome. That is why most leaders learn the wrong lessons from their decisions over time.

The Different Kinds of Reviews You Can Do

Not every decision needs the same level of review. Small decisions need quick reviews. Large decisions deserve more structured ones. Building a practice that includes different kinds of reviews allows you to match the depth of the review to the importance of the decision.

The Quick Individual Review

For most everyday decisions, a quick review of three to five minutes in your own mind is enough. What did I decide? What happened? What did I expect? What was different? What can I take from this? This kind of review can happen during a walk, during a quiet moment between meetings, or at the end of the day. It does not require a meeting or a document. It does require the discipline to actually pause and do it rather than letting the decision fade without reflection.

The Written Personal Review

For more significant decisions, a written review captures the learning in a form you can return to later. Even a few sentences in a notebook or a document is far more valuable than holding the reflection only in your memory. Memory is selective and shaped by your current state. Writing forces specificity and creates a record you can compare against future decisions. A simple structure: what I decided, what I expected, what happened, what I learned. Five sentences is often enough.

The Team Retrospective

For decisions that involved the team in execution or that affected the team significantly, a retrospective with the team produces shared learning. Retrospectives can be informal (a fifteen-minute conversation at the end of a meeting) or structured (a dedicated session with a specific framework). The team's perspective often reveals things the leader cannot see alone. And the act of conducting retrospectives builds the team's own capability to learn from their work.

The Strategic Decision Review

For major decisions, especially ones with long time horizons or significant resource commitments, a more thorough review is worth the time. This kind of review typically happens at planned milestones or at the end of a quarter, a year, or a project. It examines not just one decision but a set of related decisions and the patterns across them. It might include data analysis, stakeholder input, and structured documentation. It often involves comparing initial projections to actual results.

The Pattern Review

Periodically (perhaps quarterly or annually), look not at individual decisions but at patterns across many decisions. What kinds of decisions do you tend to get right? What kinds do you tend to get wrong? What biases or tendencies show up across your decision-making? This kind of review reveals patterns that individual reviews cannot. It is one of the most powerful forms of leadership development available.

The Components of a Useful Review

Whatever the size of the review, certain components make it useful. Reviews without these components tend to produce shallow reflection rather than real learning.

1. Reconstruct the Decision

Start by reconstructing what you actually decided. Be specific. What was the choice? What were the alternatives? Why did you choose what you chose? This step matters because memory of decisions distorts after the outcome is known. You may remember the decision as more obvious than it was, or more reluctant than it was, or different from what it actually was. Reconstructing it forces you to be honest about what you actually committed to.

2. Recall What You Expected

What did you think would happen? What outcomes did you hope for? What risks did you anticipate? What was your confidence in the decision at the time? Comparing expectation to outcome is where most of the learning lives. If you skip this step, you will lose the ability to calibrate your own judgment.

3. Examine What Actually Happened

What was the outcome? Be specific. Use real data when you can. Distinguish between what you observed and what you assumed. Notice what surprised you, what confirmed your expectations, and what was different from what you thought would happen.

4. Evaluate the Decision Quality

Was the decision sound given what was known at the time? Did you gather the facts you needed? Did you evaluate the options thoughtfully? Did you weigh the trade-offs honestly? Did you involve the right people? Did you make the decision in a timely way? This is the place to be honest about the quality of your thinking, separate from the quality of the result.

5. Evaluate the Execution Quality

How well did the decision get executed? Was the action plan clear? Did the execution match the plan? Where did execution succeed and where did it struggle? Some decisions look like they failed when really the execution failed. Some decisions look like they succeeded when really the execution rescued them.

6. Identify the Surprises

What surprised you? Surprises are the most valuable source of learning because they reveal where your model of the situation was wrong. What did you not anticipate? What turned out to be more important than you thought? What turned out to matter less?

7. Extract the Lessons

What have you learned that will apply to future decisions? Lessons should be specific enough to act on but general enough to transfer. "Next time, I will spend more time talking to engineering before committing to a timeline" is more useful than "I should not have decided this way" or "I should be smarter."

8. Resist Overfitting

Be careful about overlearning from a single decision. One bad outcome does not mean a decision-making approach is broken. One good outcome does not mean it is bulletproof. Try to identify which lessons are likely to be robust across many decisions and which lessons are specific to this situation.

9. Capture the Learning

Write the lesson down somewhere you will return to. A notebook. A document. A shared retrospective record. Lessons that are not captured tend to fade. Lessons that are captured can be reviewed before future decisions of similar kind.

10. Apply the Lesson

The next time you face a similar decision, deliberately apply what you learned. This is what closes the loop. Lessons that are captured but never applied are just records. Lessons that are applied are the actual growth in your judgment.

How to Build the Review Habit

The discipline of reviewing decisions is valuable only if it becomes a habit. Sporadic reviews of dramatic decisions, with no review of the much more common everyday decisions, produces uneven learning. Building the habit requires structure.

Build It Into Your Calendar

Set aside specific time for reviews. Fifteen minutes at the end of each week to review the decisions you made. An hour at the end of each month to do a deeper review. A half-day each quarter for a pattern review. If reviewing is on your calendar, it happens. If it depends on finding time, it does not.

Make It Lightweight

The first instinct of many leaders is to build elaborate review structures. These rarely sustain. Start small. A few sentences in a notebook. A simple template. A short conversation with a peer. Build the habit first. Add depth as the habit takes hold.

Connect It to Existing Rhythms

Build reviews into existing rhythms. End each one-on-one with a brief reflection on a recent decision. Use the last fifteen minutes of a team meeting to review a decision the team executed. Tag the end of a project naturally with a retrospective. Reviews that are connected to existing rhythms are easier to sustain than reviews that require separate effort.

Use Simple Prompts

Have a few standard questions you ask in every review. What did I decide? What did I expect? What happened? What did I learn? What will I do differently next time? Five questions can be answered in five minutes. Simple prompts make reviews easy to start.

Track Patterns Across Reviews

Over time, look for patterns across your individual reviews. Are you consistently underestimating timelines? Are you consistently overestimating capacity? Are you consistently making particular kinds of decisions well or poorly? Patterns are the highest-value lessons. They emerge only from reviewing many decisions, not from reviewing any single one.

Share Some Reviews

Some of your most powerful learning comes from sharing reviews with peers or coaches. They notice things you cannot. They ask questions you would not. They reflect back patterns that you would miss alone. Building peer review into your habit, even with just one person, multiplies the value of your reflection.

Be Patient With the Habit

The first weeks of building a review habit feel awkward. You will skip days. You will write shallow reflections. You will wonder if it is producing anything. Stay with it. The compounding effect is real but invisible at first. Most leaders who build this habit say that within a few months they cannot imagine going back.

Common Mistakes in Reviewing Decisions

Even leaders who recognize the importance of reviewing decisions make predictable mistakes that reduce its value. Recognizing these mistakes helps you avoid them.

Practical Workplace Scenario

Scenario

A leader named Geetanjali had been running a marketing team for about four years. She had been making dozens of decisions every week. Some had worked out well. Some had not. But she had never really reviewed them. She had been too busy making the next set of decisions to look back at the previous ones. She had been doing this for years without recognizing the cost.

Then a senior peer pulled her aside. They had been working together on a cross-functional initiative. The peer said gently: "I have been watching how you make decisions, and I want to share something with you. You make decisions thoughtfully. But I notice that you do not seem to learn from them. I have watched you make the same kind of decision in three different situations over the past year, each time with the same approach, each time with similar problems in the outcome. And I do not think you have noticed. You might benefit from building a practice of reviewing your decisions deliberately. I have done this for years, and it has made a real difference in my own judgment."

What She Did

Geetanjali was surprised. She had thought of herself as a learning-oriented leader. But when she examined her own practice honestly, she realized that her peer was right. She made decisions, executed them, and moved on. She did not pause to look back. She did not extract lessons. She did not compare expectations to outcomes. She had been operating on accumulated experience without converting it into refined judgment.

She decided to build a deliberate review practice. She started simple. At the end of each week, she set aside fifteen minutes on a Friday afternoon to review the significant decisions she had made that week. She kept a small notebook. For each decision, she wrote down what she had decided, what she had expected, what had actually happened (when known), and what she had learned. Some weeks she had three significant decisions to review. Some weeks she had just one.

For larger decisions, she did deeper reviews. She would set aside an hour, usually at the end of a project or a quarter, to do a more thorough examination. She would compare her initial expectations to actual outcomes. She would identify what surprised her. She would extract specific lessons. She would write them in a separate document she called her "decisions journal."

For decisions that affected her team, she started running brief retrospectives with the team. Not elaborate ones. Fifteen minutes at the end of relevant meetings. What did we do? What worked? What did not? What will we try differently?

Quarterly, she did a pattern review. She would read back through her notebook and journal entries. She would look for themes. What kinds of decisions had she been consistently getting right? What kinds had been consistently producing disappointing outcomes? What patterns showed up across many decisions?

What She Discovered

Within the first three months, Geetanjali discovered patterns she had not seen before. She tended to underestimate the time required for cross-functional coordination. She tended to weight stakeholder pressure more heavily than was warranted, particularly when the pressure came from senior leaders. She tended to make decisions about technical platforms without consulting her engineering peers enough, even though almost every time she did consult them, the conversation changed her thinking. She tended to commit to timelines based on optimistic execution rather than realistic execution. She tended to do well at decisions involving customer-facing creative work and to do less well at decisions involving operational infrastructure.

Some of these patterns surprised her. She had thought of herself as good at cross-functional coordination. The data from her own reviews told her otherwise. She had thought of herself as resistant to senior pressure. The data told her she was more responsive to it than she realized. These were not weaknesses she had been hiding from others. They were weaknesses she had been hiding from herself, and they had been quietly shaping her decisions for years.

What She Changed

Within six months of starting the practice, her decision-making had shifted in concrete ways. She started adding buffer to timelines that required cross-functional coordination. She started consulting her engineering peers earlier and more deliberately. She started questioning her own urgency in responding to senior pressure, asking whether her response was really warranted by the situation. She started being more skeptical of her own optimism about execution and more deliberate about realistic planning. She started bringing more discipline to operational decisions because she knew this was an area where her instincts were less reliable.

Over the following year, the effects compounded. Her decisions started producing better outcomes more consistently. Her peers noticed. Her team noticed. Her own confidence in her judgment grew, but in a calibrated way: confidence about the kinds of decisions she had developed strength in, and humility about the kinds where her instincts were less reliable. She was no longer making decisions on accumulated experience alone. She was making them on refined judgment built through deliberate reflection.

Two years after she had started the practice, she reflected: "I had been operating for years without really learning from my own decisions. I thought experience was the same as growth. It is not. Experience accumulates patterns. Reflection turns experience into judgment. I have grown more as a decision-maker in these two years than I did in the previous five. And the practice that produced the growth was a fifteen-minute Friday afternoon habit and a quarterly pattern review. That is it. No special training. No course. No mentor. Just the discipline of actually looking back at my own decisions. I cannot believe I waited so long to start. And I cannot imagine ever stopping. This practice has changed how I lead and how I will continue to develop for the rest of my career."

Learning

This scenario illustrates the central truth of reviewing outcomes and learning from decisions. Most leaders do not do this work. Most leaders accumulate experience without converting it into refined judgment. And most leaders, as a result, find that their decision-making capability plateaus after a few years and stays largely the same for the rest of their careers. The leaders who build a deliberate review practice produce something different. Their judgment improves continuously across years and decades. They become more calibrated about their own strengths and weaknesses. They become more capable of making decisions in areas where their instincts are less reliable. And they become, over time, leaders whose decisions can be trusted because they have done the slow patient work of refining their judgment through deliberate reflection. This is what reviewing decisions makes possible. And it is available to any leader willing to invest a small amount of time, consistently, in the discipline of looking back at the choices they have made.

Reviewing Outcomes and Learning from Decisions Checklist

Self-Reflection Questions

Use these questions to think about your own practice of reviewing outcomes and learning from decisions.

1. How often do I pause to look back at my decisions and examine what happened?
2. What is my current rhythm for reviewing decisions, if any?
3. How well do I separate the quality of a decision from the quality of its outcome?
4. What patterns might exist in my decision-making that I have not noticed because I do not review my decisions?
5. What kinds of decisions do I tend to get right? What kinds do I tend to get wrong?
6. How honest am I in my reflections, or do I tend to defend my original thinking?
7. Do I capture lessons in writing or do I rely on memory?
8. Do I apply lessons from past decisions to current ones?
9. When was the last time I did a pattern review across many decisions?
10. What is one specific habit I will adopt to start building a more deliberate review practice?

Key Takeaways

• Reviewing outcomes and learning from decisions is the deliberate practice of looking back at decisions you have made, examining what happened compared to what you expected, separating the quality of the decision from the quality of the outcome, and extracting transferable lessons for future decisions.
• It has four essential elements: pausing to look back, comparing expectation to outcome, separating the decision from the outcome, and extracting transferable lessons.
• Most leaders do not review their decisions. They make decisions, move on to the next, and never extract the learning their decisions are offering them. As a result, their decision-making capability plateaus after a few years even though their experience continues to accumulate.
• Good decisions can produce bad outcomes. Bad decisions can produce good outcomes. The world is uncertain. Confusing decision quality with outcome quality is one of the most common reasons leaders fail to learn from their decisions.
• Different kinds of reviews fit different situations: quick individual reviews (3-5 minutes mentally), written personal reviews (a few sentences captured), team retrospectives (15-minute group conversations), strategic decision reviews (thorough examination of major decisions), and pattern reviews (periodic look at themes across many decisions). A good practice includes all of these at different rhythms.
• The components of a useful review are: reconstruct the decision, recall what you expected, examine what actually happened, evaluate the decision quality, evaluate the execution quality, identify the surprises, extract the lessons, resist overfitting, capture the learning, and apply the lesson to future decisions.
• Building the habit requires structure: build it into your calendar, make it lightweight, connect it to existing rhythms, use simple prompts, track patterns across reviews, share some reviews with peers, and be patient with the habit.
• Common mistakes include skipping reviews entirely, reviewing only dramatic decisions, confusing decision quality with outcome quality, defending the decision rather than examining it, hindsight distortion, overlearning from one decision, self-flagellation, blaming others, vague lessons, not capturing lessons, not applying lessons, and reviews that become politics.
• The practice does not require special talent, new skills, or significant time. Fifteen minutes a week of structured reflection, sustained over months and years, produces dramatic compounding effects on the quality of a leader's judgment.
• The leader who builds a deliberate review practice produces something rare: a track record of continuously improving judgment across many years. Most leaders accumulate experience. Few convert that experience into refined judgment. The discipline that distinguishes the two is the willingness to look back at decisions honestly and extract their lessons.
• Over the long arc of a career, this discipline becomes one of the most distinguishing features of leaders whose judgment is trusted. They are the people whose decisions tend to work out more often than chance would predict, not because they are smarter, but because they have spent years refining their judgment through deliberate reflection on what worked, what did not, and why.
• The practice is one of the most accessible and most powerful capabilities in leadership development. It is available to any leader willing to invest a small amount of time, consistently, in the discipline of looking back at the choices they have made and extracting what those choices were trying to teach them.

Conclusion

Reviewing outcomes and learning from decisions is one of the most quietly powerful disciplines in leadership. It does not require special talent. It does not require new skills. It requires the willingness to slow down, after a decision has played out, and look honestly at what actually happened. What you expected. What you got right. What you got wrong. What you would do differently. This work takes very little time. It produces enormous returns. And over months and years and careers, it compounds into the kind of judgment that distinguishes leaders whose decisions continue to improve from leaders whose decisions plateau after a few years and stay the same for decades.

A leader who has developed this discipline thinks about decisions differently from a leader who has not. They see each decision as a small experiment that will produce data. They expect to learn from it regardless of the outcome. They build the time into their week to capture the learning. They look for patterns across many decisions, not just lessons from individual ones. They distinguish honestly between good decisions that produced bad outcomes and bad decisions that produced good outcomes. They extract specific lessons that they can actually apply. They capture those lessons somewhere they can return to. And they bring the lessons forward into the next decision of similar kind. Over many years, this practice produces leaders whose judgment grows in ways they can name and whose decisions can be trusted because the judgment behind them has been deliberately refined.

The most important lesson is this: Experience is not the same as growth. Most leaders accumulate experience throughout their careers. Few convert that experience into refined judgment. The difference between them is the discipline of reflection. The leader who makes hundreds of decisions a year and never looks back at any of them has hundreds of opportunities to learn that are slipping past them every twelve months. The leader who builds a fifteen-minute weekly habit of reviewing those decisions captures the learning that the others are losing. Over a year, this is the difference between accumulating experience and building judgment. Over five years, it is the difference between a leader who has become more confident and a leader who has become more capable. Over a career, it is the difference between leaders whose judgment is trusted and leaders whose judgment is merely tolerated. Most leaders never build this discipline because the cost of not having it is invisible. You do not see the decisions that would have gone better if you had been learning from your previous ones. You do not see the patterns you would have noticed if you had been reviewing your work. You do not see the judgment that you would have developed if you had been investing in your own reflection. But the cost is real, and it accumulates silently across years. The leader who develops this discipline produces something rare: a track record of decisions whose quality improves visibly over time. Practice this discipline. Start small. Fifteen minutes a week. A few sentences in a notebook. Quarterly pattern reviews. Team retrospectives at the end of significant projects. That is enough to start. Build the habit gradually. Allow it to become a permanent part of how you lead. And let it compound over months and years into the kind of refined judgment that no amount of unreflected experience can match. The chapter ahead will close with a summary that brings the entire arc of decision-making and accountability together. But this article has given you something essential. The recognition that decisions are data. The willingness to capture the data your own decisions are generating. The discipline to extract the learning that the data offers. And the patience to build a practice that pays returns over years rather than over weeks. Hold this practice carefully. Develop it steadily. And let it become one of the most valuable habits you carry through the rest of your leadership career. Because in the end, the leader you become is, more than by almost anything else, shaped by what you have learned from your own decisions over the long arc of your work. Most leaders never extract that learning. You can. Start now. Review your most recent significant decision in the next twenty-four hours. Capture the lesson. Then do it again next week. Then again the week after that. And let the cumulative effect of this practice produce the leader you are capable of becoming through the slow patient refinement of your judgment, decision by decision, across the years that lie ahead of you.