Workplace Fundamentals (Or: How Employees Grow)
The essence of business society is mastering interpersonal dynamics. Once you've secured the people, you can handle anything.
Fundamental Skill #1:Master Data, Communicate Clearly.
In other words, become a human database.
For management roles, the most critical aspect is reporting. If you can't speak clearly, you cannot report to superiors, nor can you assign tasks to subordinates.
"Communicating clearly" means that when asked about any data, you can provide specific figures. If something falls under your responsibility, you can explain it clearly. If it pertains to your department, you can articulate it precisely.
Compared to masons, who has greater professional potential—designers or laborers? Certainly the designers, because they have the opportunity to present themselves in front of clients. Designers who win over clients also control resources and may one day become bosses, opening their own decoration companies, while masons simply hustle around, bent over, laying bricks. The most important thing isn't whether you're actually impressive, but whether you appear impressive. You need to make leaders and clients perceive you as competent. Achieving this boils down to one crucial point: mastering data and communicating clearly.
By not giving colleagues time to think or verify, you can quickly seize leadership's needs and rapidly become their trusted confidant.
Furthermore, someone who doesn't master data will be stunned when facing someone who does.
During meetings, with so many people present, no one has time to individually verify the data you cite on the spot. In other words, as long as others can't find flaws on the spot—and no one happens to have memorized the same data you cited (which turns out to be wrong)—they'll be overwhelmed by you.
Once they fall behind, it becomes difficult for them not to follow your lead.
At this point, everyone will falter and pause, captivated by your references, your eloquence, and your cited data. Everyone will follow your train of thought. At this moment, slipping your own agenda into your analysis becomes much easier.
Fundamental Skill #2:Process Management.
Direction determines the direction of success or failure; details determine the outcome. Wrong direction wastes effort, but even with the right direction, wrong details lead to failure.
When customers ask designers questions, and designers can only respond, "I need to check with the project manager," then relay the project manager's response back to the customer—do you think such designers would satisfy clients? When salespeople need to consult product manuals before responding to customers about products, would customers be satisfied?
If you don't personally manage down to the finest granularity, the data reported to you may well be false. And judgments based on false information will inevitably be inaccurate, often failing to identify key systemic issues. Your leadership will become dissatisfied with you, feeling that projects are stalled while you can't pinpoint where the problems lie.
Process management is detail management—understanding every phase's materials, each person's competency level at every stage, the actual site conditions, and exactly where bottlenecks occur. These represent new data generated during project advancement.
For leaders, having someone who can resolve matters through single-point contact brings peace of mind. Such a subordinate always knows which battlefronts need reinforcement, which require supplies, and which lack provisions. This gives leaders confidence to delegate authority, take vacations, and relax, knowing this person handles things reliably. This person's influence naturally grows—ultimately because the leader needs this person to hold power.
So, if the previous fundamental skill was about mastering historical market data, this one is about capturing new data generated anytime, anywhere during work.
Together, these form the "human database." Don't think this is burdening anyone; if someone can't handle complex situations, they're simply not suited for promotion.
As a doctor, what's the most critical factor for their career?
Is it medical skill or professional ethics? Neither. The key factor is writing medical records. Big data reveals that those who peacefully advance to senior chief physician positions aren't necessarily the best doctors or the most ethical—they're typically the best at documenting cases. What's the essence of medical records? It's process management. For ten or a hundred patients, you can discuss medical skill and ethics. But for ten thousand or a hundred thousand patients, what do you rely on? Only medical records, only process management. Over sufficiently long periods and with enough work samples, medical accidents will certainly occur, disputes will inevitably arise, and unclear situations will inevitably emerge. At that point, what matters is the quality of your records.
When process management is perfected, you can trace any aspect of your work without issue. This is the essential element for ultimately surpassing others and standing out through sustained effort. Often, you don't defeat competitors in any single project—you outlast them through continuous work, where their mistakes or lapses in process management cost them further advancement opportunities.
We're not competing on any single evening, but on every evening. Competitors are never defeated by you—they're eliminated by their own mistakes.
Everyone makes mistakes. I never play a brilliant move, nor do I err. I simply wait for others to falter. I'm convinced they'll make mistakes. Investment works the same way—it's never about how many times you win, but about waiting for others to err. When they falter, you capitalize on it, stepping over them to rise. It's that simple.
Fundamental Skill #3:Silent Guardianship.
Before decisions are formed, I privately share my personal views with leadership. Note: privately. And importantly, this viewpoint shouldn't take the form of conclusions—only analysis. This matters because, from an identity perspective, I'm a subordinate without decision-making authority. I have no right to conclude or tell leadership what can or cannot be done.
I can only analyze specific circumstances.
Even if you told me you wanted to launch a satellite, I would solemnly prepare a detailed plan—specifying how many engineers are needed, what resources are required. I'd make everything clear and transparent.
Later, when leadership reviews it and thinks, "Good grief, we don't have that many resources—let's drop it," this veiled suggestion might actually sink in.
First, I genuinely put in the work—who else would compile such a detailed plan?
Second, I'm extremely obedient and show profound reverence for leadership.
While making you feel my unconditional physical compliance and spiritual admiration, I also demonstrate my capability.
If you judge a situation as unworkable, prepare thoroughly during execution. Prepare what? Prepare to clean up leadership's messes.
Whether you can actually rescue the situation doesn't matter at all. The workplace is a performance—showcasing yourself to impress bigger employers constitutes your personal triumph.
Fundamental Skill #4:Always Carry a Notebook Around Leadership.
When conversing with leadership—whether in public settings like group meetings or privately during one-on-one task assignments—we typically display two emotional responses.
The first: perhaps what you say is reasonable, but you're adding to my workload, so internally I resist. Those unfamiliar with this emotion should observe their own children—if you ask them to do homework, their faces drop faster than a donkey's. That's the gist. It's not about whether you're unreasonable; it's that you're making them uncomfortable, and their inner feelings surface visibly.
The second: compared to leadership, you're actually the expert. You understand the actual situation far better than they do. They may be giving blind instructions or spouting nonsense. In this case, your facial expression reveals impatience—not because they're adding workload, but because you look down on them. This leads to unconscious scene-stealing: you'll preemptively voice points leadership hasn't considered, making them appear foolish and risking retaliation afterward.
This is where (the second scenario) the notebook comes in. Our subconscious assumes notebooks are only for important or incomprehensible content worth recording and studying later. You need to reverse this. When encountering genuinely incomprehensible content, don't write—just listen attentively. Since you already don't understand it, dividing attention to take notes will only worsen comprehension. But when encountering content that clearly irritates you, that's when the notebook proves valuable.
What's the benefit? Your intelligence temporarily drops because most brain cells are diverted to rapid sketching. When leadership watches you doing this, they feel superior—a sense of accomplishment. Among numerous subordinates, everyone avoids listening to their nonsense, yet here you are, a big-shot expert, diligently taking notes like a primary school student. Whenever leadership is present, always appear like a humble student—clumsy but earnestly recording every word. In their eyes, you're someone they've watched grow. Outside work, your true capability is Chen Jiangnan-level mastery, but beside leadership, you appear as Little Kui—unremarkable, all trained by them. This creates the effect seen in *The Deer and the Cauldron*. Why did Emperor Kangxi favor Xiao Bao? Because when Xiao Bao achieved merit, Kangxi claimed it as his own. When Xiao Bao defeated skilled opponents, Kangxi felt he'd defeated them himself. To Kangxi, Xiao Bao was his disciple, personally trained by him. Xiao Bao's victories equalled Kangxi's victories.
You essentially provide your leader with an intense sense of cultivation and ownership.
It's like playing a game where that character is you. You make them feel they've invested countless hours nurturing you, making them increasingly reluctant to let you go. Perhaps they've experienced repeated frustrations raising their own biological sons, but you—a Chen Jiangnan-level master—give them the satisfaction of having cultivated talent themselves. They begin treating you like a半个 son.
Then
Whenever they suddenly remember something but can't quite recall the details, they'll look to you, knowing you alone have this habit. You produce your notebook and say, "Leadership, on such-and-such date, you mentioned such-and-such—did you see it?" Perfect coordination. With repeated cooperation, they become dependent on you, like the elderly depend on canes, or Qianlong on Heshen.
Fundamental Skill #5:Truly Understand What a Tool Person Is—Because You Are One Too.
What should workplace communication revolve around? Not willingness or usefulness, but interests—benefit relationships.
When advocating for a subordinate's raise, the rationale is never that they're underpaid or pitiable. Nor is it about past merits or overtime hardships. Seriously presenting these arguments is useless—no one will listen.
If they're underpaid, they could leave. Since they haven't resigned, they're either well-compensated or receiving the market's current maximum offering.
If they're pitiable—coming from difficult circumstances—what does that have to do with the company? This isn't a welfare institution.
If they've earned merit, that's already done. It can't be taken back. A person's value isn't reflected in what they've done, but in what they can still do.
If they've worked hard, who hasn't? Who hasn't worked overtime? If this were grounds for raises, what about everyone else?
See? These seemingly reasonable, empathetic arguments, once submitted, simply won't be accepted. The reason is straightforward: reviewers won't treat you as a person, nor themselves as people.
We're essentially all tool persons occupying ecological niches. So learn the linguistic art between niches. In other words, don't argue your subordinate needs a raise—argue what the system requires and what it can deliver.
What about resisting work assignments?
Suppose leadership asks you to do something utterly impractical—like putting a lid on the Pacific Ocean because they're having a crazy day.
Simple. First, remember Skill #1: enthusiastically support. Regardless of what they say or how you feel, immediately display eagerness—flushed with excitement, impatient, itching to work overtime to prove yourself. This is step one and leaves your first impression on leadership, which matters enormously.
Next, two scenarios emerge.
If you're on the client side, able to mobilize substantial external resources and supplier capabilities, how should you proceed?Accelerate progress.
If they demand the Pacific be capped within a year, tell suppliers we'll strive to complete it in eight months.
Suppliers obviously can't deliver. They have two options: either push back hard, in which case you stand firmly with leadership and clash with them. After escalating conflicts to leadership—where suppliers collectively declare impossibility—you maintain unwavering loyalty to leadership. Understand the implication? When clients have bizarre demands, you don't directly reject them. Instead, you channel resistance through workers, letting clients witness practical difficulties. You then "defend" the client, arguing heatedly, making them perceive you as their devoted ally. The impractical project fails, but opposition comes from suppliers, not you. You earn leadership's goodwill. At that moment, they see you as truly trustworthy—only you understand and support them.
The second scenario: suppliers passively resist, neither volunteering nor opposing openly, hoping to drift through. How to handle this? Escalate tension—don't let them slip away, or responsibility falls on you. Knowing it's impossible yet pretending otherwise, you strictly enforce timelines, forcing suppliers to protest visibly to leadership. Never soften here; if suppliers clear this hurdle, you're finished. Leadership might mistakenly believe impractical projects succeed—you'd be blamed for poor supervision causing delays.
If you're on the supplier side, stall. Your troops are your personal soldiers; whipping them destroys future team morale. What matters during stalling is redirecting conflict externally. "Insufficient resources"? That's not my fault. I've already expended existing ammunition immediately; now it depends on logistics. My troops are fighting fiercely on the frontlines, highly motivated—they're simply waiting for your ocean lid. You transform from being pressured to pressuring others. Complain to finance, blame other departments, report to leadership: "Why hasn't the lid arrived yet? My troops have been waiting at the Pacific for days!" Portray yourself as heartbroken over wasted time and disrupted schedules, appearing wholly dedicated to leadership's project. When it ultimately fails, whose fault is it? Unreliable allies. Even if finance or other departments later expose the root cause—leadership's erratic commands and the absurdity of capping the Pacific—it doesn't concern you. You didn't say those words. You始终 maintain leadership's impression of your loyalty and enthusiasm.
But note carefully— including when suppliers revolt—addresses the same issue: proactively accepting responsibility. You must take full accountability, bearing all blame.
Privately before leadership, say: "The fault is mine, not the project, not the decision. If I'd exerted more effort, perhaps we'd have succeeded. Ultimately, my execution fell short." Acknowledging mistakes here matters little—leadership already understands. Having received your earlier hints, they fully realize their own blind commands. Suppliers and rival departments have been forced to tell the truth.
Speaking this way now saves their face, earns gratitude, and more crucially—the workplace不允许存在 a person without responsibility. Moreover, you're not shouldering blame but warming leadership's heart. Plant this seed carefully.
Subsequently, regarding this impractical project, two public meetings likely follow—one internal, one external.
Half-completed failures demand explanations.
During internal meetings with leadership and colleagues present, proactively attribute decision errors to yourself. Lie openly: "Leadership was misled into this course of action." How will leadership respond? They'll gracefully accept the台阶 you've provided.
Having privately communicated beforehand, they already know you're preparing to shoulder blame publicly. Announcing it openly maintains their authority. Leaders must maintain authority—they can't be wrong; only you can err. They appreciate your goodwill, accept readily, offer mild criticism perfunctorily, and later reward you. Projects fail, yet you receive promotion.
Privately, you've bonded through shared hardship. Publicly, you've shielded their authority. As long as they need loyal subordinates like you, they'll reward rather than punish. You become a benchmark for others to emulate.
Others witnessing your success through this method will imitate you. Leadership gains stability, accumulating supporters and eager future confidants. Win-win—understand? Win-win magnificently. Project fails, yet everyone wins comprehensively.
The external public meeting requires different handling: shoulder blame for suppliers. Before suppliers and leadership, openly admit: "The problem lies with me—I failed to master proper work methodologies."
Having whipped suppliers earlier, they undoubtedly harbor resentment. Indeed, you exploited them—鞭打 them while forcing them to antagonize leadership. Now stands your sole relationship-repair opportunity. Despite a thousand shortcomings, step forward courageously, displaying fearlessness and brotherly loyalty. Suppliers' reaction? "This buddy acts hastily, occasionally clashes with us, but fundamentally innocent—an executor defending us at critical moments. Righteous, worthy of friendship."
Understood? Though appearing to bear all responsibility, none actually sticks. You've placated both sides; everyone praises you. An absurd project, destined to fail, becomes your ladder to success.
This embodies mastering tool-person communication principles.
Never directly request reasonable accommodations, nor directly contradict unreasonable demands. Fully leverage workplace systems, conveying messages systemically to achieve satisfying outcomes.
Survival space exists between these two boundaries: accomplish the impossible, endure the unbearable. If you claim limited ability, making the impossible achievable unworkable, lower your底线—endure what others cannot bear.
Former leaders you've supported inevitably fall. Former companies you've served inevitably collapse. But individuals can continuously advance because clinging to powerful figures demands speed. Like restaurants competing on table turnover rates, this game hinges on velocity.
When You Become Wealthy, How Do You Raise Your Children?