Andrew Luxem

Silent Meetings: Replace presentation narration with shared evidence and a decision

A presenter spends most of the meeting narrating background, leaving little time to test the evidence or make the decision. This brief shows the mechanism, failure check, and adoption test.

Andrew Luxem
Andrew Luxem
CRM, Lifecycle & AI Strategy

2 min read
The argument
A presenter spends most of the meeting narrating background, leaving little time to test the evidence or make the decision.
The skill should replace presentation narration with shared evidence and a decision.
Use the format for one recurring decision. Track repeated clarification questions, decision time, and actions closed by date.

A presenter spends most of the meeting narrating background, leaving little time to test the evidence or make the decision.

The useful response is not more ceremony. It is a mechanism that can replace presentation narration with shared evidence and a decision.

What the skill produces

The Silent Meetings skill turns supplied context into a self-contained pre-read, a defined reading block, a recorded decision, and dated actions. It should expose missing evidence instead of inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the practitioner remains responsible for the facts and final decision.

Run the mechanism

  1. Write the decision request, evidence, recommendation, risks, and open questions.
  2. Reserve measured reading time before discussion begins.
  3. Use the remaining time for questions, the decision, and owned follow-up.

The owner should review the output against the original evidence before it is used. Any unresolved assumption stays labeled, with an owner and date when it affects the decision.

Failure check

A silent meeting fails when the document needs narration, the reading block is skipped, or the discussion has no decision protocol.

Attribution boundary

The format should be attributed to Amazon silent-reading practice when presented publicly; the skill focuses on making that practice runnable.

Adoption test

Use the format for one recurring decision. Track repeated clarification questions, decision time, and actions closed by date.

Keep the skill only if it improves the artifact or decision against that baseline. Revise the playbook when the same failure survives more than one review cycle.

Infographic

STOP NARRATING THE MEETING infographic
Andrew Luxem
20 years building CRM and lifecycle programs at Amazon, Ancestry, and Stanley Black & Decker.