Radical Transparency as Information Infrastructure
CEOs get bad data because they give bad signals — transparency is a reciprocal exchange protocol
Most CEO advice treats organizational transparency as a sentiment or cultural value — 'build psychological safety,' 'create open-door policies.' Khosrowshahi reframes it as a mechanical information protocol: the quality of data a CEO receives is directly downstream of the quality of data the CEO emits. If you communicate smoothed, optimistic, political-safe messages downward, your organization learns that smoothed, optimistic, political-safe messages are the expected format — and that's what flows back up to you.
The practical implication is that organizational information quality is not an HR problem or a trust problem. It is a signal problem. The CEO's communication style is the training data for what the organization considers acceptable to say. Once reframed this way, the fix is mechanical: consistently transmit accurate, uncomfortable data downward, and the organization's information-sending behavior calibrates to match.
Khosrowshahi extends this with structural reinforcement: supplement the formal reporting chain with direct random-access channels to operators several levels down. Engineers in particular are valuable because they have low political incentive to filter — they will describe system reality accurately because their professional identity is tied to technical correctness, not organizational harmony.
- The CEO's communication style is the training data for the organization's information culture — bad inputs produce bad outputs.
- Most CEO failures are data failures, not judgment failures — wrong decisions made on wrong information.
- Transparency is a reciprocal exchange: give real assessments first, and employees update their model of what is safe to report.
- Random direct access to operators several levels down provides an unfiltered reality check that formal reporting chains cannot.
- Accepting the tradeoff of scaring away comfort-seeking employees is worth it — the remaining team has self-selected for reality tolerance.
- Audit your own outgoing signal qualityReview recent all-hands, team updates, and 1:1s for evidence of smoothing, hedging, or omission of bad news. The frequency of uncomfortable truths in your outgoing communications is your baseline.Pro tipAsk a trusted direct report: 'When I share bad news, do I lead with it or bury it?' The answer is usually diagnostic.
- Transmit accurate uncomfortable data firstIn the next major communication opportunity, lead with the real assessment before the positive framing. Name the problem directly. Accept that some people will be unsettled — that is the point.WarningDo not confuse radical transparency with pessimism. The goal is accuracy, not negativity — positive news should be transmitted with equal directness.
- Build random direct-access channelsSchedule regular direct conversations with operators 3-4 levels below you, outside the formal reporting chain. Engineers are particularly valuable targets because they have low political filtering incentive.Pro tipKeep these sessions structured as information pulls, not performance reviews — you are asking what is actually happening, not evaluating the person.
- Hold the line on the tradeoffWhen HR or advisors warn you that your directness is scaring people, acknowledge the tradeoff explicitly and maintain it. The people who leave because they cannot handle accurate information were a liability in the information infrastructure.Pro tipDocument your reasoning at the time so you can return to it when the social pressure to soften increases.WarningThis tradeoff has a limit in high-attrition environments — calibrate the intensity to the organization's capacity for change, not just your personal tolerance for discomfort.
- Monitor the upward flow changeTrack whether the quality of information coming up to you changes over 60-90 days. Specifically: are people surfacing bad news earlier, naming problems more precisely, and disagreeing more openly in meetings?
On arriving at Uber, Khosrowshahi assessed that the company had a real culture problem requiring a turnaround, not just operational tuning. He said this plainly to the organization. His head of HR told him directly that he was scaring people and should soften the message. He declined, accepting the tradeoff that some people would leave.
Khosrowshahi builds systematic sessions with engineers 4 levels below him, outside formal reporting chains. His stated reason: 'Engineers don't give a [expletive]. They'll tell me anything and everything.' He treats this as a calibration check against the filtered information that flows through management layers.
Khosrowshahi noted a systematic gap between what AI company CEOs say in private versus public: 'The private conversations I hear about the sheer amount of disruption that they anticipate... and then when I see them on CNBC or Davos, it's be fine and figure it out.' He applies his own transparency framework by giving the honest private assessment publicly.
Learned primarily from Barry Diller at IAC, who was known for cutting through organizational layers to source information directly. Diller's style was to go around the official reporting chain when he wanted accurate data. Khosrowshahi internalized the mechanism and extended it into a proactive rather than reactive practice — rather than bypassing the chain when suspicious, he built systematic direct access into his management operating model.
The framework was stress-tested on his first day at Uber. After assessing the company, he told the organization plainly that Uber had a culture problem, not a tuning problem — that it was a real turnaround. His head of HR told him he was scaring people. Khosrowshahi's response was deliberate: 'I'm going to err in telling the truth and potentially scaring someone away. I'll take that.' The people who stayed after that signal were self-selected for being able to handle reality — which improved the organization's overall information quality in subsequent months.