Helping teams regain control of complex software systems

You can think of me as senior technical judgment temporarily embedded into the team.

I work with teams whose software systems have become hard to manage, hard to change, risky to evolve, and where that complexity is starting to hurt the business.

Over time, many important systems grow under real-world pressure: changing priorities, tight deadlines, partial fixes, and workarounds that made sense at the time. Eventually, delivery slows down. Not because people lack skill or effort, but because the system itself has become difficult to reason about and make safe decisions around.

My role in these situations is to restore clarity, reduce uncertainty, and help the team regain control.

I have spent over two decades working with long-running software systems in product companies, agencies, and consultancies.

Over time, my work has centered less on specific technologies and more on judgment: understanding complex systems quickly, recognizing real risk early, and helping teams make decisions they can stand behind.

I work calmly and deliberately. I stay close to the system where hands-on involvement matters, and step back when perspective and framing are more valuable than activity.

Read more about my background

When teams typically bring me in

I am usually brought in when:

• A system or project is business-critical, but no longer feels under control
• Delivery is at risk due to technical complexity, accumulated debt, or unclear ownership
• The system has grown organically and no longer fits how the organization actually works
• Previous attempts to “fix it” did not work, or made things worse
• Rewriting everything from scratch is not a realistic option

In short: when something important needs to keep working, but clarity has been lost.

What I bring to these situations

My role is not to move fast or impose big changes.

I help teams regain control by:

• Building a shared understanding of how the system actually works today (not how people wish it worked)
• Making real constraints visible: technical, organizational, and budgetary
• Identifying where the actual risks are
• Distinguishing between problems that can hurt the business and those that are uncomfortable but safe to live with

From there, I work with the team to define a realistic path forward. Not an ideal solution, but a plan that can actually be executed with the people, time, and constraints you have.

How this usually works

My work is focused and often time-bounded.

Early on, I focus on understanding the system, its history, and how decisions are actually made. Changes come later, and only when there is shared understanding and a clear reason to act.

The goal is fewer unknowns, clearer priorities, and decisions that stop being guesses. The system becomes more stable, more predictable, and easier for the team to work with confidently.

When I leave, the business is in a stronger long-term position. I work closely with the team and make decisions in a way they can understand, own, and continue. I don’t create solutions that only work while I’m around.

Continuing the conversation

If this sounds relevant, the next step is simply to get in touch.

Send me a short message describing your situation and I will let you know how I might be able to help.