# ADR 2026 05 16 * **File:** ADR-2026-05-16.md * **Author:** Nicolette Martine Langendam — NikiDigitals * **Location:** LES-Master/docs/decisions/ * **Decisions covered:** ADR-000065 through ADR-000066 * **Session type:** LES-MENTOR — Learning Methodology & Depth Standard *** ## Context This file records decisions made on 16 May 2026 establishing the foundational learning methodology and depth standard for the entire LES programme. These two decisions are among the most consequential in the programme — they define not what is studied but how it is studied, and to what depth. Both are permanent and non-negotiable. *** ## Operational Decisions ### ADR-000065 — Five-Step Learning Methodology Adopted **Decision:** All learning in the LES programme follows a five-step progression without exception. No step may be skipped. **The five steps:** | Step | Activity | Tool | Purpose | | ---- | -------- | ---------------------------------------------------------------- | -------------------- | | 1 | Study | Microsoft Learn, textbook, official documentation, or equivalent | Build the knowledge | | 2 | Discuss | LES-LEARN session with mentor | Verify the knowledge | | 3 | Sandbox | Standalone build committed to a LES-LABS repository | Test the knowledge | | 4 | Review | LES-LEARN session — assess the sandbox, identify gaps | Refine the knowledge | | 5 | Apply | Implement in LES with understanding fully verified | Prove the knowledge | **The non-negotiable rule:** No concept is implemented in LES until Step 4 is complete and understanding has been verified. Step 5 — Apply — always follows Steps 1 through 4 in sequence. **Context:** The LES programme combines deep study with active building. Without a structured methodology, the risk is that building begins before understanding is sufficient — producing work that cannot be explained, debugged, or extended. Equally, study without application produces inert knowledge that does not transfer to real systems. **Rationale:** The five-step structure ensures understanding precedes implementation at every stage. Step 2 (Discuss) catches gaps that solo study misses. Step 3 (Sandbox) forces the knowledge into practice in a low-stakes environment. Step 4 (Review) closes remaining gaps before the concept enters the production system. This sequence applies whether the concept is a database join, an Azure service, an accounting standard, or an AI capability. **Consequences:** * All LES-LEARN sessions are structured around this methodology * No LES module receives new code until Step 4 is passed for the relevant concepts * Sandbox outputs (Step 3) are committed to LES-LABS repositories — not throwaway practice * Mentor instructions updated — never suggest skipping a step ### ADR-000066 — Learning Depth Standard Formalised — Global Expert Level **Decision:** All learning in the LES programme is pursued to global expert depth. This is a permanent, non-negotiable standard. **Definition of global expert depth:** The deepest possible understanding that exists in a given domain — not what is required to pass an examination, not what a practitioner needs to function, not what is sufficient to complete a deliverable. The standard is what the world's leading experts in each discipline know and how they think. In practice this means: * Reading primary sources — original papers, official standards, founding texts — not only textbooks and summaries * Understanding the why before the what — the mathematical derivation before the formula, the legal principle before the rule, the architectural rationale before the implementation pattern * Connecting every concept to LES — no abstract knowledge for its own sake * Producing original analysis — not summarising what others know but synthesising what it means for the system being built **Context:** The LES programme targets the Finance Transformation Architect role at the highest professional level. That target cannot be reached by accumulating surface knowledge across many domains. It requires deep, connected understanding that holds together under scrutiny — in a professional setting, in a research context, and in a live system. **What this standard explicitly rejects:** * Minimum viable answers to learning questions * Summaries in place of full explanations * Exam-pass level engagement with any topic * Moving to the next concept before the current one is genuinely understood **Rationale:** The programme is designed over five years precisely because the depth standard takes time. Shortcutting the depth in order to cover more ground faster defeats the purpose of the programme. A Finance Transformation Architect who can answer the follow-up question — and the question after that — is worth orders of magnitude more than one who can answer the first question only. **Consequences:** * All LES-LEARN and LES-MENTOR sessions operate at this standard * Mentor instructions updated — no minimum viable answers, ever * Study sessions are not counted by hours spent but by depth of understanding achieved * Where the depth standard conflicts with schedule, the depth standard wins --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nikidigitals.gitbook.io/les/03-architecture/decision-log/phase-0-foundation/adr-2026-05-16.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.