Before You Build

Teams often begin a build by listing outputs: a website, a campaign page, a dashboard, or a new set of sales materials.

The list describes what will exist. It does not explain what should become easier because it exists.

Start With Change

Name the decision or behaviour the work needs to support. A customer may need to understand an unfamiliar offer, compare options, trust a claim, complete a task, or return with better information.

For example, someone booking a workshop needs to know who it is for, when it runs and what it costs. Those questions tell you what belongs beside the booking button.

Choose The Parts

Then decide what to build. That workshop might need a clear course page and a short booking form before it needs a full learning platform.

Start with the smallest useful change. Watch where people still hesitate, then decide what to improve next.

Test The Brief

Before approving the work, finish these sentences:

• The person using this needs to be able to…
• Today, they get stuck because…
• We have seen this in…
• The change we will make is…
• We will know it helps when…

If the evidence is missing, investigate before committing to the build. Ask the team handling enquiries, watch someone attempt the task or review where people abandon it. A suspected problem is a useful starting point, but it still needs checking.

In Practice

For HRM Asia, event registration had to adapt to visitors’ choices across five markets. The work connected ticket selection, attendee details, totals and payment in one journey. The brief became specific because the decisions were specific.

Use that same discipline at a smaller scale. A better answer beside a booking button may be more useful than another page.