Someone asks for a simpler way to do something, then carries on using the spreadsheet they’ve complained about for years. A team likes a new product, sees where it could help, and still puts off adopting it.

There’s usually more going on. The spreadsheet is familiar. Changing means finding time, getting other people on board, and being responsible if it doesn’t work. Our better solution has arrived with a small project attached.

People can understand the value perfectly well and still not want to change how they work to get it.

I find those decisions interesting. What people are willing to try, what reassures them, and what makes them quietly return to the old way. A lot of what a business experiences as growth—or the lack of it—starts here.

People bring the previous experience with them.

By the time someone encounters a product, they already have expectations. The website has explained it a certain way. Sales has made a promise. Something they’ve used before has taught them what to trust and what to double-check.

No single perspective explains all of that. Neither does one moment in an experience. A hesitation today might have started with a conversation months ago.

From the customer’s side, the boundaries between brand, website, sales, and product aren’t nearly as clean as the teams working on them make them. Their confidence carries from one encounter into the next. So does their doubt.

Their experience with the product has to make that promise come true.

As the business grows, keeping that promise takes more deliberate work. Customers shouldn’t have to explain themselves again because two teams don’t share context, or work out which answer is correct because each department has a slightly different one.

This is what interests me about systems. Decisions made behind the scenes eventually become somebody’s experience. They also determine how much effort the business has to put into delivering it again.

That understanding has to lead somewhere.

I like bringing together what customers experience, what the business needs, and what the people building it know. Each can change how you understand the others.

Sometimes we need to explain something differently. Sometimes we need to ask less of someone, give them more information, or finally resolve a decision we’ve been leaving them to figure out. An insight should change what we do next.

This part can be chaotic. Pulling things apart, questioning an explanation I was quite sure about, and figuring out how the pieces could work better together is oddly my zen mode. It’s also why I work across product, brand, websites, and systems. The problem rarely stays within the boundaries of the brief.

There’s usually a point where we understand the problem better than we know how to solve it.

You try things, find out what you’ve missed, and gradually the understanding starts showing up in the work.

And then, sometimes, it feels obvious.

Something that took a lot of questioning and untangling starts to make sense. People see what’s possible. They know enough to make a decision. They can get on with what they came to do.

They may never know how much had to change for that to happen. But they feel the difference.

The experience gives them a reason to engage, to interact and to return.

I find a lot of joy in that. All those conversations, loose ends, and difficult decisions becoming an experience someone can take in their stride. What the business hoped to make possible starts becoming useful to someone.

That’s what draws me to ambitious businesses in the first place. The possibility of changing how something works, solving a problem that matters, or putting a little more joy into the world. I like being part of making that happen.