The four tools from the back of the book

Appendix A

The Trust Account

The one model this whole book runs on, on one page.

Every client relationship has an account. Every interaction is a deposit or a withdrawal — there are no neutral transactions.

The three rules

1. There are no neutral transactions. Every touch moves the balance, one direction or the other.
2. The balance compounds. The fuller the account, the more every new deposit is worth — and the more forgivable an honest mistake becomes.
3. You cannot withdraw from an account you never funded. When the crisis comes — and it’s coming — the only trust you have to spend is what you already banked.

The test, in one phrase: treat it like it’s your money. A vendor never says it. A partner means it.

Appendix B

The Partner Test

Ten questions to ask anyone who touches your technology.

For the business owner deciding who to trust. Ask these of your current provider — or the one across the table from you. The answers tell you whether you’re looking at a vendor or a partner.

1. “What have you noticed about my business that I didn’t ask you about?” A vendor will have nothing. A partner will have a list.
2. “Tell me about a time you talked a client out of buying something.” If they can’t, every recommendation they’ve ever made is suspect.
3. “How do you make money on this recommendation?” Watch whether the answer comes easily. A partner’s incentives survive daylight.
4. “If my building lost power tomorrow, walk me through exactly what happens.” “We’d figure it out” is a hope, not a plan. A partner has already rehearsed it.
5. “Who besides you knows how my environment works?” If the answer is one person’s memory, you’re a hostage, not a client.
6. “What would you do differently if my budget were your own money?” Then watch their face. That phrase is the whole game.
7. “What’s the last hard truth you told a client that cost you revenue?” Honesty that never costs anything isn’t honesty. It’s marketing.
8. “When something breaks that’s your fault, how will I find out?” The right answer: from them, first, in plain language.
9. “What are you doing for my business when there’s no open ticket?” A vendor waits for the request. A partner is thinking about you when nobody’s paying them to.
10. “Why should I still be a client in ten years?” Listen for whether the answer is about their product — or about you never having to worry.

Appendix C

The Three Threes

Three sets of three questions, for three different rooms.

They show up throughout the book; here they are side by side.

Appendix D

The First Thirty Days

For the leader onboarding anyone new to infrastructure — and for the new hire smart enough to ask for it.

Fight the urge to throw them straight onto the ticket queue. Give them their first thirty days to map the place:

• Every server, and what actually runs on it
• Every application, who owns it, and who screams when it breaks
• Every pipeline and integration, end to end
• Every circuit and what fails over to what — tested when?
• Every system that only one person knows how to run
• The undocumented one-offs — the ad-hoc service somebody stood up two years ago that turns out to be vital to exactly one critical person

Most shops have documentation that’s a real polite word for “none.” That map is how a stranger turns into somebody you can lean on — and it pays for itself the first time something’s on fire at four in the morning and your new person already knows where the bodies are buried.