LEADERSHIP SCENARIO

The Platform Proposal

3-5 day simulationBeginnerStaff+ IC TrackFree

Three frontend teams at DataFlow have independently built similar abstractions — auth wrappers, API clients, error handling. Nobody has the mandate to fix it, but everyone complains about it in retros. Your manager just mentioned the Director asked about "the frontend tooling situation." No formal project, no authority, no deadline. Just an opening.

From
Raj Mehta
Subject
Frontend tooling — thoughts?

Hey, Quick thought — I was chatting with Jennifer Park yesterday and she asked me about "the frontend tooling situation." Apparently she's been hearing about it from a few different directions. I know you've noticed the pattern too — Alpha, Beta, and Infrastructure all maintaining their own auth wrappers, API clients, the whole thing. Three slightly different implementations of basically the same stuff. No pressure and no mandate here, but if you're interested in looking into it, I think there's something worth exploring...

THE SITUATION

Nobody asked you to fix this

DataFlow’s three frontend teams — Product Team Alpha, Product Team Beta, and Infrastructure — have independently built similar abstractions. Auth wrappers, API clients, error handling patterns. Three teams, three slightly different implementations.

Technical debt is growing quietly. Everyone sees it. Nobody has the mandate to fix it. The duplication compounds every quarter, and new engineers pick up whichever version their team uses.

Your manager Raj Mehta casually mentioned that Jennifer Park asked about "the frontend tooling situation." No formal project, no authority. But the Director is paying attention, and your manager is watching how you handle the opening.

As a Staff Engineer, this is the test: can you turn a vague organizational signal into a concrete proposal that survives skepticism from three teams with three different philosophies?

WHAT YOU'LL PRACTICE

4 leadership skills, one scenario

Building cross-team alignment without formal authority

You have no mandate. No deadline. No team of your own. Your only tools are credibility, conversation, and the quality of your proposal.

Navigating competing technical philosophies

One team values pragmatism. Another values technical rigor. A third tried to fix this before and was ignored. Each perspective is valid.

Writing a proposal that survives organizational skepticism

Conversations don’t change organizations. Proposals do. But only if they address the real concerns, not just the technical ones.

Turning a vague opening into a concrete initiative

The Director asked a question. Your manager passed it along. The distance between that and an actual project is entirely on you.

HOW IT WORKS

From inbox to insight

1

Receive Raj’s email

A casual mention that the Director is asking questions. Not a mandate. An opening.

2

Respond with your approach

Your real email, your real words. How you frame your interest signals how you’ll lead the effort.

3

Lena, Marco, and Aisha respond

Three stakeholders with three philosophies: pragmatism, rigor, and hard-earned skepticism from the last attempt.

4

Navigate technical and political alignment

Each conversation shapes what your proposal can look like. Buy-in earned from one team constrains what you can offer another.

5

Submit your proposal

You write the proposal — or you don’t. Talks without documents don’t change organizations.

6

Get your debrief

A personalized coaching assessment: how you built influence, navigated skepticism, and what your approach reveals about your Staff Engineer instincts.

Start this scenario

Already playing? Log in

The duplication is growing

Three teams, three implementations of the same thing. The problem is visible to everyone, but solving it requires influence you don’t technically have. The question is whether you can turn a casual "thoughts?" into organizational change.

Start The Platform Proposal

Free — no credit card required.