Description

A focused course, tailored for you

The Senior SAP UX Design System Governance Playbook

Run design system intake, token governance, accessibility review, and Fiori adoption telemetry as a single operating cadence a senior UX lead can defend in any portfolio review.

The portfolio review that asks why one product family sits below the design system adoption average, and the trail behind the number cannot be reconstructed from the tickets, the token registry, or the accessibility audit log.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

Senior UX leads inside large SAP product organisations sit at a specific friction point. They are accountable for the design system across product families they do not staff, for accessibility conformance on screens they did not draw, and for the adoption telemetry their head of product reads before any roadmap conversation. The intake queue is a mix of token requests, pattern variations, and feature work that should have been a component contribution. The token registry has overrides nobody remembers granting. The Horizon migration is partial, the classic Fiori shell still ships, and the screens that fail an EAA review tend to be the ones that have been quietly running for years. The course replaces that scramble with an operating cadence. Intake triage with named owners and weekly throughput numbers. Token governance with a single registry, approved-deviation log, and a quarterly reconciliation. Accessibility review with WCAG 2.2 AA conformance evidence stored against the screen, not the sprint. Adoption telemetry that ties pattern usage to product family, release, and reviewer, so the next portfolio review starts with the answer instead of the search. Each artefact is a working template, not a slide.

What you walk away with

Run a weekly design system intake triage that closes 80 percent of requests inside two cycles, with named owners and a public throughput number.
Govern design tokens through a single registry with an approved-deviation log and a quarterly reconciliation a head of design can sign.
Produce EAA and WCAG 2.2 AA conformance evidence stored against the screen, not the sprint, so a regulator request resolves in a day.
Tie Fiori and Horizon pattern adoption telemetry to product family, release, and reviewer, so the portfolio scorecard reads itself.
Defend a below-average adoption number in a portfolio review with a one-minute answer backed by intake, token, and accessibility receipts.

The 12 modules

Module 1. The senior SAP UX accountability map

Names the four artefacts a senior UX lead is actually accountable for in a large SAP product organisation, the design system registry, the accessibility conformance evidence, the intake throughput log, and the adoption telemetry. Walks through who else has a hand on each artefact, what the head of design expects to see, and how the reader's name ends up on the portfolio scorecard. Establishes the operating cadence the rest of the course builds on.

Module 2. Design system intake triage as a weekly cadence

Replaces the ad hoc Slack and Jira mix with a single intake schema, a weekly triage meeting with named owners, and a throughput number that goes on the wall. Covers how to classify a request as token, pattern variation, component contribution, or product work, how to route each class, and how to publish the queue so product owners stop asking for status. Includes the intake form, the triage template, and the throughput dashboard query.

Module 3. Design token governance and the deviation log

Builds a single source of truth for colour, spacing, typography, elevation, and motion tokens across Fiori and Horizon shells. Defines the approval path for a deviation, the deviation log schema, and the quarterly reconciliation that retires overrides nobody remembers granting. Covers how to handle product family branding asks without forking the registry, and how to express tokens so engineering can consume them in UI5, React, and the Build Apps low-code surface.

Module 4. Fiori and Horizon shell coexistence

Names the reality that classic Fiori, Quartz, and Horizon coexist across the portfolio and will for some time. Lays out a shell strategy that lets the reader hold both, defines which screens migrate when, and produces the migration scorecard a head of product accepts. Covers the patterns that change shape across shells, the patterns that do not, and the accessibility implications of the transition.

Module 5. Accessibility conformance under the European Accessibility Act

Translates EAA obligations and the WCAG 2.2 AA target into a per-screen evidence schema a senior UX lead can defend to a regulator and an enterprise customer procurement team in the same week. Covers the manual review protocol, the automated checks worth running, the screen-level evidence store, and the remediation queue. Distinguishes a finding that blocks release from one that enters the remediation backlog.

Module 6. Design QA at the release gate

Defines the design QA step that sits between developer-ready and release-ready, with a checklist the engineering lead and the design system lead both sign. Covers token usage, component selection, accessibility conformance, and pattern fidelity, and produces the design QA log that feeds the portfolio scorecard. Includes the gate criteria, the reviewer rotation, and the escalation path when a release ships with a known deviation.

Module 7. Adoption telemetry tied to product family and release

Instruments pattern and component usage across the portfolio so the adoption percentage on the portfolio scorecard has a trail behind it. Covers the instrumentation choices that work across UI5, React, and Build Apps surfaces, the reporting schema that ties usage to product family and release, and the dashboard that reads itself. Distinguishes adoption from compliance and explains why both belong on the same report.

Module 8. Pattern contribution model for product family designers

Opens the design system to contributions from product family designers without losing the registry. Defines the contribution path, the review criteria, the maintainership model, and the deprecation policy. Covers how to handle a pattern that one product family insists on keeping after the system has moved on, and how to retire a contributed pattern without burning the relationship with the contributor.

Module 9. Working with engineering on UI5, React, and Build Apps

Names the engineering interfaces a senior UX lead actually has to land design system work, the UI5 library team, the React component team, the Build Apps low-code surface team, and the platform teams that ship the shells. Covers the artefacts each interface needs from design, the cadence that holds them together, and the escalation path when one team ships a deviation that everyone has to live with.

