There is a familiar tension in offices: one side says the team needs more humanity, the other says the team needs clearer process. People who lean toward relationships worry that too many rules will make work cold and rigid. People who lean toward systems worry that too much sentiment will make everything vague, where familiar people are treated gently and newcomers are disadvantaged. Many meetings never say this directly, but underneath the conversation is the same question: are we managing by trust or by rules?
The material places Liu Bei and Cao Cao on two useful sides. Liu Bei reminds me of people-centered leadership: winning hearts, honoring relationships, humbling oneself to seek talent, and building a core team through trust. Cao Cao reminds me of rule-based management: using people by capability, fitting people to roles, building operating systems, enforcing discipline, and staying practical. If we read them as opposing camps, it is easy to choose one and accuse the other of being either cold or ineffective. But after working for a while, I think healthy organizations rarely live at only one extreme.
In the very early stage, a team often needs more Liu Bei. Five or seven people sit close together, everything is new, every role overlaps, documentation is thin, data is incomplete, and sometimes the product itself is not stable yet. In that environment, trust is glue. People get through sleep-deprived days not only because of process, but because they feel they are doing something worthwhile with people they can trust. A timely thank you, a founder taking responsibility in front of a client, or a team fixing production without blaming one another can build culture before culture is ever written into slides.
But when a team grows, relying only on the Liu Bei side becomes tiring. New people cannot learn internal history through oral tradition. An important decision cannot live only in the heads of three early employees. A release cannot depend on one person remembering every step. A compensation decision cannot rest on a feeling that someone seems hardworking. At that point, the team needs some Cao Cao: systems, standards, authority, process, data, and operations that do not depend too heavily on the memory of a few old-timers.
Onboarding is a simple example. In a small team, a new hire can sit beside a senior teammate and ask anything. That is warm, fast, and human. But when the team grows to dozens of people, oral onboarding becomes uneven. Someone who meets a patient senior is lucky. Someone who joins during a release crunch has to swim alone. A good onboarding system does not remove humanity. It prevents humanity from carrying the work that documentation should carry. Seniors still talk with newcomers, but they no longer repeat the same basics twenty times. New hires still feel cared for, but they also have a clear path toward independence.
Feedback is another example. Humanity keeps feedback from becoming a weapon. The manager remembers that behind a mistake is a person with pressure, limits, and context. But rules keep feedback from dissolving into vague feeling. If someone repeatedly misses deadlines, saying that they need to be more proactive may be true, but it is not enough. The team needs to define which deadlines were missed, why it happened, when early warning is expected, what done means, what support is needed, and what happens if the pattern continues. Humanity keeps the conversation from causing needless harm. Rules keep the conversation from disappearing into air.
I think many organizations get stuck because they treat these two forces as enemies. Some use warmth to avoid clarity. Everyone is afraid to speak directly because they want to preserve harmony, and eventually the most responsible people become quietly tired. Others use process to avoid listening. Everything follows policy, but people inside do not feel seen as human beings. One side makes the team soft but messy. The other makes the team firm but cold. Both have a cost.
From everyday work, the more useful question may be this: does this situation need more trust, or more structure? When a new person is afraid to ask questions, the team may need more safety. When a project keeps slipping because no one knows who decides, the team needs more structure. When people hesitate to report mistakes early, the team needs more trust. When the same mistake repeats across releases, the team needs more process. When conflict between departments rests on assumptions, the team needs both: enough trust to sit together, and enough rules to stop arguing from feeling alone.
Startups often need to learn from Liu Bei first: hold people, stay humble, and create the sense of being on the same side when everything is still incomplete. Scale-ups need to learn more from Cao Cao: turn experience into systems, use people by real capability, and let process carry the ambiguity that people should not carry forever. The key is not to forget the earlier lesson when learning the later one. A large company still needs kindness. A small team still needs a few minimum rules. No stage is exempt from both.
This note leaves me with a personal reminder: good management is not choosing between warmth and clarity. It is making warmth bounded, and making clarity humane. A good manager does not only ask whether someone is okay, and does not only ask whether the task is done. Maybe they need to ask both, at the right time, with enough sincerity and enough discipline. If a team is growing, a useful question may be: which part of our work needs to be treated more humanely, and which part needs to be written into clearer rules?