Sam Altman’s Secret Email That Instantly Kills Work Friction
How OpenAI Uses a "Magic Word" to Cut Through Bureaucracy and Move at AI Speed
TL;DR: OpenAI has a special email address —
friction@— where any employee can report things slowing them down. Leadership reviews these emails, and if the issue is big enough, even the CEO steps in to fix it now. It’s a powerful tool for speed, but some say it creates chaotic "fire drills" for already-busy teams.
What Is "Friction" at OpenAI?
Imagine you’re building a rocket ship, but every time you need a wrench, you have to fill out three forms, wait for a manager to sign off, and then find out the wrench is broken. That’s friction — the small, annoying obstacles that make work harder than it needs to be.
At OpenAI, "friction" isn’t just a word — it’s a formal process. Any employee can email friction@openai.com to flag something broken, slow, or silly. It could be:
- A software tool that crashes constantly
- A meeting that wastes everyone’s time
- Not enough IT vending machines (yes, really)
- A process for getting API credits that takes forever
Important Point:
The word "friction" acts like a magic override button. When leadership takes a friction report seriously, it carries the weight of CEO Sam Altman or President Greg Brockman. Teams are expected to drop everything and fix it — fast.
How the Friction System Works: Step by Step
-
You Spot a Problem
Something is slowing you or your team down — a broken tool, a dumb rule, a missing resource. -
You Email
friction@
No forms. No approval chain. Just write what’s wrong and hit send. -
Leadership Triages the Inbox
A dedicated team (led by VP Irina Kofman) reads every email. They decide: Is this a real blocker? Does it affect many people? Is it worth leadership’s time? -
Action Is Taken — Fast
- Small fixes: Assigned to the right team with a deadline.
- Big issues: Altman or Brockman may personally intervene.
- Example: Employees complained about parking. Leadership launched a pilot prioritizing spots for long-commute staff.
- Example: Teams needed a reliable way to grant API credits at scale. A new system was built.
- Progress Is Shared Company-Wide
Every month, a Slack update shows what was fixed — so everyone knows the system works.
Why It Was Created: The Growing Pains of a Fast-Scaling Company
OpenAI is growing fast — expected to hit 8,000+ employees by end of 2026, with offices worldwide. With that growth comes:
- More meetings
- More approvals
- More "we’ve always done it this way"
- More tiny frustrations that compound
Important Point:
As Fidji Simo (former CEO of Applications) put it:"Companies rarely become bureaucratic all of a sudden. It happens one unnecessary meeting, one extra approval, one small frustration at a time. Each makes it only 1 or 2% harder to do your job… but those frictions compound."
She joined in fall 2025, did a three-month "listening tour", and heard the same thing again and again: "We’re slowing down." So she formalized the friction@ process — assigned an owner, added tracking, and made sure leadership followed through publicly.
The Good: Why Employees Like It
- Anyone can speak up — intern to VP, no gatekeepers.
- Leadership actually listens — and acts.
- Problems get fixed before they fester.
- Transparency — monthly updates prove it’s not theater.
- Cultural signal: "We care about speed. We care about you."
Former employee to Fortune:
"Literally anybody can complain about big company bullsht directly to Sam and they can act on it. If you want to ruthlessly cut through bureaucracy, you have to be ruthless about it."*
The Bad: Why Some Find It Disruptive
Not everyone loves the "drop everything" nature of friction escalations.
- Teams are already "underwater" — understaffed, overworked, working late into the night.
- A friction email can trigger a fire drill: Stop your project. Fix this now.
- The reporter thinks their issue is #1. The team getting the order has 10 other #1s.
- "Shut up and do it" culture — if Altman or Brockman backs it, debate is over.
Former team leader:
"It’s the single most disruptive thing you could do… a drop everything kind of deal."
The Bigger Picture: Speed vs. Stability in the AI Race
Why tolerate the chaos? Because the AI race doesn’t wait.
- Rivals: Google (Gemini), Anthropic, xAI, Meta — all moving fast.
- In December 2025, OpenAI declared a "Code Red" — all hands on deck to accelerate key products.
- "Lockdowns" (intense, focused sprints) are common in tech — like when Zuckerberg locked down Facebook to launch Facebook Live.
Important Point:
In this environment, shaving off every drag on speed trumps comfort. The friction system is a feature, not a bug — a deliberate choice to favor velocity over predictability.
A Familiar Pattern: The Amazon "Question Mark" Email
This isn’t new. Jeff Bezos at Amazon did something similar:
- Customers emailed
jeff@amazon.com. - If Bezos cared, he forwarded it to the responsible team with just a question mark: "?"
- That "Jeff B escalation" meant: Drop everything. Find the root cause. Fix it. Report back.
OpenAI’s friction@ is the internal version — same urgency, same top-down force, but aimed at employee pain points, not customer complaints.
Summary
| What | Why It Matters |
|---|---|
friction@ email |
Gives every employee a direct line to leadership |
| Leadership triage | Ensures only real bottlenecks get escalated |
| Executive involvement | Adds urgency and authority to fixes |
| Monthly Slack updates | Builds trust — proves the system works |
| Trade-off | Speed wins, but teams face disruptive "fire drills" |
| Inspiration | Modeled on Bezos’s "?" escalation emails at Amazon |
Bottom line: OpenAI uses "friction" as both a diagnostic tool and a cultural weapon — hunting down drag so the company can move at AI speed. It’s messy, intense, and not for everyone — but in a race where weeks matter, it might be their edge.
FAQ
1. Can anyone at OpenAI email friction@?
Yes! Interns, engineers, admins, managers — no restrictions. It’s designed to be completely open.
2. Does every email get a response?
Every email is read, but not every one gets escalated. Leadership triages — only the most impactful bottlenecks get the "drop everything" treatment.
3. What happens if a team ignores a friction escalation?
They don’t. If Altman or Brockman backs it, it’s treated as a top priority. Ignoring it isn’t an option — it’s a direct order from the top.
4. Is this unique to OpenAI?
The formal email address is distinctive, but the idea isn’t. Amazon’s "Jeff B escalation" (a single "?") is the most famous precedent. Other fast-moving tech companies have similar "escalation paths."
5. Has the system changed since Fidji Simo left?
No. She left in July 2026, but the friction@ process and monthly Slack updates remain active — now part of OpenAI’s permanent operating rhythm.