Operations Efficiency
The obvious fix isn't the real one. I find the actual bottleneck and build systems around it.
Most operations problems aren't what they look like on the surface. A founder tells me they need better processes, but the real issue is that they're the bottleneck for every decision. A team says they need more people, but the real issue is that new hires take months to become productive because nothing is documented. The obvious fix isn't the real one.
This is where cross-domain thinking changes the game. When Uber came to me needing to onboard Seattle drivers, the obvious solution was more space and more hours. But the actual problem was something nobody had thought to measure. Seeing the problem differently led to a 98% cost reduction.
That's what I do with operations: diagnose the real constraint, apply frameworks the industry hasn't seen, and hand you a playbook your team can run on their own.
How We'll Work Together
Diagnose the real bottleneck, not the symptom your team is describing, but the structural constraint underneath it
Design systems using cross-domain frameworks (throughput optimization, capacity planning, process engineering) applied to your specific context
Build the playbook so your team owns it: documentation, accountability structures, and KPIs that actually tell you what's working
- 1Diagnose the real bottleneck, not the symptom your team is describing, but the structural constraint underneath it
- 2Design systems using cross-domain frameworks (throughput optimization, capacity planning, process engineering) applied to your specific context
- 3Build the playbook so your team owns it: documentation, accountability structures, and KPIs that actually tell you what's working
Frequently Asked Questions
Ready to Find the Real Bottleneck?
Tell me what's not working. I'll tell you what I see.