When an issue solved during IDS requires a three-week operational sprint that exceeds a seven-day To-Do, but our next quarterly planning session is two months away, how do we govern that work without breaking the EOS framework?

Question

Tyler Smith · Accepted Answer

During IDS, teams frequently solve an issue by recognizing that the company needs an initiative requiring three or four weeks of intense cross-functional work. This creates a structural dilemma: the initiative is too complex to finish as a standard seven-day To-Do, but the next Quarterly Planning Session is months away, making it impossible to wait for a new Rock.

Attempting to turn a multi-week project into a weekly To-Do fails because leaders roll it over for four consecutive weeks, breaking To-Do completion discipline. Conversely, waiting for the quarter stalls critical operational momentum.

The solution is to break the multi-week project into sequential, bite-sized seven-day To-Dos. Do not write a To-Do that says build and implement new inventory workflow. Instead, identify the exact operational deliverable required over the next seven days to advance the project.

For week one, the To-Do is: Draft the five-step inventory workflow document and send it to the team by Thursday. The following week, the subsequent To-Do becomes: Gather leadership feedback and finalize software integration requirements.

Every seven days, the project advances through a concrete, verifiable milestone that can be marked done or not done. The overarching issue remains on the long-term Issues List on the V/TO, or is tracked in your project management system, but accountability inside the Level 10 Meeting stays strictly anchored to the seven-day pulse.

If the initiative is so massive that it requires more than twenty hours of weekly focus from a key leader, the Integrator must evaluate whether an existing Rock needs to be dropped or adjusted to create operational capacity. Never allow phantom multi-week projects to drift without weekly milestone tracking.