Software consulting

A useful discovery pack contains a workflow with exception branches, a vocabulary for important records, access rules, sample inputs, acceptance examples and a list of external dependencies. Keep a decision log showing what was chosen, why and what evidence would reopen it. An estimate should refer to those artefacts rather than rely on the memory of the workshop participants. Give unresolved items an owner and a next action; “to be confirmed” without either is not a managed uncertainty. The pack should remain understandable when the person who commissioned it is absent.

An inaccessible production account or missing backup is a finding, not evidence that the corresponding system is healthy or broken. State the limitation and the decision it prevents. Request only the access needed for the assessment, through authorised accounts with an agreed lifetime. Use protected or synthetic data for demonstrations and avoid copying customer records into the report. Before accepting a takeover, review unresolved risks with the business owner and identify who will obtain the missing evidence. The handover decision should include operating responsibility from the first day, not just permission to start editing code.

Organize the brief into known facts, working assumptions and decisions still needed. A known fact might be that purchasing currently uses a shared mailbox. An assumption might be that existing employee accounts can sign in to a new tool. The open decision might be whether finance needs an immediate integration or can begin with a reviewed export. Give each significant uncertainty a person who can answer it and the evidence they would need. This keeps the supplier from quietly pricing an invented version of the business.

For the seasonal portal example, sketch the expected pattern of work after the launch. Separate urgent incidents, small adjustments, new product decisions and routine maintenance. Ask who must respond to each and what context they need. Concentrated construction followed by occasional changes is a different staffing problem from continuous discovery and frequent releases. Do not assume that a quiet roadmap means nobody needs to own security updates, account administration or support questions.