About

Code to community to customer experience

Spend enough years watching people try to figure things out online, and a pattern shows up.

The person stuck was rarely the problem. They were smart, motivated, already doing the work. What stopped them was the thing around them. A dead-end search. An answer living three clicks from the question. A path that quietly stopped being designed.

So I started building the thing around them instead.

But unsticking people was only half of it. The other half was the people already doing great work in the dark. The researcher with the answer nobody could find. The peer whose fix solved it for a hundred others. Systems that let capable people carry everyone else and never put them forward.

So the job became the whole loop. Clear what stops capable people from moving. Surface the ones worth surfacing. Give them a path to contribute back. The person you help today becomes the one whose answer helps the next hundred.

That's an ecosystem. The value isn't in any one surface. It's in the people, the knowledge, and the trust between them, and it compounds.

"You do not rise to the level of your goals. You fall to the level of your systems." — James Clear

What I believe

What I Believe

• · Customers should not have to become the integration layer between your teams and tools.
• · Better self-service moves the system closer to the customer's intent.
• · The system has one job: keep customers moving toward their intent. Friction is the only thing that stops them — and help is what happens when momentum breaks. Recovery, not the goal.
• · Every re-login, re-explanation, and dead-end search is a tax your customers pay for your architecture choices, and it shows up on your cost-to-serve.
• · You don't rise to the level of your growth goals. You fall to the level of your customer experience systems.
• · A system that doesn't learn from its own friction will repeat every failure at the scale of every new customer.
• · Dropped context is the most expensive friction there is. Every re-login, re-explanation, and ungrounded AI answer is the system making the customer re-supply what it should have carried.
• · AI doesn't fail because the model is weak. It fails because the knowledge, routing, escalation, and governance underneath it are broken.
• · AI readiness is about what you own, not which model you pick. Own the knowledge and routing layer and your AI runs on a foundation that outlives any single tool.
• · CX is an ecosystem, not a department. You engineer the system; the ecosystem — customers, peers, partners, agents — lives on top of it.
• · Community is one subsystem of the customer ecosystem — people, knowledge, and the trust infrastructure between them.
• · A good fix should become infrastructure, not another workaround.
• · Don't accept the defaults.
• · EX = CX. The same loop runs internally. When teams can’t share knowledge or skills, and internal friction goes unautomated, customers feel it as wait time and inconsistent answers. You can’t build the customer ecosystem without building the internal one.

Current work

Where the work lives