Assume Good Intent and Trust People — The Basic Premise of Collaboration

• Opening: One Line, Two Different States of Mind
• What Assuming Good Intent Means
• The Mechanism by Which Good Intent Reduces Conflict
• Verification Is Still Necessary: Trust but Verify
• Curiosity Instead of Blame
• Reducing Misunderstanding in Remote and Async Work
• Responding When Trust Breaks
• A Case: The 3 a.m. Commit
• Self-Diagnosis Checklist
• More Cases: Same Principle, Different Endings
  • Case 1: A Terse Slack Message Across a Time Zone
  • Case 2: When "Why Did You Do It This Way" Was Genuine Curiosity
  • Case 3: A Repeated Broken Commitment and Correct Escalation
• Suspicion Mode vs. Good-Faith Mode: Same Message, Different Reply
• The Four Components of Trust: Trust Is Not a Vague Feeling
• The Trust Equation and the Emotional Bank Account
  • The Trust Equation
  • The Emotional Bank Account
• Templates for Turning Blame Into Curiosity
• Frequently Asked Questions
  • Doesn't assuming good intent just make me a pushover?
  • Do you assume good intent even toward someone clearly acting in bad faith?
  • Misunderstandings keep happening over text — what do I do?
  • People say verification feels like distrust to them — what about that?
  • Do I always have to be the first to assume good intent? What if the other side doesn't?
• A Counterpoint: When Assuming Good Intent Becomes Poison
• From a Personal Habit to a Team Culture
• A One-Week Practice Guide
• Closing: Solid Trust
• References

Opening: One Line, Two Different States of Mind

Monday morning, a message arrives from a colleague: "Why did you do it this way?" It is the same single line, yet it reads entirely differently depending on the receiver's state of mind.

• Suspicion mode: "They are blaming me. They are saying my approach is wrong."
• Good-faith mode: "They are probably curious about context I have. I can just explain."

The sender was merely curious, but the day's collaboration turns on which state of mind the receiver reads it in. Read in suspicion mode, a defensive reply goes out, the other side receives it defensively, and a small misunderstanding spreads into conflict. Read in good-faith mode, it ends with a single line of context.

This essay is not a naive plea to "just trust everyone." Quite the opposite. It is about building solid trust by assuming good intent and verifying.

What Assuming Good Intent Means

Assuming good intent connects to what philosophy calls the "principle of charity." When someone's words or actions are ambiguous, you first interpret them in the most reasonable, most charitable way available.

Beneath this lies a simple but powerful premise: most people do not wake up in the morning and head to work thinking "today I will torment my colleagues." Most frustrating behavior has context we do not see. They were chased by a deadline, lacked information, had other priorities, or simply had a bad day.

Psychology has a concept called the "fundamental attribution error": we tend to attribute others' mistakes to their character ("that person is just irresponsible") and our own to circumstance ("there was nothing I could do at the time"). Assuming good intent is a tool for consciously correcting this bias. You give others the same situational benefit of the doubt you give yourself.

The Mechanism by Which Good Intent Reduces Conflict

Why does assuming good intent smooth collaboration? It becomes clear when you compare it with the vicious cycle in which conflict amplifies.

[Vicious cycle of assuming bad intent]
ambiguous message -> "this is blame" -> defensive reply -> they get defensive too
   -> relationship stiffens -> next message read worse -> conflict

[Virtuous cycle of assuming good intent]
ambiguous message -> "are they curious about context" -> calm reply -> they stay calm too
   -> trust accumulates -> next message read better -> cooperation

The key is that interpretation is self-fulfilling. If I interpret the other person as an enemy, my reaction actually makes them an enemy. If I interpret them as a colleague, my reaction actually makes them a colleague. The first interpretation sets the trajectory of the relationship that follows.

Verification Is Still Necessary: Trust but Verify

Here balance matters. If assuming good intent becomes "blind trust," it is dangerous. The phrase "trust but verify" shows the exact balance point.

Assuming good intent is about a person's intent. Verification is about the facts of the work. The two do not conflict.

• Assuming good intent: "My colleague did not miss the schedule on purpose." (interpreting intent)
• Verification: "Still, the schedule did slip, so let us confirm a new deadline together." (confirming facts)

