Using The Trust Equation to enhance PDSA Cycle

What each one is actually for

The Trust Equation

The Trust Equation is a diagnostic, not a technique — it exists to stop "be more trustworthy" from being a single vague goal and turn it into four separate, workable ones. Credibility is about your words: does what you say check out, is it accurate, does it hold up under scrutiny. Reliability is about your actions over time: when you say you will do something, does it actually happen, on time, repeatedly, so a pattern forms. Intimacy is the trickiest of the three to name and the one people most often skip — it is whether the other person feels it is safe to tell you something true, including something uncomfortable, without you flinching, punishing them, or using it against them later. The equation divides the sum, or product depending on the version, of those three by self-orientation, meaning how much of your attention in the interaction is visibly on your own needs, your own image, your own outcome, rather than theirs — because a person can be accurate, reliable, and safe to confide in, and still come across as untrustworthy the moment it becomes clear they are performing all three for their own benefit.

PDSA Cycle

PDSA is a discipline for testing a change on a small enough scale that being wrong costs you almost nothing, before you decide whether to keep doing it. Plan means writing down, in advance, exactly what you are going to try, and — this is the step people skip — what you predict will happen if it works, specific enough that you could later say clearly whether the prediction came true or not. Do means actually running the small test, once, in a real but limited setting. Study means comparing what actually happened against what you predicted, not against what you hoped, and being honest about the gap. Act means deciding, based on that comparison, whether to adopt the change, adjust it and run another cycle, or drop it. The whole loop exists to replace "I tried something and it seemed to go okay" — which tells you almost nothing, because memory and self-serving impressions distort in predictable directions — with an actual comparison between a stated prediction and a stated result.

What you get out of pairing them

What the Trust Equation buys you is a vocabulary for a problem that usually just feels like "people don't quite trust me" with no further handle on it — now you have four separate dials instead of one fog. What PDSA buys you is proof, or disproof, instead of a feeling. Without it, a person who decides their self-orientation is too high will typically make one effortful, visible attempt — asking more questions in a meeting, say — notice it felt uncomfortable and effortful, and privately conclude either that it worked (because effort felt like progress) or that it did not (because the discomfort read as failure), with no actual check against what happened in the other person's head. Put the loop under the equation and that guess becomes a testable claim: you predict, before the conversation, what a lower-self-orientation version of you would look like and what you expect the other person to notice, then you actually ask, or watch for the specific signal you named in advance, rather than trusting your own read of how it went. That is the door: turning "I think I'm getting more trustworthy" from a hope you privately hold into a claim you have actually checked, on the one lever where you are weakest, this week, not eventually.

What The Trust Equation rests on

• Externalizing makes pattern visible randomised trials
  Putting an internal pattern into an external, structured form makes it visible and available for examination instead of remaining implicit and merely enacted.
• Self orientation inversely predicts trust practitioner report
  The degree to which a person appears focused on their own interests rather than the other party's interests inversely predicts how trustworthy they are perceived to be.

What PDSA Cycle rests on

• Feedback against prediction corrects belief plausible mechanism
  Comparing the actual result of a change against the predicted result before adopting it corrects mistaken beliefs faster than adopting or rejecting changes based on intuition alone.
• Small scale testing precedes scaling observational studies
  Running a change through a small planned test cycle before wider adoption reveals real-world effects while limiting the risk of being wrong.

Where they actually meet

Both practices refuse to let a global, fuzzy judgment stand unexamined — "am I trustworthy" and "did that change work" are both the kind of question a person will normally answer with a felt impression, and both practices insist on breaking the impression into a specific, checkable claim first. The Trust Equation does this by decomposing a single verdict, trusted or not, into four separately named factors so you know which one is actually in question. PDSA does the same decomposition to a change over time: instead of one blurry judgment, "that seemed to help," it forces a named prediction and a named result that can be compared side by side. Neither practice trusts a global impression on its own; each one insists you name the specific thing before you judge it.

The principle underneath both

The pattern underneath both is that a global, felt judgment about a relationship or a change is far less reliable, and far less actionable, than a named, specific claim checked against what actually happened. "I seem trustworthy" and "that change helped" are both verdicts arrived at by impression; the equation and the loop are both machinery for replacing an impression with a decomposed, checkable claim before you act on it.

What that makes the real goal

If specific, checkable claims are what actually move a fuzzy impression toward something reliable, then the objective both practices serve is closing the gap between what a person believes is happening — in a relationship, in a change effort — and what is actually, verifiably happening, by forcing belief into a form that can be wrong and therefore corrected. That objective is not owned by professional-services trust-building or by quality-improvement methodology specifically; it belongs to any domain where a person's private sense of progress tends to drift from the observable reality.

Other practices that serve the same goal

Cognitive behavioral therapy's behavioral experiments serve the identical objective in a therapeutic setting: a client names a specific feared prediction — "if I say no, she'll be furious" — carries out the action, and records what actually happened, with a large randomized-trial evidence base behind the broader approach. In workplace settings, 360-degree feedback processes attempt something structurally similar for the trust question specifically, gathering other people's actual perceptions of you against your own self-assessment, though the research on 360 feedback's effect on behavior change is decidedly mixed and depends heavily on how it is delivered. In personal habit change, the practice of prospective journaling — writing down what you expect a behavior to produce before you do it, then checking the entry afterward — is a lighter-weight, single-person version of the same predict-then-compare structure PDSA formalizes for organizations.

