Citing Brené Brown, the speaker argues that trust isn't earned by "saving the day" on a schedule or feature. Instead, it is forged through small, daily actions like asking questions, learning each other's tools, and demonstrating genuine interest in each other's work.
Related Insights
To move beyond status updates in one-on-one meetings, managers should open up about their own challenges. Asking a team member for their perspective on a decision the manager is making fosters trust, shows respect, and can uncover valuable insights you hadn't considered.
Trust isn't just an emotion; it can be built methodically. First, use repeated exposure to move from being a stranger to a known entity. Second, before making a key point, establish a baseline of shared values to create an environment of agreement.
To transform team dynamics, leaders should intentionally ask questions that invite challenges and alternative viewpoints. Simple prompts like 'What might we be missing here?' or 'Does anyone have a different point of view?' create psychological safety and signal that all contributions are valued.
The strength of a team's trust isn't defined by avoiding mistakes, but by a leader's willingness to go back, take responsibility, and "repair" after a conflict. This builds more security than striving for perfect, error-free leadership.
Instead of avoiding risk, teams build trust by creating a 'safe danger' zone for manageable risks, like sharing a half-baked idea. This process of successfully navigating small vulnerabilities rewires fear into trust and encourages creative thinking, proving that safety and danger are more like 'dance partners' than opposites.
Joining as a new tech lead for an existing team, the speaker built trust by forbidding himself from giving direct orders or rejecting designs. He instead embedded with teams and used strategic questioning to guide them, helping them arrive at the right conclusions while respecting their expertise.
Go beyond "knowing" to "noticing": deliberately observing and remembering small details about a person's work and life. One manager used a simple notebook to track these details for weekly micro-check-ins, creating immense trust and engagement by showing she remembered.
At Menlo, PMs foster a fear-free culture by thanking developers who report budget or time overruns. This counter-intuitive reaction encourages early and honest communication, allowing the PM to manage issues proactively with the client instead of having them surface unexpectedly later.
While precise communication is important, consistently delivering results builds a deep well of trust with stakeholders. This operational trust can forgive minor inconsistencies or imperfections in how a message is communicated, as the track record speaks for itself.
Instead of faking expertise, openly admitting ignorance about technical details builds trust and empowers specialists. This allows you to focus on the 'what' and 'why' of the user experience, giving engineers and designers the autonomy to own the 'how', which fosters a more collaborative and effective environment.
