Building trust before you need it

You will need a rushed review, a production change or a painful trade-off. The people who say yes are the ones who already believe you keep promises. Trust is a store of credit. You build it in quiet weeks, not in the incident channel.

You cannot manufacture trust in the middle of a fight. If you only show up when you need something, every ask feels extractive.

The big idea

Think of a tab at a café the owner already knows. Small bills paid on time mean the next unusual request is easy. The analogy breaks in a real incident: competence still matters more than charm. But competence without a track record of kept commitments still reads as risk.

Keep a mental map of who owns what and what they optimize for — reliability, revenue, headcount, deadline. Influence starts with their scoreboard, not your rehearsed argument.

Walking through it

Concrete deposits:

• Do what you said. Small commitments kept ("I'll reply by EOD") compound. Broken ones compound faster the other way.
• Make others look accurate. When you cite a teammate's work in a doc or launch note, you signal you are not a glory vacuum.
• Share context early. A short heads-up ("we may need your API next sprint") beats a surprise ticket with a Friday deadline.
• Be easy to review. Clean pull requests and clear writes teach people that time spent with you is not wasted.
• Assume good intent once. Most "blocking" behavior is local optimization or missing information, not malice. Investigate before escalating.

A platform team measured on reliability will resist risky launches near quarter end. Name that constraint when you ask: "I know you're frozen for the launch — can we schedule the API change for the week after?" You are not being political. You are showing you see their job.

When you later need influence without authority, this credit is what you spend. Homework and a small ask still fail if the last three times you promised a reply, you vanished.

Common mistakes

• Showing up only when you need something. Every ask then feels like a withdrawal with no deposits.
• Broken micro-commitments. "EOD" that arrives Thursday trains people to discount your dates.
• Assuming malice. Investigate incentives and missing information before you escalate.

Check yourself

1. You need a Friday review from a team you have never helped. What should you have done two weeks earlier?

A heads-up that you would need their API, plus a clean PR or draft they could trust — credit before the rush.

2. A teammate is "blocking" your launch. What do you check before you escalate?

Their scoreboard (reliability freeze, headcount, deadline) and whether they are missing information. Most blocking is local optimization, not malice.

Key takeaways

• Trust is built in quiet weeks and spent when you need speed.
• Kept micro-commitments, early context and visible credit are the usual deposits.
• Learn the other person's scoreboard before you make the ask.

Further learning

Next: disagreeing well.