The WishBuilt Method

How every engagement runs.

Every engagement follows the same order.

We start from the business problem.

Understand: business problem, business analysis. Design: system design, technology choice. Build: implementation. Measure: measurement.

Same sequence every time. No stage skipped. No stage begun early.

We find the primary bottleneck—not the brief, not the symptom list.

We agree what improvement looks like, what the baseline is, and what is in scope.

Design does not begin until that is agreed.

If the ask is only to add something onto a process that will not change, we pause.

Design is a picture of how the work should run once the stuck point is gone: who does what, what information moves where, what changes day to day.

The change stays as small as it can be and still remove that point.

Technology comes after that picture is clear—and only if the design requires it. Existing tools may be enough. New software may not be needed.

Build does not begin until the blueprint is agreed, including the technology decision it implies.

If the design can be met without new software, we do not invent a build to justify one.

We build to the signed Design. Nothing beyond it.

If the design needs to change, we return to Design before continuing.

We hand the system over so the team can run it.

Then we measure.

Shipping ends Build. It does not end the project.

We compare the operation to the baseline agreed in Understand.

We check whether the stuck point is gone—and whether the change holds in normal use.

If the numbers do not move, we say so.

The engagement is not complete until that confirmation exists.

A clean launch with no improvement is not a finished project.

If something in the operation is stuck, that is enough for a first conversation.

Not a quote request. A conversation about whether we can help.