These are the principles I return to when thinking about technology, organisations, and how work actually gets done. They’re not universal truths, but they’ve held up across enough projects that I trust them as a starting point.

Process before tooling. Most companies don’t have a technology problem. They have a process problem dressed up as a technology problem. The tool won’t fix the handoff that nobody owns, the step everyone skips, or the decision that keeps getting re-litigated. Map the process first. Then decide what tool (if any) you actually need.

Build, don’t only describe. I still configure systems, wire automations, and stay close enough to delivery to know whether the idea works. Strategy documents and architecture diagrams are useful, but they’re not the work. The real test is whether the thing runs, whether people use it, and whether it produces the outcome you said it would.

Discovery is the whole game. Talk to sales, marketing, operations, and the people doing the work. The stated problem is rarely the whole problem. What leadership describes in a steering committee and what the team experiences on a Tuesday morning are often different things. You can’t solve a problem you don’t understand, and you can’t understand it without talking to the people who live in it.

Use what already exists. The gap between what companies buy and what they actually use is enormous. Most organisations are sitting on capabilities they’ve already paid for but never properly adopted. Before adding something new, look at what’s already there. The fastest path is often through existing systems, not around them.

Small teams move. Fewer meetings, faster decisions, nowhere to hide. One person who builds and thinks is worth a team that only coordinates. The best work I’ve seen came from small, focused groups where everyone understood the outcome and had the autonomy to reach it. Scale the team only when the constraint is capacity, not clarity.

Visibility creates alignment. When teams can see the same work, the argument changes. It stops being about who said what and starts being about what’s actually happening. Shared visibility doesn’t solve every disagreement, but it removes the ones that exist only because different people have different information.

The constraint is often imagination. Most companies underestimate what’s possible with what they already have. The people, the systems, the data, the relationships: there’s usually more leverage in the existing situation than anyone has mapped. The gap isn’t always resources. Sometimes it’s just the belief that things could work differently.