Where this theory sits

An organization does not move just because the strategy is right. A good product does not take hold just because you bring it in. The stagnation that happens on so many sites is not a lack of ability or of will — it happens because we work only on individuals while ignoring the distinct logic of how the collective (the organization as an aggregate body) behaves.

Collective Management is a body of technique for diagnosing this "logic of the collective," moving an organization in an intended direction, and carrying a transformation through to success. It puts twenty-two years and four companies' worth of on-the-ground practical knowledge into words as a reproducible framework.

Running through this theory is one deeper hypothesis: "An expert's judgment, once structured, can be transplanted to another place." Collective Management is itself a proof of it — a case where the "judgment for moving an organization," which would otherwise stay buried inside one person's experience and vanish, was extracted, structured, and made into a form anyone can use. The same idea is also embodied as a product that transplants an expert's tacit knowledge into an AI (ghoost).

So this book is not merely a theory of organizations. It is the application, in the organizational domain, of one consistent methodology: turning buried judgment into a mechanism.

---

Part 1: Foundational theory

1. What Collective Management is

Collective Management is the technique of moving an organization (a collective) in an intended direction and bringing a transformation to success.

Its object is not the individual but a gathering of two or more people — a team, a department, a company, a community. Its aim is to move the collective in an intended direction, make it produce results, and bring about change.

The technique for persuading an individual and the technique for moving a collective are different things. The collective has its own logic; push with an individual's enthusiasm alone, without handling that logic, and the organization will not move.

2. Why organizations don't move

An organization does not move not because the people in it are incompetent or lazy. Usually it is because the following four forces are at work.

• Inertia: if things run as they are, there is no reason to change
• Psychological resistance: people want to avoid change itself
• Cognitive bias: they have not noticed there is a problem at all
• Structural constraint: they want to change, but the system won't let them move

Collective Management is the technique of diagnosing where these four forces reside and removing them one by one.

3. Three premises

Premise 1: the collective is a "second individual."
The whole collective behaves as if it were a single living body. A set of individuals does not become a collective by mere addition. The collective has, as a collective, its own "sense of crisis," "pride," "sloth," and "obtuseness," and these exist on a different dimension from individual emotion.

Premise 2: the collective is a "mass of inertia."
A moving collective keeps moving; a stopped collective keeps stopping. That is exactly why at what timing, where, and with how much force you apply pressure becomes decisive.

Premise 3: the collective has a "layered (fractal) structure."
The collective has an upper, a middle, and a lower layer, and a different logic works in each. The point at which to intervene changes by layer.

4. Fractal structure

The collective's greatest feature is that the same structure repeats at changing scales.

individual → small collective → mid collective → large collective → super collective

For example, one individual is "a member of the collective" within their team, but that team behaves as "a single individual" within the division. The division is one individual within the company, and the company is one individual within the industry. At every layer, the same logic — "the collective is a second individual" — appears again and again.

See through this nested structure and you can map a move that worked at one layer onto another. Collective Management's generality rests on this similarity of structure.

Between layers there are interactions in three directions. From above, policy, resources, and authority "come down." From below, results, issues, and proposals "go up." And within the same layer, sharing, competition, and propagation of information run sideways. To intervene is to design where and how you put your hand into this flow.

5. Eleven elements for understanding a collective

To diagnose and move a collective, observe it from the following eleven viewpoints.

1. The psychology of people — What does each member fear, and what do they want? Status-quo bias, loss aversion, conformity pressure.
2. Hierarchy — Who decides, and who executes? The location of authority and the asymmetry of information.
3. Sense of crisis and stamina — Does the collective recognize a crisis (sense of crisis = the imagination for crisis)? Can it bear change (stamina = endurance against alteration)? Has it become a "boiling frog"?
4. Face and pride — Are appearances and pride distorting decisions? Fear of overstepping, the emergence of blame-shifting.
5. Sloth and obtuseness — Is the collective in a state of "can but won't" (sloth), or "hasn't even noticed" (obtuseness)? The move differs between the two.
6. Timing and organizational culture — Is now an easy time to move it? Does the organization affirm change, or affirm continuity?
7. Competition and market position — What does the collective fight against externally, and in what position (top / challenger / niche) does it sit?
8. Purpose and difficulty — Is the purpose clear and condensed into a catchphrase? Is the difficulty set within "reachable if you try"?
9. Leadership and membership — Is the relationship between leader and members functioning? Being healthy and being functional are different.
10. Propagation and culture formation — Are information and behavior transmitted within the collective? The accumulated trail of behavior becomes culture.
11. Media operation — Is there a mechanism for continuous transmission within the collective? Distinctiveness, continuity, and freedom let awareness soak in.

