Key Takeaways
- The former CEO of Siemens managed direct reports without recurring calendar catchups, answering project proposals strictly with "OK" or "No."
- Marc Andreessen calls this extreme minimalism "1-bit communication," reducing managerial friction to binary signals.
- Jeff Bezos used a single "?" character forward on customer complaint emails to trigger urgent, systemic root-cause investigations at Amazon.
- Real-time unblocking beats scheduled status updates by removing executive calendar lag.
- The core method is formalized in The 1-Bit Executive Communication Systems.
The 1-Bit Executive Communication Systems
Executive calendars get choked by status updates and conversational drift. Two distinct binary protocols eliminate meeting theater and isolate operational failures:
Siemens Binary Approval Rule
Direct reports email project proposals or decisions; the CEO replies strictly with 'OK' (approved) or 'No' (rejected). If nuance is required, the employee must initiate an immediate, unscheduled conversation rather than waiting for scheduled calendar meetings.
As Shaan Puri observed about the Siemens executive: “They go, 'So, you don't have any recurring meetings with your direct reports to sit and just catch up and discuss?' And he goes, 'I don't entertain people and they don't need to entertain me.'”
Bezos '?' Escalation Protocol
CEO forwards customer complaints with a single character: '?'. This encodes a mandatory three-step investigation: 1) Is this customer's claim true? 2) Why did our system allow this to happen? 3) What systemic fix will ensure it never happens again?
Puri explained the discipline: “He trained the team that the question mark has a very specific meaning. If he sends you the question mark, it means: Is this true? Why is this happening? And what are we going to do about it? All encoded into a one question mark thing.”
Anecdote vs. Data Diagnostic
When customer anecdotes conflict with 98%+ positive operational metrics, assume the metric is incomplete and investigate the friction signal in the underlying machine.
When This Works (and When It Doesn't)
This framework works for CEOs managing large organizations who want to prevent executive calendar congestion, eliminate meeting theater, and spot hidden operational defects quickly. It forces team leads to submit crisp, decision-ready proposals instead of vague conversational agendas.
It fails in early-stage product discovery. If your team is still searching for product-market fit, binary approvals kill creative debates. You cannot give an "OK" or "No" to an ambiguous prototype idea that needs messy iteration. Use 1-bit protocols only when the operating model is defined and the primary goal is operational speed.
What to Do With This
Audit your inbox and calendar tomorrow morning. Pick your three most frequent recurring internal meetings: one-on-ones, status check-ins, or cross-functional reviews.
Cancel one recurring status meeting. Tell the project owner to send a three-sentence proposal whenever they need a decision, with a clear binary question at the end. Reply with "OK" or "No" within two hours. If they need to explain context that cannot fit in three sentences, tell them to walk over or call immediately for five minutes, make the decision, and hang up. Track how many hours of calendar time your team recovers across the week.