37 - How to Get Buy In

Scott, Dillon, and Matt discuss how to get support for technical changes. They cover trust, demos, early feedback, and deadlines. They also compare browsers after Arc and explain why testing only in Chrome can hide problems.

Hosts:

Released:

Episode length: 31m 53s


Summary

A sound technical plan does not guarantee support. The hosts discuss how to explain a problem, understand other teams, and help people agree on a change.

Build Trust and Show the Work

Dillon works with a small team, where fewer people need to approve a technical decision. He prefers a working proof of concept to a long proposal. Scott also builds prototypes, but work across teams has brought more resistance. A good document alone does not always resolve it.

Matt describes trust as something you build over time and can later borrow against. Changes to a team can reduce that trust. Sometimes the work requires repeated discussions and answers to several rounds of questions.

Agree on the Problem First

Explain why the change matters before you explain the design. Other teams need to understand how the work affects them. People often arrive at a meeting without having read the document, so start with the problem and the shared goal.

Ask for early feedback from people who agree with you and people who might object. Use public discussions to make the plan visible before a formal review. AI can help write a document, but you still need to understand the details and answer questions about them.

Use Deadlines to Reach a Decision

A deadline can stop a team from discussing options without choosing one. Agree on the smallest useful change, deliver it, and improve it over time. The hosts also discuss resistance that comes from people who want control or credit. No method guarantees agreement.

Browsers After Arc

The hosts return to Arc and their search for a replacement. Dillon reports display problems in Firefox. Matt describes a text display problem in a WebKit browser that worked correctly in Chrome. This leads to a discussion of browser testing and company rules for internal tools.

Scott uses Dia with its AI features off. He misses some Arc features, including the way it handled bookmarks. Matt discusses Yab and Helium. The hosts compare browser features, work requirements, and the cost of changing familiar tools.

Standup / Life Updates

The personal updates focus on browser use. Scott wants a reliable replacement before Arc stops working for him. He also tries Zen and Yab on his personal computer. Dillon calls the browser discussion a fitting subject for the show. Matt asks listeners which browser they use.