tyler-smith.com · Questions & Answers

We use modern communication channels and automation, but our team complains that maintaining the weekly Level 10 Meeting pulse feels redundant with our asynchronous updates. Why shouldn't we move to an async format?

Asynchronous communication is fantastic for status updates, notifications, and simple task management. It is terrible for resolving complex, multi-departmental friction. When teams attempt to run an asynchronous Level 10 Meeting, healthy debate disappears and issues get swept under the rug.

The real power of the weekly Level 10 Meeting pulse is not the reporting. The Scorecard, Rock review, and customer headlines take less than fifteen minutes combined. The heart of the meeting is the sixty minutes dedicated to IDS.

Complex business problems are inherently messy. They involve competing departmental priorities, interpersonal friction, and trade-offs that cannot be effectively negotiated through Slack threads, shared spreadsheets, or video memos. Asynchronous debate drags on for days, breeds defensiveness, and frequently ends in passive agreement rather than true resolution.

A live, ninety-minute meeting pulse forces your leadership team into real-time, face-to-face conflict resolution. It compels leaders to look each other in the eye, challenge assumptions, and commit to clear solutions in a single sitting.

Use your AI tools and automations to populate your Scorecard and compile your dashboard data before the meeting starts so no time is wasted reporting. But keep the ninety-minute live pulse intact. Speed of execution depends entirely on the speed at which your team identifies and solves hard problems together.

Category: Level 10 Meetings

← All questions