Maverick: The Success Story Behind the World's Most Unusual Workplace
Source: https://www.hachettebookgroup.com/titles/ricardo-semler/maverick/9780446670555/ ↗
Semler inherited his father's Brazilian manufacturing company at twenty-one and proceeded to dismantle almost every feature of conventional industrial management — no organisational chart, no dress code, employees setting their own salaries, managers being reviewed by their reports.
The company not only survived but thrived, and Maverick is his account of the experiment.
For product direction the book is useful not as a playbook (Semler himself says it is unrepeatable) but as a case study in how radically organisations can be restructured if the experiment is pursued seriously.
Read alongside McCord's Powerful and McChrystal's Team of Teams for complementary radical restructurings.
The book is dated in places but the argument is not.
Central argument
Semler argues that conventional management controls — hierarchy, fixed salaries, rigid job descriptions, top-down strategy — are not prerequisites for organisational performance but obstacles to it. At Semco, removing those controls and distributing authority radically to workers, including letting employees set their own pay and evaluate their managers, produced a more resilient and profitable company than the conventionally managed firm he inherited. His core thesis is that trust, transparency, and genuine autonomy are not idealistic luxuries but operationally superior to the surveillance and control paradigm dominant in industrial management.
Critique
The central tension the book never fully resolves is the question of replicability under structural conditions Semco happened to enjoy: a privately held company, a founder with near-total ownership authority, and a specific Brazilian industrial context in which labour relations and market pressures differed sharply from publicly listed firms or fast-moving technology markets. Semler himself concedes the experiment may be unrepeatable, but this admission sits awkwardly against the prescriptive energy of the narrative — it is never made clear which elements of the model travel and which were artefacts of his unique position. A thoughtful reader is left admiring the case study while lacking any principled framework for deciding what, if anything, to transfer.
Why it matters for product
For a CPO, the book's most direct application is to the perennial tension between product team autonomy and organisational control: Semler's evidence that removing managerial overhead can increase rather than decrease accountability challenges the instinct to add process and reporting layers when delivery slows. It is particularly pertinent when thinking about how discovery teams are structured — the question of whether product managers, designers, and engineers self-organise around problems or are coordinated top-down maps almost directly onto the experiments Semco ran with autonomous business units. Read against McCord and McChrystal, it helps triangulate what conditions actually generate high-performance autonomous teams versus which autonomy frameworks are performative.