What 14 Years in Procurement Taught Me About Leadership

I did not learn leadership from a book. I learned it on shop floors, in supplier negotiations that ran past midnight, and in project rooms where one delayed shipment could stall an entire programme worth crores. Across thirteen plus years at GE, Baker Hughes and Air Liquide, most of it heading procurement and running projects, I figured out something that no leadership seminar had told me. Your title buys you almost nothing. How you behave when things go wrong buys you everything.

These are the lessons that have actually held up, and the ones I now work through with the founders and teams I coach.

Be clear, then be clear again

In procurement you learn fast that ambiguity is expensive. A vague specification becomes the wrong part sitting in a warehouse. A loose deadline becomes a missed one. The same is true of how you lead people. Most of what looks like a performance problem is really a clarity problem in disguise.

I run short, regular check-ins with my teams for exactly this reason, not to monitor people but to make sure everyone is solving the same problem I think they are solving. I also learned to listen before reacting. When someone brings you a problem, the instinct is to jump to the fix. The better move is to repeat back what you heard first. Half the time the person corrects you, and you realise the real issue was something else entirely. That one habit has saved me from more costly mistakes than any process ever did.

And you cannot fake this part. If you want a team that hits deadlines and stays calm under pressure, you have to be the one doing it first. People copy what you do, not what you say in the all-hands.

Treat disruption as the job, not the exception

If the last few years taught supply chain people anything, it is that the disruption is not a one-off event you wait out. It is the operating environment. I stopped treating change as a threat to be managed and started treating it as the actual work.

That mindset changes how a team behaves. When people are not afraid of things going wrong, they tell you when things are going wrong, early, while you can still do something about it. So I make it safe to surface bad news. I would much rather hear about a slipping vendor in week one than discover it in week six.

Two practical things matter here. First, give people the support and cover to deal with obstacles instead of leaving them to firefight alone. Second, mark the small wins out loud during a hard stretch. When a team is grinding through a tough quarter, recognising progress is not soft. It is how you keep people in the fight.

Lead by serving, not by sitting above

For a long time leade

rship in industry meant authority and control. The leader decided, everyone else executed. I do not believe that model produces good work anymore, and I am not sure it ever did.

The way I see it now, my job is to remove the things blocking my team and then get out of their way. Clear the obstacle, supply the resources, make the call they cannot make, and let them own the rest. That means pushing decisions down to the people closest to the work, trusting their judgement, and putting the team's outcome ahead of my own visibility. It is less flattering to the ego. It produces far better results.

Make decisions faster, and lower

Efficiency in a growing organisation rarely dies in one dramatic failure. It dies in a hundred small delays, most of them waiting for a sign-off that did not need to involve a senior person at all.

The single biggest unlock I have seen is delegating decisions to the lowest level where someone has the context to make them well. It speeds everything up and it tells your people you trust them, which is its own form of fuel. Pair that with a few honest numbers. Decide what good actually looks like, measure it, and review it on a fixed rhythm rather than by gut feel. You do not need a dashboard with fifty metrics. You need three that tell you the truth.

Keep working on yourself

The leaders I respect most are almost uncomfortably honest about their own gaps. They ask for feedback they may not enjoy hearing, and they act on it.

I set my own development goals the same way I would for any project, with milestones I can check against. I ask peers and mentors where I am getting in my own way. And I pay real attention to managing my own emotions, because a leader who loses composure under pressure gives the whole team permission to do the same. Emotional steadiness is not a personality trait you are born with. It is a skill you build, and it shows up most when things are hardest.

Break big problems into small ones

Complex problems are unavoidable when you are scaling. What separates people who handle them well is not raw intelligence. It is method.

When something feels overwhelming, I break it into parts small enough to actually attack, and I pull the team in to find the root cause rather than chasing symptoms. Bringing people into the problem does two things at once. It surfaces ideas I would never have reached alone, and it builds genuine buy-in for whatever we decide to do. Through all of it, I keep one eye on the long game. Solving today's fire in a way that creates tomorrow's is not a solution. It is a deferral.

The thread running through all of it

None of this is complicated, and that is rather the point. Lead with clarity. Expect disruption and stay steady inside it. Serve your team instead of ruling it. Decide faster and lower. Keep growing yourself. Break hard problems down and solve them together.

Do those consistently and you build something that does not just survive a difficult market but gets stronger in it. That, to me, is what leadership is actually for.

If these ideas are useful to you, there is more where this came from at Shelly Thoughts.