In Chapter 1, we broke the ice in our thinking, moving from being a "Reckless Charger" who put faith in "courage" to becoming an "Open-Map Navigator" who pursued "grounded confidence." We came to understand that victory is not carved out by brute force but designed through wisdom.
Now the question arises: what exactly is this "map" we are meant to "open"?
If the map itself is wrong, then no matter how high the resolution of the satellite or how precise the navigation, it will only lead us astray.
The fundamental reason the "Reckless Charger" fails is that the "map" in his mind is wrong, or rather, radically oversimplified. On Wang Ze's map, there were probably only a few isolated points: the client company's building, Director Li, Xiao Zhang. He took a complex organization for a simple collection of independent individuals. He believed that if he could just "handle" these few points, he could take the entire map.
This is a fatal cognitive bias.
The "Open-Map Navigator" can "secure victory before engaging in battle" because he holds a more advanced map, one closer to reality. On this map, what he sees is not isolated points but a "system" in which countless elements are connected and interact with one another.
In this chapter, we will learn how to draw the "sketch" of this advanced map. We will introduce the first and most important core concept of the "open-map" methodology: the Decision System. You will learn to treat any challenge you face -- whether winning over a client, passing an interview, or entering a circle -- as the task of understanding and influencing a unique "decision system."
Master this perspective, and you hold a "master key" that opens the hidden logic behind any complex situation.
Section 1: A Shift in Perspective -- From "Winning People Over" to "Understanding Systems"
When most of us face a challenge, our most instinctive mode of thinking is "winning people over."
To close a sales order, we think: "Which key person do I need to win over?" To push a project forward in a company, we think: "Which department heads do I need to persuade?" To secure an investment, we think: "How can I make that investor like me?"
This way of thinking is simple, direct, and consistent with our social intuition. It reduces a complex organizational problem to an interpersonal one. In some cases it actually works. But more often, it traps us in the same predicament as Wang Ze.
Why Is "Winning People Over" Increasingly Unreliable?
Reason One: The "De-Personalization" of Decision-Making
In modern organizations, in order to avoid risk and ensure compliance, major decisions are less and less often made on a whim by some single "key figure." They tend to pass through a complex process involving many participants, cross-departmental coordination, and checks and balances across multiple procedures.
Wang Ze assumed that winning over Director Li and Xiao Zhang would settle everything, but he overlooked that both of them were merely "cogs" in this vast decision-making machine. They might be able to offer certain conveniences within their own authority, but they could not change the direction in which the whole machine turned. Vice President Liu, who made the final call, weighed far more than his personal likes and dislikes; he was driven above all by the organization's strategic goals, its tolerance for risk, and its political ecology.
Even the highest decision-maker, who appears to speak with one decisive voice, does not decide in a vacuum. He too is constrained by pressure from the board, feedback from the market, the requirements of laws and regulations, and the tug-of-war among competing internal factions.
Pinning all your hopes on "winning over" a single person is like staring at one player's face in a complex card game while ignoring the cards on the table, the other players' moves, and the rules of the game itself. It is a dangerous gamble.
Reason Two: The Multi-Facetedness and Unreliability of People
The "winning people over" mindset rests on a naive assumption: that people are rational and consistent. As long as someone agrees with you to your face and expresses approval, the matter is settled.
But reality is that people are complex, multi-faceted, and changeable.
The client who claps you on the shoulder and calls you "brother" over drinks may, back in the office, reject your application without hesitation because of a single compliance document.
The colleague who lavishes praise on your proposal in the meeting may, in the anonymous review round, vote against you because of conflicting departmental interests.
The "key figure" who gave you a verbal promise may easily change his mind because of one remark from his superior or a sudden external event.
You think you have "won him over," but what you have won over may be no more than one "role" he plays in a particular setting. You have never truly understood the deeper, invisible forces driving his behavior.
The Open-Map Navigator's Shift in Perspective: From "People" to "Systems"
The Open-Map Navigator's perspective transcends the level of "people" from the very start. He knows that "organizational people" are products of the system. The behavior, speech, and decisions of any individual within an organization are, to a large extent, shaped and decided by the "system" in which he operates.
Consider a tree. The direction its branches and leaves grow, and the fruit it bears, depend not only on its own genes but also on the environment where it grows -- the sunlight, the water, the soil, and the competition of the plants around it.
Therefore, to truly understand and influence a person's behavior, you cannot fix your gaze on the person alone; you must understand the complete, complex "ecosystem" behind him.
That "system" is what we call the "Decision System."
What Is a "Decision System"?
A decision system is a collective body in which a group of interrelated roles, operating under a set of explicit or implicit rules, process information and make value judgments, ultimately producing decisions, all in service of a particular goal.
The definition may sound a little unwieldy, but it contains the key elements for understanding every complex challenge. Let us unpack it.
Your target is no longer "the client" but "the decision system."
When you apply for a job, your target is not the friendly-looking HR representative, nor the highly skilled interviewer, but the "recruitment decision system" formed by HR, the hiring department, company executives, the corporate culture, and the recruitment process. When you raise capital, your target is not the celebrity investor holding forth on stage, but the "investment decision system" formed by the investment manager, the investment committee, the risk-control department, the fund's investment preferences, and the industry cycle. When you want to enter a high-caliber circle, your target is not the "big name" inside it, but the "circle decision system" formed by the circle's entry threshold, its core values, the interaction patterns among its members, and its unwritten social etiquette.
This shift in perspective is the starting point of "open-map." It transforms you from an ordinary person who could see only the "trees" (people) into a strategist who can see the entire "forest" (system).
Once you begin to see the world through the lens of "systems," many problems that once baffled you become suddenly clear.
You will no longer feel defeated by someone's coldness, because you understand that he may simply be playing the "gatekeeper" role the system has assigned him. You will no longer be infuriated by someone's fickleness, because you understand that he may be constrained by more powerful forces within the system. You will no longer pin your hopes on some intangible "relationship," because you understand that what truly moves a system is deep insight into its underlying logic.
So what, exactly, is a "decision system" -- this complex forest -- made of? And how can we read it and draw its map?
The answer is that any complex decision system, however varied it may appear, is held together by a core skeleton of just three fundamental elements. Master these three elements, and you hold the "legend" for drawing any "map."
These three core elements are: Goals, Rules, and Roles.
Section 2: The Three Pillars of the System -- Goals, Rules, and Roles (the GRR Model)
Imagine you are traveling to a foreign country. To get around smoothly, you need to know at least three things:
- What do the people of this country broadly pursue? (Wealth, ease, or honor? This determines their prevailing values and behavioral motivations.)
- What important laws and customs does this country have? (What must be done, and what must never be done? This defines your boundaries of behavior.)
- What are the key institutions and figures in this country? (Who is the president, which department handles visas, where is the police station? This tells you whom to turn to when problems arise.)
These three things correspond to the three core pillars for understanding a "decision system": Goals, Rules, and Roles. I call this the "GRR Model."
The GRR Model is the "prism" of your "open-map." Through it, you can decompose a beam of seemingly chaotic white light (complex reality) into three clear monochromatic beams (the system's three core elements).
Let us unpack these three pillars one by one.
Pillar One: Goals -- The "Soul" of the System, Where Is It Heading?
"Goals" answer the most fundamental question: what is the meaning of this system's existence? What does it ultimately pursue?
A system's goal is its "soul" and its "North Star," the primal force that drives the entire system into motion. Every rule and every role behavior within the system exists, at bottom, to serve this ultimate goal.
If you cannot read a system's goal, everything you do may be pulling in the wrong direction.
Wang Ze's failure lay largely in misjudging the "goal" of the client system. He assumed that a company buying software had the goal of "cutting costs and boosting efficiency," so he strained to emphasize how powerful his product was and how favorable his price.
But he failed to see that for a traditional manufacturing giant in the midst of a difficult digital transformation, the first priority at that particular stage might not be "efficiency" but "stability." Its goal was to "ensure the transformation proceeds without major upheaval, and that the transition is smooth." Under this supreme goal, "risk control" mattered far more than "powerful features" and "low price."
Company A's salesperson, precisely because he understood this, built every conversation around "how we help you achieve a safe, reliable, risk-free system upgrade," striking the system's true goal with precision.
How to Identify a System's "Goals"?
A system's goals are often layered, even contradictory. You need to dig down layer by layer, like an archaeologist.
The First Layer: Public Goals
These are the goals the system declares openly, usually found in annual reports, on the "About Us" pages of websites, and in government work reports -- for example, "become the industry leader," "create maximum value for customers," "achieve sustainable development." These public goals are an important reference, for they define the system's "political correctness." Any proposal of yours must, on the surface, remain consistent with them. Where to find them: the company website, annual reports, leaders' public remarks, press releases.
The Second Layer: Real Goals
These are the more specific, more practical goals that drive the system's day-to-day operations. They are usually tied directly to KPIs and resource allocation. For example, the sales department's real goal is "30% revenue growth," the production department's is "cut costs by 5-10%," and the R&D department's is "launch two new products within the year." Real goals often conflict with one another. Sales wants lower prices to hit its numbers; Production wants fewer process steps to control costs; R&D wants more investment to drive innovation. Understanding these interdepartmental "goal conflicts" is the key to reading the internal maneuvering of an organization. Where to find them: industry analysis reports, internal company publications, interviews with mid-level employees, job postings (observe which positions the company is most urgently hiring for).
The Third Layer: The Core Goal
Behind all public and real goals lies the single most fundamental goal -- the one that proves decisive at critical moments. It is usually closely bound up with the system's current "state of survival" and the top leader's "core concerns." A startup's core goal may be "to stay alive"; at that point, cash flow matters more than anything. A listed company's core goal may be "to hold up the share price"; at that point, a "story" that makes a good narrative may matter more than solid profit. A century-old firm in crisis may have "stability" as its core goal; at that point, any radical plan for change may be seen as a threat. A company led by a strong-willed founder may have as its core goal "to realize the founder's personal vision."
The core goal is the system's "vital point." Find it, and you have found the strongest lever for moving the entire system. The "risk control" that Company A's salesperson identified was precisely the core goal of that manufacturing giant.
Pillar Two: Rules -- The "Skeleton" of the System, How Does It Operate?
"Rules" answer a key question: how are things accomplished within this system, and where are the boundaries of behavior?
If "Goals" are the soul of the system, then "Rules" are its skeleton. They define the system's structure, processes, and culture, and regulate how the various roles within it interact.
Ignoring the rules is like driving in an unfamiliar city without looking at traffic lights or road signs: you will often be stuck, or even cause disaster.
Rules can likewise be divided into two levels.
The First Level: Explicit Rules
These are the public, formal rules written down in black and white. They include: Laws and regulations: industry-entry requirements, compliance obligations, environmental standards, and so on. The organizational chart: who reports to whom, how departments are divided. Workflows: how many approvals a purchase requisition must pass through, what documents a project must submit to be initiated. Policies and procedures: the employee handbook, financial reimbursement rules, and so on.
Explicit rules are the "floor" for your conduct within a system. You must fully respect and make use of them. For example, preparing your bid strictly according to the requirements of the tender documents is respecting the explicit rules; skillfully exploiting how the rules describe certain technical parameters to create an advantage for yourself is using them.
The "Reckless Charger" often ignores explicit rules because they are troublesome, and ends up eliminated on the most basic procedural grounds.
Where to find them: legal documents, the company website, tender documents, and conversations with execution-level employees (such as those in administration, legal, or procurement).
The Second Level: Implicit Rules
These are the unwritten codes of conduct that everyone in the system understands and follows without saying a word. Implicit rules often influence a system's operation more truly and more powerfully than explicit rules. They are what we usually call "corporate culture" or "circle culture."
Implicit rules take countless forms: Communication culture: In this company, is face-to-face communication encouraged, or is it customary to leave an email trail? Is direct disagreement valued, or is it customary to speak privately after the meeting? Decision-making culture: Does decision-making here rest on rigorous data analysis, or on the leader's intuition and experience? Is it a matter of "one voice," or does it require repeated meetings to reach consensus? Relationship culture: Is this a professional "task-oriented" culture, or a "people-first" culture of favors? How complicated is the office politics? Risk culture: Does this organization encourage innovation and tolerate failure, or does it dread risk and demand that nothing go wrong?
Wang Ze's other major mistake was failing to read the client company's "implicit rules." He dealt with a rigorous, conservative, process-driven technical organization in the back-slapping, brotherhood style of the street, and that in itself was a cultural "mismatch." His warmth, in their eyes, may well have read as "unprofessional" and "unreliable."
Company A's salesperson, by contrast, demonstrated a style of behavior that matched the organization's "implicit rules" through one brief, professional, on-target working lunch, and so quickly earned trust.
Where to find them: This is the hardest information to obtain and the most valuable. It comes mainly from long-term, deep observation (detailed in the next chapter) and from sustained conversations with the "old hands" inside the system (senior employees) or with "clear-eyed outsiders" (such as long-standing suppliers and former employees).
Once you understand a system's "rules," you know the "language" and "posture" in which your proposal must be presented to be accepted and recognized by that system. You become like a swimmer who knows the water, moving with the current rather than struggling against the undercurrent.
Pillar Three: Roles -- The "Organs" of the System, Who Plays a Part?
"Roles" answer an execution-level question: who specifically brings this system to life, and how are they related to one another?
If "Goals" are the direction and "Rules" are the road, then "Roles" are the vehicles traveling on it. They are the concrete executors and influencers of the system's will.
Under the "winning people over" mindset, we see isolated individuals named "Zhang San" and "Li Si." Under the "system" perspective, we see the "functional roles" these individuals play within the system.
A person's title does not fully equal the role he plays. You must look through the title to the function he truly performs in the chain of decision-making. In any decision system, four key roles typically appear (this taxonomy is in the same lineage as the common "decider / influencer / implementer / gatekeeper" division in sales theory, but we generalize it here):
The Decision-Maker
This is the person or group with ultimate authority, the one who can say "Yes" or "No" to your proposal. They are usually senior leaders in the organization -- the CEO, a vice president, an investment committee. How to identify them: Who bears responsibility for the final outcome? Who holds the sign-off or final approval authority? What to focus on: What are their core concerns? (These usually align closely with the system's "core goal.") What channels do they draw information from? (They rarely read long reports; they rely more on the summaries of key subordinates and the recommendations of insiders.)
The Influencer
They hold no decision-making authority themselves, but their opinions can greatly shape the decision-maker's judgment. They are typically technical experts, senior advisors, the decision-maker's confidants, or authorities in the industry. Director Li played the role of "Influencer": his technical review was one of the key bases for Vice President Liu's decision. How to identify them: Whose opinion does the decision-maker habitually consult before deciding? Whose expertise is most respected within the organization? What to focus on: What are their professional standards and value judgments? What is their relationship of trust with the decision-maker?
The Implementer
They carry out decisions and handle the concrete processes and affairs. They include procurement specialists, project managers, and HR specialists. Xiao Zhang was a typical "Implementer." They may have little influence on the final decision, but they can offer you convenience -- or create trouble -- in the process. They are also an important source of information. How to identify them: Who handles the specifics of contracts, payments, scheduling, and the like? What to focus on: What are their pain points at work? (Will your proposal add to their workload?) How can you make their work easier and more efficient?
The Blocker / Gatekeeper
They may, actively or passively, obstruct your access to key roles or your progress through the process. They may be receptionists or secretaries, or they may be the heads of business departments who resist because your proposal threatens their interests. How to identify them: Who controls the channel of information between you and the key roles? Whose interests does your proposal harm, or whose authority does it challenge? What to focus on: For "gatekeepers," show respect and make things easy for them. For those whose interests are harmed, think in advance about how to dissolve their misgivings or offer them a compensating arrangement.
Drawing the "Role Relationship Map"
Identifying these roles is only the first step. What matters more is understanding the "relationships" among them.
Reporting relationships: the most basic structural relationship in the organization. Trust relationships: who counts as whose "insider"? Whose opinion does one person trust unconditionally? Interest relationships: do they share common interests or points of conflict? Information-flow relationships: how does information move among them? Top-down or bottom-up? Is there a central "information hub"?
When you put these roles and their relationships on a single sheet of paper, you obtain a preliminary "role relationship map." This map will show you, at a glance, where power truly flows within the system and how your "line of attack" should be planned.
The GRR Model: A Dynamic Whole
Goals, Rules, and Roles -- these three pillars together constitute a complete "decision system." They are not isolated; they influence and shape one another.
Goals determine the direction in which rules are formulated. (A company that aims at "innovation" will create rules that encourage experimentation and tolerate failure.) Rules shape the behavioral patterns of roles. (A strict, hierarchical rule system will produce cautious, by-the-book roles.) The interplay among roles, in turn, feeds back to reshape the setting of goals and the evolution of rules. (A powerful head of sales may push the company to treat "market share" as a goal more important than "profit margin.")
Therefore, throughout the process of "open-map," you must hold a dynamic, holistic, systemic way of thinking. Like a doctor diagnosing a patient, you must come to understand the complete internal working of this "living organism" through observation, listening, questioning, and probing -- not treat the head when the head aches and the feet when the feet ache.
Section 3: Chapter Exercise -- Draw Your First "Decision System" Sketch
Theory is gray, but the tree of life is ever green.
Now it is time to put the GRR Model we have learned into practice. Choose one challenge you are currently facing as your "target," and try to draw its "decision system" sketch.
The challenge may be a project you are working on, a job search, an exam, or even a major decision within your family (for example, persuading your parents to accept a choice you have made).
Prepare a large blank sheet of paper and a pen. We will complete this sketch in three steps.
A worked example: suppose you are a recent graduate aiming to enter a major Internet company of your dreams (let us call it "Dream Company"), applying for a "Product Manager" role.
Step One: Define the "Decision System's" Boundaries and Final Output
System name: Dream Company's "Product Manager" recruitment decision system.
System boundaries: everything that takes part in this matter, from the moment I submit my resume to the moment I ultimately receive (or fail to receive) an offer. Final output (the decision): "hire" or "do not hire" me.
Step Two: Use the GRR Model to Fill In the Three Pillars
Goals -- What Does This Recruitment System Really Want?
Public goals:
(Found on the website or job posting) "Recruit the most promising future product leaders," "inject fresh blood into the company," "find outstanding talent who loves our products."
Real goals:
- (By analyzing the job description) Find someone for a specific business line (e-commerce, social, content) who can step in immediately and fill the gap.
- (By analyzing the company's financial reports and news) Is this business line a "cash cow" or a "strategic" new venture? The former may favor steady, dependable executors; the latter may favor pioneers with new ideas.
- Control recruitment costs: find the most cost-effective candidate who still meets the requirements.
Core goals (hypotheses to be verified):
- Hypothesis A: If the role sits in a core profit-making department, the core goal may be "find a highly intelligent, fast-learning young person who can withstand intense pressure," with professional background and experience only secondary.
- Hypothesis B: If the role sits in a marginal or innovative department, the core goal may be "find someone with great passion and distinctive insight in this particular field," even if his overall profile looks less impressive.
Rules -- By What Rules Does This Recruitment System Operate?
Explicit rules:
- Process: online application -> written test -> group interview -> first business interview -> second business interview -> director interview -> HR interview -> offer issuance.
- Hard requirements: a 985/211 university degree, relevant internship experience, proficiency in tools such as Axure.
- Timeline: the fixed windows of autumn and spring recruitment.
Implicit rules (hypotheses to be verified):
- Screening preferences: Is there a "prestige hierarchy" of schools? Are there special preferences for certain universities or for internships at certain companies? (This can be analyzed by looking at the LinkedIn profiles of the company's product managers.)
- Cultural fit: Is the company culture dominated by an "engineering culture" (valuing data and logic) or an "operations culture" (valuing user empathy and creativity)? This determines which traits I should foreground in the interview.
- Interview style: Do the interviewers prefer to challenge candidates with stress interviews, or to exchange ideas in a more Socratic way? (This can be gauged through interview accounts on platforms such as Niuke.com.)
- The weight of "referrals": Can an internal referral bypass certain screening stages? How much difference does a strong referrer make?
Roles -- Who Is in This Recruitment System?
The decision-maker:
The ultimate decision-maker: the business director or higher authority with the power to approve the offer. You may never meet him, but he will read your final interview evaluation.
The influencers:
- The core influencer: your direct superior (likely the interviewer in the second business round). His "strong recommendation" is decisive.
- Secondary influencers: the interviewer in the first business round (usually a senior colleague), and the "teammates" who performed well in the group interview (who may be asked their opinion of you).
- The hidden influencer: your "referrer." If he enjoys a strong reputation within the company, his recommendation carries considerable weight.
The implementers:
HR: responsible for arrangements, compensation discussions, and background checks. They do not decide whether you are hired, but they can determine whether you pass through the process smoothly.
The gatekeepers / blockers:
- The online application screening system (ATS): if your resume's keyword match is insufficient, even HR may never see it.
- The written test: a single question type you have not prepared for can eliminate you outright.
- (Possibly) the overly assertive participant in the group interview who likes to interrupt others.
Step Three: Draw the Sketch and Connect the Elements
Now put all the points you have written onto the paper.
Use the largest circle to write "core goal." Around it, use boxes to write the various "rules." Use different shapes (for example, circles for influencers, diamonds for decision-makers) to draw each "role." Use arrows to connect these roles, annotating their relationships (for example, reporting, trust, conflict).
Consider how these elements interact. For example, the company's "engineering culture" (an implicit rule) determines that the interviewer (a role) will place particular weight on your "data-analysis ability" (a requirement placed on candidates).
When you finish this sketch, you may feel an unprecedented clarity.
You are no longer a "Reckless Charger" who knows nothing and merely mass-submits resumes. You hold a preliminary "battle map."
Based on this map, you can begin to devise your "open-map" strategy:
- Against "Goals": in your resume and interview, foreground the qualities that match the "core goal" of the role.
- Against "Rules": optimize your resume's keywords to pass ATS screening; practice the written test with targeted questions; study interview accounts to adapt to the interview style.
- Against "Roles": make every effort to find a reliable "referrer"; in the interview, do not merely answer questions but also ask yourself, "what is the interviewer (the influencer) trying to prove to his boss (the decision-maker) by asking this question?"
This sketch may still be rough, filled with many "hypotheses awaiting verification." That is fine. It gives you a clear framework and direction for the "intelligence collection" to come (the next chapter) and for your "decision simulation."
You have successfully transformed from a passive "job seeker" into an active "strategist of the recruitment system."
You have taken a solid and important step toward becoming an "Open-Map Navigator."
Chapter Summary
In this chapter, we completed a fundamental shift in perspective, from "winning people over" to "understanding systems." We introduced the core analytical framework of the "open-map" methodology: the Decision System.
We understood that any challenge we face is in essence a complex system built on three pillars: Goals, Rules, and Roles.
Goals are the soul of the system, defining the direction it takes. Rules are the skeleton of the system, defining how it operates. Roles are the organs of the system, the executors and influencers of its will.
By applying the GRR Model, we learned how to draw a preliminary "decision system" sketch, giving us a foundational map for seeing the hidden logic behind complex situations.
And yet this map is still shrouded in fog and unknowns. Those "hypotheses awaiting verification" call for more refined methods to confirm or refute.
In the next chapter, we enter the second part of the "open-map" methodology: the Methods section. There we will learn the first core skill: Intelligence. We will learn to gather information systematically, like a professional intelligence analyst, dispersing the fog from the map until every detail comes clearly into view.
The tools for drawing the map are ready. Now let us set out to find the precious "pigments" that will fill it.