Capability building vs. consultant dependence: a decision framework
Every engagement either strengthens your team or creates dependence. Here's how to demand the first and avoid the second.
Last updated
The short answer
A good consulting engagement leaves your team able to make the next decision without the consultant. Insist that your people own decisions from the start, that every recommendation comes with its reasoning, and that your team runs the first stage of execution while the consultants are still available.
The dependence trap
Traditional consulting engagement: Week one, consultants arrive and take over. Your team becomes spectators. By week twelve, if someone asks how a decision was made, the answer is 'the consultant decided.' After they leave, your team has to reverse-engineer their own transformation plan. Sound familiar?
What capability building actually looks like
Week one: Your team and the consultants sit together. Consultants ask questions; your team answers them. Week four: Your team is making 80% of the decisions; consultants are asking 'have you considered X?' Week eight: Your team is leading; consultants are spotting edge cases. Week twelve: Your team runs it alone.
The test: can your team explain it?
Six months after the engagement ends, ask your finance person to explain the strategy without slides or consultant notes. If they stumble, you bought dependence. If they explain it confidently and spot problems independently, you bought capability.
What capability building requires
Four non-negotiables: (1) Your team owns decisions from the start, consultants advise. (2) Every recommendation comes with the reasoning, not just the output. (3) Your team runs the first 30 days of execution while consultants are still available. (4) Documentation captures why you decided that way, as well as what you did. That is how we run our technology advisory: we act as your sounding board and you make the decisions.
Red flags for dependence
Watch for these patterns: 'The consultant will handle that.' Key decisions made in consultant-only meetings. Final plans that your team doesn't fully understand. Implementation playbooks that require consultant interpretation. Post-engagement knowledge transfer scheduled for the last week. Any of these signals dependence, not capability.
The business impact
Strong internal capability means: faster decisions in year two (your team knows the reasoning, can adapt it to new situations). Reduced risk (your team spots problems before they compound). Ownership mentality (success is internal, not external). Cost savings (you stop hiring consultants for similar decisions).
Contract language that ensures capability
Before you sign: 'Engagement success is measured by our team's ability to lead similar decisions independently after this concludes. That means your recommendations must include the decision logic, not just the output. Our team will own 80% of execution by week six.'
How WaTo can help with this
Build lasting capability
We design engagements so your team owns the strategy from day one. You get both the solution and the strength to execute independently.
Mon to Fri, 8:30am to 5pm
