Business and Management

Someone just made responsible for a team can begin with Talking with Tech Leads (2021), in which first-time and seasoned leaders answer the same questions,[1] and Habits that Ruin your Technical Team (2018), a short mirror for a manager's own behaviour.[15] Anyone who runs meetings has A Coach's Guide to Facilitation (2024),[3] and the most widely read book here, Introducing EventStorming (2021), shows a whole company's process being laid out on a wall in an afternoon.[4]

For strategy there are THE ART OF STRATEGY (2026), a short introduction,[5] and Wardley Maps (2018).[16] A manager who wants to know when a number deserves a reaction can read Measures of Success (2026),[8] and one who wants to change how a team works, without authority to order it, Changing Your Team From The Inside (2020).[17]

People at the start of a career have Be effective (2025), on working methods that training tends to skip,[11] and Software Engineering - The Soft Parts (2025).[18] Those who have sat through one improvement programme too many may prefer to start with Corporate Sabotage Field Guide (2026).[2]

Management became a subject of study with the factories and railways of the nineteenth century, and the early twentieth gave it its first doctrines, the measurement of work and the principles of administration. The business school, the consultancy and the management book followed. After 1945 the study of people at work, of quality and of strategy grew into separate fields, and from the 1980s Japanese methods of production were widely copied in the West. Software added its own vocabulary after 2001, when a group of programmers published a short manifesto on working in small steps with the customer, and much recent writing on management comes from that industry.

The shelf reaches further back than any of this. THE ART OF STRATEGY re-reads an ancient treatise on war for business,[5] and two books read an ancient Chinese classic as advice on leading: THE ART OF LEADERSHIP (2026), in eighty-one short sections for those who would lead through purpose and integrity instead of pressure and control,[19] and the agile way (2026), a verse translation offered as an alternative to bureaucracy.[20] Building Organizational Intelligence (2026) traces its own subject to a sociologist's book of 1967.[7] The spread of software's methods into other work can be followed in The Agile Agency (2013), on creative agencies,[21] and The Lean Change Method (2014), on change programmes;[22] the newest books, 10X ORG – Powered by Org Topologies (2026) and Rethinking Capital Project Delivery (2026), are about organisations and projects that include AI.[23][24]

THE ART OF STRATEGY sets each part of its ancient text beside passages from a twentieth-century military strategist and a contemporary writer on mapping. The old text holds that success or failure can be judged before an engagement begins, by careful assessment of advantages, and that strategy is a matter of shaping conditions. It asks, before any contest, whose people are better trained and who gives clearer feedback, and advises keeping those who weigh such things. The modern strategist defines strategy as a tapestry of changing intentions that harmonises and focuses effort in an unfolding and often unforeseen world, whose purpose is to improve the ability to shape and adapt to circumstances so as to survive on one's own terms; the famous loop of observing, orienting, deciding and acting is to be run more quickly and less predictably than a competitor's. For success over a long period, the strategist adds, one needs a unifying vision attractive enough to draw in the uncommitted.[5] Wardley Maps is an edition of that mapping writer's own account, which builds a map from users' needs and the chain of components that serves them.[16] Impact Mapping (2014) applies a related discipline to software, linking what is to be delivered to the business goal it serves.[25]

Structure is the next question. Six Viewpoints of Business Architecture (2026) argues that the structural complexities of a business, in its accounting, its bundling and pricing, its outsourcing, can critically affect performance, and that aligning the computer systems with them is only a small part of the task. Thinking architecturally, on its account, helps to see how structure affects performance, to define and justify structural change and to explain it to those concerned; the booklet offers six viewpoints for doing so and was written for business analysts being pushed into architectural work. Its author finds popular accounts of the subject too much dominated by thinking in processes, and says plainly that the booklet is an incomplete draft.[6] Building Organizational Intelligence asks what makes an organisation collectively intelligent and names six connected capabilities: gathering information, making sense of it, deciding and acting, remembering, learning, and communicating. An organisation is unintelligent when one of these is weak or the loops between them fail, and the book warns that advanced systems are worth buying only if the organisation can use them, since technology sometimes merely amplifies what is wrong. It lists the labels under which vendors have sold parts of the idea, the agile enterprise, collaboration networks, smart work and now AI, and observes that organisations often fail to use the tools they have, or collect expensive ones without knowing how they will work together.[7]

Wholehearted (2025) rebuilds a classic cybernetic model of the viable organisation as a way of looking at relationships between people, scopes and scales,[26] and 10X ORG – Powered by Org Topologies, a business novel with sections of theory, argues that the design of the organisation has to come first if AI is to add to people's work.[23]

Talking with Tech Leads defines its subject as a leader responsible for a development team who still spends at least thirty per cent of the time writing code with it. Its introduction tells a fictional version of how the role usually arrives: a respected developer is taken to breakfast by the founder, told the company has won three large customers and must double the team, agrees to lead it, and sits wondering what to do next. Such leaders, the book observes, almost always work alone; a developer can ask other developers about a tool or a design, but there is seldom another lead at hand to ask about a problem with people. The author holds that writing some code is part of technical leadership, a technical background alone not being enough to steer a discussion or reduce a technical risk. The contributors lead teams in very large organisations and very small ones, in travel, finance, property, media and consulting; the interviews were given the same structure so that answers could be compared, and they show no single best way. The author acknowledges that many contributors are connected with one consultancy.[1]

