You Need to Manage Digital Projects for Outcomes, Not Outputs

Jared Spool

February 10th, 2017

In this week’s article Josh Seiden and Jeff Gothelf tell us about an effective strategy for defining when a project is finished.

Here’s an excerpt from the article:

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.

Read the article: You Need to Manage Digital Projects for Outcomes, Not Outputs

How do you know when a project is finished? Let us know below.

Add a Comment