Pre-read 4: The Law of Connection
Connect with people before you ask them for work. Connection comes before influence, and it is exactly the skill a code-first career never trained.
The standard first: Google Project Aristotle
After Project Oxygen measured managers, Google's Project Aristotle studied 180 teams to find what makes a team effective. The starting guess was team composition: put the best people together and you get the best team. The data said no. Who was on the team mattered much less than how the team members treated each other.
The number one predictor, above everything else, was psychological safety: the shared belief that you can take a risk in front of your team without being punished for it. You can ask the "stupid" question, admit a mistake, or disagree with a senior person, and nothing bad happens to you. Psychological safety is built, or destroyed, in small everyday moments. That makes connection a measurable engineering concern, not a soft extra.
The second standard: SBI and Radical Candor
Connection is tested most in the hardest moment: giving feedback. Two tools make it practical.
SBI (Situation, Behavior, Impact). Name the specific situation. Describe the exact behavior you saw, without guessing at motives. State the impact it had. Example: "In yesterday's design review (Situation), you rejected the proposal before the author finished speaking (Behavior), and the two junior engineers stayed silent for the rest of the meeting (Impact)." No judgment of character, no mind reading, nothing to argue about.
Radical Candor. Two questions: do you care about the person, and do you challenge them directly? Challenging without caring is just aggression. Caring without challenging is what Kim Scott calls "ruinous empathy": you stay quiet and let a colleague fail, because the conversation feels uncomfortable. Most engineers hide in that corner. The point of the model: the kind thing and the comfortable thing are usually not the same thing.
The law behind the standard
Maxwell says leaders connect with people before they ask them for anything. Remove the emotion and a clear mechanism remains: people decide how much effort to give you based on whether they believe you see them and want good things for them. That belief is built before you need it, or not at all. Connection is the deposit. Influence is the withdrawal.
On your track
- IC (Staff/Principal): win the skeptical senior on the other team before your RFC goes out, not after it lands. Three short conversations before the document beat ten pages of appendix.
- Lead/EM: win the person before the hard performance conversation. Feedback lands only as well as the connection it travels over.
The story: Nadella's Microsoft
When Satya Nadella became CEO of Microsoft in 2014, the company was famous for internal fighting. A well-known cartoon of the org chart showed the divisions pointing guns at each other. His turnaround engine was not a strategy document. It was a culture instruction: move from "know-it-all" to "learn-it-all". That is psychological safety, installed from the top. The stock price followed, but the mechanism was connection at scale.
Before the session
Come with one question this reading left you with. Starting points:
- Pick the person you work with that you know least. Can you write three true things about their goals? (Most people cannot fill three lines. That is the exercise.)
- What feedback have you been avoiding? Which Radical Candor corner are you hiding in while you avoid it?