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.

Related Insights

In a highly collaborative and fast-paced environment, assign explicit ownership for every feature, no matter how small. The goal isn't to assign blame for failures but to empower individuals with the agency to make decisions, build consensus, and see their work through to completion.

When entering a new domain, don't feign expertise. Build trust faster by openly admitting "I don't know" and explicitly leaning on stakeholders for their subject matter knowledge. This positions you as a partner who values their expertise, rather than an outsider imposing solutions.

Bupa's Head of Product Teresa Wang requires her team to explain their work and its value to non-technical people within three minutes. This forces clarity, brevity, and a focus on the 'why' and 'so what' rather than the technical 'how,' ensuring stakeholders immediately grasp the concept and its importance.

Effective product development starts with internal alignment. Using exercises like Instagram's "Stories Mad Libs" creates a shared, candid understanding of the product's current state. This "organizational therapy" is a prerequisite for overcoming team biases and conducting successful user research.

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.

Instead of siloing roles, encourage engineers to design and designers to code. This cross-functional approach breaks down artificial barriers and helps the entire team think more holistically about the end-to-end user experience, as a real user does not see these internal divisions.

Many leaders, particularly in technical fields, mistakenly believe their role is to provide all the answers. This approach disempowers teams and creates a bottleneck. Shifting from advising to coaching unlocks a team's problem-solving potential and allows leaders to scale their impact.

To encourage participation from everyone, leaders should focus on the 'why' behind an idea (intention) and ask curious questions rather than judging the final output. This levels the playing field by rewarding effort and thoughtfulness over innate talent, making it safe for people to share imperfect ideas.

Gaining genuine team alignment is more complex than getting a superficial agreement. It involves actively surfacing unspoken assumptions and hidden contexts to ensure that when the team agrees, they are all agreeing to the same, fully understood plan.

To foster a learning environment, especially for non-technical team members exploring code, rebrand "dumb questions" as "safe space questions." This linguistic shift removes judgment and encourages the fundamental inquiries necessary for beginners to grasp new technical concepts without fear.

Accelerate Team Buy-In by Admitting What You Don't Know | RiffOn