Frequently Asked Questions


A business owner, relevant users and the people responsible for data, technology and any applicable risk decisions.

The person responsible for the problem and representatives of the teams on either side of the handoff.

It should remove avoidable repetition while keeping an accountable person visible where judgement and reassurance matter.

Only for actions explicitly authorised in the agreed design. Other actions are prepared for review.

Yes. Findings are ranked by business relevance, dependency, risk and effort rather than presented as an unprioritised issue list.

It can improve source and pipeline evidence. Attribution depends on available data and assumptions, which should remain clear.

No. The aim is to reduce avoidable discovery, routing and follow-up gaps. Demand, capacity, service quality and patient choice also affect appointments.

A better fit reduces friction. Adoption also requires ownership, training and consistent management practices.

Migration or restructuring requires mapping, backups, testing and reconciliation. The scope should define what moves and how it is checked.

Where useful, after defining the use case, data, users and constraints.