Implementation consulting begins where strategy ends
Implementation consulting is not another method, it is a stance. It differs from classic strategy consulting in that it does not end with the handover of the concept but begins exactly there. And it differs from pure specialist consulting in that it does not solve a single specialist topic but orchestrates change across functions and levels of hierarchy.
“Strategy ends where implementation begins. That is exactly where we start.” That sentence is more than a claim, it describes the way of working. Implementation consulting is not measured by the quality of its presentations but by what remains in the company after the project.
From that follows a second principle that separates good implementation consulting from standard consulting: enablement instead of dependency. The goal is not the next follow-on assignment but an organization that can carry on by itself. Or, put pointedly: we have done good work when we are no longer needed.
That claim, however, can rarely be met by a single firm across the whole value chain. Anyone who steers programs at leadership and project level is not necessarily deep in lean methodology and operational value creation, and the other way round. This is where the partnership comes in.