The Trust Equation: Building Trust as a Chief of Staff

Takeaway: The Trust Equation is a reflection tool for four parts of a working relationship: credibility, reliability, intimacy, and self-orientation. It helps an operator identify a specific trust gap without treating trust as a personality trait.

A chief of staff may handle unfinished strategy, sensitive personnel questions, executive priorities, and decisions that haven't been communicated. Access to that work depends on the principal's confidence in the operator's judgment and discretion.

When trust weakens, the consequences are often practical. The principal shares less context, reviews more work, narrows delegated decisions, or keeps the operator out of sensitive conversations. Trust isn't the whole job, but it shapes how much of the job the operator can do.

The Trust Equation gives both people a more precise way to discuss it.

Use the equation as a prompt, not a score

In The Trusted Advisor, David Maister, Charles Green, and Robert Galford expressed trustworthiness this way (Trusted Advisor Associates):

Trust = (Credibility + Reliability + Intimacy) / Self-Orientation

The formula is conceptual. Its terms aren't objective quantities, and a total score can't predict whether someone will be trusted. Its value is in separating four questions that otherwise blur together:

• Credibility: Do your words hold up?
• Reliability: Do your actions match your commitments?
• Intimacy: Does the other person feel safe sharing difficult or unfinished information with you?
• Self-orientation: How much does your own agenda distort your attention or advice?

Three terms sit in the numerator and one in the denominator. The arrangement reminds the reader that visible expertise and follow-through aren't enough if the relationship feels unsafe or the advice appears self-serving.

Credibility: make the edges of knowledge visible

Credibility grows when an operator understands the business, uses accurate information, and distinguishes evidence from interpretation.

Suppose a project is behind. A credible update doesn't stop at "red." It says which milestone slipped, what caused the delay, which assumptions remain uncertain, and what decision is needed. The principal can rely on the statement because its basis is visible.

The useful habit is simple: say "I don't know, I'll check" when you don't know. Cialdini's authority principle also connects influence with perceived expertise and trustworthiness, rather than position alone (Influence at Work). Credibility doesn't require certainty. It requires accuracy about what is known.

Reliability: close the loop you promised to close

Chief of staff work produces many small commitments. You said the board draft would be ready Thursday. You agreed to confirm the hiring decision. You promised to send the leadership team a record of owners and deadlines.

Reliability comes from completing those commitments or renegotiating them before they fail. A dependable operator doesn't need to accept every request. They need to be clear about what they accepted and keep the other person informed when circumstances change.

Use a simple loop:

1. Record the commitment and owner.
2. Confirm the deadline and definition of done.
3. Surface a risk before the due date.
4. Close the loop with the result, decision, or revised agreement.

This is less dramatic than rescuing a late project and more useful over time.

Intimacy: create safety without blurring boundaries

In this framework, intimacy refers to the safety of the relationship. A principal needs room to test an idea, express uncertainty, or discuss a sensitive problem without seeing the conversation repeated elsewhere.

Discretion is part of that safety. So is candor. A trusted operator can say that a plan lacks evidence, a meeting landed poorly, or a decision needs another perspective. The point isn't to agree with the principal. It's to handle disagreement without using confidential context as leverage.

Safety also has limits. Confidentiality doesn't require hiding misconduct, ignoring legal obligations, or carrying a concern alone. The operator should understand which matters require HR, legal counsel, a board channel, or another appropriate process.

Self-orientation: check for distortion, not self-erasure

Self-orientation asks where the operator's attention sits. It rises when someone shades information to protect their reputation, withholds a risk because it reflects badly on them, or turns a company decision into a personal contest.

Low self-orientation doesn't mean caring less about your career, absorbing blame, or placing the principal's interests above your own ethics and boundaries. It means keeping personal advantage from distorting the advice you give.

Before a consequential recommendation, ask:

• Have I included evidence that weakens my preferred answer?
• Am I protecting my own work from reasonable scrutiny?
• Does the recommendation serve the stated organizational goal?
• Have I named a conflict of interest or personal stake?
• Would I make the same recommendation if someone else received the credit?

If the answer reveals a conflict, disclose it and bring in the right decision maker. Quiet self-denial isn't a substitute for a transparent process.

Diagnose a trust problem by behavior

A strained relationship is easier to repair when both people name the behavior rather than the character judgment.

Credibility problem: A figure in a memo was wrong, and the operator can't explain its source.

Reliability problem: A deadline passed without an update.

Intimacy problem: A sensitive conversation was repeated outside its intended audience.

Self-orientation problem: A recommendation omitted a risk that would make the operator's project look weaker.

Each problem calls for a different response. More expertise won't repair a confidentiality breach. A warm relationship won't compensate for repeated missed commitments.

Repair trust directly

Trust can change after a mistake, but repair depends on what happened and how serious it was. Avoid promises that every breach is recoverable.

A useful repair includes:

1. Name the specific action. "I sent the draft after the agreed deadline and didn't warn you."
2. Acknowledge the effect. "That left you without time to review before the meeting."
3. Correct what can be corrected. Send the accurate file, notify the right people, or restore the missing process.
4. Change the operating practice. Add an earlier review point or a clear escalation trigger.
5. Let the record rebuild over time. Don't demand immediate reassurance.

If the issue involves a serious breach of confidence, legal obligation, harassment, or safety, use the appropriate formal channels. A relationship framework doesn't replace them.

Use the framework in a principal check-in

Don't present the equation as a scorecard for the principal to grade. Use it to ask for concrete feedback:

• Which updates do you rely on most, and where do you need better sourcing?
• Which commitments have felt uncertain or required too much follow-up?
• Where do you need more candor or more discretion from me?
• When has my own preference made a recommendation less useful?

Agree on one behavior to change and a date to revisit it. Trust becomes more workable when the next step is observable.

Which factor should a new chief of staff work on first?

Start with the behavior the relationship needs. Reliability and discretion can be demonstrated from the first week. Credibility grows as you learn the business, and self-orientation can be checked in every recommendation.

Is intimacy the same as being liked?

No. In the framework, intimacy is the safety to share difficult or incomplete information. A warm relationship may help, but discretion and candid handling of sensitive material matter more.

Can the Trust Equation measure trust?

No. It organizes reflection around four components. It doesn't supply objective units or a predictive score.

The first 90 days operating plan offers a practical place to define working norms, decision rights, and early commitments with a new principal.