Dynamic projects demand that teams not so much follow plans as continuously rethink and reinterpret them, continuously collaborating on the way to value-driven results. Likewise, stakeholders and project managers must appreciate that clearly communicating their “command intent” has become more critical to success than dictating discrete orders.
“We spent as much money as we could, and got as little for it as people could make up their minds to give us.” — Charles Dickens, Great Expectations
Communicating command intent is no easier challenge, for all of the reasons stated in Part I of this series (see “Clabberation”) and more. What is command intent? It is not a requirement or a set of requirements, nor is it specifications. It is a “know it when I see or feel it” sense that cannot be discretely defined. Yet those operating in concert with it, just like those who are not, can tell when they understand it and when they do not.
I recently interviewed a CIO who was trying to turn around a meandering Enterprise Resource Planning project. At the risk of annoying him, I asked what he thought he would have if he could bring the project in by January. “I will have satisfied my commitment to the Board,” he replied.