Scott Farquhar

If his name comes up in a clip about how teams should be run, it is usually attached to two ideas: software built for groups rather than individuals, and a culture designed to hold up over long stretches of time. That pairing is what his career indexes. An Australian entrepreneur and chief executive, born in Sydney in December 1979, he spent the middle of his working life turning prototypes into platforms and user bases into communities.

The method came together early and slowly. His first projects showed a knack for taking loose, informal opportunities and giving them formal structure. Mentors and competitors acted less as obstacles than as constraints that sharpened his judgement, and progress arrived as a run of small improvements that eventually added up to something recognisable as a method. One habit stands out from the start: he treated distribution and trust as things to be designed deliberately, not as by-products of a good product.

At scale, the decisions that drew attention were about product architecture, incentives and governance — and they became reference points for other people trying to build with discipline rather than noise. Failed experiments were written down as knowledge instead of buried. Engineering, design, operations and policy were made to work together, which is what produced coherence when pressure arrived. What marked the period was less the size of the thing built than the fact that the standard of work could be repeated.

Later he leaned into mentorship, institutional memory and standards portable enough to survive being handed to someone else. The record sits in talks, memos and design notes, and what remains lives mostly in how organisations and teams operate by habit rather than in any single product. It is a demanding approach — think clearly, execute carefully — and its influence tends to be measured in the people who carried it forward.