There is a skill that rarely gets talked about in leadership development programmes, team workshops, or performance reviews. It isn’t glamorous. It doesn’t have a catchy acronym. But when you look closely at the people and teams who consistently perform well in complex, uncertain environments, this skill is almost always present.
It is the ability to reflect, to step back from what you are doing long enough to notice how you are doing it, to examine your own assumptions before they lead you somewhere unhelpful and to learn from experience in a way that actually changes what you do next, rather than simply confirming what you already believed.
Reflection is the skill that makes all the other skills work better. Without it, people keep repeating the same patterns. With it, they keep getting smarter.
What reflection actually is
Reflection, in the context of the i2 Skills framework, is not the same as thinking hard about something. It isn’t rumination, it isn’t sitting quietly hoping for insight and it is definitely not the kind of vague journaling exercise that makes busy professionals roll their eyes.
Reflection is a specific, learnable capability. It is the ability to notice your own thinking patterns, test your own assumptions, learn from what has happened and adjust your approach based on what you discover. It operates on two levels.
The first level is what researchers call reflection in action. This is the ability to notice what is happening while it is happening, to catch yourself in the middle of a conversation and realise you have stopped listening. To notice that you are defending an idea not because it is good but because it is yours. To recognise that the team has drifted from the actual question into a more comfortable but less useful discussion. This kind of real time self awareness is surprisingly rare, and it is enormously valuable.
The second level is reflection on action. This is the ability to look back at an experience and extract genuine learning from it. Not “what went wrong” in a blame sense, but “what patterns do I notice? What assumptions was I making? What would I do differently?” This is what turns experience into capability. Without it, someone with twenty years of experience may simply have one year of experience repeated twenty times.
What reflection is not
It is worth being clear about what reflection is not, because the word carries some baggage that can put practical, action oriented people off.
Reflection is not navel gazing. It is not about sitting in silence for an hour contemplating your feelings. It can take thirty seconds. It can happen in the middle of a meeting. It can be as simple as pausing before you respond to a question and asking yourself: “Am I about to give the honest answer or the easy one?”
Reflection is not hesitation. Reflective people are not slow or indecisive. In fact, research suggests they tend to make better decisions faster, because they have a clearer picture of their own biases and blind spots. They do not need as long to course correct because they catch problems earlier.
Reflection is not the same as feedback. Feedback comes from other people. Reflection comes from within. They complement each other, but reflection is the skill that allows you to actually use feedback rather than just hear it and move on.
And reflection is not something only introverts are good at. It is a behaviour, not a personality trait. Extroverts can be excellent reflectors. They might just do it out loud rather than in their heads.
Why reflection matters now
Every working environment is getting more complex. The problems people face are less predictable, more interconnected, and more ambiguous than they were ten years ago. AI is handling more of the routine cognitive work, which means the tasks that land on people’s desks are the ones that require genuine judgement.
In that kind of environment, the ability to learn quickly from experience is not a nice to have. It is a core capability. Teams that reflect well adapt faster and leaders who reflect well make fewer repeated mistakes. Individuals who reflect well develop more quickly than those who rely on talent alone.
There is also a relationship between reflection and every other skill in the i2 framework. Opportunity seeking improves when you reflect on how quickly you narrow your focus. Collaboration improves when you reflect on how well you actually listen. Scientific reasoning improves when you reflect on whether you are testing ideas honestly or just confirming what you already believe. Reflection is the meta skill. It is the one that accelerates all the others.
This is supported by the research. Dr Jeanne Liedtka’s work at the University of Virginia’s Darden School of Business which has consistently shown that reflection is one of the strongest predictors of innovation capability. People who score higher on reflection also tend to show stronger growth across the other skill clusters over time. They learn faster because they learn from themselves.
How reflection shows up in practice
In individuals, reflection looks like a quiet pause before responding to a difficult question. It looks like a leader who says “let me think about that” instead of giving an immediate answer. It looks like someone who finishes a project and writes down three things they would do differently next time, not because anyone asked them to, but because they have built the habit.
In teams, reflection looks like a five minute debrief at the end of a meeting where someone asks: “How well did we think together today? Where did we get stuck? What should we try differently next time?” It looks like a group that is comfortable saying “we got that wrong” without turning it into a blame conversation.
In organisations, reflection shows up as a culture where learning from failure is not just tolerated but expected. Where post project reviews are honest rather than political. Where leaders openly share what they have learned from their own mistakes. This is rare, but the organisations that build it consistently outperform those that do not.
What it does not look like is adding another meeting to the calendar. Reflection is most powerful when it is woven into existing routines, not bolted on as a separate activity.
How to strengthen your reflection skills
The good news is that reflection is one of the most accessible skills to develop. It does not require expensive programmes or complicated tools. It does require intention and consistency.
Start with one question a day. At the end of each working day, ask yourself: “What is one thing I would handle differently if I could do today again?” Do not try to reflect on everything. Pick one moment. Be specific. Over time, this builds a habit of noticing your own patterns.
Pause before you respond. When someone asks you a question or challenges your idea, give yourself two seconds before you answer. That tiny pause is often enough to shift from reacting to responding. It does not slow you down in any meaningful way, but it changes the quality of your thinking.
Write it down. Reflection becomes more powerful when you externalise it. Keep a short running log of observations, not a formal journal, just brief notes. “Noticed I kept pushing my idea even after two people raised concerns. Why?” A few sentences like this, written regularly, compound into genuine self awareness.
Reflect with others. Some of the best reflection happens in conversation. Find a colleague, a coach, or a peer group where you can think out loud about what you are noticing in your own behaviour. The act of articulating it to someone else often reveals things you would not see on your own.
Use structured prompts. If open ended reflection feels vague, use specific questions to guide it. “What assumption was I making?” “What did I miss?” “What would someone who disagrees with me say?” “Where did I feel most uncomfortable today, and why?” Prompts like these give reflection focus and make it more productive.
A short example
A product manager at a technology company had a reputation for being decisive and efficient. She made quick decisions, kept projects on track, and delivered consistently. But her team’s innovation metrics were flat. They were shipping reliably but not improving. The same kinds of products, solving the same kinds of problems, in the same kinds of ways.
When she completed an i2 skills assessment, her reflection score was notably lower than her other capabilities. She was strong at execution but had not built the habit of stepping back to question whether she was executing on the right things.
She started small. At the end of each week, she spent ten minutes reviewing her major decisions and asking: “Was this the best option, or was it the most familiar one?” She started asking her team the same question in their Friday retrospectives.
Within a few months, something shifted. The team started surfacing ideas earlier. They began questioning briefs that previously would have been accepted without discussion. Two projects were significantly reshaped based on insights that emerged from these reflective conversations. The product manager’s efficiency had not decreased. But the quality of what she was being efficient about had improved considerably.
Questions to reflect on
Here are some prompts you can use right now, on your own or with your team.
- When was the last time you changed your approach to something based on what you learned from doing it, rather than based on new information from someone else?
- Think about a recent decision you made quickly. What assumption were you making? Was it tested?
- How often does your team talk about how they work together, as opposed to what they are working on?
- If you had to describe your default response to uncertainty, what would it be? Is that response serving you well?
- What is one pattern in your work that you keep repeating even though you suspect it is not optimal?
If any of these questions feel uncomfortable, that is worth noticing too. Discomfort is often a signal that there is something useful to learn.
