Leadership Case: Designing the Future of Work (Distributed Work)
This case got me thinking a lot — I absolutely loved it.
Everyone understands the principles in it; the hard part is execution.
It's like losing weight: "eat less, move more."
There's no secret martial-arts manual; the skill is built day by day.
What I most need to improve next is execution — actually making things land.
A good operating system empowers a team and helps it "win" better.
Making the team succeed is every leader's ultimate dream.
Case Overview
Atlassian turned "distributed work" (employees collaborating without being in the same location) into a company-wide system: policies + tools + metrics + space. The data is striking: faster hiring, higher satisfaction, more controllable costs, stronger connection. 2019–2024: a product portfolio (Jira/Confluence/Trello/Bitbucket), annual revenue reaching $4.17B, 250k+ customers, covering 85% of the Fortune 500. The distributed policy became part of company strategy. 2020: the two co-founders made a "one-way door" decision: employees can work from anywhere in the 13 countries where the company has legal entities, with no mandatory return to the office. 2022–2024: they set up the Team Anywhere Lab (a ways-of-working lab) to run experiments around a system of work built on "information → goals → execution": page-led meetings, async-first, regular in-person gatherings (ITGs), and more. Space and data: they invented Cost Per Visit and Tidal Flows, and used them to close floors, redesign spaces and open new sites, matching real usage of "few people on site permanently + teams gathering periodically." Results: job applications doubled, offer acceptance rate +20%, 92% say distributed work lets them do their best work, 91% say it's an important reason they stay; one "swap meetings for Loom" experiment saved 5,000 hours in two weeks.
Class Notes
01 | Using a "leave experiment" to reveal organisational fragility
Put key people on a mandatory one-week leave.
See which processes stall and which knowledge exists only in someone's head.
Two kinds of fragility get exposed:
System fragility: handoffs with no documentation, meetings that depend on one person, approvals done over private chats.
Financial fragility: revenue concentrated in one client, tight cash flow, heavy fixed costs for physical offices.
A truly resilient organisation can "keep running fine with one person missing" at any time.
02 | Remote Work: Benefits vs. Challenges. Benefits
Services/support cover more time zones.
Better hiring: a larger talent pool and more favourable demographics.
Challenges
Need a system: without standard operating procedures and documentation, remote only gets messier.
Misplaced effort ("don't work hard"): it's not that people don't try, but that the effort goes into low-leverage synchronous meetings.
Disengaged teams: trust decays over time.
Meeting addiction: Zoom hogs the whole day, and deep work gets fragmented.
03 | Key plays. Product and rhythm
An intangible product (software) means output must be amplified through processes and accumulated knowledge.
Flexible hours: guarantee at least 4 hours of time-zone overlap each day, and move everything else forward asynchronously.
"Replicate interaction": even online, you need the weak ties of "chatting while walking" — use short videos, walking 1:1s and open collaboration hours to stand in for the office kitchen. Culture & Norms
Write habits down as "explicit norms": how to set up a meeting, how to do documents first and discussion second, how to decline unnecessary meetings.
Explicit/Transparent: information is public by default, lowering the cost of "asking around." Documentation-first
Documents are "AI's raw material": write down goals, decisions, dependencies and next steps clearly, and only then can AI search, summarise and remind.
Move beyond the "remote vs. in-person" debate: as long as documentation + async are in place, in-person time is just a periodic "amplifier." Emphasize differences
Remote amplifies individual differences: those who are self-driven, write clearly and collaborate asynchronously will stand out markedly.
Management should put "output and contribution," not "hours online," into performance reviews. Communication
Digital meetings come with "5 minutes of silent reading together before the meeting."
Ask: "Does being together actually bring a net gain?" If the answer is unclear, let async go first. AI assistant (AI recommend you what to do?)
Make AI the "recommendation engine for your schedule and tasks":
read your documents and meeting notes → remind you of next steps → generate to-dos and assignments.
Offer suggestions and templates for "replacing meetings with video/documents." Formalizing good practices
Lock in policies & procedures:
Every meeting invitation must include "goals and expected outputs."
Recording and filing of notes by default.
A purposeful in-person gathering every quarter (3–5 days) to fully recharge the "connection battery."
04 | Two iron rules under the remote assumption
Transparent process: you can see who's pushing things forward, where they're stuck, and when they'll deliver.
AI better: only if things are "well written and structured" can AI truly act as an assistant.
05 | The pitfalls of hybrid (disadvantages of location)
Geographic bias: people near headquarters are more "visible," while remote people are left passive.
Split cultures: the office forms cliques, and remote staff feel like outsourcers.
Efficiency loss: the same team stratified by location, and decisions slow down.
Govern hybrid with "remote-first" processes. All important information is completed in documents first, then confirmed synchronously.
What are the assumptions about people and work behind remote work?
Assumptions: frontline employees are able and willing to manage themselves; pushing information down improves quality and speed; a sense of belonging drives performance.
Agree: provided goals are clear, incentives are aligned and training is in place, self-management improves responsiveness and reduces hierarchical friction.
Risks: unclear goals lead to loss of control; seniors mentoring newcomers is uneven; when external volatility is high, a stronger central coordinator is needed.
Pros and cons of self-managing teams?
Pros: faster decisions on the ground; stronger engagement; problems surface earlier.
Cons: inconsistent standards; short-term performance swings; leadership development has to keep up.
How do you make it land?
Three steps:
-
Clearly define the boundaries (list the red lines on safety/quality/finance).
-
Training + shadowing: rotate team leads, dual sign-off on key decisions.
-
Rolling reviews: retrospectives every 4–6 weeks, keeping a rollback switch and a "library of experience templates."
Overall, I think remote work is more conducive to becoming AI-native — using AI to amplify reuse, and rhythm to sustain connection.
If you're also running a remote/hybrid team, I'd love to hear from you in the comments:
What's your most painful remote scenario?
What are the 3 little things you'd most like AI to automate for you?
—— End ——