The Trusted Advisor: the book from 2000 that teaches FDEs how to win technical trust
Three consultants broke trust into four variables. The one in the denominator decides whether a customer listens to you.
In brief
- The Trusted Advisor (Maister, Green, Galford, 2000) argues that professional success depends on winning client trust, not only on technical skill
- The trust equation puts credibility, reliability and intimacy in the numerator and self-orientation in the denominator: the more you think about yourself, the less you are trusted
- Harper's FDE job posting explicitly asks for a trusted technical advisor, which makes this a foundational book for anyone moving into the role
Trust = (Credibility + Reliability + Intimacy) / Self-orientation. The larger the denominator, the lower the trust.
Graphic: FDE Times
Harper’s job posting for a Forward Deployed Engineer asks candidates to act as a trusted technical advisor throughout the customer relationship. It defines the goal of the role plainly: earning technical trust, the thing that “lands and expands enterprise contracts”.
Trust, then, is not a decorative soft skill. For an FDE it is an output metric. The trouble is that trust is rarely taught as a skill, so it is easy to walk into a meeting assuming that if you solve the problem, trust will follow.
The closest thing to a textbook on the subject came out in 2000. The Trusted Advisor, by three consultants, David H. Maister, Charles H. Green and Robert M. Galford, makes a simple and uncomfortable argument: the key to professional success is the ability to earn the trust and confidence of clients, not expertise alone. Green founded Trusted Advisor Associates, a firm named after the concept itself.
Trust has a formula
The book’s most memorable contribution is the trust equation, a model that splits trust into rational and emotional parts. Three variables sit in the numerator. Credibility is about your words: whether the customer believes what you claim about their system. Reliability is about your actions: whether you do what you promised, when you promised it.
The third variable, intimacy, deserves the most attention from engineers. The authors define it as the human connection and understanding of the other person, to the point where they feel safe showing you their weaknesses.
Picture a data lead at a customer admitting that their pipeline is patched together and nobody dares touch it. If they tell you that, you have intimacy. If they only say it internally, your deployment will hit a wall you never knew was there.
These three variables explain why an FDE who writes excellent code can still fail. High credibility with low reliability, such as promising a fix by the weekend and then going quiet, drags the whole fraction down.
And an engineer who talks only in system architecture, and never asks what the customer is worried about, will stay “the person hired to do the work” rather than “the person whose opinion is sought”.
The denominator is what decides
The fourth variable sits alone in the denominator: self-orientation, the degree to which you focus on yourself. Raise the denominator and trust falls. Trusted Advisor Associates calls it the most powerful variable in the equation.
This is a trap specific to FDEs, because the role sits close to sales. Harper says outright that technical trust is what expands contracts, so the pressure to prove the product is always in the room. An engineer who walks into a discovery session aiming to “show them what our agent can do” is pushing self-orientation up without noticing.
The customer notices. They will nod politely and not call back.
One exercise worth trying to keep the denominator in check: before each meeting, write one sentence describing the customer’s problem in their own words, without your product’s name in it. If you cannot write it, you are not ready to propose anything.
Five steps from first meeting to commitment
The 20th anniversary edition describes a five-step process, with a chapter for each step: engage, listen, frame, envision, commit. The order is what matters. Look back at your most recent customer meeting: chances are you went from a quick listen straight to proposing a solution, skipping frame and envision.
The five steps map closely onto a deployment cycle. Engage and listen are customer discovery. Frame is when you restate the problem so the customer confirms, “Yes, that’s exactly it.”
Envision is describing the state after the system is running, in business outcomes rather than architecture diagrams. Only at commit do you discuss scope and timeline.
| Step in the book | What the FDE does at that step |
|---|---|
| Engage | Open the conversation around the customer’s concerns, without talking about the product yet |
| Listen | Ask, then stay quiet; note the language they use to describe the problem |
| Frame | Restate the problem so they confirm or correct it |
| Envision | Describe the post-deployment state in terms of outcomes they care about |
| Commit | Agree scope, milestones and what you are accountable for |
Who should read it, and how
The book was written by three professional consultants, so translating it into the context of deployments and agents is work you have to do yourself. That is also why it is worth reading: its central argument is that professional success goes well beyond technical expertise, which is exactly what engineers are rarely told directly.
Developers aiming for an FDE role should start with the trust equation to get a way of measuring, then read the five steps to get a process. Those who have worked as FDEs for a year or two can reverse the order: read the five steps first, review a recent deployment to see which step they skipped, then return to the equation to understand why.
The telling detail in Harper’s posting is the phrase “throughout the relationship”. Trust is not won once at a demo and then put away; it is something you top up on every call, every pull request, every time you say “I don’t know yet, let me check”. This 26-year-old book will not teach you to make an agent run better.
It teaches you how to make sure that when the agent breaks, the customer calls you rather than a competitor.