About
I take ideas from zero to operational.
A builder with depth across every function a product requires, and the operating system to build continuously, not just once.
I build products, capabilities, and operating systems. The through-line across all of it is the same philosophy: treat whatever you are building like a product, something that gets shipped, learned from, and continuously improved.
I have spent 15 years accumulating depth across every function that building requires. I started as a digital transformer, learning how organizations work and why they resist change. I became a product deliverer, learning how to ship. A capability builder, learning how to change organizations across all four dimensions. A product builder, learning to write code and architect systems. A system builder, learning how to design and run a product operating model. And now an AI builder, using AI as a force multiplier across every layer of the work.
Each phase stacked on the last. None of them went away. That accumulation is what makes it possible to walk into ambiguity with no team, no process, no product, and build something operational that others can own and grow.
How I got here
A builder's origin story.
Each phase added a new layer. None of them went away.
2024 — Present
AI Builder
Built my own operating system — the methodology, frameworks, and tools that enable me to go into an organization and build capability systems and products. AI is the multiplier that makes one person able to do what previously required a team. Currently applying that OS to build DiverseCiti and APOLLO1, and to help organizations move to an AI-native operating model.
What I learned
The bottleneck is no longer capability. It is clarity. With AI, the limiting factor is how well you understand the problem, not how many people you have to work on it.
2021 — Present
System Builder
Moved from building individual capability systems to building the organizational operating system across a global organization — the system across capabilities that defines how an org learns, builds, and improves continuously. Designed and implemented operating models across functions, connecting how teams learn from customers to how they decide, build, and deliver.
What I learned
The organizational operating system is itself a product. Most organizations inherited theirs and never designed it intentionally. When you treat it like a product and improve it continuously, the org's ability to build and serve compounds over time.
2018 — Present
Product Builder
Learned to code. Started building products end-to-end, from architecture to deployment. Worked on APOLL01. Closed the gap between knowing what to build and being able to build it myself.
What I learned
That understanding how something gets built changes how you think about what to build. The best product decisions come from people who can see both sides. Start simple, launch, learn, and improve.
2015 — 2018
Capability Builder
Built and improved specific capabilities within organizations — each one designed across people, process, policy, and technology. A capability is not a tool or a role. It is a system built across all four dimensions that enables the organization to do something it couldn't do before, or do it better. Built capabilities across CRM, knowledge management, marketing operations, and customer engagement.
What I learned
Every capability is its own system. You can't fix the technology without fixing the process. You can't fix the process without addressing the people and policy around it. Change only sticks when all four dimensions move together.
2010 — 2018
Product Manager
Customer and market discovery, writing PRDs and BRDs, defining product vision and roadmap, product ownership, and scrum-based iterative delivery. Worked directly with engineering teams to prioritize backlogs, write user stories, and continuously ship and improve products. Ran the full product lifecycle from understanding what customers actually need to getting it built, shipped, and improved.
What I learned
That the best product decisions come from staying close to the customer throughout the build, not just at the start. And that owning a product means owning the outcomes, not just the backlog.
2010 — 2018
Project Manager
Digital transformation program management, IT project management, and Scrum Master across large-scale platform rollouts including CRM, customer engagement, and marketing technology. Process design, stakeholder management, requirements gathering, and coordinating delivery across cross-functional teams.
What I learned
How organizations actually move work through a system and why they struggle to. How to run structured discovery, facilitate executive conversations, and keep complex programs on track across competing priorities.