How We Think

We start with the problem. We decide on the solution after we understand the need.

First we look at who the work is for, what needs to happen, and which outcome matters. The technology decision comes after we know what the thing needs to do.

The starting point.

Every conversation follows a simple sequence.

PROBLEM
“We're doing this manually every day.” It's slow. Or it's confusing. Or it lives in WhatsApp and a spreadsheet and nobody knows what the real answer is.
QUESTION
“Why does it have to work this way?” What is the actual job the customer, staff member or owner is trying to get done? Let's look at the job, not the tools.
POSSIBILITY
“What could make it better?” Now that we understand the real job, what does the smallest, most useful version of a solution actually look like?

Start with the outcome.

What do you need people to do. The right solution becomes clearer from there.

What do you need people to do? Start with the outcome. The right solution becomes clearer from there.

If the real need is information… the direction is a website. A complete platform would be more than is needed here.

DIRECTION 01

Need: A customer needs to find out what you actually do, whether it applies to them, and how to get in touch.

Key lesson: The solution follows the problem. You don't decide you need a website and then figure out what goes on it.

Focus on what matters. Build around it.

Find what matters first. Build around it.

TOO MUCH 7 items

Features, modules and reports that sit unused.

WHAT MATTERS 3 items

What remains is exactly the useful part.

Find the right fit.

Use what already works when it solves the problem.

Create something new when the problem calls for it.

Build what makes sense. .

Sometimes the answer is already out there. Sometimes the right answer needs to be created. The approach fits the situation.

Bring the problem. We will figure out what makes sense. Whether that is an existing tool, some glue between tools, or a product built for the job.

Start Something