A good collaborator trusts people while building a safety net with systems. Code review, tests, documentation, and meeting notes exist not because we suspect anyone, but because anyone can make mistakes. The healthiest stance is "I trust you, but since we are both human, let us keep the checks in place."

The table below shows applying good intent and verification together.

Curiosity Instead of Blame

The most concrete way to practice assuming good intent is to swap blame for curiosity. When a problem arises, ask not "whose fault is this?" but "what happened?"

Here are two dialogue examples handling the same situation.

[Blame mode]
A: Why didn't you announce the deploy in advance? It caused an outage.
B: I posted it to the channel. Isn't it your problem you missed it?
A: Who reads all of that?
-> No fact-finding, just hurt feelings

[Curiosity mode]
A: I don't think the deploy notice reached me. Where did you post it?
B: The deploy channel. Oh, maybe you're not subscribed to it.
A: Right. From now on, should we add a mention for important ones?
-> Root cause + prevention

The difference in curiosity mode is that it reframes the problem as a system issue, not a person. The higher the psychological safety Amy Edmondson described, the more natural these curiosity-based conversations become, because people do not take mistakes as attacks on their character but as problems to solve together.

Reducing Misunderstanding in Remote and Async Work

Where assuming good intent matters most is the remote, async environment. Text has no facial expression, no tone of voice, no immediate feedback. The human mind fills the gaps left by missing information, and when the mind is in a bad state, it fills those gaps negatively.

Practices run in two directions.

The receiving side (the reader):

• Do not read a short message as rudeness. "Got it" may not be cold, just busy.
• If there is room for misunderstanding, do not conclude immediately; ask. "Do you perhaps mean X?"
• If emotions escalate over text, switch to a video or voice call. Text easily amplifies conflict.

The sending side (the writer):

• Add one more line of context. Instead of "why did you do it this way?", try "I'm curious about the context. Could you tell me why this part ended up this way?"
• In async, state intent explicitly. A single line of "not blame, just a confirming question" makes a big difference.
• Praise in public, deliver hard feedback one-on-one.

Responding When Trust Breaks

Assuming good intent has clear limits. If the same person breaks the same promise repeatedly, assuming good intent every time then is not good faith but self-deception. Trust is not given without limit; it is recalibrated when broken.

A staged approach works well.

1. First time: Assume good intent. Anyone can slip. Let it go lightly.
2. Second time: Check whether it is a pattern. Ask directly, but without blame: "The deadline has slipped twice recently. Is something blocking you?"
3. Third time and beyond: Treat it as fact. Set a clear boundary using specific examples and impact, not emotion. Involve a third party or manager if needed.

The key is to hold both the generosity of the first time and the firmness of the third. Be only generous and you become a pushover; be firm from the start and you wreck the relationship. Assuming good intent is a starting point, not a destination.

A Case: The 3 a.m. Commit

On a remote team, a colleague went days without responding to code reviews. At first everyone was frustrated. "Why is this person so uncooperative?"

One teammate sent a message with curiosity instead of blame: "A few review requests have piled up. Are you swamped lately? Let me know if we need to reprioritize." A reply came. The colleague worked in a different time zone and, while caring for a family member, could only carve out time in the early hours. That was why the commit timestamps read 3 a.m.

Had they gone with bad-intent assumptions, they would have branded the colleague "uncooperative" and the relationship would have soured. Approaching it with good intent plus verification surfaced the real cause, and the team rebalanced the review load. It preserved both the colleague's situation and the team's progress.

Self-Diagnosis Checklist

[ ] When I get an ambiguous message, I first try the most charitable reading
[ ] When a problem arises, I ask "what happened" before "whose fault"
[ ] I handle intent (the person) and facts (the work) separately
[ ] When emotions escalate over text, I switch to a call or in person
[ ] I see verification as a safety net for everyone, not as suspicion
[ ] When the same problem repeats, I escalate from generosity to firmness
[ ] I add one more line of context and intent to the messages I send

More Cases: Same Principle, Different Endings

Beyond the 3 a.m. commit, moments where assuming good intent changes the course of collaboration are scattered through everyday work. Here are three more.

