Making a platform transformation tangible through tenant onboarding.

A shared commerce platform was being separated from the teams that consumed it.

HP's e-commerce modernization was refactoring legacy Adobe Commerce modules toward a unified Platform-Tenant model built around the Single Responsibility Principle. Four tenant teams depended directly on the platform, so technical changes also created a product-communication and coordination problem.

I worked with the US-based PM, engineering, architecture, and program partners to connect FY26 platform outcomes and quarterly goals to executable work while keeping tenant teams informed about releases and platform direction.

The architecture was changing, but joining the platform was still a long manual process.

• Tenant onboarding took three to four months. The existing process was manual and depended on coordination across multiple participants.
• Platform concepts were abstract. Teams needed a shared view of the Platform-Tenant model and what it meant for their work.
• Four tenant teams depended on the roadmap. Releases and technical announcements needed a consistent communication path.
• Product documentation needed to sit beside architecture documentation. Functional requirements, user flows, and delivery intent had to be explicit.

Translate the platform strategy into a flow that teams could review and challenge.

1. Connect outcomes to execution. I translated platform goals into roadmap and requirements work with engineering and program partners.
2. Document the product layer. I introduced product documentation in Confluence alongside architecture material, including functional specifications, requirements, and user flows.
3. Prototype the onboarding experience. I led requirements and built a high-fidelity clickable portal prototype intended to replace the manual onboarding path with a self-serve flow.
4. Review with the system owners. The requirements and prototype went through architect reviews so product behavior could be tested against the platform model.
5. Create communication loops. With the US-based PM, I co-launched a platform newsletter, opened a Microsoft Teams channel, and ran quarterly tenant interviews.

Public evidence boundary.

The source materials behind this work include journey maps, prototype screens, platform-tenant explainers, and requirements. The public version describes the evidence boundary without exposing HP internal materials.

The work reached validated requirements and a high-fidelity prototype.

Before leaving the program, I completed the onboarding requirements and iterated the clickable prototype through architecture review. The defensible outcome is a clearer, reviewable product direction for replacing a three-to-four-month manual pain point.

A prototype can be a coordination tool before it becomes a product surface.

The most useful role of the prototype was to turn a platform concept into something product, architecture, and tenant teams could inspect together. This public story keeps the trade-offs, review moments, and evidence boundary visible without exposing internal HP materials.