Organization
What Institutions Can Learn from Software Engineering and What They Cannot
📕 E-Book카이 프뢰프 에디션 · 기초 저작
버전 1.4 (2026-11-18) (Deutsch) · 새 버전 알림 받기(RSS)
이 책은 현재 한국어판이 없습니다.
이용 가능한 언어:
Nobody feels responsible, the same information is requested three times, decisions are made without those who know. Anyone who works in a public office, a company, a hospital or a club knows these complaints. This book treats them as questions of design that can be answered.
In half a century, software engineering has learned to build large systems based on division of labour in such a way that they can be understood, checked and changed. What it found are rules for the division of labour, and many of them do the same work in institutions. If a piece of information is kept in three places, the copies drift apart; so every question needs one authoritative source. Procedures that people understand are followed, which makes simplicity a condition for rules to work. An error that is swallowed causes damage later, where nobody can find the cause; it is shown where it arises, and one asks how it could happen instead of looking for someone to blame. Whoever changes something creates a new version instead of overwriting the old one, and the institution keeps a memory that outlasts the people who leave.
Each of these transfers breaks down at a particular point. The parts of a program want nothing; the people in an institution have purposes of their own, are at the same time parents, neighbours and citizens, and think about their work. When a measure becomes a target, it no longer measures. A second file on the same matter can be intended, as an independent check or as protection against an office that knows everything. What is called legacy in a program is often, in an institution, a vested position that people depend on. So every chapter asks two things: what a rule of software engineering achieves in organizations, and where it breaks down with people. At the second point it is no longer technology that decides, but what the institution owes to those who work in it and to those it affects.
Structure
Purpose and justification – Everything an institution does is a means to its purpose. The questions are whether it fulfils that purpose, and whether the purpose, together with its means, can be justified to everyone it affects; a well-built institution that does harm only does it more thoroughly.
Dividing, one source, simplicity – Responsibilities by task rather than by person, handovers that say what remains open, one authoritative source for each question, and procedures as simple as the matter allows, with an orderly path for the exception.
Knowledge and decision – Whoever prepares a decision knows more than whoever makes it. Each owes the other something: the one everything relevant, including what speaks against their own proposal; the other a hearing and a reason where they decide otherwise.
Measuring, errors, versions – Measuring without the measure becoming the target; errors that get reported because reporting pays off; changes with a name, a date and a reason, and transitions that say who loses and what is owed to them.
Rules, machines, openness – A rule carried out by a machine needs an open path to a person who is allowed to decide otherwise. Whoever is affected by a decision should be able to read what it rests on, and those who control others must let themselves be controlled.
Working with language models – What has become cheap is writing, not checking. A model carries out the given purposes without the objections that people bring from their other roles, and it can keep alive an institution that would otherwise have been reformed.
How much effort – Every form costs something, and demanded everywhere it produces the very bureaucracy it was meant to prevent. An organization keeps measuring its own rules against their purpose and drops what no longer serves it; where this self-examination stops, bureaucracy takes on a life of its own and people become parts of a machine. Reason has a chance where the right thing is easy and the harmful thing is hard – Hegel’s hope, tested against Marx’s objection.
Conclusion: where to begin – With a single process that runs badly rather than with a reform; with what one person can do in their own place, what only many can change together, and what those at the top owe to everyone who decides under the conditions they set.
Each chapter ends with a summary in italics; readers short of time can read the book through its summaries.
What is special
The book assumes no specialist knowledge, either of software or of organizations. Its examples come from the public office, the hospital, the sports club and the company. It offers no method that replaces judgement, but seven questions with which one can follow a process in one’s own institution.
Relation to the other books
This book is an extension of the ethics, the third of the foundational books. 진리 deals with checking, 사고 – 잃지 않고 정리하기 with ordering, 윤리학 – 우리가 이미 행하는 선 with what we owe one another; this book asks how institutions must be built so that this can take effect in them. What it needs from the others it develops itself, and it can be read on its own.
참고 문헌
- 연도
- 2026
- 에디션
- 카이 프뢰프 에디션 · 기초 저작
- 다음 책의 확장
- 윤리학 – 우리가 이미 행하는 선
내려받기
이 저작물은 Zero Marginal Cost License에 따라 무료로 읽고 공유할 수 있습니다.
| 언어 | 제목 | 형식 | 내려받기 |
|---|---|---|---|
| 🇩🇪 Deutsch | Organisation | PDF, EPUB | 📄 PDF (0.3 MB) 📄 EPUB (0.2 MB) |
| 🇬🇧 English | Organization | PDF, EPUB | 📄 PDF (0.3 MB) 📄 EPUB (0.2 MB) |
| 🇫🇷 Français | L'organisation | PDF, EPUB | 📄 PDF (0.3 MB) 📄 EPUB (0.2 MB) |
| 🇪🇸 Español | La organización | PDF, EPUB | 📄 PDF (0.3 MB) 📄 EPUB (0.2 MB) |
| 🇮🇹 Italiano | L'organizzazione | PDF, EPUB | 📄 PDF (0.3 MB) 📄 EPUB (0.2 MB) |
| 🇵🇹 Português | A organização | PDF, EPUB | 📄 PDF (0.3 MB) 📄 EPUB (0.2 MB) |