Case 1: A Terse Slack Message Across a Time Zone

On a distributed team, a developer got a message from a designer: "I think we need to redo this screen." Just one line. It arrived as his day was ending and the sender's was just beginning.

The developer bristled for a moment. "Redo two days of work? Without a word of discussion?" He typed and deleted a reply several times. Fortunately he stopped before sending. It occurred to him that the time zone gap might have left the designer no time to explain at length.

So he replied: "Which part specifically is the problem? Let me know if there's context I'm missing." When the designer came online in the morning, a long answer came back. It turned out the PM had decided the day before to change the target audience, and that decision had been shared only with the designer. "We need to redo this" was not a criticism of the developer's work; it was a terse relay of a change handed down from above.

Had the developer fired off the angry reply, the designer would have wondered "why is he upset?" and gone defensive, and every future collaboration between them would have carried a thorny tone. A short message is often the product of a time zone and a busy schedule, not carelessness. One choice to fill the missing information with good faith headed off an entire unnecessary conflict.

Case 2: When "Why Did You Do It This Way" Was Genuine Curiosity

In code review, a senior engineer left a comment on a junior's PR: "Why did you solve this with recursion?" The junior lost sleep over that one line. "I got it wrong. I should have used a loop, and I stupidly used recursion." The next day, without asking, he rewrote the whole thing with loops and re-submitted.

The senior commented again: "Oh, I actually think recursion reads better here. I was curious about your reasoning, in case there was a constraint I didn't know about. The original was better, so why did you change it?" Only then did the junior realize the question had been genuine curiosity, not blame.

The tone of a question is decided by the reader's state of mind. Because the junior read it in suspicion mode, he needlessly tore up perfectly good code and wasted a day. Had he instead asked back, "I thought recursion was more natural for the tree structure here. Do you see it differently?", the two of them would have confirmed each other's intent in a short exchange and reached a better decision together. The word "why" can be blame or curiosity. What makes the difference is often the reader.

Case 3: A Repeated Broken Commitment and Correct Escalation

There are also cases where assuming good intent runs out. A teammate promised every sprint, "This time I'll definitely finish," but missed the deadline three times in a row. Each time there was a reason. The first was an urgent outage, the second a request from another team, the third "more complex than expected."

The team lead let the first two go in good faith. Everyone is busy; reasons happen. But by the third, the lead admitted that repeating the same good faith was no longer generosity but avoidance. Each time a commitment slipped, other teammates filled the gap, and that burden was quietly accumulating.

The lead set up a one-on-one, without blame but firmly. He brought facts, not feelings. "I went back over the deadline situation across the last three sprints. I understand each had a different reason. But I see a pattern, and I'd like us to look together at what's structurally getting in the way — whether it's estimation, or priorities shifting, or something where you need help." By the end of the conversation, the real cause surfaced. The teammate was weak at estimation and, unable to say no, kept absorbing requests from other teams.

The solution was not punishment but structural change. Estimates were done in pairs, and outside requests were routed through the lead. The key is timing. Good faith was the starting point for rounds one and two; escalation was the justified next step at round three. Escalate too early and the relationship breaks; assume good intent forever and the whole team collapses.

Suspicion Mode vs. Good-Faith Mode: Same Message, Different Reply

Let us place side by side the replies that go out when the same async message is read in each mode.

[The message received]
"This doc still isn't updated. I said I needed it before the meeting."

[Read in suspicion mode]
Inner voice: "They're calling me lazy, aren't they? Look at that tone."
Reply: "I had other urgent things. I don't work 24 hours a day either."
Result: They flare up too -> "You should have said so earlier" -> a fight

[Read in good-faith mode]
Inner voice: "The meeting must be urgent. They're feeling the pressure."
Reply: "You're right, I dropped it. What time is the meeting? I'll handle
       it now and share within 30 minutes. If there's a part you need
       before that, tell me first."
Result: They relax -> "Thanks, it's the 2 p.m. meeting" -> problem solved

