Principles · Thinking · Work
How I think
People commit to outcomes when they understand what those outcomes will actually mean for them.
Before any work starts, I make sure everyone in the room understands not just where we're going, but what it's going to ask of them personally. That's what turns agreement into actual commitment.
Most people get stuck on what they can't control. That's what stops them from moving what they can.
Stuck usually isn't stuck. It's misplaced focus. Once you name what's actually in reach, people start moving.
Hard problems don't go away when you minimize them. They become manageable when you give them room to be hard.
Some of my best work has been on problems we haven't solved yet. Keeping a team honest, engaged, and willing to try again. That's not a consolation prize. That's the work.
Clarity is contagious. When you name your own motivations out loud, you give everyone else permission to do the same.
I don't just clarify the goal. I share why I personally care about getting there: what I'm hoping for, what I'm worried about, what success means to me. That kind of honesty changes the room. People stop performing and start contributing.
If getting value from something is hard work, it stops being valuable. Our job is to make the value obvious and accessible, not impressive and complex.
It's easy to mistake completion for value. Platform live, access granted, research running. We might call that valuable. But did it make their work easier? Did the journey feel worth it? We stay focused on both: the mechanics that make delivery efficient and whether the customer actually experiences the difference. Value isn't what we ship. It's what they feel.
I measure my success by how much easier I'm making it for the people around me. That includes my team, my customers, and the person I report to.
This started as pragmatism. Make the people around me more successful and my own growth accelerates. But what it actually taught me was something different: when everyone around you has what they need, the work gets easier, faster, and more creative. It stops feeling like managing up or down. It starts feeling like real partnership.
On AI
AI doesn't make you better. It makes you more.
That's the problem. It accelerates output but not judgment. It reduces the barrier to producing, not the barrier to producing something worth reading.
The people who use it best aren't the most technical. They're the most self-aware. They know their strengths well enough to amplify them, and their blind spots well enough not to.
I use AI to close my gaps, not paper over them.
Most people never do that audit. They adopt the tool and assume the output is better because it came faster. But speed isn't quality. And a well-written version of a flawed idea is still a flawed idea.
The question worth asking isn't "what can AI do for me." It's "what expertise am I actually applying, and is AI making that sharper or just faster."
The work
50% faster to value
The problem
The implementation process worked. Customers got live, teams hit their milestones. But customers were waiting 30 days to get value from a platform they'd already bought, because the process was built around our internal rhythm, not their time to value.
What we changed
We audited every step and asked a simple question: does this belong to us or to them? The complex, ambiguous, expertise-heavy decisions. We took those back. Built the internal capability to absorb them. Stopped leading with questions and started leading with recommendations. Customers brought the context. We brought the expertise, knowing what questions to ask, what was missing, and when to push them further than they'd pushed themselves.
The outcome
Time to first value dropped from 30 days to 15. Not because we moved faster, but because we put our effort in the right places and stopped asking customers to do work that was never really theirs to do. That shift became the model everything else was built on.
4/7 phases live in production
The problem
Implementation runs on repeatable phases, but the highest-friction moments (kickoff prep, status updates, audience structuring, handover documentation) were still being handled manually, every time, at every account.
What I designed
Mapped AI assistance to the specific friction points across a 7-phase implementation methodology. Built and deployed four tools, each targeting a distinct phase, and established a pipeline structure for future additions as new friction points are identified.
The outcome
Four of seven implementation phases now have active AI tooling in production. Recurring admin at each touchpoint is handled by the system. New capabilities are added against a defined methodology rather than as one-off fixes.
60% setup time reduction · 20→8 hours per deployment
The problem
Launching AI-powered Marketing Agents required manually reviewing and categorizing large volumes of client files, a 20-hour process that created a bottleneck before any customer value was delivered.
What I built
Designed and built a custom GPT that ingests client files at scale, recommends the appropriate agent association, and generates agent-ready content summaries, including making visual assets usable as structured inputs for faster processing.
The outcome
Setup time dropped from ~20 hours to 8–10. That compression reduced internal delivery cost and cut customer lead time — accelerating time-to-value on a flagship AI product for every new deployment.
0→1 visibility · pricing leverage gained
The problem
We had no idea where the time was actually going. Which meant every pricing conversation was a guess, scope had no floor, and the cost accumulation had nowhere to land.
What I built
Conducted an internal audit to define what needed to be measured and why. Designed a tracking framework from scratch, calibrated for accuracy, and built the measurement system that captured effort at enough granularity to surface real trends.
The outcome
Identified hidden effort sinks growing month-over-month. Provided the data foundation that defended scope in client conversations and justified price increases that previously lacked any supporting evidence.
Impact log
Ask Merlin
Powered by Claude · Usually instant