Get AI summaries of any video or article — Sign up free
My 3-7 Time Blocking Method (Boss Edition) to GET EVERYTHING DONE thumbnail

My 3-7 Time Blocking Method (Boss Edition) to GET EVERYTHING DONE

Dr. Tiffany Shelton·
5 min read

Based on Dr. Tiffany Shelton's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use the Boss Matrix to sort weekly tasks by both “coded” energy and business impact, not by urgency alone.

Briefing

Entrepreneurs burn out when their calendars become a dumping ground for tasks that feel busy but don’t advance the business. The core fix here is a “boss” time-blocking system that forces weekly planning to prioritize what’s both high-impact and truly “coded” to the founder—then organizes execution through batching and planned sprints so energy lasts through launches.

The method starts with a weekly rhythm built on BBB: book weekly non-negotiables (meetings and routines), complete a weekly review, decide what must happen next week, batch tasks on designated batch days, and then time-block each task using a structured daily layout. That daily structure splits the day into three blocks—morning, work, and evening—each containing specific routines (early morning, AM work, lunch, PM work, wind-down, and an evening routine). The “boss edition” upgrade comes after the weekly review: before adding items to the to-do list, pause and sort tasks using a new framework called the Boss Matrix.

Instead of the Eisenhower matrix’s “urgent vs. important,” the Boss Matrix asks two questions: how much a task is “coded” (energizing, aligned with the founder’s strengths, often the face of the business) and how much it impacts the business positively. Four quadrants follow. Low-impact, low-coded work becomes the “swamp”—admin perfectionism and micro-decisions that create motion without growth (examples include fiddling with fonts, responding to every comment, or manually fixing tech issues). High-coded but low-impact work becomes the “candy bowl”—things that feel satisfying but don’t feed the bottom line (DMs, graphics, overediting slides). The prescription is not to hate these tasks, but to limit them (the creator uses a timed weekly window—about 30 minutes—for YouTube comment responses).

High-impact, low-coded work lands in the “engine room,” where the goal is to automate, systemize, or delegate. Editing videos, managing email flows, and maintaining a website fit here: they matter, but they don’t have to be done personally. High-coded, high-impact work becomes the “CEO flow zone,” where the founder should spend most time—filming content, casting vision, creating teaching frameworks, or designing the next product. To scale without doing everything, the system borrows the “1080/10 rule” from Dan Martell: start with about 10% of the work for vision and branding, outsource or delegate the bulk (around 80%), then return for the final 10% of finishing touches.

Execution then shifts from scattered effort to strategic batching. Batch days are organized into four categories: admin/operational maintenance to prevent chaos; onstage marketing tasks (content creation, PR, ads) to avoid invisibility; business and personal development for planning and deep work to prevent stagnation; and deep work for visionary, mission-aligned creative breakthroughs to prevent burnout and misalignment. Finally, the system adds “cope ahead” planning using a long-distance runner mindset: most of the quarter is pacing (about 80% of time), while planned “sprint zones” (about 20%) concentrate launches or marketing pushes. Support in life—meals, extra help, cleaning, boundaries, and recovery days—gets scheduled alongside the business sprint so the push doesn’t become unplanned collapse.

Cornell Notes

The “boss edition” time-blocking method prioritizes founder energy and business impact using the Boss Matrix. Tasks are sorted by how “coded” they are (energizing, aligned with the founder’s strengths) and how much they positively impact the business. Low-impact work is cut (the “swamp”), enjoyable but low-value work is limited (the “candy bowl”), and high-impact but low-coded work is automated, systemized, or delegated (the “engine room”). High-coded, high-impact work becomes the CEO flow zone, supported by the 1080/10 rule (10% vision, 80% delegated heavy lifting, 10% finishing touches). Weekly execution then uses batch days for admin, marketing/onstage work, planning/development, and visionary deep work, plus quarterly “sprints” planned in advance with recovery and life support.

How does the Boss Matrix replace the usual “urgent vs. important” sorting for entrepreneurs?

It uses two axes: (1) how much a task is “coded” (energizing, aligned with the founder’s strengths, often the face of the business) and (2) how much it impacts the business positively. The result is four quadrants: the “swamp” (low-coded/low-impact) for work that creates motion without growth; the “candy bowl” (high-coded/low-impact) for satisfying tasks that don’t feed the bottom line; the “engine room” (low-coded/high-impact) for work that should be automated, systemized, or delegated; and the “CEO flow zone” (high-coded/high-impact) for tasks only the founder (or partners) should do.

