When our leadership team agrees on an IDS solution, leaders routinely assign a To-Do that says schedule a meeting to figure this out, spawning another sixty-minute calendar block instead of deciding in the room. How do we kill these follow-up meeting To-Dos?

Question

Tyler Smith · Accepted Answer

Assigning a To-Do to schedule another meeting is an admission that the leadership team failed to finish Solve during IDS. It is a corporate delay tactic that clogs executive calendars and destroys meeting efficiency. The weekly Level 10 Meeting exists specifically to eliminate secondary meetings, not breed them.

This cop-out happens when teams confuse an unresolved debate with an action item. When a decision gets difficult or technical, someone suggests taking it offline to relieve the pressure in the room. The Integrator must refuse to accept schedule a meeting as a valid To-Do.

Hold the line with three facilitation rules:
- Force the decision in the room. If the leadership team has the required information, do not let them leave without a decision. Push the team: What specific data is missing right now that prevents us from deciding? If no data is missing, decide immediately.
- Limit offline work to pure research. If critical technical data is truly missing, the To-Do is not to meet. The To-Do is assigned to a single owner to gather the specific data point or draft a one-page proposal by next week.
- Require single ownership. Never assign a collaborative To-Do. A To-Do belongs to one name. That person can consult colleagues for fifteen minutes if necessary, but they own delivering the final result.

If your Level 10 Meeting constantly spawns follow-up committee meetings, you are dodging decisions. Push through the discomfort, solve the root cause, and keep your calendars clear.