Overview
When design is not about the design…
Background
The Real Challenge
Strategy: Designing the First Wrong Answer
The Demo

Driving large scale alignment across multiple orgs through design.

Google

Driving large scale alignment across multiple orgs through design.

When the design effort drives alignment in landscape of fragmented orgs and stakeholders.

Talent @ Google

When design is not about the design…

This case is about using design as a strategic tool, not to ship pixels, but to align stakeholders, surface shared reality, and create a foundation for convergence across a fragmented organization.

Background

An ex-Meta program manager I'd collaborated with on talent management strategy brought me in to tackle the same problem space at Google, but Google was 3-4 years behind.

The challenge: Envision a holistic talent ecosystem that supports Googler career and performance while giving the business clarity on workforce optimization. Conceptual, with a 5+ year horizon.

The Real Challenge

Through conversations with team leads and HR leadership, the design concept became a tertiary goal. The real problems were organizational:

Fragmented product ecosystem

e.g., 4 separate learning platforms

Unclear ownership

Leading to minimal strategic collaboration

No horizontal awareness

Siloed teams without cross-cutting visibility

Near-sighted goals

No affordance for system-level efficiencies

The right solution wasn't a design, it was converging many people who each care about different pieces of the puzzle, and creating a shared reality to ground future conversations and efforts.

Strategy: Designing the First Wrong Answer

In spaces that are both very big and very blurry, conversation and documents can make things harder to clarify. Instead of a "northstar" to anchor on, I positioned the concept as "the first wrong answer", a provocation everyone could reference as we figured out what's actually right.

My approach:

1. Map the stakeholder landscape

Identify every team with skin in the game, capture their aspirations and constraints.

2. Find the path, not the map

Focus on key moments that demonstrate unlocking the hardest problems, rather than designing the entire ecosystem.

3. Break the design

Avoid golden-path scenarios, attack the hardest problems head-on.

4. Balance tangibility with ambiguity

Leave room for each vertical partner to complete the sentence in resulting conversations.

The Demo

While the focus of this case isn't the design itself, below are walkthroughs I created for Google HR leadership showing how the Talent Ecosystem could work across three personas: the Googler, Manager, and Org Leader.

Would you like some music
for the right vibes?

What's the mood?