Portfolio Work Sample Sanitized / Anonymized

Balancing Shared Tech with Brand Autonomy.

Discovery, operating model design, RACI development, and pilot execution—building the central-federated architecture for a Fortune 500 multi-brand organization.

Client Profile

Fortune 500 Apparel Company

4 Brands, Central Tech Org, $3B+ Rev

Engagement Focus

Embedded Strategic Lead

Organizational Design (2024–2025)

The Engagement

Retained by the centralized technology organization of a publicly traded multi-brand apparel retailer. The organization had correctly identified its strategic direction: enable shared infrastructure investment while preserving the agility of the individual brands.

The mandate: Restructure the enterprise digital and technology operating model. This spanned functional assessment, RACI development, operating model design, and executing a "Commerce Enablement" pilot across all four brand organizations.

4
Distinct Brand Organizations
3
Engagement Phases Executed
The Core Design Distinction
Build ÷ Run
Separating Capability from Activation

The Core Challenge

The right vision, a missing operating model.

Digital centralization has a well-documented failure mode: the central model gets built, the brands don't trust it, shadow IT proliferates, and everyone ends up worse off than before. The company had the vision, but lacked the organizational mechanics to make it work.

The Centralization Trap

Friction & Shadow Ops

  • Lost in Translation: The central tech team spoke in requirements; the brand teams spoke in customer experiences. Neither understood the other.
  • Blurred Ownership: It wasn't clear where building the platform ended and running the brand marketing began.
  • Shadow IT: Brands began spinning up their own rogue tech solutions to bypass the central bottleneck.

The Structural Fix

The Central-Federated Model

  • The "Build vs. Run" Line: Drew a hard organizational boundary separating the building of capability (Central Tech) from the activation of the customer experience (Brands).
  • The Translation Layer: Designed and stood up a "Commerce Enablement" team to bridge the gap between engineering and brand marketing.
  • Pre-Launch RACI: Forced hard, uncomfortable conversations about ownership and authority *before* the model went live.

Central-Federated Operating System

Avoiding failure required doing the hard design work upfront. This is a conceptual view of how we architected the engagement, defined the boundaries, and rolled out the pilot.

Operating Model Architecture

Bridging Centralized Technology with Brand Autonomy.

The "Build ÷ Run" Distinction

Solving the structural disconnect between IT and Marketing.

Centralized Tech Org

The "Build" Function

Platform Infrastructure
Core Engineering
Data Architecture
Speaks in: Requirements

Commerce Enablement

The Translation Layer

Translating brand strategy into tech requirements, and tech capabilities into brand activation plans.

4 Brand Organizations

The "Run" Function

Brand Strategy
Merchandising
Customer Experience
Speaks in: CX & Revenue

Strategic Takeaways

Why avoiding the digital centralization failure mode requires doing the hard design work upfront.

1. The Translation Layer is the Missing Piece

When engineers are expected to translate brand strategy into technology requirements—and brand marketers are expected to translate technology capabilities into activation plans—both sides end up frustrated and the CX degrades. The Commerce Enablement Team wasn't overhead; it was the mechanism that made the whole model functional.

2. RACI Before Launch is Non-Negotiable

Every competing agenda that isn't surfaced in RACI development becomes a delay during delivery. Doing the RACI before the new model went live — and treating every surfaced conflict as signal rather than friction — was what allowed the pilot to operate from day one with clear decision rights.

3. Pilot Before Scaling

Digital centralization has a well-documented failure mode. Avoiding that failure requires separating build from run, resolving ownership before launch, and crucially, piloting the model in a controlled environment before rolling it out across a $3B+ enterprise.