We bring the relevant teams into discovery, clarify the definitions, and work through the constraints. The scope follows what the organization needs to do and the system its people need to maintain.
We ask what people need to decide, how the current system works, and where it gets in their way. Finance, operations, product, engineering, and research teams can hold different parts of the answer. A source inventory and a short definition record make those assumptions concrete, including freshness, access, volume, and ownership.
We compare what to keep, what to repair, and what needs a new foundation. An options note records the tradeoffs, dependencies, and maintaining team's responsibilities. If a smaller repair serves the organization better than a rebuild, we recommend it. The process adapts to the work rather than imposing a fixed discovery period.
Definitions become models, integration rules, test cases, and acceptance checks. We review changes in useful increments and compare results with agreed source records or control totals. Unresolved differences remain visible. Privacy shapes field selection, access boundaries, test data, and logging throughout implementation.
The team maintaining the result needs more than a successful run. We document the decisions, dependencies, failure cases, validation, and recovery steps. A handover record identifies owners and the questions that remain open. Continued support and further analysis can follow an agreed improvement backlog.
Tell us what needs to change, what a useful result would look like, and what your team needs to keep working along the way.