He found the app confusing. So I changed it.

01 / The observation

What came into view.

The app needed to make sense to the person using it.

The app was built and live. Then the person it was for found it confusing. The delivery record captures the change: simplify the home screen around his four words, quotes, jobs, customers and invoices.

A question to think with

What does the person doing the work actually call each part of it?

An editorial prompt drawn from this case, rather than a transcript of the session.

02 / The decision

So the work changed.

Change the structure around the user’s language. Make those four jobs the big buttons on the home screen and match them in the bottom navigation.

1. Take the feedback seriously

   He found it confusing. That was something to fix.

   The important feedback was about using the app. The record shows a decision to simplify the home screen around the language he actually used.

2. Change the interface

   Quotes. Jobs. Customers. Invoices.

   Those four labels became the main buttons and the bottom navigation. The structure followed the work he recognised.

3. Follow a real task

   Can an invoice actually leave the system?

   The delivery record confirms an invoice sent to a real customer through the app. That establishes a concrete use of the build, rather than just a feature on a screen.

03 / The result

What happened next.

A delivered app, changed in response to actual use.

The record confirms the simplified home screen, customer and job search, invoice PDFs and sending quotes and invoices from the app. A real customer invoice was sent through it on 21 August 2026.

Source: Build and client records, updated August 2026.