Same sentence, same fact (the doc is late), yet a single reply decides the day. Notice the good-faith reply is not letting the other person off the hook. It acknowledges the fact that the doc was late (verification) while interpreting the other person's intent as pressure rather than hostility (good faith). Face the facts, be generous with the person — that combination is the key.

The Four Components of Trust: Trust Is Not a Vague Feeling

When trust breaks, we tend to lump it together: "I just can't trust that person." But trust is not a single block. The coaching expert Charles Feltman, in "The Thin Book of Trust," breaks trust into four distinct components. Knowing which one collapsed lets you have a concrete conversation instead of vague distrust.

This breakdown is powerful because it pinpoints the real problem when trust breaks. In the 3 a.m. commit case, the colleague's sincerity, competence, and care were all intact. The only thing shaken was reliability (responding on time), and that was due to time zone and circumstance, not a lack of ability. Lump it as "I can't trust them" and you doubt the whole relationship; narrow it to "only the response timing is the issue" and the exact fix — rebalancing the load — comes into view.

In the repeated broken commitment case, what collapsed was reliability. In the senior code review case, what the junior briefly doubted was his own competence, but in fact nothing had broken at all. Next time someone gives you the feeling of being "untrustworthy," ask which of the four components actually wobbled. Usually it is one, not all.

The Trust Equation and the Emotional Bank Account

There are two frameworks for handling trust more practically.

The Trust Equation

David Maister, in "The Trusted Advisor," explains trust as a single relational formula. Stated in words rather than drawn as a fraction: trustworthiness is proportional to the sum of three things, divided by one.

trustworthiness = (credibility + reliability + intimacy) divided by self-orientation

- credibility: this person's words have grounding
- reliability: they do what they say, they're predictable
- intimacy: it's safe enough to share sensitive things
- self-orientation: how much they only look out for themselves
  (the larger it is, the lower the trust)

The larger the three numerator terms (credibility, reliability, intimacy), the higher the trust. But the real crux is the denominator, self-orientation. However capable and consistent someone is, if the other person feels "this person ultimately only looks out for their own interests," the denominator grows and trust collapses. Conversely, a person with low self-orientation — one who genuinely weighs the other's interests too — keeps trust well even through small mistakes. This is exactly why assuming good intent is so powerful. The very act of interpreting the other person's intent charitably sends them the signal "this person isn't self-serving," which lowers the denominator.

The Emotional Bank Account

Stephen Covey, in "The 7 Habits of Highly Effective People," likens trust to a bank account. Keeping promises, showing kindness, respecting the other person, and offering small considerations are deposits. Breaking promises, being rude, and disregarding the other person are withdrawals.

The power of the metaphor is that trust is a balance. In a relationship with a healthy balance, an occasional mistake (a small withdrawal) does not shake the relationship, because the other person reads it charitably: "they're a good person, they must have just had a bad day." In a relationship whose balance is drained, a single small mistake pushes the account into the negative and the relationship breaks.

The important insight here is that everyday deposits are buying future good-faith assumptions in advance. If the 3 a.m. commit colleague had been someone steadily making deposits, the team would naturally have read days of silence as "they must have a reason." The healthier the trust balance, the easier assuming good intent becomes; the emptier the balance, the more easily the same behavior is read as malice.

Templates for Turning Blame Into Curiosity

Resolving to be charitable and actually putting it into words are different things. Below are ready-to-use templates for converting sentences that sound like blame into curiosity-based ones.

You can see the common structure. It turns assertions into questions, "you" into "my understanding," and past blame-seeking into future problem-solving. "Why didn't you do it" points at the person, but "is something blocking you" points at the problem. This small shift in vocabulary keeps the other person's defensive mode from switching on.

Frequently Asked Questions

Doesn't assuming good intent just make me a pushover?

This is the most common misunderstanding. Assuming good intent means interpreting intent charitably, not turning a blind eye to facts. A pushover concedes the facts too. "They probably didn't mean it" (good faith) and "still, the schedule slipped, so let's set a new deadline" (verification) hold at the same time. Because it faces the facts squarely, assuming good intent actually keeps you from becoming a pushover. Real good-faith assumption includes the stage of firmly drawing a boundary when something repeats.

Do you assume good intent even toward someone clearly acting in bad faith?

