The New Medium — Boardroom Workflow

Some decisions deserve
more than one voice.

Architecture choices, build vs. buy, tech stack bets, team structure, strategic pivots — these are the decisions that compound. A single-agent answer misses the tension that makes them hard. The Boardroom structures real disagreement into a usable output.

Zone 1 — When to Use It

Architecture Decisions

Choosing between approaches with long-term implications. When the wrong call compounds for years.

Build vs. Buy

Evaluating whether to build internally, adopt a dependency, or use a managed service.

Strategic Pivots

Direction changes that affect the roadmap, team, or product positioning.

Risk Assessment

Pre-launch or pre-investment review of a decision's failure modes.

Zone 2 — The Four Benches

Technical Bench

Engineering Lens

Architecture · Performance · Debt

CTO perspective · Senior engineer · Security lead · Infra specialist

Strategic Bench

Business Lens

Value · Timing · Positioning

CEO perspective · Product strategist · Market analyst · Customer voice

Risk Bench

Risk Lens

Failure modes · Reversibility

Risk officer · Legal/compliance · Ops · Finance

Product Bench

User Lens

Experience · Adoption · Friction

Product manager · UX researcher · Support lead · Power user

Zone 3 — The Session Flow

The Debate Pattern

structured disagreement → synthesis

Frame the Question

One precise question. Not 'should we rewrite?' but 'should we migrate auth to a dedicated service before Q3, given current load?'

Positions

Each active advisor takes a position. Stated clearly with the 2-3 strongest reasons. No hedging.

Challenge

Advisors challenge each other's reasoning, not conclusions. What assumption is most likely wrong? What's the steelman of the opposing view?

Synthesis

Facilitator synthesizes: areas of agreement, core tension, recommended path, what would change the recommendation.

Zone 4 — Output

Session Record

Saved to docs/BOARDROOM/sessions/{date}-{slug}.md. Includes: the question, each position, key challenges, synthesis, and recommended path. Permanent record — can be referenced in epic retrospectives.

Decision Rationale

Not just what was decided, but why. Which risks were accepted. What assumptions the decision depends on. What would trigger a revisit. This is what prevents relitigating the same decision 6 months later.