The Mastercard Principle: Why Great Communication Is Really Infrastructure

What if the best writing has less in common with literature than with a payment network?

That sounds absurd until you notice what both systems actually do. A payment network does not create the money, manufacture the goods, or own the bank accounts. It connects parties that need to trust one another. Good communication works the same way. It does not merely transmit information. It connects an idea to a person who must understand it, believe it, and do something with it.

This leads to a useful and surprisingly powerful thesis: the value of communication comes less from the information it contains than from the friction it removes between people.

A writer who ignores the audience is like a payment network that only works for one bank, in one country, using one currency. The underlying technology may be impressive, but the system is not useful at scale. By contrast, writing that understands its audience becomes infrastructure. It lets knowledge travel across differences in expertise, incentives, vocabulary, and context.

The question is not simply, “Is this accurate?” The more important question is: Can this idea cross the distance between me and the person who needs it?

The hidden business of connection

Mastercard’s most important asset is not a collection of cards. It is the network that allows a shopper, merchant, bank, and payment system to coordinate in seconds. The company does not issue most of the cards used on its network, and it does not sell the goods purchased with them. Its role is to make transactions possible between parties that would otherwise struggle to coordinate.

That role creates unusual economics. Once a network becomes widely accepted, each additional participant makes the system more valuable to everyone else. More cardholders attract more merchants. More merchants attract more cardholders. More transactions strengthen the relationships, data, security systems, and habits that keep the network in place.

Communication has a similar structure. Every organization contains knowledge that is valuable to some group but inaccessible to another. Engineers understand systems that customers cannot see. Doctors understand conditions that patients cannot diagnose. Finance teams understand numbers that executives need to interpret. Product teams understand features that users must learn to trust.

The writer functions as a translator and network operator. The job is not to pour information into an empty container. It is to establish a reliable connection between a source of knowledge and a recipient with a specific need.

Consider a software error message that says:

Authentication failed due to an invalid credential configuration.

Now consider:

Your password did not work. Check that Caps Lock is off, then try again.

The second message does not contain more technical knowledge. It contains less. Yet it is more valuable because it reduces the distance between the problem and the next action. It understands the likely reader, the reader’s level of expertise, and the reader’s immediate goal.

This is the first communication principle borrowed from networks: a message becomes useful when it works for the people on both sides of the exchange.

Audience is not a demographic. It is a transaction.

Writers often define an audience with broad labels: customers, managers, beginners, professionals, investors, or the general public. These categories are sometimes useful, but they are not precise enough to guide difficult decisions.

A better question is: What transaction is this reader trying to complete?

A reader may be trying to:

1. Understand a new concept.
2. Decide whether to trust a recommendation.
3. Complete a procedure without making a costly mistake.
4. Persuade someone else.
5. Compare alternatives.
6. Act quickly under pressure.

The same person can occupy several audience roles in one day. In the morning, a manager may need a concise decision brief. At lunch, that same manager may need a detailed explanation of a technical problem. In the evening, the person may become a novice while trying to repair a household appliance.

Audience, therefore, is not primarily a question of identity. It is a question of context, intent, risk, and existing knowledge.

This distinction matters because writing fails when it optimizes for the wrong transaction. A product manual that tries to demonstrate the intelligence of its engineers may be technically impressive but operationally useless. A persuasive essay that explains every background detail before revealing its central claim may be accurate but fail to persuade. A financial report filled with unexplained acronyms may be comprehensible to its authors and opaque to its decision makers.

The writer’s first responsibility is to identify what must happen after the reader finishes. Is the goal comprehension, action, confidence, or consent? Each goal requires a different design.

A useful audience brief can fit into four questions:

• Who is reading? What do they already know?
• What do they need to accomplish? What decision or action follows?
• What could prevent them from succeeding? Confusion, distrust, time pressure, jargon, or missing context?
• What would count as a successful transaction? A correct action, a changed belief, or a confident decision?

This is more rigorous than asking whether the writing “sounds good.” It treats communication as a system with inputs, obstacles, and outcomes.

Trust is the currency of every message

A payment network must solve more than connectivity. It must solve trust. Merchants need confidence that payment will clear. Banks need confidence that transactions are legitimate. Customers need confidence that their money and identity are protected.

Writing faces the same problem. Before readers accept an unfamiliar claim, they ask several silent questions:

• Does this person understand my situation?
• Is the information accurate?
• Has the writer omitted something important?
• Is this advice intended to help me, or to manipulate me?
• Can I safely act on this?

This is why audience awareness builds credibility. When readers recognize their concerns, constraints, and vocabulary in the message, they infer that the writer has done the work of understanding them. A concrete example can create more trust than an additional paragraph of abstract explanation because it demonstrates contact with reality.

Suppose a company announces, “We are enhancing our authentication architecture to deliver a more seamless security experience.” The sentence may be technically defensible, but it offers no practical handle. What changes for the customer? Will logging in take fewer steps? Will a code be required? What happens if the phone is lost?

A clearer version might say:

Starting in June, you will use your phone to approve new logins. You will no longer need to answer security questions. If you lose your phone, use the recovery link on the sign in page to regain access.

The second version creates trust by making the exchange visible. It tells the reader what is changing, when it changes, what to expect, and what to do if something goes wrong.

Plain language is not a reduction in intelligence. It is an increase in transaction reliability.

This is why active voice matters. “The request will be reviewed by the team” conceals responsibility and timing. “The support team will review your request within two days” identifies the actor and sets an expectation. The reader can now evaluate the promise and decide what to do next.

In high trust communication, clarity performs the role that security performs in a payment network. It reduces uncertainty at the exact point where uncertainty would otherwise stop the exchange.

The real cost of jargon is conversion loss