No. Assuming good intent is a default, not an absolute principle. It must be updated as evidence accumulates. The key difference is the starting point. Keep good faith as the default until bad intent is proven, but once a clear pattern emerges, adjust your response to fit that fact. That said, the judgment "they're acting in bad faith" must rest on repeated facts, not one or two impressions. Concluding that a single act of rudeness is permanent malice is itself the fundamental attribution error.

Misunderstandings keep happening over text — what do I do?

Three suggestions. First, confirm before concluding. Not "are you being sarcastic?" but "do you perhaps mean X?", filling the gap with a question instead of a guess. Second, change channels when emotions rise. Text amplifies conflict, so when a few rounds of ping-pong get heated, switch to voice or video. Third, state intent up front as the sender. A single line of "not blame, just a confirming question" switches off the other person's suspicion mode in advance. Misunderstanding usually comes from missing information, so the habit of adding one more line of context is the most effective.

People say verification feels like distrust to them — what about that?

The key is to apply verification to the system, not the person. The frame is not "I check because I don't trust you" but "we're both human and can make mistakes, so we keep a procedure." Code review, tests, and meeting notes target no one in particular and apply equally to everyone, so they don't feel like distrust. Sharing the purpose of verification also helps ("I'm recording this so both of us remember later"), reducing defensiveness. A safety net applied consistently to everyone reads as care, not distrust.

Do I always have to be the first to assume good intent? What if the other side doesn't?

The value of assuming good intent lies in being self-fulfilling. If I respond charitably first, the other person's defensive mode switches off, opening room for them to turn charitable too. Someone has to start, and that choice usually rests with the one reading the message. This does not, however, mean unlimited one-sided concession. If I keep approaching with good faith and the other person stays hostile, that is a pattern and a signal to escalate. Give good faith first, but do not give good faith forever to someone who never returns it.

A Counterpoint: When Assuming Good Intent Becomes Poison

For balance, let us honestly note the cases where assuming good intent turns harmful.

When good faith becomes enabling. If you cover someone's harmful behavior every time with "they probably didn't mean it," that is not generosity but acquiescence. Especially when that behavior repeatedly harms others, "their intentions were good" cannot be a get-out-of-jail card. Even if the intent was good, when the impact is harmful, the impact must be addressed. Assuming good intent is generosity toward intent, not exemption from consequences.

Charity fatigue. Assuming good intent takes energy. Straining to read every ambiguous message in the best possible light is exhausting, especially when that good faith is only ever consumed one way. If one side is endlessly generous while the other only takes, assuming good intent is not sustainable. Caring for yourself is part of the balance. Boundless good faith is not a virtue but a shortcut to burnout.

The problem of power dynamics. Assuming good intent is not equally easy for everyone. It is far harder for the person with less power. A new hire reading an executive's cold message charitably and an executive reading a new hire's mistake charitably carry completely different stakes. The person with less power has more to lose if they read it wrong. So demanding that the less powerful "just take it more positively" can be unfair. If anything, the responsibility for assuming good intent should fall more heavily on the side that holds the power. The right direction is for the powerful to state their intent clearly first, create a safe atmosphere, and spare the less powerful from having to squeeze out good faith.

These counterpoints do not topple assuming good intent. They simply remind us that it must be a mature stance that holds facts, impact, and power in view together — not "unconditional generosity."

From a Personal Habit to a Team Culture

So far the focus has been on how an individual reads a message. But assuming good intent is hard to sustain if it depends on one person's effort alone. However charitably one person reads things, if the team's default atmosphere is suspicion and blame, that person burns out quickly. Assuming good intent shows its real power when it moves from a personal virtue to a team default.

There are several concrete mechanisms for making it a team culture.

A norm of stating intent. Make it a team habit to prefix hard feedback or potentially ambiguous questions with a line of intent. When phrases like "not blame, just confirming" or "this is only a suggestion, not a mandate" become natural, the receiver is far less likely to slip into suspicion mode. One person doing it feels awkward; everyone doing it becomes culture.

Blameless retrospectives. When an outage or mistake happens, routinize a retrospective that asks not "who did it" but "what system made this possible." When the promise not to blame people is made explicit, people stop hiding mistakes and surface them. Hidden mistakes repeat; surfaced mistakes get fixed.