A tradition that already does this

Interpersonal Process Recall, a supervision method developed in counselor training, already runs something close to this exact fusion: a trainee predicts, before a session, how a client will respond to a particular intervention, then reviews video of the actual session afterward and compares the prediction against what the tape shows, on relationship-quality dimensions that overlap substantially with credibility, reliability, and intimacy as the Trust Equation names them. It is, in effect, a PDSA loop built specifically to test claims about how trustworthy an interaction actually was, rather than how trustworthy it felt from inside.

Using the Trust Equation to enhance PDSA

Most PDSA cycles run on operational metrics — did the wait time drop, did the defect count fall — and skip past the fact that a change is often being proposed, planned, and studied by a small group of people whose willingness to report an honest "study" result depends entirely on how much they trust each other. Before your next cycle, use the four factors to diagnose the team itself, not the process: is the person who will report the actual result someone whose account of failure will be believed (credibility), has this team's improvement work followed through on past commitments to change course when a cycle fails (reliability), can someone say "this didn't work and it was my idea" without it costing them (intimacy), and does the person running the cycle visibly care more about being right than about the truth of the result (self-orientation). A PDSA loop studied by a low-trust team quietly drifts toward reporting results that flatter the plan rather than results that are true, and naming which of the four factors is weakest tells you specifically what to fix in the team before you trust its next "study" step at all.

Using PDSA to enhance the Trust Equation

Pick the single weakest of your four factors — for most people it is intimacy or self-orientation, since credibility and reliability are easier to self-monitor — and run one actual PDSA cycle on it rather than a general resolution to "work on it." Plan: name one specific upcoming conversation, and predict, in writing, one concrete thing you will do differently — for example, asking one genuine follow-up question about the other person's stake in the outcome before stating your own view — and predict what you expect to happen if it lands, such as them offering more detail than they usually do. Do: have the conversation, actually doing the named thing. Study: afterward, compare what you predicted against what actually happened, specifically — did they offer more, the same, or less than usual, and how do you know, not how did it feel. Act: if the prediction held, keep the specific move and try it again in a different conversation next week; if it did not, that is real information about which of the four factors is not actually improving no matter how effortful the attempt felt, and worth revising the theory rather than just trying harder at the same guess.

After the meeting where you finally didn't jump in first

You are walking out of a Tuesday project meeting where you had decided, the night before, to let your co-lead finish outlining a problem before you offered your own read of it — a specific, planned attempt at lowering your self-orientation, because you had privately noticed you tend to interrupt with solutions before people finish naming what is actually wrong. In the meeting itself it felt awkward, like biting your tongue, and afterward your first instinct is the usual one: it probably didn't register with her at all, or worse, it read as you having nothing to say. Instead of settling for that guess, you pull up the note you wrote the night before, where you had predicted that if the pause actually landed, she would mention feeling heard, or would bring up the same problem again unprompted later in the week because she trusted it had actually registered. Two days later she does exactly that, referencing the same issue in a different context, clearly assuming you already understood it. That is not a feeling — it is your prediction, checked against an actual, specific, later event, and it tells you the pause worked in a way your Tuesday-afternoon anxiety could never have told you on its own.

When this is worth reaching for

Reach for this pairing when you already know, roughly, which of the four trust factors is weakest for you, but your attempts to work on it have stayed vague — "try to listen more," "be less defensive" — and have not visibly moved anything after repeated effort. It is also useful in a team or organizational context where an improvement process depends on people reporting honest results to each other, since a PDSA cycle run inside a low-trust group tends to quietly produce flattering rather than true findings.

Where this does not apply

If the trust problem in question is acute — a specific betrayal, a recent broken commitment, an active rupture — running a structured, predicted-outcome test on the other person's reaction is likely to feel clinical or manipulative to them, and to you; that moment calls for a direct, unstructured repair conversation, not an experiment. And a single PDSA cycle, run once, proves very little about something as slow-moving as how trusted a person is generally perceived to be; treat one cycle as one data point on one specific behavior in one specific relationship, not as a verdict on your overall trustworthiness.

What the evidence does and does not support

The Trust Equation's central claim, that self-orientation is the denominator that most sharply drags down perceived trustworthiness even when the other three factors are strong, rests on Maister's professional-services consulting observations and has not, to this writer's knowledge, been tested as a formal quantitative model against independent trust measures; treat the four factors as a well-argued, widely used framework rather than a validated psychometric instrument. PDSA's core logic, that comparing a predicted result against an actual result improves decisions faster than intuition alone, draws on decades of use in manufacturing quality control and, more recently, clinical improvement science, where it has reasonable observational support for producing better-calibrated organizational decisions. Nobody has run a study that fuses the two — using PDSA cycles specifically to test claims about one's own trustworthiness — and it is hard to picture what such a study would even measure, since the outcome, being trusted more, is itself a slow, socially distributed judgment that resists the kind of short, discrete cycle PDSA was built for. Treat everything above the FAQ as a reasoned bridge between two separately grounded ideas, not as a reported finding.