← All posts

How to be needed

In every team I’ve been part of, there’s one person whose absence everyone feels by Tuesday. They’re rarely the most brilliant one in the room. They’re the one people go to when something has to actually get done.

I’ve spent a lot of time trying to be impressive. It took me longer than it should have to notice that impressive and needed are different things, and only one of them keeps you employed, booked, and called back.

Impressive is about you. Needed is about them.

Impressive is what people say when you leave the room. Needed is what they feel when you’re not in it.

You can be impressive by yourself — a clever project, a sharp opinion, a long list of skills. You can’t be needed by yourself. Being needed only exists in relation to someone else’s problem. That’s the whole shift: stop asking how do I look good, and start asking whose problem do I make go away.

People don’t need talent. They need someone who makes a specific problem stop being their problem.

This works whether you write code, run a shop, teach, cook, or manage people. The field changes. The mechanics don’t.

1. Find the pain, not the passion

Most of us choose what to get good at by what we find interesting. That’s fine for a hobby. For being needed, start from the other end: what keeps the people around you stuck?

Listen for the complaints that repeat. Nobody knows how this system works. The reports are always late. Customers keep asking the same question. We lose half a day every time this breaks. Every repeated complaint is a job description nobody has written yet.

Pick one and become the person who handles it.

2. Be predictable

This is the cheapest skill on the list and the rarest one in practice.

Do what you said, when you said. If you can’t, say so before the deadline, not after. That’s all. It sounds too simple to matter, which is exactly why so few people do it consistently.

Someone who delivers good work unpredictably is a risk. Someone who delivers decent work predictably is an asset. People build their plans around the second person — and once their plans depend on you, you’re needed.

3. Close the loop

Most work dies at ninety percent. The task is “basically done,” the email is “about to go out,” the bug is “almost fixed.”

Be the one who finishes. Then tell the person it’s finished. That second step — done, here it is, here’s what changed — is the part almost everyone skips, and it’s the part people remember. It means they never have to chase you, and not having to chase someone is a relief people will pay for.

4. Make other people’s work easier

The fastest way to become needed is to make someone else better at their job.

Write the guide nobody wrote. Clean up the file everyone dreads opening. Answer the question before it’s asked. Prepare the meeting so your manager walks in ready. None of this is glamorous, and that’s the point — it removes friction from people’s days, and they start routing everything through you because things go smoother when you’re involved.

5. Stand where two skills meet

Being the best at one thing is hard. Being good at two things that rarely sit together is much easier, and often more valuable.

A developer who can explain things to non-technical clients. An accountant who understands software. A nurse who can train others. A designer who understands the business numbers. Each skill alone has a crowd. The combination usually has a short queue — and when someone needs exactly that combination, there’s only you.

The simple test

Ask yourself one question: if I disappeared for a week, what would stop working?

If the honest answer is “not much,” that’s not a judgment on your worth. It’s just information. It tells you there’s no problem yet that you own.

So pick one. Something small, real, and annoying to the people around you. Make it reliably yours, finish it every time, and tell them when it’s done.

Start there. Being needed isn’t a personality. It’s a habit of making problems disappear, repeated until people stop imagining the work without you.