How I work
Before any plan, I listen. Once I understand what you and your business really need, we chart the path forward together.
Discovery ends in a blueprint. The plan carries guardrails into the Roll out. The data collected in Review recasts the plan, because the business keeps moving.
Tap a step to see what happens in it.
From inside the day to day, it's hard to see the whole picture. Discovery steps out of the weeds long enough to see how the business really runs, so we fix the cause and not the symptom.
You and your leadership team, or a department lead. And me. The number of sessions depends on the size of the problem.
Symptoms aren't always the root cause. Every request gets one question before any answer: what is this really for?
A blueprint of where things stand today, agreed by the people in the room.
The blueprint shows everything. The roadmap decides what goes first, ranked by the value it unlocks against the effort it takes, and how deep each fix needs to go.
The same people as Discovery, so the plan belongs to the team that has to run it.
If the plan only works with the owner in every decision, it isn't finished yet.
A structured roadmap with owners, guardrails and safety checks.
Alerts on website traffic, leads and visits. Regular check ins and one to ones, plus people on the team who keep a good pulse of the ground. Leadership meetings where everyone hears the goals for the year and the quarter, with incentives tied to them, so everyone rows in the same direction.
The plan goes live in the order the roadmap set. Guardrails are the checkpoints and fail safes that tell you early when something drifts, instead of when a customer complains.
Your team does the work. I stay close, coach the people leading it and, where it helps, build the tools myself.
A guardrail nobody looks at is decoration. Each one has a name next to it.
The plan running, with signals that tell you early if it slips.
The business at review is not the one we mapped at the start. Markets move, people change roles, and some fixes work better than others. So we review on a set rhythm and feed what we learn back into the plan.
The leadership team and me, on a rhythm we agree up front.
Reassessing isn't admitting failure. It's how a plan survives contact with a real business.
An updated roadmap, and a team that knows how to run this loop without me.
Inside the plan
Not every problem needs a transformation. Some need a tune up. The expensive mistake is tuning when the design is the problem, or redesigning what only needed a tune up. Discovery tells us which depth fits. You decide.
Same goals, same model. The work itself runs better: a plan put in a better order, a cleaner handoff, a tool set up properly.
The process itself gets questioned. Who does what, in what order, who decides, and which tools carry it.
What you offer, who you serve or how you win work changes, because what you've built makes something new possible.
Why the depth matters. The organizational theorist Chris Argyris compared simple fixes to a thermostat that switches on the heat when the room drops below 68 degrees. Deeper learning is the thermostat asking why it's set at 68. He found that capable, successful people are good at the first kind and often bad at the second. A tune up is the first kind. A redesign or a pivot is the second.
Real cases, names left out on purpose
What gets asked for is rarely what's needed. Each case shows the symptom the client saw, and the cause Discovery found, on the same People, Process, Technology and Data model.
A global company was about to let its data and analytics agency go.
It was People and Process.
What I did. I interviewed the teams on both sides and drew how the work actually ran. Nobody had seen it whole: departments inside the company that didn't talk to each other, and no communication process between the company and its agencies.
What changed. A newly defined process with the client inside it, a cross functional team and a governance rhythm. The agency won back the client's trust and nearly tripled its revenue in three years.
A client wanted a redesigned, rebranded website with new products in under half the agreed time.
It was a meeting nobody had mentioned.
What I did. Instead of saying no, I asked what the date was for. There was a big meeting where the client needed to show progress, and it never came up when the contract was signed. The analytics team pulled the site's own data: the highest traffic pages and the ones with the most structural weight.
What changed. Those pages were finished first. The client made the date, and the agency learned how to serve them better.
An agency needed six to eight months or more before a new client saw a single report.
It was nothing being named the same way twice.
What I did. Every client, team and department named its databases, tables and fields differently, so every project started from zero. I designed a data accelerator: ready models such as customer lifetime value and churn, mapped to specific fields and built by industry.
What changed. A new client supplied a feed or an API, or the team built the fields it needed, and visualization started within weeks. It became a differentiator and helped win new business.
A property management team spent its week chasing clients for paperwork.
It was tools that didn't talk to each other.
What I did. Onboarding and resident information lived in separate subscriptions. I built them an onboarding tool in Claude that tracks what each applicant still owes and reminds them, on desktop and mobile, in their brand. Then a team dashboard of every client's progress, and one for each property owner showing what the team does for them.
What changed. Owners renewed without hesitation, trust grew, they added services, and revenue rose 18% year over year.
A window installation company's jobs lived in spreadsheet exports from its estimating app, and sales tax dates had to be worked out job by job.
It was Data sitting where the team couldn't use it.
What I did. I built a jobs and sales tracker on top of the exports. From each job's description, cost and timeline it estimates when sales tax is due and how much, and it updates itself from the start and finish dates the team enters.
What changed. The team chats with it like a colleague for answers, reminders and follow ups, and what they discuss is logged back into the tracker.
It depends on the size of the problem. For a small business it's often a few sessions. Typically, the blueprint and the roadmap are done before anything rolls out.
You and your leadership team, or a department lead. The people who will run the plan should help build it.
Both. Where a tool would help, I build it, often in Claude, like the property management onboarding tool on this page.
They usually do. That's why Review and reassess is its own step, and why the roadmap loops back to planning instead of ending.
The four steps are the same. What happens inside them, and how fast, depends on the door you came through.
20+ years leading change for Fortune 500 brands and growing businesses. Now I work with owners and leaders directly, and I build with Claude every day.
In person across Orange County, South LA and San Diego. Online anywhere.
Tell me where you are, where you want to be and what's in the way. No pitch. I read every note myself.
