Reflective Competency: Learning From Your Own Experience
Experience isn't the same as learning
We like to think that time on the job makes us better at it. Ten years in, surely we know more than we did in year one. But anyone who has worked alongside a long-serving colleague who keeps making the same mistakes knows this isn't automatic.
Experience only becomes learning when we stop and make sense of it. That capacity to pause, look honestly at what happened, and change how we act next time is what we call reflective competency. It is one of the quietest professional skills, and one of the most powerful.
What reflective competency is
Reflective competency is the ability to examine your own practice (your actions, decisions, assumptions, and reactions) and use what you find to keep improving. It goes beyond asking "did that go well?" to asking why it went the way it did, and what that says about how you work.
It has three layers:
Awareness: noticing what you did, thought, and felt in the moment.
Analysis: questioning the assumptions, values, and patterns underneath.
Action: turning insight into a concrete change in how you practise.
Many professions now treat it as a core requirement. Health, education, social work, counselling, and leadership frameworks often expect practitioners to show evidence of reflective practice, not just technical skill.
Where the idea comes from
Three thinkers shaped how most professions talk about reflection today.
John Dewey argued early in the 20th century that we learn not from experience itself but from thinking carefully about it. That idea sits underneath everything that followed.
Donald Schön, in The Reflective Practitioner (1983), drew a useful distinction. Reflection-in-action is thinking on your feet: adjusting mid-conversation when something isn't landing. Reflection-on-action is looking back afterwards to understand what happened. Skilled practitioners do both.
David Kolb (1984) described learning as a cycle: a concrete experience, reflective observation, forming new ideas, then trying them out. Graham Gibbs (1988) built on this with a six-stage reflective cycle (description, feelings, evaluation, analysis, conclusion, action plan) that is still widely taught in health and education training.
What it looks like in practice
Reflective competency is rarely dramatic. It shows up in small, everyday moments:
A team leader notices she talks over one quiet staff member in meetings, and asks herself why.
A support worker feels unusually frustrated with a client, and recognises the client reminds him of someone from his own past.
A trainer's session falls flat, and instead of blaming the group she reviews how she pitched the content.
A manager asks for feedback after a difficult conversation, and actually listens to it.
In each case, the person turns their attention back on themselves with curiosity rather than blame. That is the heart of it: treating your own practice as something worth studying.
How to build reflective competency
Like any competency, reflection gets stronger with practice. A few habits make the biggest difference:
Keep a short reflective journal. Five minutes at the end of a day or week is enough. Write about one moment that stuck with you, not a full diary.
Use a simple structure. Three questions go a long way: What happened? So what does it mean? Now what will I do differently? (This "What? So what? Now what?" model, associated with Rolfe and colleagues, is easy to remember.)
Include your feelings. Emotions are data. Frustration, anxiety, or pride often point to the values and assumptions worth examining.
Seek other perspectives. Supervision, mentoring, peer reflection groups, and honest feedback show you what you cannot see alone.
Reflect on successes, not just problems. Understanding why something went well makes it repeatable.
Close the loop. Reflection that never changes behaviour is just rumination. End each reflection with one small, specific action.
Common pitfalls
Reflection can go wrong in a few predictable ways.
Harsh self-criticism. Reflection is not a tribunal. If every review ends in "I'm hopeless at this", you are more likely to avoid reflecting altogether.
Going through the motions. Reflective logs written only to tick a compliance box tend to be vague and safe. The value is in honesty, not polish.
Only looking inward. Sometimes the problem really is the system, the workload, or the policy. Good reflection considers context as well as self.
Endless looping. Replaying the same event without reaching a conclusion drains energy. Set a limit and move to action.
Start small, start this week
Reflective competency isn't a personality trait some people are born with. It is a skill, and it grows through regular, honest practice. The professionals who keep getting better over a whole career are rarely the ones with the most experience. They are the ones who keep learning from it.
This week, pick one moment from your working day and ask yourself: What happened? So what? Now what? Write down the answer. That's the first step.
