A business app begins with a task that needs to work better. “We need a dashboard” describes a screen. “Our office cannot tell which field reports still need approval” describes a problem that a screen might help solve. Start with the problem so the first version has a useful job.
1. Follow one item from start to finish
Choose a familiar example: a service request, a completed inspection, or a customer document. Write down where it starts, who handles it, where information moves, and what marks it complete. Include the awkward parts. A photo sent by text and later copied into a spreadsheet is part of the workflow, even if nobody calls it a system.
For a fictional maintenance team, the path might be: a customer reports an issue; an office coordinator assigns it; a technician records the visit; a manager reviews the result. That is enough to map the first conversation without designing every future screen.
2. Name the handoff that causes trouble
Ask where someone waits, repeats information, or loses visibility. Choose one handoff to improve first. If technicians finish visits but the office must chase the notes, the first goal could be a clear submission and review process. Inventory management and advanced reporting can wait unless they are necessary to complete that process.
3. Define a result you can observe
Replace “make things easier” with an acceptance example: a technician can submit a visit report from a phone; the coordinator sees it in a review queue; the manager can mark it reviewed. Decide who will confirm that this works using representative sample records.
4. List the information and permissions
Write down the minimum fields: request reference, location, assigned person, visit date, notes, and status. Mark which fields are required and who can read or change each one. Use fictional examples for planning. Do not send passwords or private customer records with an initial inquiry.
5. Separate the first release from the wish list
Put every proposed feature into one of two lists: needed to complete the chosen workflow, or useful later. When a feature seems essential, ask what would break without it. A status list may be enough before a custom chart is justified. A manual export may be sufficient before connecting accounting software.
Your project brief
- The workflow we want to improve is…
- The people involved are…
- The slowest or least reliable handoff is…
- The first version must let us…
- We will know it works when…
- These ideas can wait until later…
Bring this short brief to a discovery call. It gives the discussion a concrete starting point and helps a builder explain scope, tradeoffs, and dependencies before estimating the work.