Discovery: Empirical Foundation of Transformation

Executive Summary

Discovery is the foundational phase of Arian Khodro's transformation. We firmly reject entering the organization with pre-packaged assumptions or off-the-shelf software prescriptions. Instead, the incoming Transformation Leader conducts a rigorous, evidence-based assessment over the first 30 to 60 days to replace speculation with measured operational facts across Business, Technology, Data, People, and AI Readiness.

┌────────────────────────────────────────────────────────────────────────────────────────┐
│                        THE 5 LENSES OF EMPIRICAL DISCOVERY                             │
├────────────────────────────────────────────────────────────────────────────────────────┤
│  1. BUSINESS      ► Map true process flows, handoff friction, and cycle times.         │
│  2. TECHNOLOGY    ► Audit legacy Tadark Delphi code, data structures, and tech debt.   │
│  3. DATA          ► Inventory VIN lifecycle, parts catalogs, spreadsheets, and silos.  │
│  4. PEOPLE        ► Assess skills, change resistance, key-person risk, and incentives. │
│  5. AI READINESS  ► Evaluate document structure, OCR feasibility, and governance gaps.│
└────────────────────────────────────────────────────────────────────────────────────────┘

---

The Scientific Discovery Principle

Every assertion produced during Discovery must adhere to an audit chain: Question ➔ Evidence Collected ➔ Empirical Finding ➔ Strategic Decision ➔ Operational Action

No software will be designed, purchased, or built until the corresponding operational problem is verified by physical evidence (audit logs, time-and-motion studies, error rates, or database schema dumps).

---

Documents in This Section

Document	Purpose	Core Output
Discovery Framework	The 30-60 day audit methodology and toolset.	Step-by-step discovery playbook across the 5 lenses.
Business Processes	Current value streams, handoff friction, and shadow IT.	Process maps of customs, warehouse, and warranty flows.
Technology Landscape	Assessment of legacy Tadark Delphi, database, and debt.	Technical risk register and interface constraints.
Data Landscape	Data silos, VIN reconciliation, and master data gaps.	Data dictionary and synchronization gap analysis.
Organization & Capabilities	Team capabilities, culture, and change readiness.	Organizational readiness score and skill gap heatmap.
Pain Points & Hypotheses	Formal registry classifying facts vs. unproven assumptions.	Auditable matrix of operational hypotheses to prove.

---

Conclusion & Governance Checkpoint

• Key Decisions: Mandate all departments to open operational records, spreadsheets, and Tadark schemas for discovery auditing.
• Open Questions: Availability of Tadark technical specialists for architecture interview sessions.
• Next Actions: Read the Discovery Framework and review interview interview schedules.