Read time: 5 minutes

We keep doing things the way we always have, long after they have stopped fitting. Not because we are careless, but because they worked once, and it rarely feels like the right moment to stop and ask whether they still do.

It is like finding clothes at the back of the wardrobe that belonged to an earlier version of you. Nothing is wrong with them exactly. They have just stopped fitting, and somehow they keep their place on the rail.

You see it everywhere. The standing meeting nobody remembers starting. The subscription you forgot you were paying. The routine that suited the person you were three years ago and quietly stopped suiting the person you are now. I noticed my own version recently, when I opened an old status pack and found sections I used to swear by, a report format and a way of asking for updates, each one built for a problem that had long since moved on.

I could remember why all of it existed. That was the awkward part. None of it had arrived by accident. Every piece had a reason, a moment where it solved a real problem. But the problem had moved on and the format had stayed behind, quietly asking for attention every week.

We expect growth to feel like addition. A better tool. A sharper habit. A cleaner framework. We look for the thing that will make us more capable and more ready for the next version of the work.

I think a lot of improvement looks like this. Yet the harder move is often removal.

James Clear, the author of Atomic Habits, once wrote about improvement requiring unlearning. He used the phrase "gentle elimination" for the habits, beliefs, and patterns that may have belonged to who we were, not who we are trying to become. I liked that phrase because it does not make removal sound brutal. It makes it sound honest.

There is a kind of kindness in leaving something behind well. That matters because most things we carry are not obviously bad. If they were, removal would be easy. The difficult ones are the processes, meetings, documents, habits, and behaviours that still have a trace of usefulness in them. They are expensive in a way we have stopped noticing.

A weekly meeting that made sense during a crisis can become a ritual no one wants to challenge. A detailed report that once gave clarity can become a place where energy goes to disappear. A way of asking for updates can keep surviving long after the team has outgrown it.

So we add. We add a shorter meeting before the long one. We add a new tracker beside the old tracker. We add a summary page because the report is too long, then keep the report anyway. Soon the work is wearing too many layers.

I have done this in my own life. I have tried to solve a heavy calendar with better calendar management. I have tried to solve unclear priorities with a more detailed list, when the more useful question was what could leave.

There is a small fear underneath this. Removing something means admitting that a previous version of you made a choice that no longer works. That can feel uncomfortable, especially when the choice helped at the time. It is easier to keep carrying it and call the extra weight experience. But experience is meant to make your judgement lighter.

In project work, this shows up everywhere. The team is rarely held back only by the capability it has not added yet. Often it is held back by the behaviours it has not retired. The inherited meeting that exists because cancelling it would require one awkward conversation.

Gentle elimination starts with noticing the weight without shaming the reason it got there. That distinction feels important to me. If you attack the old thing, people defend it. If you acknowledge why it once helped, there is more room to ask whether it is still helping now. The tone changes from criticism to care.

"This served us for a while" is a very different sentence from "why are we still doing this?" The first gives people a way to let go without feeling foolish. The second can turn a practical improvement into a small trial. Removal can feel like judgement.

That is why the elimination has to be gentle. Gentle does not mean vague. It means precise. It means retiring one thing cleanly rather than declaring war on everything. It means asking whether a meeting has a current job, or whether a habit is still earning the space it occupies.

The best people I have worked with are good at this. They do not make improvement feel like a bonfire. They make it feel like opening a window. A little more air comes in.

Sometimes they remove a recurring meeting and replace it with a short note. Sometimes they cut three slides and the conversation gets clearer. Sometimes they stop asking for an update in one format because the answer already exists somewhere better.

The gain is not always dramatic. It is a few minutes returned here, a decision made faster there, a little less friction in the week. But those small removals change the feel of the work. People stop having to step around things that no longer matter.

There is a personal version of this too. The identity we carry into work can become outdated before we realise it. The person who always says yes because they once needed to prove themselves.

Those patterns may have protected you once. At some point, protection can become restriction. A habit that helped you survive one season can quietly limit the next one.

I find that strangely hopeful. Improvement does not always require a bigger push. Sometimes it begins with a smaller load. You may simply have to retire one thing that keeps asking for energy it no longer deserves.

And maybe that is the quiet challenge for this week. Before adding another tool, meeting, tracker, habit, or promise, look at what is already in your hands. Some of it still belongs there. Some of it carried you this far. Some of it can be thanked and left behind.

The project may not be waiting for more. It may be waiting for less.

MAKING IT HAPPEN: Your Weekly Strategy

This week, take ten minutes to look at what you are still carrying, and notice what has quietly stopped fitting.

Pick three things you have been carrying for the longest. A meeting, a report, a habit, a format, a decision route, anything that feels familiar enough to avoid scrutiny. For each one, ask one question: if I started this role fresh today, would I deliberately add this?

If the answer is no, design the smallest clean retirement. Cancel it for two weeks. Merge it into something that already exists. Cut one section. Change the frequency. Ask the people affected what they would lose if it disappeared.

The aim is not to strip the work bare. The aim is to create a little more room for what still matters.

CHEAT SHEETS

The free cheat sheet library is here. I'll keep adding to it. Save the link and grab whatever helps.

If this one landed, forward it to someone who is carrying something that used to help but now quietly gets in the way.

bilaljamil.com | Newsletter archive

Hit reply and tell me one thing you are ready to retire this week. I read every one.

Have a great week and speak soon,

Bilal