A practical framework that extends the classic Rocks-Pebbles-Sand analogy to help leaders prioritize work by impact, ROI, and throughput, ensuring strategic projects get the time they need while keeping tactical work flowing.
The core insight is that work-ordering isn't just about size; it's about allocating time to the most impactful strategic initiatives (Rocks) while still delivering tactical value (Pebbles) and high-throughput fixes (Sand). By treating each class of work as a distinct bucket with its own goals-impact for Rocks, ROI for Pebbles, and throughput for Sand-the framework prevents easy or urgent tasks from crowding out long-term value.
Rocks require deliberate, executive-level decisions and should span three to twelve months. They must deliver dramatic, measurable impact, not incremental improvement. The article warns that over-optimizing for ROI or speed dilutes strategic intent, and it cites Hofstadter's Law to stress that both time and impact estimates are habitually optimistic.
Pebbles occupy the middle ground, typically one to four sprints, and are evaluated on ROI. They serve as the bridge between strategic Rocks and the quick-fire Sand items, allowing teams to stay productive while pursuing high-impact goals. The piece stresses that Pebbles need a structured decision process but should remain adaptable.
Sand represents the smallest work-tasks that fit within a sprint or less. Their value is realized only in aggregate, so the goal is to maximize throughput. The article cautions against excessive administrative overhead for Sand, urging teams to self-schedule these items to preserve morale and avoid wasted process time. By aligning each work type with its appropriate mindset and decision-making speed, leaders can sustain momentum without sacrificing strategic progress.
Check out the full stdlib collection for more frameworks, templates, and guides to accelerate your technical leadership journey.