Habits that Ruin your Technical Team names seven habits by which technical managers harm their programmers and says what to do about each.[15] The Leadership Game (2018) is the manual of a three-hour game in which participants try commanding, coaching and leaving a team to organise itself.[27] Dynamic Reteaming (2019) treats changes in a team's membership as inevitable and worth doing deliberately, with patterns for adding and losing members and for splitting, merging and rotating teams.[28]

Two books concern the conditions of work. The Ultimate Guide to Remote Work (2019) is one software company's account of working without an office from its founding,[29] and Mental Health in Tech: Guidelines for Mental Wellness in the Workplace (2018) is a short handbook on mental health at work in the technology industry, with the steps towards a policy and advice to leaders on how to speak about it.[30]

Measures of Success is about the numbers managers already look at. It proposes three questions for any measure, whether the target is being met, whether performance is improving, and how to improve. Comparing a figure with a target or with last month, it argues, says little; one or two data points cannot show whether a result is exceptional or within its usual range, and that is what decides whether to investigate at once or to improve the system patiently. Its first principle is that a manager does not manage the metric but the system that produces it.[8] The Mistakes That Make Us (2026) makes the companion argument about people: leaders who punish mistakes usually call it accountability, and a team at one company in its sample was instead rewarded for how it handled a failed product test.[9] Practicing Lean (2026) collects sixteen practitioners' accounts of their own early errors with one improvement method, and insists that the method has two pillars, flow and quality at the source, and is not only about speed.[10] Root Cause Analysis (2026) follows a team as it builds a programme for tracing failures to their causes without blame.[31]

Change itself has methods. The Lean Change Method runs a change programme as a start-up would run a product, planned on a canvas, cut down to the smallest viable changes and tested one at a time with the people affected.[22] Changing Your Team From The Inside begins with the reader and works outward to the team, other teams and the organisation.[17] The Agile Agency explains why older ways of managing projects fail in creative agencies and what can replace them,[21] and Rethinking Capital Project Delivery argues that stage gates, planning loaded at the front and contracts built on control no longer suit complex capital projects.[24]

Much of management happens in rooms, and several of the best-read books here are about what to do in them. A Coach's Guide to Facilitation takes as its definition that a facilitator plans, guides and manages a group event so that its objectives are met with clear thinking, good participation and the agreement of everyone involved. A well-run meeting, on its list, has a purpose everyone knows, keeps to its time, lets all contribute, reaches decisions and ends with actions that have owners. Preparation is the neglected part, and may take as long as the meeting. The authors divide a meeting into starting, diverging, converging and closing, and prefer a check-in to an ice-breaker: its purposes are to have everyone speak in the first five minutes, after which they are likelier to contribute, and to connect people to the topic and to each other.[3]

Introducing EventStorming describes a workshop of another scale. In one of its stories a mid-sized company's systems have become a burden, and some key people have declined to attend. The facilitator takes the room half an hour early, pushes the chairs into the corners, fixes eight or nine metres of paper to the wall, and asks representatives of each department to write the key events of the business on orange notes, in the past tense, and place them along a timeline. The book's judgement of the ordinary meeting room, a large table ringed with chairs, is that nothing clever will come out of it. Within minutes the room is working, and a participant confides that after two weeks in the job the company's business has at last become clear. There is, the author says, no one best way to run such a session.[4] Collaboration Games (2024) is a collection of games meant to leave teams with a memory of what collaboration is worth,[32] and Getting Value out of Agile Retrospectives (2016) a toolbox of exercises for a team's regular review of its own work.[33]

Be effective is addressed to people starting their careers, who are, it says, thrown in at the deep end with training in technical skills and little in method. It names three disciplines, managing oneself, one's development and one's energy. Its advice on time is to put the hardest tasks in the hours of greatest alertness, to recognise that the difficulty lies in keeping to a plan and not in making one, and to plan only two thirds of the available time, leaving the rest for what cannot be foreseen. It asks the reader to fix hours for starting and stopping work and to reserve time for exercise and family, and speaks of integrating work with life as well as balancing them.[11] Software Engineering - The Soft Parts gives lessons on the unwritten skills of the job from its author's first ten years at a large technology company.[18]

Developer Hegemony (2017) argues that the pyramid-shaped corporation suits knowledge work badly. Its sample is autobiography: the author graduated into a downturn, saw offers withdrawn one after another, and came to regard the corporate world as a promised land that had shut its doors. A meeting that the author took for a job interview proved to be a recruiting session for a pyramid of salespeople, where the crowd chanted that people are unhappy because they are sick of having jobs; the author, who wanted nothing more than a job, left in disgust.[12] Learn by Doing (2015) reduces a year of lectures by founders and investors to lists of one-line points, among them that capital is always available when it is not needed, that three founders should not overlap in their skills, and that experience creates blind spots, because a person who knows the pattern stops seeing new data.[13]

Corporate Sabotage Field Guide presents the common failings of organisations in reverse, as instructions to an operative. Its seven pillars are a catalogue: erode trust by design; replace clarity with compliance and require ritual over results; reward visibility over impact; tell people they own the work and then quietly tie their hands; fragment knowledge until no one can make a decision; ask for suggestions, stage listening sessions and do nothing; and keep success shared and failure personal. The pillars are for use when no single tactic can be applied in full, and their aim is an organisation that sabotages itself and resists correction. Under the joke each is a diagnosis: of cultures in which people speak up once and never again, of tools kept up to date while the work is not done, of feedback controlled by people who are not involved in the work. The sample includes the case file of an operative installed as a director of process excellence at a financial firm.[2] The Incredible Story of Deft (2nd ed.) (2025) is a business novel set in a training workshop, where an invented method that stands for all the fashionable ones at once is pitched as the one management approach to rule them all.[14]