Discovery and decision workbook

Append-only. What to capture in early workshops, and what each field decides.

Use this in early workshops. It records the basis for the initial method choice; detailed analysis follows as the design develops.

Discovery topics, what to capture, and the decision each informs
TopicCaptureDecision use
Source contextPlatform, version, features, volume, growth, change rate, workload groupsIdentify viable methods and compatibility checks
Model complexityDependency depth, uniformity, statefulness, non-data objects, physical and feature exoticaPredicts which methods remain viable — more decisive than volume
Target contextDeployment model, region, network, capacity, target dispositionsConfirm which methods are available at all
Layer dispositionsMigrate, rebuild, archive or retire — decided per layerEstablishes what volume actually has to move
ConstraintsDowntime, RPO/RTO, security, sovereignty, windows, skills, scheduleTest feasibility and trade-offs
External reporting exposureWhich outputs feed financial, regulatory or market reporting, and who owns themEstablishes the restatement risk before any correction is designed
Operational dependencyWhat now depends on each asset beyond reporting, and the impact of a day’s outageSeparates reporting migration from work that needs operational governance
Evidence and assumptionsSource, owner, date, confidence, review dateSeparate confirmed facts from working assumptions
Method decisionChosen method, alternatives rejected, reasons, approverExplain how the choice was reached
Risks and actionsTrigger, impact, owner, due date, responseTrack conditions that may change the plan
Open questionsWhat must be confirmed, and by whenShow which decision is waiting on an answer

Close every workshop by agreeing the next concrete piece of work — a compatibility assessment, throughput test, target confirmation, security review or rehearsal plan — and treat the method as provisional until the conditions that matter to it have been checked.

Reviewed 25 August 2026

These are my own views, written from years of building and moving large Oracle data platforms. They are not Oracle’s official guidance and this is not Oracle documentation. Volatile product claims are quarantined in Product facts that will date.