Before the Room: Staff+ Engineering Leadership Without Authority
by Mike Salari · Books for mobile engineers
$199
Read the free sample (desktop)Read the free sample (mobile)
The technically correct answer is the entry fee.
Your design can be right and another team can still say no.
Everyone can agree in the architecture review and reopen the decision two days later.
A migration can be right for the company and irrational for every team asked to move first.
Every team can report green while the customer path has never worked end to end.
Before the Room is a field guide for those moments.
It is written for senior, staff and principal engineers, tech leads and architects who are accountable for outcomes across teams they do not manage.
It does not teach persuasion. It gives you a practical system for moving decisions when technical correctness is necessary and no longer enough.
Surface. Shift. Secure.
The book is built around a simple operating system.
SURFACE
Find the decision that is being made. Identify:
who owns it
who can say yes
who pays the cost
who owns the risk
what evidence would settle it
what could reopen it later
SHIFT
Change the decision with the right artifact, trade-off and conversation. Not another slide deck. Not a louder technical argument. A concrete object that makes the decision easier to understand, compare and own.
SECURE
Make sure the outcome holds. Define:
the escalation threshold
the evidence that proves the outcome
the follow-up signal
the conditions that legitimately reopen the decision
Agreement in a meeting is not yet a durable decision.
What this book helps you handle
Before the Room is built around situations engineers meet at senior and staff+ level:
another team owns the dependency and refuses your proposed change
an architecture decision keeps reopening after everyone agreed
a public deadline exists before engineering has validated the scope
a migration benefits the organization but costs every adopting team first
five teams all mean something different by done
every dashboard is green while the integrated outcome is still unproven
a technically brilliant engineer becomes a private veto
an escalation is turning into blame instead of producing a decision
an incident needs restoration now and learning later
important staff+ work disappears by promotion-review season because nobody preserved the evidence
The goal is to make the real decision, trade-off, owner and evidence visible enough that the organization can act. Sometimes the correct outcome is still no.
16 practical artifacts
The book includes a complete artifact system for turning conversations into durable decisions:
Hidden-decision worksheet
Stakeholder and incentive map
Decision-rights map
Decision-rights transfer
Pre-alignment plan
Architecture decision record with reopen criteria
Three-option scope memo
Strategy one-pager with adoption triggers
Outcome contract
Migration wave plan
Weekly operating-system checklist
Outcome evidence table and truth test
Escalation brief
Systems postmortem
Evidence ledger for promotion
Thirty-day repair plan
Each artifact exists because some decisions are too important to survive as conversations alone.
Also inside the book
20 chapters in five parts, each ending with the move, the artifact, the signal, the level, the boundary and the line to say
12 figures
three sections where the method fails on purpose, and what to do then
notes on the sources behind the research and platform claims
an operational index: problem, chapter, artifact and the line to say, with page numbers
What you will learn
You will learn how to:
uncover the hidden decision underneath a technical request
distinguish a real technical objection from an incentive conflict
identify who proposes, decides, pays, executes and can reopen
pre-align without rigging the room
turn impossible deadlines into explicit choices
make cross-team migrations economically adoptable
stop architecture decisions from drifting after the review
separate local completion from outcome evidence
escalate without turning status into a weapon
attach accountability to control instead of blame
turn ambiguity into executable work
preserve evidence of staff+ impact while the work is still alive
Choose your edition
BOOK
The complete Before the Room book, PDF and EPUB. Best if you primarily want to read and study the system.
BOOK + FIELD KIT
Everything in the Book edition, plus the reusable operating kit for applying the system at work:
Before the Room PDF and EPUB
the complete Field Kit
all 16 practical artifacts, fillable
fillable workbook
Surface, Shift, Secure field card
Best if you want to use the system, not just read about it.
TEAM / 10 READERS
Everything in the Book + Field Kit edition, licensed for up to 10 people inside one organization. A good fit for:
staff+ development cohorts
architecture groups
platform teams
technical leadership programs
engineering book clubs
senior-to-staff development
Who this is for
senior engineers moving into broader scope
staff engineers
principal engineers
tech leads
software architects
platform engineers
mobile leads
senior individual contributors whose outcomes depend on teams they do not manage
If your work increasingly involves coordination, adoption, architecture, trade-offs, escalation and decisions across organizational boundaries, this book is for you.
Who this is not for
beginners in engineering
readers looking for a generic management book
readers looking for a guide to office politics
readers looking for a persuasion or manipulation handbook
anyone hoping to replace technical competence
anyone expecting every organization to make the decision they want
The framework does not give you authority you do not have. It helps you work with the authority, incentives, evidence and decision rights that already exist.
Why this title
The visible meeting is often only the final stage of a decision: the architecture review, the launch meeting, the escalation, the promotion committee.
The important work often begins earlier:
surfacing constraints
finding the real owner
understanding the trade
creating the artifact
testing what would change the decision
deciding what evidence will prove the outcome
By the time the room is full, the quality of that earlier work often decides what the room can realistically decide.
About the author
Mike Salari is a staff mobile engineer with about fifteen years of building production mobile software and more than five hundred technical interviews conducted from the hiring side.
Before the Room comes from that practice, not from pretending organizational work can be reduced to a perfect formula. The scenes are composites, and the examples are built to be used, challenged and adapted to your own environment.
BEFORE THE ROOM
A field guide to leading outcomes you have no authority to command.
Surface. Shift. Secure.
Resources: https://salari.dev/books/before-the-room