Purpose is a Problem

Here’s a simple way to evaluate the value of software:

1. What is it’s purpose?
2. How well does it fulfill that purpose?

The problem we run into, however, is focusing on the solution space rather than the problem space.

We say, the software is supposed to generate invoices when the green button is clicked.

Yes, that’s what the software does, but is that its purpose?

No.

Its purpose is to solve a problem. The problem is the purpose.

So, going back to the first example:

• Before: The software generates invoices when the green button is clicked.
• After: The software ensures we are paid when we need to be paid.

Before locks you in. When we have the green button, we are done, right?

After opens your mind to ways of making your software more valuable, simply by rephrasing its purpose:

• We can have invoices automatically generate at the first of the month, based on the values the software has captured throughout the month.
• We can have the software include payment options directly on the invoice, to make it easier for clients to pay.
• We can have the software automatically remind customers on a schedule about invoices, to make sure we capture funds sooner and to ensure our customers are not hit with late fees.
• We can have the software send weekly progress updates to clients with running totals to prevent unexpected charges.

And the list goes on.

The purpose of your software is not a set of specs. It’s to solve a specific problem.