Every audience has an invisible conversion rate. Out of all the people who begin reading, how many understand the central idea? Of those, how many believe it? Of those, how many take the intended action?

Jargon reduces this conversion rate by imposing an unnecessary entry fee. Sometimes specialized terms are essential. A surgeon cannot explain every procedure without technical vocabulary, and a software engineer cannot describe a complex system using only everyday words. The problem is not technical language itself. The problem is unpaid cognitive cost.

A term becomes expensive when the reader must stop, infer its meaning, determine whether it matters, and then reconstruct the sentence. If the writer never explains it, the reader must either abandon the transaction or pretend to understand.

That is a dangerous failure mode. Confusion often remains invisible because readers do not always ask for clarification. They nod, continue, and later make the wrong decision.

The solution is not to remove every technical term. It is to establish a shared vocabulary before relying on one. For example:

A chargeback is a payment reversal requested through a customer’s bank. It usually occurs when a customer disputes a transaction.

After this definition, “chargeback” becomes efficient shorthand. The term now lowers friction rather than creating it.

The same logic applies to examples and analogies. An analogy is a temporary bridge between what the reader knows and what the writer needs to explain. A payment network, for instance, can help explain an unfamiliar communication platform because both systems coordinate independent parties. But a bridge must lead somewhere. The analogy should clarify the structure, not become a decorative comparison.

One useful test is to remove every specialized word from a paragraph and ask what meaning disappears. If the answer is “not much,” the jargon was probably serving the writer’s status rather than the reader’s understanding.

Network effects in writing

Some communication becomes more valuable as more people can use it without translation. A clear explanation can move from a specialist to a manager, from a manager to a customer, and from a customer to a colleague. Each successful handoff extends the reach of the original idea.

This is a form of network effect. The best explanations are not merely understood once. They are reusable across relationships.

A well designed instruction may be read by a new employee, copied into a support response, adapted for a training session, and quoted in a policy document. Its value grows because it can travel. A vague explanation cannot travel far because every new reader needs a private interpreter.

This suggests a practical measure of writing quality: not only “Did the first reader understand?” but also “Could the first reader explain this accurately to someone else?”

That is why coherent words matter. Constantly replacing a concept with synonyms can create the illusion of variety while weakening the reader’s mental model. If a document uses “account,” “profile,” “record,” and “customer file” to mean the same thing, readers may reasonably assume these are different objects. Consistency gives an idea a stable address in the reader’s mind.

Structure matters for the same reason. Background information should arrive before it becomes necessary, not after confusion has already occurred. Examples should appear near the abstract claim they illuminate. Instructions should use direct verbs and visible sequences. These choices make the message easier to pass along without distortion.

The goal is not to make every sentence simple. The goal is to make the path through the idea simple.

A practical framework: design the route, not just the message

Before writing, imagine that your idea is trying to travel through a network. What obstacles will it encounter? Which readers are acting as gateways? Where might the message be rejected, delayed, or misunderstood?

You can design that route with five steps.

1. Define the destination

Write the intended outcome in one sentence. “The reader will understand our new policy” is too vague. Try: “The customer will know whether the policy applies to them and what they must do by Friday.”

A defined destination prevents the common mistake of confusing information volume with usefulness.

2. Identify the starting point

Estimate what the reader already knows, believes, fears, and expects. A novice needs background and definitions. An expert may need evidence and exceptions. A skeptical decision maker may need tradeoffs more than explanation.

Do not write for an imaginary average reader. Write for the real person at the moment of use.

3. Locate the friction

List the points where the reader might stop. Is the opening unclear? Is a key term undefined? Is the evidence hard to verify? Does the reader need to perform an action that has not been described? Does the message bury the answer beneath context?

The highest value revision is often the one that removes the largest obstacle, not the one that makes a sentence more elegant.

4. Establish trust before asking for movement

Show that you understand the reader’s situation. State relevant constraints. Explain the reason behind a recommendation when the reason affects compliance. Use examples that resemble the reader’s reality.

Trust does not require excessive warmth or personal disclosure. It requires evidence that the message has been designed with the reader in mind.

5. Test the handoff

Give the draft to someone who represents the intended audience. Ask them to explain the main point and describe what they would do next. Do not ask merely whether they like it. A reader can approve a document and still misunderstand it.

If possible, observe where they hesitate. Surveys and forms can reveal what audiences expect, but direct observation often reveals what they cannot articulate. Confusion leaves behavioral traces: rereading, skipping, clicking the wrong link, or asking a question the document should have answered.

Key Takeaways

• Treat audience as a transaction, not a label. Identify what the reader is trying to understand, decide, or do.
• Measure clarity by friction removed. Ask where a reader could hesitate, distrust the message, or take the wrong action.
• Use plain language as a trust mechanism. Clear wording, active voice, and concrete next steps make responsibility visible.
• Explain necessary jargon before using it. Specialized vocabulary should reduce repetition only after it creates shared understanding.
• Design for handoffs. A strong explanation can travel from one reader to another without losing its meaning.

The deepest lesson is that communication is not a performance delivered from one mind to another. It is infrastructure built between minds.

A payment network succeeds when strangers can exchange value without negotiating every detail from scratch. A piece of writing succeeds when readers can cross a gap in knowledge without needing a private guide. In both cases, the visible exchange is only the surface. Beneath it lies a carefully maintained system of trust, shared standards, clear signals, and reduced friction.

So the next time you write, do not ask only whether your argument is intelligent or your prose is polished. Ask a more consequential question: What must be true for this idea to move?

The answer will lead you toward your audience, your structure, your examples, and your words. It may also change your definition of good writing. The best communication is not the message that says the most. It is the network that lets the right meaning arrive intact.