What The Power Trio Actually Is
I first ran into this framework about three years ago when a client asked me to streamline their operational workflow. They'd hired a consulting firm that kept referencing "Watkins Garrett And Woods" like it was some secret weapon. Turns out it's a triangulation methodology used to identify structural inefficiencies across organizations. The core idea is straightforward enough. You analyze any system through three overlapping lenses — the Watkins lens examines process flow and bottlenecks, the Garrett lens maps stakeholder incentives and misalignments, and the Woods lens tracks resource allocation against output quality. Where all three intersect is usually where the real problems live. Not where management expects them to.
Watkins Garrett And Woods Decoding The Power Trio Redefining Industry Paradigms
Here's how you actually run this without getting lost in abstraction. Start by picking one process. Not your entire operation. One thing. A product launch cycle, a client onboarding sequence, whatever burns the most time. Map the Watkins flow first — write out every step from trigger to completion, noting where handoffs happen and where work sits idle. This usually takes 30 minutes if you're honest about it, or 4 hours if you try to make it look pretty for a presentation. Then do the Garrett mapping. Go talk to the actual people doing the work. Not the managers. The ones who know why things take twice as long as they should. Find out who benefits from the current mess and who doesn't. Incentive mapping isn't about accusing anyone of being shady. It's about identifying where individual rationality creates collective irrationality. I found this out the hard way on a logistics project where the warehouse team's bonus structure literally rewarded them for ignoring cross-dock efficiency. Every individual action was perfectly rational. The outcome was terrible. Finally, the Woods layer. Pull the actual numbers — budget spend per stage, headcount allocated, output metrics. Compare resource against throughput. This is where most people skip ahead and build their slides. Don't. If you haven't done the first two, the numbers will just confirm your biases instead of correcting them.
The sweet spot is finding where all three data sets converge on the same problem. A bottleneck that appears in the process map, is sustained by misaligned incentives, and receives disproportionate resources without proportional return. That triple overlap is your intervention point. I've seen this method break down when applied too broadly. Once tried running it across a whole department and ended up with 200 pages of analysis that pointed nowhere actionable. The workaround was scaling back to one process at a time, then building up. It's not that the framework is wrong. It's that it generates a lot of heat and not much light unless you constrain the scope tightly. Budget two weeks for a thorough run on a single workflow, not two days for a company-wide sweep. Also worth noting — the Garrett lens only works if people actually tell you the truth during incentive mapping. In my experience, that requires one-on-one conversations, not group workshops. Group settings optimize for social desirability, not honesty. I stopped trying to get straight answers in meetings and started doing coffee chats with people who had nothing to lose by being direct.
Get the Full Details
The methodology doesn't come with a manual or a software tool. There's no branded platform. You need spreadsheets, willingness to have uncomfortable conversations, and the patience to sit with messy data before drawing conclusions. If you're looking for a clean PowerPoint template, you've come to the wrong place. What it does well is reframe problems that feel personal or political into structural issues. Once you can show a team that their bottleneck isn't incompetence but misaligned incentives visible across all three lenses, the conversation changes completely. You stop pointing fingers and start redesigning systems. That shift — from blame to architecture — is what makes this framework useful beyond academia.
