Governance, Architecture, Assurance

I advise on decisions that shape an SAP landscape for years: the transformation path, target architecture, clean core, extensions, integration, and the governance structures in which they are decided. Governance, architecture and assurance are the three perspectives from which I assess these decisions. Emerging technologies such as automation or AI are factored in when they are relevant to a decision, and judged by the same criteria as any other solution.

Governance: decisions with a clear mandate

Good SAP governance is lean. It defines which questions are decided where, by which criteria, and how exceptions are deliberately approved and closed again. A board alone achieves little. It takes a mandate, clearly defined decision types, entry criteria, roles and escalation paths, and an organization that applies them.

What you gain

Decisions are made where context and responsibility meet, and they are made consistently. Exceptions become visible instead of quietly piling up.

Typical questions

  • Who decides on deviations from the SAP standard, and by which criteria?
  • Which topics belong in the architecture board or design authority, which in the change board, which in the steering committee?
  • How does clean core move from a strategic goal to an applied rule?
  • Who approves automation and AI scenarios that access SAP data and processes, and who owns them in operations?
  • How can recommendations from external partners be evaluated transparently?
Governance Starter Package

Architecture: solutions that hold up across releases

Whether an extension belongs in the core, on SAP BTP or in another system, which integration option stays maintainable, and what a target architecture means for operations: I make these consequences clear before the decision is made. I distinguish vendor announcements from what is actually available and operable today, and I name prerequisites and limitations.

What you gain

You choose an architecture knowing its consequences for upgrades, operations and future initiatives.

Typical questions

  • Does this extension belong in the core, on BTP or in another system?
  • Which integration option stays manageable across further releases?
  • Which transformation path fits processes, data and organization?
  • What does a planned AI use case, for example with SAP Business AI or Joule, require in data foundation, integration, authorizations and operations, and how much of that is in place today?
  • Which assumptions are missing from the current target architecture?

Clean Core Quick Check S/4 Scenario Assessment

Assurance: an independent second opinion

Major SAP decisions usually come with well-argued recommendations, from partners, vendors or your own team. Assurance means testing them independently before you commit: which assumptions carry them, how well they are evidenced, which risks remain, and whether the decision is ready to be made.

What you gain

Your steering committee decides with an independent assessment and knows where the recommendation is strong and where it is not.

Typical questions

  • Does our partner's recommendation hold up under our actual conditions?
  • Which risks are evidenced, and which are only assumed?
  • Is the steering committee proposal complete, and what is still needed for a decision?
  • Is the business case for an AI or automation initiative involving SAP robust enough for a decision?