What should an entrepreneur do with “swamp” tasks and “candy bowl” tasks?

Swamp tasks should be eliminated because they drain energy without moving the business forward—examples given include fiddling with fonts, responding to every comment, or manually fixing tech issues. Candy bowl tasks should be limited rather than removed: they feel good and may be in the founder’s zone (DMs, designing graphics, overediting slides), but they’re low nutritional value for business growth. The creator uses a timer-based approach—about 30 minutes per week for YouTube comments—so the habit doesn’t expand uncontrollably.

Why does the “engine room” quadrant push automation, systemizing, or delegation?

Because tasks there are high-impact but not necessarily “coded” to the founder. The method argues that “important” doesn’t automatically mean “must be done by you.” Examples include editing videos, managing email flows, and maintaining a website. The practical goal is to design the engine (systems and oversight) rather than get caught in the gears (manual execution).

How does the 1080/10 rule help founders stay in flow while scaling?

The rule splits work into three parts: the founder handles the first ~10% for vision and branding, delegates or supports the middle ~80% (the heavy lifting), and returns for the final ~10% of finishing touches. The example given is designing a planner: the founder owned the vision, content, design, and techniques; a graphic designer and supplier handled most of producing the physical product; then the founder made final edits and revisions.

What are the four batch-day categories, and what problem does each one prevent?

Batch days are organized to address different failure modes: (1) admin/operational maintenance to stop chaos and clutter (automated/systemized maintenance, later delegated); (2) onstage tasks/marketing to prevent invisibility and inconsistency (content creation, content marketing, ad creation, PR); (3) business development and personal development to prevent stagnation and short-term thinking (strategic planning, systems building, skills building, CEO decision-making); and (4) deep work for visionary, mission-aligned creative work to prevent burnout and misalignment, where breakthroughs and legacy-level ideas are executed.

How does “cope ahead” change time planning across a quarter?

It uses a long-distance runner model: most time is spent in a pacing zone (about 80%), handling regular routines like content posting, weekly newsletters, fulfillment, and customer service. Then planned sprint zones (about 20%) concentrate effort for launches or marketing pushes—going live more, emailing more, and increasing social activity—while life support gets scheduled too (freezer meals, takeout planning, extra help like a copywriter or VA, extra cleaning, boundaries for late work). Recovery days are also carved out after sprints to protect energy and avoid burnout.

Review Questions

  1. Which tasks belong in the “swamp,” and what specific behaviors are cited as examples?
  2. If a task is high-impact but low-coded, what three actions does the method recommend—and why?
  3. How do batch days and quarterly sprint planning work together to reduce burnout?

Key Points

  1. 1

    Use the Boss Matrix to sort weekly tasks by both “coded” energy and business impact, not by urgency alone.

  2. 2

    Eliminate low-coded, low-impact work (“swamp”) and cap high-coded, low-impact work (“candy bowl”) with timed windows.

  3. 3

    Treat high-impact, low-coded work (“engine room”) as automation/systemization/delegation territory, even when it’s important.

  4. 4

    Reserve most time for high-coded, high-impact founder work (“CEO flow zone”), supported by the 1080/10 rule for scaling.

  5. 5

    Batch days should be designed around operational stability, visibility, long-term planning, and visionary deep work.

  6. 6

    Plan quarterly sprints in advance using a long-distance runner mindset, and schedule life support plus recovery days alongside business pushes.

Highlights

The Boss Matrix replaces “urgent vs. important” with two questions: how “coded” a task is and how much it impacts the business positively.
Swamp work is framed as admin perfectionism and micro-decisions that create busyness without growth—examples include font fiddling and manually fixing tech issues.
The 1080/10 rule structures founder involvement: ~10% vision/branding, ~80% delegated heavy lifting, ~10% finishing touches.
Batch days are mapped to four business risks: chaos, invisibility, stagnation, and burnout/misalignment.
Quarterly planning uses “cope ahead”: about 80% pacing for routines and about 20% planned sprint effort with recovery and added life support.

Topics