One email address, from system failures to vending machines

The solution is disarmingly simple: one email address, four steps.

Two real examples back up "it can be about anything":

One is a parking space, the other a business process — worlds apart in significance, but they go through the same door. That's the point: the system doesn't pre-judge what's "worthy" of being reported.

Bureaucracy is built 1% at a time

So why should a missing vending machine warrant the CEO's attention?

Fidji Simo gives the strongest argument for the system. She joined OpenAI in fall 2025 as CEO of Applications, and told Fortune:

Companies rarely become bureaucratic overnight. It happens one unnecessary meeting, one redundant approval, one small frustration at a time. Each one makes your job 1% or 2% harder, so it's easy to ignore. But friction compounds.

Fidji Simo, former CEO of OpenAI Applications

That statement contains a full causal chain — and explains why the email system is designed the way it is:

Individually, none of these things feels worth complaining about. It's just one extra meeting, just one more approval. Who's going to make a fuss over that? So nobody reports it. And if nobody reports it, nobody fixes it. Over a year, dozens of these add up. The company gets slower, but when you try to find the single culprit? You can't point to any one thing.

The fix, therefore, has to be extreme on both ends: a low bar for reporting — just send one email — so that trivial issues surface, and high enough stakes that the CEO gets involved, so that what surfaces actually gets fixed. Miss either end, and the system breaks down.

An email address wasn't enough — Simo added three more pieces

The email address had actually existed for a while, but nobody paid it much attention. It only started working after fall 2025.

When Simo came in, she spent her first three months on a "listening tour," asking people what was wrong and what she could fix. A recurring theme: the company had gotten big. How could it stay fast?

She added three things to the existing system:

These four pieces matter, because any company can set up a suggestion box email. It only works if the other three parts are in place. Without a dedicated owner, emails get buried. Without public progress updates, people stop sending after two failed attempts. Without executive backing, the named department can simply drag its feet.

Simo herself left OpenAI in early July 2026 to focus on her health and her health-tech startup. The friction@ process and the monthly Slack updates remain.

Two former employees had completely opposite takes

The report spoke to two former employees who had almost directly contradictory views on the same system.

The positive view: it gives leadership real on-the-ground feedback. Problems get handled before they fester, and teams keep moving forward. The bigger the company, the more critical this channel is.

The negative view lands on the people being pointed at. In a company where working past dinner or into the night is the norm, a friction email triggers an unwanted fire drill:

If Sam and Greg think it's worthy and it makes sense, then essentially a "friction" is launched, and the party that's blocking it is basically told to shut up and do it. This is no joke. It's a drop-everything thing.

A former OpenAI team lead

Put both sides together and the real cost of the system becomes clear: Who gets disrupted is decided by the reporter and the top brass — not by the team on the receiving end. Every time the priority lane is opened, that team's own carefully planned priorities get upended. In a hyper-competitive industry, OpenAI has decided the trade-off is worth it.

Bezos's question-mark emails faced outward. Friction faces inward.

This isn't a new invention. It brings to mind a more famous rule at Amazon: founder Jeff Bezos's question-mark emails.

Back then, customers could write directly to jeff@amazon.com. If Bezos thought something warranted the team's attention, he'd forward the email to them with just a question mark — not a single other word. It was known internally as a "Jeff B escalation," and the receiving team had to drop what they were doing, dig in, and fix it.

Both share a tradition: give everyone a known address, and use the boss's attention as a crowbar to pry open things the normal process can't. The only difference is which direction the crowbar points.

Four steps: any employee sends directly, no manager approval needed; it can be about anything — system failures, broken processes, office annoyances (the report cited the IT vending machine shortage); leadership reviews; if important enough, it reaches Sam Altman or President Greg Brockman, and the blocker is essentially told "drop it and do it."

Fidji Simo's (former CEO of Applications) take: companies rarely become bureaucratic overnight. It's one unnecessary meeting, one redundant approval, one small frustration at a time. Each one makes the job 1% or 2% harder, easy to ignore. But friction compounds. Nobody reports the trivial stuff → nothing gets fixed → after a year, it's piled up, but you can't identify the cause.

So the system is extreme at both ends: a bar low enough that one email suffices, so trivia surfaces; and stakes high enough that the CEO steps in, so what surfaces gets fixed. The address existed for a while but was ignored. It only started working after Simo joined in fall 2025, did a three-month listening tour, and added three more parts.

Fortune spoke to two former employees with almost opposite views. The cost is visible when you put them side by side.

Who gets disrupted is decided by the reporter and leadership — not the team being hit. Every time the priority lane opens, that team's planned priorities get overturned. One former lead said they received "dozens" over several years — the only scale clue in the report.

This is the same tradition as Jeff Bezos's question-mark emails at Amazon: give everyone a known address, use the boss's attention to pry open what normal process can't. Bezos's was open to customers, pressure from outside; friction@ is open to employees, pressure from within.