Solventum / Design systems + AEM
All workDesign intent,
through delivery.
I handled the design-system migration, aligned component mapping with AEM, and participated through QA/UAT.
System migration · AEM component mapping · Governance through QA/UAT
From library to experience
Make the next
step clear.
GuideFind a useful resource.
Clear hierarchy and a purposeful action help people move through the content.
Preserve design intent.
Advocate for users and the business.
New conceptual artwork represents continuity. The interface uses fictional content and reconstructed patterns from the supplied library.
01 / Continuity across the migration
One system.
Across every phase.
I stayed involved from the design system through QA/UAT to govern how design intent became an implemented experience.
01
Design
system
Foundations
Tokens + componentsHandled the design-system migration.
02
Component
mapping
Alignment
Design-system patternAEM componentAligned component mapping with AEM.
03
Implementation
Translation
Pattern → pageDesign intent in context
Governed the translation of design intent.
04
QA / UAT
Design review
Design intentImplemented experienceParticipated through quality review and acceptance testing.
My continuous role
Preserve design intent. Advocate for users and the business.
Design-system ownership and cross-functional participation across delivery.
Reconstructed process summary from my account. It describes my contribution across phases, not sole ownership of the wider AEM program or every discipline’s work.
02 / Component mapping
Preserve the pattern’s
meaning in AEM.
I aligned component mapping with AEM. The library’s guidance helps explain what a mapping needs to preserve.
Documented content roles
GuideMake information
easier to use.
A practical guide organized around a clear task.
Fictional content · Reconstructed pattern
| Design intent | What the mapping should preserve |
|---|---|
| Heading hierarchy | The semantic heading level is distinct from visual font size. |
| Content context | A tag classifies the content; its role differs from a filter. |
| Next step | An action communicates a destination or the next step. |
My role
Stay involved through implementation, QA, and UAT.
Govern the translation of design intent while advocating for users and the business.
03 / Governance through QA and UAT
Quality lives
in the details.
My involvement continued through QA/UAT. The library provided specific guidance to discuss alongside the implemented experience.
Behavior
Collapsed and
expanded states.
The library documents both states of an accordion. Its behavior is part of the pattern’s meaning.
Structure
Semantic level
and visual size.
A heading’s place in the document structure is separate from the way its typography is styled.
Accessible media
Subtitles
and transcripts.
The library includes guidance for video content with audio, including subtitles and transcripts.
What should remain consistent through implementation?
Content hierarchy, the purpose of each element, and the documented interaction states. This working accordion is a new portfolio reconstruction that illustrates the discussion; it is not a shipped Solventum component.
How does this connect to my contribution?
I participated through implementation, QA, and UAT, helping govern the translation of design intent and advocating for user and business needs.
The guidance above is drawn from the supplied library. It does not establish a particular test result, pass rate, or accessibility certification.
04 / Contribution + reflection
A system needs
continuity of care.
At 3M, my story begins with recognizing drift and taking ownership of the foundation. At Solventum, it continues with migration and maintaining design intent as the system moved through delivery.
My contribution
Design-system migration, AEM component-mapping alignment, and participation through implementation and QA/UAT.
The shared work
I worked across disciplines to support implementation and acceptance. My contribution was to govern the system’s translation and represent user and business needs throughout.
What I would carry into the next system
Stay close to the work after design handoff. A component’s meaning needs to survive the move from the library into the authoring environment and the implemented page.
This case presents my reported responsibilities and source-supported system guidance. It does not claim a quantified migration outcome or that the reconstructed examples shipped.