The Lessons Learned Session You Never Run on Yourself

We will happily spend two hours in a lessons learned session, taking apart a project that already ended, arguing about whether the delay came from the vendor or from the scope change nobody documented, and then go three or four years without running that same exercise on our own career.

The instinct is trained, and trained well. You can read a risk register and know where the trouble is before anyone says it out loud, you can look at a status report and feel in your stomach that the date is going to move, and you can sit in a steering committee and tell within five minutes who has already decided and who is still politely pretending to listen.

All of that attention points outward.
At the project, at the plan, at the team, at the stakeholder who went quiet.

So when was the last time you pointed it at yourself?

What follows is the short version of a reflection I run on myself, built around three questions. It takes about an hour if you are honest, and about fifteen minutes if you are not.

Start With Strengths, and Skip the Ones on Your CV

"I know Jira" is not a strength. It is a tool, and tools show up on every profile in your feed.

Your real strengths are the things you do so naturally that you barely notice doing them, and they hide in three places.

How you get things done. Which part of the delivery process could you teach a new team member tomorrow morning with zero preparation? That is not a random talent, that is the thing your brain has already automated, and it is usually the most reusable asset you own.

Why people trust you. Who comes to you first with bad news, and what did you do to earn that? People bring problems early only to the person who does not punish them for it. If that is you, it took years to build and it is worth naming out loud.

How you move direction without authority. Think of a room where priorities were a mess and the tension was real. What did you do that made the room settle? Whatever that was, it is leadership, even if your title says coordinator.

Write down one sentence for each. Three sentences, and most people find that two of them are things they have never put on a CV, a profile, or a promotion case.

Then the Uncomfortable Part, Which Is Your Patterns

Failures usually have external causes, and those causes are often real. The budget was cut, the sponsor changed, the vendor missed. I have used every one of those explanations, and some of the time I was right.

The question that actually moves your career is the other one...

What do I consistently do when things go wrong?

Two prompts here are worth more than all the rest.

The first: when a project starts sliding, what is your first move? Some of us take all the work back into our own hands. Some go quiet and stop communicating exactly when communication matters most. Some get defensive in front of the sponsor. You already know which one you are.

The second: when pressure rises, what is the first thing you stop doing? Documentation, one-on-ones, the gym, lunch away from the screen, the Friday review nobody checks.

The thing you drop first under pressure is almost always the thing that was keeping the pressure from compounding.

It is a bit like skipping the car service because you are already late for work. Saves you an hour today, costs you a Tuesday morning on the side of the road three months later.

And then the good pattern, which almost nobody documents. Think about your best work in the last two years, and describe the conditions around it. Team shape, sponsor clarity, how much autonomy you had, how rested you were. Most of us treat great outcomes as luck. They are usually a recipe, and a recipe can be requested.

Name Your Gap, and Be Honest About Which One It Is

Gaps are not weaknesses. They are the places you stopped growing because the next step requires something uncomfortable, and there are three that show up again and again.

The strategy gap. Could you explain to someone outside your company, in plain language, why your current project matters to the business? And here is the sharper version of the same test: you are probably very good at managing risks to the schedule, the things that make a project late. Are you equally good at spotting the risks that make a project useless?

The influence gap. When you present to the people who decide, do you talk about effort and detail, or about the outcome and your recommendation? A lot of us describe how hard the work was, hoping someone will draw the conclusion for us. They rarely do.

The knowledge gap. A tool, a certification, a domain you keep working next to without ever learning properly.
Now, notice something. The third one is by far the easiest to close, and that is exactly why so many of us pick it. Signing up for a course feels like progress, and it is real progress, but it is also a very comfortable place to hide from the strategy conversation or from the executive you have been avoiding for eight months.

One Page Beats a Plan

Reflection that stays in your head evaporates by Thursday. Compress everything into three sentences and one commitment.

My anchor strength is the one I will deliberately use and make visible in every project. My critical pattern is the one behavior I will interrupt. My primary gap is the single thing I will close, chosen on impact and not on comfort.

Then one measurable behavior change for the next 30 days, small enough to survive a bad week. Not "I will be more strategic", which means nothing on a Monday morning. Something closer to "I will not answer any non-urgent message before 10, and those two hours go to the work nobody is asking me for yet."

Three months on those three items beats five ambitious goals abandoned in week two. You already know this from projects. Scope discipline is not just for the plan on your screen.

The projects will keep coming, they always do, and nobody is going to book that hour in your calendar for you.

So, if you ran a proper lessons learned on your own last 12 months, with the same honesty you demand from your team, what would come out of it?