top of page

How many of your finished projects paid off?

Oct 1
2 min read

To measure project success, you compare what a project returned with what it was supposed to return. Most teams can't, because the return was never set at the start; they can only say the project was finished.

What did your last project return? If you hesitated, you're not alone. Your roadmap is probably full of finished projects, and when someone asks what each one returned, the room goes quiet. You're accountable for the result, and you can't show it.

Why is "finished" counted as success?

Because finished is easy to see. Dates, scope, tickets closed: all of it reports itself. It's tempting to believe that if it shipped on time, it succeeded.

But a project can hit every date and change nothing. Shipping is the output. What it returned for the company and its customers is the outcome, and that's what you're accountable for.

How many of your finished projects paid off?
How many of your finished projects paid off? | Truvle

Why is a project's return so hard to show?

Two reasons.

It was never set. At kickoff, teams agree on what to build and when. They rarely agree, in writing, on what the project should return. Without that, there's nothing to measure against at the end.

Reviews ask a different question. Post-launch reviews usually ask how delivery went: what slipped, what to do differently. Useful, but they skip the question your leadership cares about: did it pay off?

Find out whether your current project is set up to pay off: Book your free project



How do you look back at a finished project? by Truvle [The 4 Answers]

Pick one finished project and answer four questions with the people who worked on it:

  1. What was it for? The problem it was meant to solve, and for whom.

  2. What did we say it would return? If nobody can find it written down, that's your first finding.

  3. What did it return? What actually changed for the company and its customers. Use the evidence you have; "we don't know" is an honest answer.

  4. Where did it drift? The changes along the way that pulled it away from what it was for.

The look-back isn't about blame. It shows you where the gap opened, so the next project starts better.

How do you set the return before the next project?

Before work starts, write down the return you expect, specific enough that someone outside the team could check it later. "Improve retention" is a hope.

"New customers are still active after their first quarter" is something you can look at.

Have everyone on the project agree to it, and hold every change against it as the work moves.

Thanks for reading. A quick breakdown from our blog.


Found this useful? Save it for later or pass it along!




 
 
 

Comments


bottom of page