LEADERSHIP SCENARIO

The Architecture Tax

5-7 day simulationAdvancedStaff+ IC Track

Last week, billing went down for two hours. Three teams opened three dashboards with three different query languages. Nobody could see the full picture. It took 45 minutes just to establish what was broken. Your VP asked you to drive observability alignment — understand why teams made different choices and write an RFC with a clear recommendation. Not a committee. A decision.

Start this scenario See how it works

Already playing? Log in

From

Jordan Ellis

Subject

Observability — need your help

You were on the incident bridge last week when billing went down. Two hours to resolve because three teams had three dashboards and nobody could see the full picture. It took 45 minutes just to get everyone looking at the same data. That's unacceptable. I need you to drive alignment on observability. Talk to the teams. Understand what they're using and why. Write an RFC with a clear recommendation. Not "let teams choose." Not "form a committee." A recommendation. I'll back whatever you recommend if the reasoning is solid...

THE SITUATION

Three dashboards, three query languages, zero shared understanding

DataFlow has a growing observability problem. Team Alpha uses Datadog with custom dashboards. Team Beta built a homegrown Prometheus pipeline over 18 months. Infrastructure runs a centralized ELK logging stack. All three work individually. Incident response is a nightmare.

Last week’s billing outage took two hours to resolve — not because the fix was hard, but because it took 45 minutes for three teams to establish a shared understanding of what was broken.

Jordan Ellis asked you specifically because two previous standardization attempts died in committee. He wants one person with cross-team credibility to drive a recommendation. Not a process. A decision.

The challenge: Nina is skeptical of standardization after failed attempts. Omar spent 18 months building the Prometheus pipeline. Elena just wants something that works operationally. Each person’s perspective is valid. Your RFC needs to honor all of them while still recommending one direction.

WHAT YOU'LL PRACTICE

4 leadership skills, one scenario

Driving cross-team standardization without steamrolling

Three teams made three choices for three good reasons. Standardization that ignores why they diverged will fail the same way the last two attempts did.

Understanding before proposing

Before you can recommend, you need to understand why each team built what they built. The reasons matter more than the technology.

Writing an RFC that synthesizes competing perspectives

A recommendation isn’t a vote. It’s a judgment call that acknowledges trade-offs and still commits to a direction.

Navigating personal investment in technical decisions

Omar spent 18 months on the Prometheus pipeline. Telling someone their work will be replaced requires more than a better architecture diagram.

HOW IT WORKS

From inbox to insight

Receive Jordan’s alignment directive

A clear mandate: talk to the teams, understand the choices, write an RFC with a recommendation. No committee.

Reply with your approach

Your real email, your real words. How you structure the engagement signals whether this will feel like collaboration or imposition.

Nina, Omar, and Elena respond

A skeptic, an 18-month investor, and a pragmatist. Each reacts based on how you engage with their perspective.

Navigate competing technical investments

Each conversation reveals trade-offs. The right recommendation isn’t always the best technology — it’s the one the organization can actually adopt.

Submit your RFC

You write the recommendation — with trade-offs acknowledged, a migration path proposed, and a clear direction committed.

Get your debrief

A personalized coaching assessment: how you balanced technical judgment with organizational empathy, and what your RFC process reveals.

Start this scenario

Already playing? Log in

The next incident is coming

Three teams, three monitoring stacks, built for three good reasons. The problem isn’t that anyone made a bad choice — it’s that the system has no shared language for "what’s broken?" Your RFC decides whether DataFlow gets one. The question is whether you can honor what each team built while still driving a recommendation.

Start The Architecture Tax

New to Prism Signal? Start with The Platform Proposal — free, no credit card.