These eleven elements can be used directly as a checklist for organizational diagnosis.

---

Part 2: The diagnostic framework

Intervention without diagnosis becomes an accident. Before moving, first make out "where I am standing" and "what state the collective is in now."

6. Positioning diagnosis (three axes)

Determine, along three axes, from what position you work on the collective.

• Axis 1: internal or external — Do you move as a member of the collective, or work on it from outside?
• Axis 2: decision-maker or non-decision-maker — Do you hold decision authority?
• Axis 3: existing or new / startup — Is the collective already moving, or one you are about to build?

The combination of these three axes yields eight positions. The effective strategy is entirely different for each.

When the position differs, the move is opposite even for the same goal. Internal and a decision-maker: you can design and allocate directly. A non-decision-maker: you move the upper layer with proof and proposals. External: making results visible and identifying the node are the keys.

7. State diagnosis (six viewpoints)

Read whether the collective "can move now" from six viewpoints.

1. Presence of a sense of crisis — How does it perceive changes in the market and competition? Is there a gap in perception between upper and lower layers? Without a sense of crisis, first make it notice.
2. Presence of stamina — Is there room to load extra burden onto normal operation? Without stamina, first make it lighter.
3. State of the leader — Speed of decision, commitment, influence. If dysfunctional, support or replacement is needed.
4. State of the members — Responsiveness, accuracy, initiative. If low, a design for visibility and support is needed.
5. Organizational culture — A culture that accepts change, or a fixed one? If fixed, begin from cultural transformation.
6. Timing — Is now a good chance? Avoid full-throttle operation and the moment just after a policy has been set.

8. Judging the possibility of intervention

Bundle the diagnostic results by "sense of crisis × stamina × timing" and the possibility of intervention comes into view.

• High (crisis present × stamina present × good chance) → bold transformation is possible. Big goal, short and concentrated.
• Mid (any one missing) → gradual transformation. Stack small successes.
• Low (no crisis × no stamina × bad timing) → first make it notice, start small, and be ready for a long fight.

The intensity of intervention is decided by diagnosis, not by will. Skip this, and even the right move ends in a swing at empty air.

---

Part 3: Methods of intervention

Once diagnosis is done, work on the collective. What is handled here is not "manipulation." It is the technique of driving transformation: unraveling the structure in which an organization cannot move, and making it carry change through to the end.

9. Meta-strategy: five principles

Principle 1: nine parts preparation, one part the field.
The contest is all but decided in advance. Gather information, prepare several scenarios (Plan A, B, C), and minimize uncertainty in the field. The idea is to win by preparation, not by dexterity.

Principle 2: small start, proof first.
Rather than waiting for a big approval, start small, show results, and formalize on the strength of proof. Gaining understanding after moving is faster than taking perfect agreement before moving.

Principle 3: structuring commitment.
Align the stakes of those involved by design, and make forward motion hard to reverse. Do not make it depend on individual effort; build a mechanism where continuing becomes natural.

Principle 4: start from a person who is a node.
Multiply organizational position, volume of transmission, drive, and external negotiating power to make out "the person with many contact surfaces." If you can work together with that person, change spreads easily to the whole collective.

Principle 5: full force and immediate retreat, together.
Once you decide to do it, apply pressure with full force. When you reach the line you decided to retreat at, retreat without lingering. Half-measures cost the most. Decide this "line of retreat," before you begin, by date and number — decide it while running, and the line keeps sliding backward forever.

10. The philosophy of preparation

In high-difficulty situations like external × new × startup, the probability of success is almost proportional to "the amount of preparation."

In field observation, the correlation between preparation rate and success rate is extremely high. If preparation is 30 percent, success converges around 30 percent; if preparation is 90 percent, success converges around 90 percent. The rule of thumb "preparation is everything" rests on this correlation.

This preparation is organized into a set of essential items for standard cases and a complete version for large, high-risk cases. The skeleton: (1) read the other side's (the collective's) issues and decision structure, (2) grasp the competition and past failures, (3) prepare several alternatives and retreat criteria in advance, and (4) design through to the execution structure and the metrics for results.

The detailed operational checklist for each item is omitted here as a practical asset. What matters here is not memorizing the items but the principle itself: that thoroughness of preparation lifts the probability of success linearly.

11. Twelve techniques for moving an organization

Building on diagnosis and preparation, choose the following techniques as the situation demands. Each is a way of working so that the organization can take on change as "its own concern."