Leaders model it first. Because of the power gap, assuming good intent is most effective when it flows top-down. When a leader admits their own mistakes first ("I dropped that announcement") and openly reads a teammate's ambiguous behavior charitably, the whole team learns that tone. Conversely, if a leader uses suspicion and blame as the default, no amount of well-written norms will function.

Rituals that build trust. On remote teams, non-work chatter, light check-ins, and short moments of sharing each other's context are deposits into the trust balance. The more you know each other as people, the easier it is to read ambiguous messages charitably. Simply knowing "what kind of person this is" sharply lowers the odds of assuming bad intent.

The key is not leaving assuming good intent as a vague appeal to "just think the best of each other." When the structure of explicit norms, regular retrospectives, leader modeling, and trust rituals holds it up, assuming good intent becomes the team's natural air rather than one person's tiring effort.

A One-Week Practice Guide

Knowing about assuming good intent from reading and actually having it in your body are entirely different. Below is a small exercise you can try, one per day, over a week. It need not be grand. One conscious shift at a time accumulates into a habit.

[Mon] Pause once
  Pick one line from today's messages that made you bristle.
  Before replying, recall once: "what's the most charitable reading?"

[Tue] Turn it into a question
  In a moment you want to blame, say "what happened" instead of "who did it."
  Throw out one question instead of a verdict.

[Wed] Add one line of context
  Add a line of intent to a potentially ambiguous message you send.
  Just one line: "not blame, I'm just curious."

[Thu] Separate fact from intent
  Pick one problem situation and write intent (the person) and fact (the
  work) separately. Treat the person generously, the facts clearly.

[Fri] Change the channel
  If a text exchange is heating up into ping-pong, switch to voice or video.

[Sat] Make a deposit
  Express one small thanks or acknowledgment to a colleague. Deposit into
  the trust balance.

[Sun] Reflect
  Recall whether a charitable reading headed off a conflict this week.
  Take the moments that didn't go well without blame, just as material
  for next week.

The aim of this exercise is not to become perfect. It is to create a very short gap between the first interpretation that springs out automatically when an ambiguous message arrives and the reply you actually send. To ask, in that gap, one more time: "is there context I don't know?" That single beat of pause becomes, over time, a default that works without conscious effort.

Closing: Solid Trust

Assuming good intent is not naivety. It is in fact the most efficient collaboration strategy. The cognitive cost of suspecting the other person's intent every time, and the emotional cost of defensive responses, are larger than you think. Set good intent as the default and you save that cost for the actual work.

At the same time, assuming good intent becomes solid only on top of verification. Trust the person's intent but confirm the facts of the work, and when trust breaks repeatedly, draw the boundary again. Collaboration is healthiest when generosity and firmness, trust and verification, are held together.

Take one ambiguous message you received today and re-read it once toward the most charitable interpretation. That small shift in interpretation may prevent more conflict than you would expect.

References

• Amy Edmondson, "The Fearless Organization" — https://amycedmondson.com/the-fearless-organization/
• Google re:Work, Psychological Safety — https://rework.withgoogle.com/guides/understanding-team-effectiveness/
• HBR, "What Is Psychological Safety?" — https://hbr.org/2023/02/what-is-psychological-safety
• Principle of Charity, Stanford Encyclopedia of Philosophy — https://plato.stanford.edu/
• Will Larson, "Engineering management" — https://lethain.com/
• The Fundamental Attribution Error, Verywell Mind — https://www.verywellmind.com/what-is-the-fundamental-attribution-error-2795261
• Charles Feltman, "The Thin Book of Trust" — https://thinbook.com/product/the-thin-book-of-trust-third-edition/
• David Maister, The Trust Equation — https://trustedadvisor.com/why-trust-matters/understanding-trust/understanding-the-trust-equation
• Stephen Covey, "The 7 Habits of Highly Effective People" (Emotional Bank Account) — https://www.franklincovey.com/the-7-habits/
• Brené Brown, "Dare to Lead" — https://brenebrown.com/book/dare-to-lead/