Most business problems don't belong neatly to one team. Marketing, sales, operations, product and data can all work in isolation while the system between them becomes slow, manual, fragmented or difficult to see.
I work across those boundaries. Sometimes the problem is a campaign or customer journey. Sometimes it's a CRM, an operational process, a reporting layer, an internal tool or a product that doesn't exist yet. I care less about which discipline owns the problem than whether the whole thing works.
The common thread is systems thinking: understand the problem in context, account for the people using it, and make the commercial machine clearer, better connected and easier to run.
The tool comes later. I start with the people, the work, the decisions and the friction.
I've always been drawn to what's underneath. The structure behind the surface. The pattern nobody named yet. The thing everyone was working around without realising it was there. That isn't something I learned at work. It's simply how I tend to see things.
I've played piano since I was 9. It's one of the few things I do without trying to improve a system, solve a problem or explain the outcome. You sit down, the room goes quiet, and you play.
I'm neurodivergent, which probably explains some of the intensity. I can disappear into a difficult problem for hours, and I tend to notice connections between systems, disciplines and ideas that initially look unrelated.
I build things outside work too. Some ship. Some teach me something and get shelved. They usually start with a question I couldn't leave alone.
The section above is the output. This is the root system.