What 100 Days as a Head Taught Me About Saying No

My whole career was built on getting things done against all odds. As a developer I asked two questions: can this be done, and can I do it? As a lead developer I asked them for a whole team. I led fifteen developers, we planned the architecture together, and when the business brought us a problem we found a way and we delivered. I am proud of those years and of that team.

A Bigger Picture

A hundred days ago I became Head of Business Applications, and the questions changed. Leading a team taught me how to deliver well. Leading a portfolio is teaching me to decide what deserves to be delivered at all. I now carry the strategy, the architecture, the delivery and the operations for every application we own, and I have a specialist team that owns the technical side. Every yes I give lands on their desks.

I have seen over the years what happens when everything gets a yes. People burn out, morale drops, and the trust you worked so hard for starts to break, because more was promised than any team could carry. Needless to say, that is not what I want for mine.

Stop asking can this be done. Start asking should this be done.

The Two-Hour Trap

The big requests are not the hard ones to turn down. The hard ones are the small ones, the things I know could be done in an hour or two. Lately most of them arrive with AI attached, and they all sound urgent. The builder in me still wants to jump in. Now I have to stop and ask what the business value is and what impact it will have, and if nobody can tell me, it has to wait, even if it is easy and even if it is exciting.

It is a big shift and I am still learning it. Some days the old hat goes back on before I notice.

Enabler or Blocker

There is one more thing these hundred days have shown me. In this seat I can be a great enabler or a great blocker, and the difference is often very small. If every technical decision has to pass through me, I slow the team down and I take away the very thing they are good at. The team needs to own the tech. My part is to guide, to make the direction clear, and then to get out of the way.

My message to anyone stepping up from leading a team to leading the bigger picture is this: the skill that got you here was proving it can be done. The skill you need now is deciding whether it should be. Ask the question, and give your team the space to do the work that matters.

Written on November 16, 2026