Manage Through the Work
Leadership happens through direct engagement with the substance of the work itself, not through 1:1s or pure people-management.
Manage the work, not the people
A design leader who manages the design team but does not design is not, on Brian Chesky's account, a design leader, and a lawyer who manages other lawyers but does not read the case law is not practicing law.1 The rule behind both is stated without qualification: "You manage people through the work. You don't manage the people, you manage the work. Otherwise, what are you doing?" The primary surface of management, in other words, is the work itself rather than the people doing it.
Chesky does not remove relationships from the picture. "Maybe a couple times a year you go out to dinner with a direct report, ask about their family, build relationships," he allows. "You should have relationships." His distinction is that this is human connection, not day-to-day management, and that management proper happens in the substance of what is being built.1
Every field has its "you must code"
Chesky uses engineering as the baseline, arguing that every engineer needs to code and that even engineering managers need to code, then generalizes it: "Whatever the version of that is for your field, you need to code. So if you're a lawyer, you're not just managing people. You have to actually read the case law and you have to get involved."1 Design leaders must design, legal managers must engage with the law itself. The abstraction he rejects is the self-description "I coordinate the people who do the real work," which he treats as a role that loses its justification once direct access to the work becomes cheap.
Why he frames it as a survival test
Chesky presents the principle as newly consequential in the AI era. He names two types he expects will not survive: pure people managers who treat leadership as coordination, motivation, and recurring one-on-one support with no contact with the work, and rigid non-adapters who will not learn the tools. His argument about the first is specific. It is not that people management becomes worthless, but that the only-managing-people model loses its footing when, as he puts it, everyone is "so close to the details, to the data" that being hands-on is available to all. When the cost of having context collapses, the value of a role that mostly mediates between people who do have context collapses with it.1
He grounds this in figures he admires. He cites Jony Ive, who in his telling "manages design. He designs and he leads people," Frank Lloyd Wright, who managed his studio through the designs rather than through weekly check-ins, and John Wooden, who coached through relentless attention to inputs down to how players put on their socks. Each, in Chesky's reading, led by being the most deeply engaged with the substance the team produced.1
The 1:1 critique and its limits
The sharpest target is the manager who runs many recurring one-on-ones and operates as a mentor or therapist: "I do not think people who have lots of recurring 1:1s are going to survive because what they're doing is: 'oh, you come to me with whatever your problem is, I'm here to help you.' That kind of leadership style is not going to work. You need to have context."1 Chesky argues that such a leader can only help by receiving problems and mediating, which requires context they no longer have when they are removed from the work. This places the pattern alongside Fake CEO, which separates the real job of building product from the performance of the role, and it pairs with Leader Should Know Every Job Poorly, which sets how much of the work a manager should be able to do.
Chesky himself surfaces the tensions. The critique lands cleanest at mid-scale, where coordination-only roles may still hold value at the largest organizations. It also sits uneasily with his own claim that a CEO should spend two to three hours a day on recruiting, which looks like managing through relationships; his answer is that recruiting builds the conditions for work-based management rather than being one-on-one support.1 And the principle is clearer as a hiring rule going forward than as advice for managers who spent a decade not doing the work and cannot become practitioners overnight.
Practiced by
Connections
Loading connections…
References
- 01
How Brian Chesky Is Redesigning Airbnb for the AI Era
Brian Chesky · podcast · 2025
Related