Module 10. The portfolio scorecard a head of product accepts

Produces the monthly scorecard the head of design and the head of product read before any roadmap conversation. Covers adoption by product family, accessibility conformance, intake throughput, deviation log status, and design QA pass rate. Includes the scorecard template, the data sources behind each number, and the narrative the reader writes to wrap them. Defines what a green, amber, and red row mean.

Module 11. Defending a below-average adoption number in review

Walks through the specific portfolio review moment a senior UX lead dreads, the one where a product family sits below the portfolio adoption average. Covers the one-minute answer with intake receipts, token deviation log entries, and accessibility evidence, the remediation path the reader proposes in the meeting, and the follow-up the head of product expects to land in the next cycle. Includes a worked example with three product families.

Module 12. The senior UX operating year

Lays out a twelve-month cadence the reader can run as the design system lead, intake triage weekly, token reconciliation quarterly, accessibility review bi-monthly, shell migration planning twice a year, and the portfolio scorecard monthly. Covers how to fit it around the rest of the role, what to delegate, what to keep, and how to evolve the cadence as the portfolio shifts. Closes with the per-buyer implementation playbook handover.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

The portfolio review opens with the adoption percentage and one product family is below the average. Modules 7, 10, and 11 produce the one-minute answer.

A product family designer pushes back on a token deviation request denial. Modules 3 and 8 give the registry, the deviation log, and the contribution path that hold the line.

An enterprise customer procurement team asks for EAA conformance evidence for a specific screen. Modules 5 and 6 produce the screen-level evidence store and the design QA log that resolves the request in a day.

The head of design asks for a Horizon migration plan that does not break classic Fiori adoption. Modules 4 and 7 produce the shell strategy, the migration scorecard, and the adoption telemetry that hold both.

What you get with this course

Twelve written modules in the Art of Service learning environment, each with worked examples drawn from large SAP product organisation realities.
Downloadable templates for the intake form, triage log, token registry, deviation log, accessibility evidence schema, design QA checklist, and portfolio scorecard.
The per-buyer implementation playbook, hand-built around the reader's actual product portfolio, intake volume, and shell mix.
A worked example of the portfolio review one-minute answer with intake, token, and accessibility receipts ready to adapt.

What you will have in hand by Day 1, Week 1, Month 1

Within 24 hours: learning environment access and the hand-built implementation playbook delivered alongside it.

Week 1: complete modules 1 to 4, stand up the intake schema and the token registry.

Week 2: complete modules 5 to 8, run the first accessibility evidence review and the first contribution cycle.

Week 3: complete modules 9 to 12, ship the first monthly portfolio scorecard.

Before and after

Before

The intake queue is split across Slack, Jira, and email. The token registry has overrides granted on calls. The accessibility audit log is a spreadsheet a contractor maintained two cycles ago. The portfolio adoption number arrives in the review without a trail. The senior UX lead spends the meeting reconstructing the answer.

After

Intake runs as a weekly triage with named owners and a public throughput number. The token registry has a single source of truth and a quarterly reconciliation. Accessibility evidence sits against the screen. The portfolio scorecard reads itself. The senior UX lead opens the review with the answer.

What happens if you do not address this

The portfolio review keeps surfacing the adoption gap, the trail behind the number keeps failing to materialise, and the senior UX lead keeps spending the meeting on reconstruction instead of strategy. The accessibility evidence gap becomes a regulator or enterprise customer escalation. The design system loses the credibility that makes contribution and adoption possible.

Who it is for

A senior UX designer or design system lead inside a large SAP product organisation who carries portfolio-level accountability for Fiori and Horizon adoption, accessibility conformance, and design intake across product families they do not directly staff.

Who this is NOT for. This is not for individual contributors working on a single product screen, for product managers who do not own design system governance, or for early-career designers building their first pattern library. It assumes the reader already runs a design system function and needs an operating cadence around it.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Roughly six to eight hours across three weeks for the modules, plus the cadence the reader stands up in their own portfolio.

Why $199 is the right number

Internal design system conferences cover patterns and tokens at the craft level but rarely cover the operating cadence a senior lead needs. External design ops courses cover the function in the abstract without the SAP shell, EAA, and portfolio scorecard specifics. This course works at the operating cadence layer with the artefacts a senior SAP UX lead is accountable for.

FAQ

Is this tied to a specific SAP product family?

No. The cadence, the registry, and the scorecard are written for portfolio-level accountability across product families, classic Fiori, Quartz, and Horizon shells, and UI5, React, and Build Apps surfaces.

Does it cover accessibility beyond the European Accessibility Act?

Yes. The conformance evidence schema is built around WCAG 2.2 AA, which serves EAA, ADA, and most enterprise customer procurement requirements without rework.

What if my design system is already mature?

The course assumes a mature system. The work is on the operating cadence around it, intake throughput, deviation governance, conformance evidence, adoption telemetry, and the portfolio scorecard.

Is there a refund window?

Yes, a 30-day money-back window applies.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.