The process, frameworks and mental models I bring to every engagement — shared here so you know what to expect.
Working with a new vendor can feel like preparing for a hike without a map. I want you to know what to expect at every turn so you feel comfortable taking the next step. Here I've outlined how we choose our heading, the path we take, and the pace we travel.
Every time I sit down with a client, I'm drawing not just on my formal education in Database Design and Financial Planning, but also on the experience, research and concepts that influence my work. Some came from patterns I've watched play out across dozens of engagements. Some of these came from books I've read. Some are based on evidence-based research on how people work. All of them influence how I design and build effective solutions.
I built this series because I, personally, prefer clarity when working with others. I want to know what happens next and my clients do as well. I also think it's important to understand that I don't just think about data - I focus intently on the user and how systems work in real life.
When you understand why I'm asking whether that workflow actually reduces friction for the Elephant, or whether the problem you're trying to fix is a symptom of something upstream, the solutions get better. And you will understand why this is just as important as the technical task or automation.
This isn't required reading. But if you want to understand how we collaborate and how I think about design this is a great place to start.
Before I dive into the frameworks and mental models, most clients want to understand the process itself. Here's a step-by-step look at how every engagement unfolds — from Discovery Call to final deliverable — and what you can expect along the way.
The Pareto Principle — and why a small number of operational improvements will do more for your firm than everything else on your wish list combined. How to identify your 20% before we start building.
Checklists aren't for people who don't know what they're doing — they're for people doing work complex enough that even experts miss steps under real conditions. Why this is the infrastructure beneath everything we build.
Every recurring problem is produced by a system. If you don't change the system, the problem keeps being produced. Why the clean CRM gets messy again — and where the real leverage actually lives.
The Rider plans, the Elephant has the power, and the Path determines whether change actually sticks. Why your workflows don't hold — and how to design for the way humans actually behave, not the way we wish they did.
Now that you know how I think — let's talk about what that looks like for your firm. Bring your list. We'll find your 20%, trace the system, and build for the Elephant.
Schedule a Call