Locate the problem before choosing the build

A website can be technically available while leaving its users unsure what to do. A working connection can transfer the wrong meaning. A staff application can save every field successfully while letting a minor correction rewrite an earlier decision. The right project starts by locating the difficulty, rather than choosing a platform from the symptom alone.

The public information leads to the wrong expectation

Look at the offer, its status and the next action together. A product page may need to remain available for existing owners even after ordering ends. A service page may explain an enquiry route while leaving a visitor to assume that submitting it reserves a time. The correction may concern the wording, the destination or both.

The business website service addresses that public journey. If the problem keeps returning because editors cannot maintain the information, include the publishing process, with a factual owner and a way to recognise obsolete content.

A returning user cannot complete a legitimate task

Identify the user, the project and the exact item they need. “Customer access” is too broad: one person may be authorised to retrieve approved handover documents but not internal discussion or another organisation’s records. A completed project may still have useful read-only tasks.

The workspace service examines membership, document states and return visits. Start with the permitted task and its limits, including what should happen after a role or project changes. Do not treat the presence of an account as the entire permission model.

Staff reconcile the same information repeatedly

First establish whether the tools disagree about identity, timing, field meaning or completion. If a source organisation and its delivery location are collapsed into one record, faster synchronisation will not repair the distinction. If a transfer is uncertain, an automatic retry may create another record without resolving the first.

System integration work follows the information across the boundary and gives exceptions an owner. Product and order work is relevant where the disagreement concerns references, variants or order states. The investigation should reveal which system is authoritative for each decision.

The rule exists only in someone’s memory

A spreadsheet may be adequate until several people need to apply consequential edits, approval rules or competing deadlines. Write down the specific rule that is being missed. Which fields can an editor correct? Which changes require renewed review? What should happen when another person has already changed the record?

The business application service turns those decisions into a supported workflow. Sometimes the best first step is to simplify the process or use an existing capability before commissioning a new tool.

People are blocked by the interaction

A task may fail because keyboard focus is hard to follow, an error does not identify the affected field or a receipt cannot be distinguished from a request to try again. Investigate the implemented journey with representative input and relevant assistive technology where required. Accessibility improvements can address a defined barrier while leaving broader specialist assessment separately scoped.

If you are unsure which category fits, describe one occurrence. A small, inspectable example is enough to begin locating the problem.