Clean Core for Management & Leads

• QuestionWhat is "The business case for Clean Core"?Tap to revealAnswerClean Core makes upgrades and new SAP features routine instead of risky, which lowers the long-term cost of change.
• QuestionIn "The business case for Clean Core", explain:Tap to revealAnswerClean Core keeps SAP standard untouched and puts custom needs beside it on supported connections.
• QuestionIn "The business case for Clean Core", explain:Tap to revealAnswerIt converts upgrades from multi-month regression projects into routine, schedulable events.
• QuestionIn "The business case for Clean Core", explain:Tap to revealAnswerIt lowers the total cost of change and speeds adoption of new SAP innovation.
• QuestionIn "The business case for Clean Core", explain:Tap to revealAnswerThe payoff is predictability, not just tidier code.
• QuestionAnalogy for "The business case for Clean Core":Tap to revealAnswerIt is the difference between a tenant who decorates with removable fittings and one who knocks down walls — only one can move out (or upgrade) easily.
• QuestionWhat is "Extensibility approaches as an investment decision"?Tap to revealAnswerThe three extensibility approaches trade cost and risk — pick the lowest-effort one (key-user, then developer, then side-by-side) that fully meets the need; side-by-side is a clean choice for a separate lifecycle, not a penalty.
• QuestionIn "Extensibility approaches as an investment decision", explain:Tap to revealAnswerKey-user (in-app): cheapest, lowest risk, done by power users — no developers.
• QuestionIn "Extensibility approaches as an investment decision", explain:Tap to revealAnswerDeveloper extensibility (on-stack ABAP Cloud): in-system custom code on supported rules — moderate cost.
• QuestionIn "Extensibility approaches as an investment decision", explain:Tap to revealAnswerSide-by-side on BTP: just as clean for the core, the right choice for a separate lifecycle, but highest cost to own (a second platform).
• QuestionIn "Extensibility approaches as an investment decision", explain:Tap to revealAnswerAlways choose the lowest-effort approach that fits the need; escalate only when forced.
• QuestionAnalogy for "Extensibility approaches as an investment decision":Tap to revealAnswerKey-user is rearranging the furniture, developer extensibility is a permitted renovation, side-by-side is building a separate annex with its own utilities bill — all sound, just different costs.
• QuestionWhat is "Governance: variants, baselines, exemptions, ownership"?Tap to revealAnswerName an owner for the rulebook and the baseline, make every exemption carry a reason, an expiry, and an approver, and treat new high-priority findings as build-breakers.
• QuestionIn "Governance: variants, baselines, exemptions, ownership", explain:Tap to revealAnswerThe check variant is the agreed rulebook; it needs one named owner.
• QuestionIn "Governance: variants, baselines, exemptions, ownership", explain:Tap to revealAnswerA baseline is a dated snapshot of accepted existing debt — new issues still get flagged.
• QuestionIn "Governance: variants, baselines, exemptions, ownership", explain:Tap to revealAnswerEvery exemption carries a reason, a validity date, and an approver — an audit trail.
• QuestionIn "Governance: variants, baselines, exemptions, ownership", explain:Tap to revealAnswerTreat new high-priority findings as build-breakers, not suggestions.
• QuestionAnalogy for "Governance: variants, baselines, exemptions, ownership":Tap to revealAnswerIt is a building-code inspection: a fixed code, a record of pre-existing issues, and signed, time-limited waivers for anything not yet fixed.
• QuestionWhat is "The migration roadmap (0 → ATC-green)"?Tap to revealAnswerMeasure live usage first, stage the checks from broad to strict, baseline the old debt, retire unused code, and warn the business about any behaviour changes.
• QuestionIn "The migration roadmap (0 → ATC-green)", explain:Tap to revealAnswerStart by measuring live usage (SCMON) to scope around code people actually run.
• QuestionIn "The migration roadmap (0 → ATC-green)", explain:Tap to revealAnswerStage the check variants: DEFAULT, then S4HANA_READINESS, then CLOUD.
• QuestionIn "The migration roadmap (0 → ATC-green)", explain:Tap to revealAnswerBaseline existing debt and set a decommission policy for unused code.
• QuestionIn "The migration roadmap (0 → ATC-green)", explain:Tap to revealAnswerPlan business communications for any change end users will notice.
• QuestionAnalogy for "The migration roadmap (0 → ATC-green)":Tap to revealAnswerIt is a phased renovation with a survey first, a staged inspection schedule, and a notice to the residents before anything visible changes.
• QuestionWhat is "Measuring progress (KPIs)"?Tap to revealAnswerTrack the findings burndown, the percent of code cloud-ready, and the count of eliminated unreleased (C2) interface uses — and make that last number visible.
• QuestionIn "Measuring progress (KPIs)", explain:Tap to revealAnswerFindings burndown against the baseline is the primary trend KPI.
• QuestionIn "Measuring progress (KPIs)", explain:Tap to revealAnswerPercentage of code that is cloud-ready shows overall readiness.
• QuestionIn "Measuring progress (KPIs)", explain:Tap to revealAnswerCount of eliminated unreleased (C2) interface uses tracks the riskiest dependencies.
• QuestionIn "Measuring progress (KPIs)", explain:Tap to revealAnswerMaking 'C2 references eliminated' visible drives adoption better than a memo.
• QuestionAnalogy for "Measuring progress (KPIs)":Tap to revealAnswerIt is a fitness tracker for the system: the trend line matters more than any single day's number.
• QuestionWhat is "How long, what it costs, and how to staff it"?Tap to revealAnswerGive a driver-based range (≈12 months for a very large estate, less for smaller ones), expect much custom code to be dead and retirable, and fund a small protected capacity with named owners rather than a one-off push.
• QuestionIn "How long, what it costs, and how to staff it", explain:Tap to revealAnswerDuration is a driver-based range, not a fixed date — anchor ~12 months for a very large (~4M-LOC) estate, less for smaller or cleaner ones.
• QuestionIn "How long, what it costs, and how to staff it", explain:Tap to revealAnswerThe biggest sizing surprise is usually upside: much custom code is dead and can be retired, not migrated.
• QuestionIn "How long, what it costs, and how to staff it", explain:Tap to revealAnswerThe cost lever leadership controls is reserved, protected capacity — a steady cadence beats a heroic push.
• QuestionIn "How long, what it costs, and how to staff it", explain:Tap to revealAnswerFund a thin cross-functional team with named owners; don't run it as a side task.
• QuestionAnalogy for "How long, what it costs, and how to staff it":Tap to revealAnswerIt's funding regular building maintenance, not waiting for the roof to fall in — a small steady budget is cheaper and more predictable than an emergency rebuild.
• QuestionWhat is "Running the programme: decision rights, conflict, and issues"?Tap to revealAnswerSet decision rights and an impersonal rulebook so conflicts settle at the gate, run a light steering cadence on the burndown and top risks, and pre-decide the response to the usual issues — tracked as an owned risk list.
• QuestionIn "Running the programme: decision rights, conflict, and issues", explain:Tap to revealAnswerSet decision rights up front: who owns the rulebook, who approves exceptions, what auto-blocks a release.
• QuestionIn "Running the programme: decision rights, conflict, and issues", explain:Tap to revealAnswerImpersonal, pre-agreed rules settle most conflict at the gate, not on a manager's desk.
• QuestionIn "Running the programme: decision rights, conflict, and issues", explain:Tap to revealAnswerRun a light cadence: one accountable owner, a short regular steering check on burndown + top risks, a clear escalation path.
• QuestionIn "Running the programme: decision rights, conflict, and issues", explain:Tap to revealAnswerMake common decisions automatic; reserve leadership attention for rare, costly trade-offs.
• QuestionAnalogy for "Running the programme: decision rights, conflict, and issues":Tap to revealAnswerGovern it like a board with clear bylaws: most matters are decided by the rules automatically, and only the rare, genuinely contested item reaches the table.

1. 1Summarise the core idea

   Analyse~10 min

   In your own words, summarise the central idea of "The business case for Clean Core". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Use it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "Running the programme: decision rights, conflict, and issues" applies. Use the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.