When is a project finished? For most of us, it seems pretty simple: when we ship the product or launch the service. But we need to take a step back and consider what “done” really means.
Most teams in business work to create a defined output. But just because we’ve finished making a thing doesn’t mean that thing is going to create economic value for us. If we want to talk about success, we need to talk about outcomes, not just outputs. And as the world continues to digitize and almost every product and service becomes more driven by (or at least integrated with) software, this need grows even stronger....
Scooped by Jeff Domansky |
Daniel Tremblay's curator insight,
February 10, 2017 9:30 AM
"With software, however, the relationship between <we’ve finished building it> and <it has the effect we intended> is much less clear."
On doit mettre le focus sur l'atteinte des objectifs d'affaires du projet. Un projet qui respect les specs, livré en temps et à l'intérieur des coûts, peut être un échec s'il ne permet pas de réaliser les objectifs d'affaires attendus.
Sign up to comment
Wonderful mantra: Manage outcomes, not output.