The common failure of "pre-read" meetings is that attendees don't do the reading. Atlassian, like Amazon, solves this by starting decision-making meetings with a dedicated, silent period where everyone reads the context document together. This guarantees shared context and makes the subsequent discussion far more effective.

Complex documents like evaluation strategies are rarely read beforehand. To ensure alignment, adopt the Amazon practice of dedicating the first 15-20 minutes of a kickoff meeting to silent, focused reading. This forces engagement and leads to a more informed and productive discussion.

Address cultural issues by applying product management principles. Use surveys to gather data and identify pain points, then empower the team to propose solutions. Test these ideas like product features and iterate based on what works, making culture-building a shared, active process.

To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.

An effective meeting has three parts: 1) "Navy SEAL" for strict accountability against goals, 2) "Suspense Thriller" for debating a strategic topic with an unknown outcome (using a pre-read memo), and 3) "Pep Rally" for authentically celebrating wins to boost morale.

After the Qwikster failure, Netflix created a framework where executives rate key decisions from -10 to 10 in a shared document. The decision-maker (the "captain") isn't bound by the votes but becomes fully informed of all perspectives, avoiding both groupthink and decision-by-committee.

Instead of using meetings for context-setting, Loom’s team sends a required 'pre-watch' video walkthrough of the strategy. This forces stakeholders to arrive with full context, allowing the live meeting to be shorter and entirely focused on critique, asking clarifying questions, and making decisions.

Elf's CEO hosts product review meetings every two weeks that are open to all employees, regardless of role. He actively monitors the meeting's chat for feedback, believing the best ideas can come from anyone, like an inventory planner with a contrarian view on a new product.

Instead of a top-down agenda, Brad Jacobs has his leadership team collaboratively create it for key meetings. Attendees submit and rank questions based on pre-read materials. Only the highest-rated topics make the final agenda. This bottom-up approach ensures the meeting focuses on what the team collectively deems most critical.