1. Fostering a sense of crisis — Show concretely the changes in market, customers, and competition, and the future that is lost if left alone. Make them feel it as their own.
2. Designing recognition and motivation — Design so that legitimate pride and esteem — "other companies have already started," "the industry is watching" — become the driving force of change. Protect the face of those involved and prepare occasions for praise.
3. Designing visibility — Create a state of being watched, a state where progress is visible. People move more easily when made visible.
4. Making the issue felt — For a collective that has not noticed, make it feel the issue through experience, not abstract argument. Obtuseness dissolves once you make it notice.
5. Choosing the timing — Strike at easy-to-move times: right after a crisis surfaces, right after a personnel change, during a strategy-planning period. Avoid full-throttle operation.
6. Changing organizational culture — First, believe overwhelmingly yourself (the heat of the source). Align your gaze with the head, share even small changes, convey the background, let the person choose by their own will, and when results come, announce it widely and praise. "Without heat at the source, the temperature drops each time it crosses a layer."
7. Using the competition — Make the moves of competitors and the market visible, and derive the necessity of change from your relative position.
8. Turning the purpose into a catchphrase — Condense the purpose into a form anyone can say in one line. A vague goal does not propagate.
9. Designing the difficulty appropriately — Set the target at "1.2 to 1.5 times the previous," within a range visible if you try. An outlandish target exceeds the imagination of those involved and does not function.
10. Switching the purpose midway — When the situation changes, turn the rudder. Share the background, narrow the changes from existing behavior to a minimum, and do not make them stop running itself. "Even when the course changes, the act of continuing to run does not change."
11. Designing propagation — Convey early, strongly, repeatedly, until it gets through. Design the experience and use sideways propagation. People experience, and when emotion moves, they change.
12. Operating media — Keep transmitting with distinctiveness (information obtainable only there), continuity (there at a set time), and freedom (under no one's control). Continuous information eventually becomes the collective's "ordinary" and lets perception soak in.

12. Designing the timing

Even the same move brings very different results depending on when you strike. The initiative belongs to the one who strikes — because they can choose the favorable timing themselves.

Easy to move: right after a crisis surfaces, right after a personnel change, a strategy-planning period, right after a success experience, when the external environment has changed. Hard to move: full-throttle operation, right after a policy is set and motion begins, when the organization is exhausted, right after a big failure.

And what matters is that timing can not only be "waited for" but "made." Surface a crisis, generate momentum with a small success, convey a change in the external environment, use the junctures of personnel and budget planning — these are means of actively creating a good chance.

---

Part 4: Domains of application

Collective Management functions with the same skeleton even when the object's position changes. Three representative domains of application are given (the details of concrete implementation are omitted, shown only as a form).

Instilling awareness through internal media.
Continuous internal transmission (a mechanism where distinct information arrives at a set time) creates an "ordinary" across a wide range of the organization in a short time. It is a compound application of element 11 "media operation" and technique 11 "propagation" and "creating stars," and can be designed all the way from the soaking-in of awareness to the birth of a request by name.

Launching a new organization.
The typical situation of "internal × non-decision-maker × startup." Combine thoroughness of preparation, leading with proof, collaboration with a person who is a node, and fostering a sense of crisis, and move the organization in substance before formal authority is fixed. Place the victory condition on reaching the result, not on the position itself.

Transforming sales and proposals.
Sales is nothing other than the act of moving the customer as a "collective." The philosophy of preparation (designing in advance the other side's issues, decision structure, competition, and retreat criteria) is itself the practice of Collective Management. The correlation that preparation rate governs success rate appears most clearly in this domain.

---

Closing

Collective Management is a body of technique for crossing the ordinary wall of "organizations don't move" — not with spiritualism, but with technique.

Its core is consistent: grasp the collective as a second individual, diagnose its logic, and unravel the structure in which it cannot move. And this very endeavor is a proof of the larger hypothesis that "an expert's judgment, once structured, can be transplanted."

Theory is verified and updated within practice. This book is its current position, not its finished form.

---

About the author

Tsutomu Tateno. Center Director of AIXC at Classmethod, Inc. In charge of product marketing for ghoost (an AI product handling the inheritance of tacit knowledge and judgment). Across twenty-two years and four companies — staffing, store development, platform business, and overseas — he has consistently worked in the area of "activating the new part of an organization's metabolism." He holds a patent (Patent No. 7857639) on technology for integrating and reproducing an expert's judgment (tacit knowledge). He continues to speak on the social implementation of generative AI, including at an AWS-hosted executive roadshow.