Free MagnÜron course
Focus and Productivity is a free, self-paced MagnÜron course on practical, evidence-based focus for small business owners and busy professionals: choosing what matters, planning the week and the day, time blocking, deep work, email and phones, habits, and a weekly review you can keep. It has 6 modules and 28 short lessons with built-in tools, a focus timer, worksheets, quizzes and a printable planner. It’s free: enter your email once to unlock every lesson and get the Focus and Productivity Planner, and your progress is saved in your browser. The energy and sleep material is general information only, not medical advice.
Free course · 6 modules · 28 lessons · 6 quizzes
Start Here: Welcome to Focus and Productivity
This course gives you a practical way to focus in a real small business: fewer priorities, a week and a day you planned on purpose, protected blocks for deep work, and a weekly review you can keep. Read the lessons in order for the full system, or jump to the topic you need; each one stands on its own.
Claims about attention and interruptions are drawn from published research and are summarized in plain language. We do not invent statistics. The energy and sleep material later in the course is general information only. It is not medical advice, and it is not a substitute for a qualified health professional.
Who this course is for
- Small business owners whose days fill with messages, meetings and leftover admin, and who still need time for the work that actually moves the business.
- Busy professionals who are good at the craft and tired of ending the week with a long list and no clear progress on what mattered.
- Anyone who has tried a productivity app and wants a simpler system: a priority, a calendar, a capture list and a weekly review.
What you will learn
- Module 1: Why Focus Is Hard, and What Matters. How to Use This Course, Why Focus Is Hard, Choose What Matters, The Eisenhower Matrix, as a Time Audit, Too Many Yeses
- Module 2: Plan the Week and the Day. A Weekly Plan That Survives Contact, Daily Planning Without Overstuffing, Time Blocking, Deep Work Blocks, Batch Admin and Similar Work
- Module 3: Protect Your Attention. A Simple Capture System, Email, Chat, and Phone, A Distraction Audit, Interruptions Have a Cost, Protect the Calendar
- Module 4: Energy, Habits, and Getting Started. Energy, Sleep, and Breaks, Habits and Routines, Procrastination, Without the Shame, A Focus Timer, Using AI and Tools Without More Busywork
- Module 5: Review, Burnout, and Recovery. A Weekly Review, Avoiding Burnout, When the Week Blows Up, Focus When You Lead Other People
- Module 6: A System You Can Keep. Write Your Own Focus Rules, A 30-Day Focus Experiment, A 90-Day Plan, Focus and Productivity Planner Checklist
How each lesson works
- A direct answer at the top, so you get the main point in seconds.
- A clear explanation and a worked example with a small-business day you can adapt. Research claims are sourced.
- Built-in tools in key lessons, including a priority and time-audit sorter, a focus-block planner, an interruption-cost calculator, a weekly review tracker and a focus timer. Type your own numbers; everything stays in your browser.
- Copy-paste worksheets and checklists with a copy button. Replace the [brackets] with your details.
- Do this now: one action step you can finish today.
- Key takeaways and links to in-depth MagnÜron articles.
Each module ends with a three-question quiz. Mark lessons complete as you go; your progress bar and checkmarks are saved in this browser only, so nothing is sent anywhere.
Frequently asked questions
Is the Focus and Productivity course free?
Yes, it is free to use on MagnÜron, with no payment. Enter your email once to unlock every lesson and receive the printable planner. Your progress is saved in your own browser.
Who is this course for?
It is for small business owners and busy professionals who are tired of a packed calendar and a scattered day. You do not need a corporate productivity stack. The tools are sized for a shop, a studio, or a solo practice that still has real interruptions.
Is the energy and sleep lesson medical advice?
No. It is general information about how energy, sleep and breaks affect attention. It is not a diagnosis, a treatment plan, or a substitute for a clinician. If sleep, mood, or fatigue is a serious problem, talk to a qualified health professional.
Do the calculators or the timer save or send my numbers?
No. The tools run in your browser and nothing you type into them is sent anywhere. Only your lesson progress and ticks are saved, in your own browser.
How long does the course take to read?
Most lessons take about 5 to 10 minutes, and the whole course can be read in a few sittings. The useful work is choosing one priority, protecting one focus block, and running a weekly review for a few weeks.
Module 1 · Lesson 1 · About 4 min
How to Use This Course
This course is for small business owners and busy professionals who need a practical way to focus in a noisy week. The work is not to collect apps. It is to choose one priority, protect one focus block, and run a short weekly review.
A system sized for a real business, not a monastery
You will still have customers, a phone, and days that blow up. A useful focus system assumes that. It helps you decide what matters, put it on the calendar, protect a few blocks of uninterrupted work, and notice when the week drifted, without pretending you can disappear for four hours every morning. If a tactic only works in a silent cabin, it does not belong at the center of this course.
The energy and sleep material later on is general information only, not medical advice, and not a substitute for a qualified health professional. Research claims about attention and interruptions are summarized from published work and attributed; this course does not invent statistics. If a number cannot be sourced, we do not use it.
How to move through the lessons
There are 28 short lessons in 6 modules. Read them in order for the full system, or jump to the topic you need: a packed inbox, a week with no priorities, or a habit of putting off the hard work. Each lesson has a worked example, a copy-paste worksheet, and one action. The examples follow Alex at Maple Ridge Reliable Clean and Jordan’s bookkeeping firm, two small businesses you may already know from other MagnÜron courses, now trying to protect time for the work that actually grows the firm.
The test for this week is simple: name one priority that would make the rest of the week easier, put a focus block on the calendar, and schedule a 20-minute weekly review. Tools, including the timer, stay in your browser. Nothing you type into a calculator is sent anywhere. If you also lead a first team, the earlier course on time management and, once you have a team rhythm, the habits in MagnÜron’s management and process courses remain useful neighbors. This course is about your own attention, which is still the bottleneck even when you have help.
Worked example
Example. Alex’s weeks disappear into texts, add-on quotes, and leftover cleaning when a crew member is out. The first-week plan is not a new app. It is one written priority (a first-visit standard that would save callbacks), a 90-minute Tuesday morning block, and a Sunday-evening review. Jordan’s weeks disappear into email and recoding. The first-week plan is one priority (finish the coding guide), a 75-minute Thursday morning block with the phone in another room, and a Friday 20-minute review before the weekend.
Copy-paste templates
FIRST-WEEK FOCUS PLAN My work, in one sentence: [ ] The one priority that, if I moved it this week, would make other work easier: [ ] A focus block I will put on the calendar (day, start, length): [ ] The 20-minute weekly review I will schedule (day and time): [ ] A tactic I will not start this week (a new app, a total inbox-zero overhaul, a 5 a.m. routine I will not keep): [ ] A health or sleep issue I will not treat with a worksheet (if any, I will talk to a professional): [ ]
Do this now
Write one priority for this week, put one focus block on the calendar, and schedule a 20-minute weekly review.
Key takeaways
- The course is for owners and busy professionals who need a system that survives interruptions, not a silent retreat.
- Energy and sleep material later is general information, not medical advice. Research claims are sourced; we do not invent statistics.
- This week’s test is one priority, one calendar block, and a scheduled weekly review.
Module 1 · Lesson 2 · About 4 min
Why Focus Is Hard
Focus is hard because unfinished work and interruptions leave a residue, and because switching tasks has a cost even when both tasks are short. The useful response is not to become a machine. It is to switch less often, and to finish or park a task on purpose before you start the next one.
Attention residue, and the cost of switching
Sophie Leroy, in a 2009 paper in Organizational Behavior and Human Decision Processes, described ‘attention residue’: when you switch to a new task before the previous one is finished, part of your attention stays with the old task, and performance on the new one suffers. The practical lesson is ordinary. If you leave a messy quote half-done to answer a ‘quick’ message, you are not only gone for two minutes. You come back less sharp, and the quote takes longer than it would have if you had finished or written a clear next step first.
Interruptions have a similar shape. Gloria Mark, who has studied attention at work for many years, has reported from workplace studies that it often takes about 23 minutes to get fully back to a task after an interruption, far longer than the interruption itself. Treat that figure as a reason to batch checks and to finish a thought before you look at the phone, not as a stopwatch you must copy, and not as a claim that every business can be interruption-free. A small firm will still have real fires. The goal is fewer self-inflicted ones.
What this is not a license to do
It is not a license to ignore customers or your team. It is a license to stop treating every ping as a fire, and to give a hard task a beginning, a middle, and an end. Write a next action before you switch, even if the switch is necessary. Close the loop later in a batch, not in twelve fragments. Thinking, Fast and Slow is a useful companion if you want a wider picture of why demanding work needs quiet: slow, careful thinking is tiring, and it is the first thing a noisy day crowds out. Deep Work, Cal Newport’s book, gives a name to the other side: uninterrupted time on something cognitively demanding. Module 2 will put that on the calendar. This lesson is only the diagnosis. You cannot out-app a day that switches every few minutes.
Worked example
Example. Alex starts a custom move-out quote, sees a text about a mop, answers it, then checks a review, then cannot remember where the quote’s hours stood. The mop could have waited 20 minutes. Alex’s new rule is: write the next line of the quote, then look. Jordan starts a messy reconciliation, accepts every chat, and restarts the same bank line three times. Jordan’s rule is a 45-minute closed-door block, with a note on the door of the digital chat: ‘back at 10:30.’ Neither pretends messages will vanish. Both stop volunteering a switch in the first five minutes of hard work.
Copy-paste templates
SWITCHING DIAGNOSIS A recent hour that felt scattered (what I was trying to finish): [ ] How many times I switched, and why (a real fire / a habit / a ping): [ ] A task I left unfinished before switching, without writing a next step: [ ] The next-step sentence I will write before I switch next time: [ ] A check (email, chat, phone) I will batch instead of taking live this week: [ ] I will not: treat every interruption as proof I cannot plan, or invent a statistic to scare myself.
Do this now
For one hard task today, write a next-step sentence before you switch, and delay one habitual check until a planned batch.
Key takeaways
- Attention residue (Sophie Leroy, 2009) means a leftover task still occupies you after you switch, and the next task suffers.
- Gloria Mark has reported that returning to a task after an interruption often takes about 23 minutes; use that as a reason to batch, not as a law.
- Write a next step before you switch, and do not invent statistics or pretend a small business can be interruption-free.
Read more on MagnÜron
Module 1 · Lesson 3 · About 4 min
Choose What Matters
A packed list is not a plan. Focus starts when you name the one or two pieces of work that would make the rest of the week easier or unnecessary, and you are willing to let other good work wait.
The one-thing question, used honestly
Gary Keller and Jay Papasan, in The One Thing, popularized a useful question: what is the one thing you can do such that, by doing it, everything else will be easier or unnecessary? You do not need to adopt their whole program to use the question once a week. Ask it about this week, not about your life in the abstract. ‘Rebuild the website’ may be a real project. ‘Write the first-visit checklist that would cut callbacks’ may be the one thing that makes this week’s jobs easier. If you cannot name it in a sentence, you do not have a priority yet. You have a pile.
Most overloaded weeks are not short on effort. They are short on a decision. Every yes is a no to something else, which is ordinary opportunity cost. A second ‘priority’ is allowed. A fifth is usually a refusal to choose. Write the one thing, then at most one backup if the first is blocked, and put both where you will see them on Monday morning. Better decisions here are mostly about saying no to work that is merely urgent or merely interesting.
What ‘matters’ is allowed to be unglamorous
The one thing is often not a new offer or a clever campaign. It is a standard, a close, a difficult conversation, a hire, or a piece of work you have been postponing because it is quiet and hard. That is still the work. If everything on the list is a fire, you are living in other people’s plans. The next lesson will sort the list with a matrix. This lesson is only the choice: if you could finish only one thing this week, what would it be, and how will you know it is done?
Worked example
Example. Alex’s list has marketing posts, a new blog, a van clean-out, and the first-visit standard. The one-thing question picks the standard: if first visits were consistent, callbacks and mid-week texts would drop. The van can wait. Jordan’s list has a new service page, a conference, and the coding guide. The guide is the one thing, because it would stop the nightly recoding that eats the hours meant for clients. Both write a done test: the page exists and has been used on a real job this week.
Copy-paste templates
ONE-THING CARD This week, the one thing I can do such that, by doing it, other work gets easier or unnecessary: [ ] What 'done' looks like, in one sentence: [ ] A second item I may do only if the first is finished or truly blocked: [ ] Good work I am letting wait, on purpose: [ ] A 'priority' that is actually someone else's urgency: [ ] I will put the one thing where I will see it on Monday: [ ]
Do this now
Write this week’s one thing, a one-sentence done test, and at least one good item you are letting wait on purpose.
Key takeaways
- Use the one-thing question for this week, not as a life slogan: what would make other work easier or unnecessary?
- Every yes has an opportunity cost; a long list of priorities is usually a refusal to choose.
- The right work is often unglamorous, and it needs a clear ‘done’ test.
Module 1 · Lesson 4 · About 4 min
The Eisenhower Matrix, as a Time Audit
The Eisenhower matrix sorts work into four boxes: urgent and important, important but not urgent, urgent but not important, and neither. Used as a time audit, it shows where a real week went, not where you hoped it would go.
Four boxes, filled with hours, not slogans
Important work moves a goal, a customer promise, a standard, or your health as a working person. Urgent work has a clock on it, whether or not it matters. The useful box is usually important and not urgent: the standard, the system, the deep work, the follow-up that prevents next month’s fire. It is also the box that gets skipped when a message arrives. MagnÜron’s guide to Eisenhower matrix examples walks through the same four boxes with small-business cases. This lesson asks you to log hours, not only to label tasks.
Look at last week, roughly. You do not need a perfect timesheet. You need a true-enough picture. If almost all the hours sat in urgent-and-important (fires) and urgent-but-not-important (other people’s priorities), the week was reactive. If almost none sat in important-but-not-urgent, you already know why the big work never moves. The ‘neither’ box is a candidate to delete, postpone, or move off the workday: busywork, extra tabs, a meeting with no decision.
Priority and time-audit sorter
Default numbers are examples of a reactive week. Log a typical week in hours, even roughly. The important, not-urgent block is the one to protect first.
What to do with the picture
Protect a block next week for the important, not-urgent work (Lesson 8). Decline, shorten, or hand off as much of the urgent-but-not-important pile as you can (Lesson 15). Delete or park the ‘neither’ hours. Keep enough room for real fires; a small business will have them. The matrix is a decision tool, not a moral score. Time management starts here: you cannot manage a week you have not looked at honestly.
Worked example
Example. With the starting numbers above, 8 of 20 hours are fires, only 3 are important and not urgent, 7 are urgent but not important, and 2 are neither. Alex finds that mid-week texts about jobs already on the board are filling the third box, and that the first-visit standard barely appears. Jordan finds that same-day ‘quick questions’ from clients who could have been batched are the third box, and that the coding guide lived in the second box at 3 hours, which is why it never finished. Both will protect a block for the second box next week, before they add anything new.
Copy-paste templates
WEEKLY TIME AUDIT Week of: [ ] Hours, even roughly: Urgent and important (fires, hard deadlines that also matter): [ ] Important, not urgent (standards, deep work, prevention, skill): [ ] Urgent, not important (other people's priorities, many pings): [ ] Neither (busywork, low-value scrolling, meetings with no job): [ ] What I will protect next week (a block for box two): [ ] What I will decline, shorten, or hand off from box three: [ ] What I will delete or move off the workday from box four: [ ] A real fire I will still leave room for: [ ]
Do this now
Log last week’s hours into the four boxes, even roughly, and name one important, not-urgent block you will protect next week.
Key takeaways
- The Eisenhower matrix is most useful as a time audit: where the hours actually went.
- Important, not-urgent work is usually where better results come from, and it is the easiest to skip.
- Decline or shorten urgent-but-not-important work, and delete or park the ‘neither’ hours, while still leaving room for real fires.
Read more on MagnÜron
Module 1 · Lesson 5 · About 4 min
Too Many Yeses
A week fails at the moment you say yes to a fifth priority, a meeting with no purpose, or a favor that can only come out of the focus block you already promised yourself. Choosing what matters includes a way to decline work without a speech.
Default to a slower yes
You do not have to answer a non-urgent request in the same conversation. ‘Let me check the week and get back to you by tomorrow’ is a complete sentence. Then look at the calendar, the one thing from Lesson 3, and the opportunity cost, and decide. If the request is a real customer fire, handle it. If it is a nice idea, a standing meeting, or a ‘quick’ project that is actually a week of work, it needs a no, a later date, or a smaller version.
A useful no is short and kind: thank them, decline the thing (not the person), and, if you can, offer a smaller alternative or a later window. You do not owe a three-paragraph apology. You also do not need to invent a fake conflict. ‘I can’t take that on this month if I’m going to finish X’ is honest. If you lead people, declining well is part of protecting the team’s attention too; a yes from you often becomes a yes they have to execute. Rework is blunt about junk meetings and half-done projects; you can take that warning without taking every other idea in the book.
Write a personal rule, not only a mood
Decide in advance what you will rarely say yes to: meetings without an agenda, same-day work that is not a genuine emergency, projects that have no owner, evening ‘quick looks’ at email. Write two or three rules on the same card as your one thing. When a request arrives, you are not inventing a personality; you are applying a rule. Lesson 14 will put this on the calendar. This lesson is the decision habit. If saying no feels impossible in every case, the problem may be pricing, staffing, or a promise you should renegotiate, not a need for one more planner. Be honest about that, and use the earlier MagnÜron work on decisions rather than heroic hours.
Worked example
Example. A vendor asks Alex to ‘jump on a quick call’ during the Tuesday focus block. Alex says, ‘I can talk Thursday at 3:00, or we can do this by email.’ The call was not a fire. A regular asks Jordan to rebuild a five-year archive ‘sometime this week.’ Jordan says the coding guide comes first, offers a scoped start date next month, and does not apologize for having a queue. Both write a rule: no new same-day projects unless a paying job is actually stalled.
Copy-paste templates
YES/NO RULES
This week's one thing, so I can test a request against it:
[ ]
Requests I will rarely take:
1. [ ]
2. [ ]
3. [ ]
A slower-yes sentence I can use ('Let me check the week and get back to you by…'):
[ ]
A short, kind no, with an optional smaller alternative:
[ ]
A yes I already regret this month, and what I will do about it (renegotiate, shrink, or finish then stop):
[ ]
A real fire that should still get a fast yes:
[ ]Do this now
Write two or three personal rules for what you will rarely take, plus a slower-yes sentence and a short no you can actually say this week.
Key takeaways
- A slower yes, checked against the week’s one thing, prevents a calendar full of other people’s plans.
- A useful no is short, kind, and specific; it can include a smaller alternative or a later date.
- Write the rules in advance, and be honest if the real problem is staffing, pricing, or a promise you should renegotiate.
Read more on MagnÜron
Module 1 · Quick check
Module 1 Quiz: Why Focus Is Hard, and What Matters
Three quick questions to lock in what you learned in Module 1. Pick an answer to get instant feedback; answer all three correctly to complete the quiz.
1. Attention residue, as described by Sophie Leroy, means:
2. The Eisenhower box to protect first is usually:
3. A useful way to handle a non-urgent request is:
Module 2 · Lesson 6 · About 4 min
A Weekly Plan That Survives Contact
A weekly plan is a short look, before the week starts, at the one thing, the calendar, and the few blocks you will protect. It is not a 40-item wish list. If the plan cannot survive one real fire, it is too tight.
Thirty minutes, before Monday if you can
Pick a standing slot, often Friday afternoon or Sunday evening, and walk a short list: what actually got done last week, what slipped and why, the one thing for next week, the appointments already on the calendar, and the two or three blocks you will add for important, not-urgent work. Write the plan on one page. If last week slipped because of a pattern (the same meeting, the same inbox hour, the same leftover job), change the pattern, do not just copy the list forward.
Leave white space. A week in a small business that is planned to the brim will overflow by Tuesday. A useful rule is to plan less than you think you can do, then pull from a short ‘if there is time’ list. SMART goals can help you date the one thing without turning the page into a corporate offsite. A very short look at operating numbers belongs here only if you already track them; do not build a dashboard as a way of avoiding the plan.
The calendar is the plan
A list that is not on the calendar is a hope. Once you have the one thing and the blocks, put them on the same calendar you use for customers. Treat those blocks as seriously as a paying job. If a real fire lands on a block, reschedule the block the same day, the way you would reschedule a customer, rather than deleting it and promising ‘later.’ Lesson 21 will turn this slot into a fuller weekly review. This lesson is only the forward plan: one page, some space, and a calendar that already shows the work that matters.
Worked example
Example. Alex uses Sunday at 6:30 for 25 minutes. Last week the first-visit standard slipped because Thursday’s block was eaten by a late job and never moved. This week Alex puts the standard on Tuesday at 9:00, leaves Thursday afternoon looser, and writes two ‘if there is time’ items (the van, a supplier call) under the one thing. Jordan uses Friday at 4:00, looks at the week just ending, puts the coding guide on Thursday morning, and refuses to stack a new service page on the same plan.
Copy-paste templates
WEEKLY PLAN Week of: [ ] Planning slot: [ ] Last week: what got done, what slipped, and why: [ ] The one thing for this week, and what 'done' looks like: [ ] Appointments already on the calendar that I must honor: [ ] Focus blocks I will add (day, time, length, and the work): 1. [ ] 2. [ ] 3. [ ] If-there-is-time list (no more than three): [ ] White space I am leaving on purpose: [ ] If a fire eats a block, I will reschedule it the same day: Y / N
Do this now
Hold a 20- to 30-minute weekly planning slot, write a one-page plan with the one thing and at least one focus block, and put that block on the calendar.
Key takeaways
- A weekly plan is one page: last week, the one thing, existing appointments, and a few protected blocks.
- Leave white space, and keep an ‘if there is time’ list short.
- The calendar is the plan; if a fire eats a block, reschedule the block the same day.
Read more on MagnÜron
Module 2 · Lesson 7 · About 4 min
Daily Planning Without Overstuffing
A daily plan is a short list, made the evening before or first thing, that names the one or two things that would make the day a success even if the rest went sideways. It is not a copy of the entire backlog.
Three items, plus the calendar you already have
Write: the one MITs (most important tasks) for the day, at most two or three; the appointments and jobs already booked; and the first focus block, with a start time. If the list does not fit on an index card, it is too long. Anything else goes on a parking list you will not look at until the important work has had a turn, or until a planned admin batch (Lesson 10). Starting the day by rewriting a 20-item list is a way of feeling organized without choosing.
Make the plan when you still have a little judgment, often the night before, in five minutes. In the morning, start the first MIT if you can, before the inbox. If you cannot (a job is already booked at 8:00), put the MIT in the first open block, not ‘sometime after the messages.’ Simple productivity habits fail when the morning is already a reaction. A daily plan is how you refuse that, even on a busy site or in a busy inbox week.
When the day blows up
It will, sometimes. The plan is still useful: you can see what got dropped, and you can choose what to recover. If a day produces none of the MITs and you also skipped the weekly block, write that down for the weekly review rather than inventing a more colorful plan tomorrow. Two blown days in a row is a signal to shrink the plan, not to add a 5 a.m. routine you will not keep. Perfectionism shows up here as a daily list that can only be completed by a different person in a quieter life. Plan for the week you actually have.
Worked example
Example. Alex writes, the night before: (1) finish the first-visit page in the 9:00 block, (2) the two booked jobs, (3) return the supplier call in the 2:00 admin batch. A late job lands at 11:00. Alex still has the page almost done, and moves the last 20 minutes to 4:00 instead of dumping the whole MIT. Jordan’s daily card is: coding-guide section before email, two client closes, a 3:00 admin batch. When a client calls at 9:10, Jordan takes it, then returns to the guide rather than wandering the inbox.
Copy-paste templates
DAILY CARD Date: [ ] MITs (at most three), with a start time for the first: 1. [ ] 2. [ ] 3. [ ] Already booked (jobs, appointments, school run, hard stops): [ ] First focus block: [ ] Admin or message batch (time): [ ] Parking list (I will not start these until the first MIT has had a turn): [ ] If the day blows up, the one MIT I will still try to recover: [ ] I will not: rewrite a 20-item backlog as a way of starting the day.
Do this now
Write tomorrow’s daily card tonight, with at most three important items and a start time for the first, and stop the list when it no longer fits on a card.
Key takeaways
- A daily plan is at most two or three important items, plus the calendar you already have, not the whole backlog.
- Put a start time on the first important item, and start it before a recreational inbox pass when you can.
- If the day blows up, shrink tomorrow’s plan rather than inventing a heroic routine.
Module 2 · Lesson 8 · About 3 min
Time Blocking
Time blocking means giving a piece of work a start and an end on the calendar, the same way you would give a customer an appointment. A block is a decision. A list is only a wish until it has a time.
Name the work, the start, and the length
Choose a realistic length. Ninety minutes is a common deep-work length if you can get it; 45 or 60 minutes is still a block. Shorter than 25 minutes is usually a reminder, not a block. Put the work in the title of the event, not ‘busy.’ Leave a buffer after, especially if you will have to talk to people again. Then show up and do only that work until the end, or until a genuine fire. Checking email ‘for a second’ inside the block is how the block dies.
Focus-block planner
Default numbers are an example of a day that still fits. If the plan is over the day, cut meetings or admin before you cut the deep-work block.
One good block beats a fantasy calendar
You do not need to block every hour. You need enough structure that the important work has a home, and that meetings and admin have a box too, so they do not leak everywhere. If you cannot find 90 minutes, find 45, and defend it. If your work is jobs on site, put the block where the day actually has a gap (early, after the last job, or a mid-week office morning), not where a blog post says peak genius lives. Time management is this habit, repeated. The next lesson is about what you do inside the best of those blocks.
Worked example
Example. With the starting numbers above, one 90-minute block, 2 hours of meetings, and 2 hours of admin leave 2.5 hours in an 8-hour workday for other work and buffers. Alex books Tuesday 9:00 to 10:30 for the standard, after school drop-off and before jobs, and leaves a 15-minute buffer. Jordan’s Thursday is heavier on calls; the planner shows that two 90-minute blocks will not fit, so Jordan keeps one 75-minute block and a 45-minute afternoon finish, and cuts a standing call that has no agenda.
Copy-paste templates
TIME-BLOCK CARD Day I am planning: [ ] Workday hours: [ ] Deep-work block(s): start, end, and the work 1. [ ] 2. [ ] Meetings already booked (hours): [ ] Admin and message batch (start, end): [ ] A buffer I will leave after a hard block: [ ] If the planner shows the day is overfull, what I will cut first: [ ] The event title I will use on the calendar (the actual work, not 'busy'): [ ] I will not: check email 'for a second' inside the block, or delete the block without rescheduling it.
Do this now
Put at least one named focus block on tomorrow’s or this week’s calendar, with a start, an end, and the actual work in the event title.
Key takeaways
- A time block is a start, an end, and a named piece of work, treated like a customer appointment.
- You do not need to block the whole day; you need the important work, and admin, to have a home.
- If the day is overfull, cut meetings or admin before you cut the deep-work block.
Read more on MagnÜron
Module 2 · Lesson 9 · About 4 min
Deep Work Blocks
Deep work, in Cal Newport’s sense, is unbroken time on something cognitively demanding. You will not get a whole day of it in a small business. You can get a block, if you shut the door on purpose and give the hard work that window.
Uninterrupted, demanding, and scheduled
Newport’s Deep Work, summarized on MagnÜron here, contrasts that kind of focus with shallow work: the email, clicks, and logistics that feel busy and rarely move a skill or a product on their own. You still need shallow work. You should not let it fill every hour. A deep-work block is for the standard, the analysis, the writing, the design, the financial close, the plan, or the craft that requires you to hold a problem in your head. If you can do the task while chatting, it is probably not the work this lesson is about.
Before the block: pick the task, close the extra tabs, put the phone out of reach, and write the first next step so you do not spend ten minutes deciding how to start. During the block: no inbox, no ‘quick’ admin, no new yeses. After the block: write where you stopped, and take a short break before you open the channels. A 90-minute block that actually happens twice a week will beat a heroic plan of four hours a day that never starts. Focused hours, accumulated, are how skill is built; the same is true of a messy first-visit standard or a coding guide.
Rituals that make the block real
Same place, same start cue, a visible ‘not now’ for other people if you can (a closed door, a status, a sign). If you work in a van or on a job, your deep-work block may have to live in an office morning or an early hour at the kitchen table. That is still a block. If someone must be able to reach you for a safety or customer emergency, give them one channel and a rule, and keep every other channel shut. You are not being precious. You are buying a condition the work requires. Lesson 16 will talk about energy; do not place your only block at a time of day when you already know you cannot think.
Worked example
Example. Alex’s Tuesday 9:00 block is the first-visit page only. The phone is in a drawer, the crew has a number for a real emergency, and Alex writes the next heading before any other tab opens. At 10:30 Alex writes ‘examples for the kitchen photo’ as the next step, then looks at messages. Jordan’s Thursday block is a hard reconciliation and a section of the guide. Slack is set to away until 10:15. The first five minutes are a written next step, not a warm-up tour of the inbox.
Copy-paste templates
DEEP-WORK RITUAL The work this block is for (one cognitively demanding task): [ ] When and where, and a start cue: [ ] What I will close or silence (tabs, phone, chat), and the one emergency channel if I need one: [ ] The first next step, written before I start: [ ] Where I will write the next step when the block ends: [ ] A time of day I will not use for this work, because I already know I cannot think then: [ ] Hours a week I can realistically protect, not a fantasy: [ ]
Do this now
Schedule one deep-work block this week, write the first next step before you start, and shut every channel except one genuine emergency route.
Key takeaways
- Deep work is unbroken time on something demanding; shallow work is necessary but should not fill every hour.
- A short ritual (next step, closed channels, a real emergency route) makes the block more likely to happen.
- A few real blocks a week beat a daily four-hour plan you will not keep.
Read more on MagnÜron
Module 2 · Lesson 10 · About 4 min
Batch Admin and Similar Work
Admin, messages, invoicing, and little logistics expand to fill any gap you leave for them. Batching means giving similar work one or two windows, so it stops leaking into the hours you reserved for harder thinking.
One kind of work, one window
Group what can be grouped: email and chat, invoicing and receipts, supply orders, social posts, callbacks that are not fires, filing, and the ‘quick’ tasks that each take four minutes and somehow take an hour. Put them in a named batch, 30 to 60 minutes, once or twice a day, at a time when your deeper energy is already spent if you can. During a deep-work block, those tasks wait. During the batch, you do only that kind of work, with a list, and you stop when the window ends. Leftovers go to the next batch, not into the evening by default.
Email batching is a well-known version of this, popularized in many productivity books, including parts of The 4-Hour Workweek. You do not need to adopt a four-hour workweek, or to check email only once a week, to get the benefit of two planned checks a day instead of a day lived inside the inbox. Lesson 12 will go deeper on channels. This lesson is the broader habit: similar work, same window. Lean thinking makes a cousin of the same point: stop mixing kinds of work when a little grouping would cut the setup cost each time you switch.
Batching is not a new pile of busywork
If a batch regularly overflows, the problem may be volume, a missing standard, or work you should not be doing, not a need for a longer batch. Cut the list. Automate or template only after you have deleted what should not exist, the same instinct as a short checklist. Do not create a 90-minute ‘admin lifestyle’ that is really delayed decisions. A batch with a next-action rule (do it, defer it to a dated list, or delete it) will shrink. A batch that is only ‘look at everything again’ will not.
Worked example
Example. Alex used to order supplies, text customers, and edit quotes in the gaps between jobs, and never had a clean hour. The new pattern is a 2:00 to 2:45 batch for messages and orders, and a Friday 30-minute invoice batch. Quotes stay in the morning block. Jordan sets 11:30 and 4:00 as email and bill-pay windows, and stops opening the inbox as a break from the guide. Both end the batch on time and park leftovers, rather than sliding into the evening.
Copy-paste templates
BATCH CARD Similar work I will group (email, invoices, orders, callbacks, posts): [ ] Windows this week (days, start, end): 1. [ ] 2. [ ] A rule for each item (do, defer with a date, or delete): [ ] What I will not do in the batch (deep work, new projects, open-ended scrolling): [ ] A batch that is overflowing, and what I will cut or template: [ ] I will not: use a batch as a reason to live in admin all afternoon, or to reopen email inside a deep-work block.
Do this now
Put one or two admin batches on this week’s calendar, move similar little tasks into them, and keep them out of your deep-work block.
Key takeaways
- Batch similar work into a named window so it stops leaking into the hours reserved for harder thinking.
- Two planned message checks can be enough for many days; you do not need an extreme inbox schedule.
- If a batch overflows, cut or template the work; do not automatically make the batch longer.
Module 2 · Quick check
Module 2 Quiz: Plan the Week and the Day
Three quick questions to lock in what you learned in Module 2. Pick an answer to get instant feedback; answer all three correctly to complete the quiz.
1. A weekly plan is most useful when it is:
2. Time blocking means:
3. Deep work, as used in this course, is:
Module 3 · Lesson 11 · About 4 min
A Simple Capture System
Your head is a bad office. A capture system is one trusted place to park ideas, tasks, and promises so they stop interrupting the work you are in the middle of. It only works if you empty it on a schedule.
One inbox for stuff that is not the work in front of you
When a thought arrives mid-block (buy filters, a blog idea, a promise you just made, a bill you spotted), write it down in one place and return to the work. The place can be a notebook, a notes app, or a simple list. It should not be five apps, a pile of texts to yourself, and a pad in the van that never gets reviewed. David Allen’s Getting Things Done made a well-known case for capturing everything out of your head so you can think about one thing at a time. You do not need the whole system to borrow the capture habit: one inbox, a frequent empty, and a next action, not a vague noun.
Empty the inbox in your weekly review, and in a short daily glance if the volume is high. For each item: do it now if it is truly a two-minute finish, schedule it, turn it into a next action on a dated list, file it as reference, or delete it. A capture list you never process becomes a second anxiety pile, which is worse than no list. A ‘second brain’ tool can help some people, especially for reference and notes; start with a boring list if you are not already in a tool you like. The tool is not the system.
Capture promises, not only ideas
The items that hurt you later are often promises: ‘I’ll send that today,’ ‘I’ll look at the invoice,’ ‘I’ll call them back.’ Write those down in the same inbox the moment you say them, and give them a date in the next processing pass. If you work with a team, a shared list for work you owe each other can sit beside your private inbox; do not mix personal errands and staff follow-ups in a way you will be embarrassed to open. The point of capture is to free the current block, then to keep the promise later, not to collect 400 notes you admire.
Worked example
Example. Mid-quote, Alex thinks of a supply order and a birthday text. Both go on a single notes list, and the quote continues. In the 2:00 batch, the order is placed and the text is sent. Jordan used to have ideas in email drafts, a phone pad, and a reminders app. Jordan picks one list, processes it in the Friday review, and turns ‘website’ into ‘draft the services page outline on Thursday.’ The old pads are retired once they are emptied once.
Copy-paste templates
CAPTURE SETUP The one inbox I will use (and where it lives): [ ] Inboxes I will stop using, after I empty them once: [ ] When I will process the inbox (daily glance and/or weekly review): [ ] My rule for each item (do, schedule, next action with a date, file, or delete): [ ] A promise I made this week that is still only in my head: [ ] The next action, and the date: [ ] I will not: start a complex second-brain system this week, or collect notes I never process.
Do this now
Pick one capture inbox, move any stray lists into it, write down one promise that is still only in your head, and set a time to process the inbox.
Key takeaways
- One trusted inbox lets you park a thought and return to the work in front of you.
- A capture list has to be emptied on a schedule, or it becomes a second anxiety pile.
- Write down promises as well as ideas, and turn vague nouns into dated next actions.
Module 3 · Lesson 12 · About 4 min
Email, Chat, and Phone
Channels are useful servants and expensive masters. If email, Slack, texts, or the phone can interrupt you at any moment, they will. Choose a few windows, a short rule for what is a fire, and a way to reach you that does not require every channel to be open.
Plan the checks, and shrink the badges
Turn off non-essential notifications on the phone and on the desktop, especially during a focus block. Check email and chat in the batches you already scheduled, not whenever a badge appears. A common, humane pattern is two or three checks on a workday, with a clearer promise to customers (‘we reply the same business day’) than an implied instant reply. If your work truly requires a live phone, keep that one line available and silence the rest. You can still be responsive without being interruptible by everything at once.
Process a message with a decision: reply, archive, or turn it into a dated next action. Do not use the inbox as a to-do list; that is a capture problem from the last lesson. Templates help with the tenth similar reply. If a thread needs a conversation, pick up the phone or book a short call rather than writing a novel. Tools should make this easier, not add a fourth messenger. If you already have too many channels, pick a primary one and tell people, once, in writing.
A fire is rarer than it feels
Write what counts as a fire: a customer on site, a safety issue, a same-day job that is actually stalled, a payroll or tax deadline today. Everything else can usually wait for the next window. If you lead a team, tell them the emergency route and the expected reply time, so they are not guessing. If you work alone, tell your frequent customers the same, in a short line at the bottom of an email or on the booking page. An always-on channel trains everyone, including you, to treat every thought as urgent. Lesson 14 will put a cost on that habit. This lesson is the rule: windows, one emergency path, and a same-day standard that you can actually keep.
Worked example
Example. Alex silences supplier group texts during jobs and the Tuesday block, keeps the crew number on, and checks messages at 11:30 and 2:00. The booking page says ‘we return calls the same business day.’ Jordan closes Slack except at 11:30 and 4:00, leaves the phone on for two clients in mid-close, and stops using the inbox as a task list by moving anything that takes more than a short reply onto the capture list with a date.
Copy-paste templates
CHANNEL RULES Channels I use for work: [ ] The primary channel I want people to use, and where I have told them: [ ] Check windows this week: [ ] Notifications I will turn off, especially during a focus block: [ ] What counts as a fire, and the one path for it: [ ] The reply-time promise I can actually keep (for example, same business day): [ ] A thread I will move to a call or a dated task, instead of leaving it in the inbox: [ ]
Do this now
Turn off non-essential notifications, write your check windows and what counts as a fire, and process one inbox with reply, archive, or a dated next action, not as a to-do list.
Key takeaways
- Check email, chat and texts in planned windows; keep at most one live emergency path.
- Do not use the inbox as a task list, and do not keep four equal channels.
- A same-business-day promise you can keep beats an implied instant reply you cannot.
Module 3 · Lesson 13 · About 4 min
A Distraction Audit
Most lost focus is not a mystery. It is a handful of repeat offenders: a phone on the desk, an open chat, a news tab, a person who always ‘has a second,’ or a habit of starting the hard work and then standing up. An audit makes those visible, so you can change the environment, not only your mood.
Watch one day, without judgment
For one typical workday, keep a simple tally: what pulled you off the work, roughly how long, and whether it was a real need, a habit, or someone else’s urgency. You will not catch every second, and you do not need to. You need the top three sources. At the end of the day, circle the ones you caused (the extra tab, the ‘just check’ habit) and the ones you can redesign (phone in another room, chat closed, a standing ‘office hour’ for non-urgent questions). Leave genuine customer and safety work in their own category; those are the job, not a moral failure.
Then change the environment first. Willpower is a weak plan against a badge on a screen that sits in your hand. Put the phone out of reach during a block. Close the extra tab. Log out of the social account on the work machine. If a person interrupts you for non-urgent things, offer a time they can have your full attention, which is better for both of you. A little more presence helps, and so does a boring physical change. If you want a cousin of this idea in habit form, Atomic Habits is clear that environment often beats intention.
Do not audit yourself into shame
The point is a redesign, not a verdict that you are weak. A noisy shop, a child at home, or a busy counter is a constraint to plan around, not a character test. Build blocks where the constraint is lighter, and shorten them if you must. If the audit shows almost no self-inflicted distraction and a genuine overload, the next step is to cut work or get help, not to buy a stricter timer. Be honest about that before you layer on more rules.
Worked example
Example. Alex’s tally for Wednesday: 11 self-checks of the phone, three supplier texts that could have waited, two real customer calls, and a news tab after each job. The redesign is the phone in the glove box during jobs and during the Tuesday block, and a 2:00 supplier window. Jordan’s tally is mostly Slack and a ‘research’ tab that becomes shopping. The redesign is Slack closed until the batch, and the shopping sites blocked on the work browser until Friday afternoon.
Copy-paste templates
DISTRACTION AUDIT Date: [ ] What pulled me off the work (tally, even roughly): 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] Top three sources: [ ] Which I caused, and the environment change I will make: [ ] Which are real job needs, that I will plan around rather than shame myself for: [ ] A constraint I cannot remove (shop floor, family, counter), and a lighter time of day I can use for a block: [ ] If this is overload, not distraction, the work I will cut or hand off: [ ]
Do this now
Tally distractions for one typical day, circle the top three, and change the environment for at least one of them before you add a new rule about willpower.
Key takeaways
- A one-day tally usually reveals a few repeat sources of distraction, not a mysterious failure of character.
- Change the environment first: phone, tabs, chat, and a time for other people’s non-urgent questions.
- If the audit shows overload rather than distraction, cut or hand off work; do not only add stricter rules.
Read more on MagnÜron
Module 3 · Lesson 14 · About 4 min
Interruptions Have a Cost
An interruption costs more than its clock time, because you have to find your place in the work again. You do not need a perfect figure. A rough cost, in hours and in money, is often enough to take batching and blocked time seriously.
Count, then multiply, then decide
Use a typical day from your audit: how many interruptions, and how many minutes each costs including the restart, not only the conversation. Gloria Mark’s reported recovery time (often about 23 minutes to get fully back, as noted in Lesson 2) is a reminder that the restart can dwarf the interruption. Your own restart may be shorter or longer; be honest, and do not invent a dramatic number to punish yourself. Multiply across the week, and, if you want, across a simple hourly rate, so the habit has a visible cost. The calculator below is a planning estimate, not a scientific measurement of your life, and not a reason to be rude to human beings who need you.
Interruption cost calculator
Default numbers are examples only. Use your audit, not a scary headline statistic. The point is to notice the cost of an always-on channel, and to batch what you can.
Spend attention where it pays
Some interruptions are the business: a customer at the door, a crew safety question, a payment that is actually failing. Those should not be ‘optimized away.’ The expensive pattern is the self-inflicted or socially inherited always-on habit: every chat, every badge, every ‘got a second?’ that could have been a daily window. Use the number to justify a door, a status, or a batch, not to justify never talking to your team. If you also have meetings that run long, the same instinct as a short, purposeful meeting from ordinary operations hygiene applies. Protect the block, and be available on purpose, at a time you chose.
Worked example
Example. With the starting numbers above, 6 interruptions of 10 minutes are 60 minutes a day, 5 hours a week, about $200 at $40 an hour, or about $10,400 a year. Alex’s audit was close to that once restarts were included. Cutting habit-checks and batching supplier texts in half is not a $10,000 guarantee; it is a serious reason to keep the Tuesday block and the 2:00 window. Jordan prices time a bit higher and still uses the default as a planning floor, then tells clients the same-business-day reply rule in the email footer.
Copy-paste templates
INTERRUPTION COST CARD Typical day, from my audit: Interruptions: [ ] Minutes each, including restart: [ ] Working days: [ ] Hourly rate I will use (planning only): $[ ] Weekly hours / weekly cost, from the calculator: [ ] Interruptions that are the actual job (I will not try to delete these): [ ] Interruptions I can batch or delay: [ ] The environment change or window this number justifies: [ ] I will not: treat the yearly figure as a guaranteed savings, or use it as a reason to be unavailable for real fires.
Do this now
Run the calculator with numbers from your audit, and use the result to justify one batched window or one protected block, not to invent a savings claim.
Key takeaways
- An interruption costs the conversation plus the restart; a rough weekly total is often enough to change a habit.
- Use your own audit and a planning rate; do not invent a dramatic statistic.
- Keep real-job interruptions. Batch the self-inflicted always-on ones.
Read more on MagnÜron
Module 3 · Lesson 15 · About 3 min
Protect the Calendar
A calendar that anyone can fill will fill. Protecting it means no-meeting blocks, a default length shorter than an hour, an agenda or no meeting, and office hours for non-urgent questions, including your own ‘quick’ yeses from Lesson 5.
Hold hours the way you would hold a customer job
Put focus blocks and at least one no-meeting window on a shared calendar if other people book you, and treat a request that lands on them as a reschedule, not as an automatic yes. Offer two alternative times instead. Default new meetings to 25 minutes, with a written purpose, and end on time. If a standing meeting has had no decision for two cycles, change it or drop it. You have already practiced a slower yes; the calendar is where that yes becomes visible to other people.
Office hours, even 30 minutes a day or a few mid-week slots, give your team or your frequent collaborators a time they can have you without punching a hole in a block. That is kinder than a closed door with no alternative. If you work alone, office hours can be the message batch, published as ‘I return calls at…’ Remote or mixed teams especially need the written version of these rules, because they cannot see that you are in a block.
Guard the edges of the day
A meeting that starts at the first hour you think clearly, or that runs into the last hour you were going to do deep work, is more expensive than its length. Place shallow meetings in the shallower parts of your day when you can. Decline recordings or extra attendees if you are only there ‘just in case.’ Recurring holds you set up (a weekly review, a deep-work morning) should be as hard to delete as a client’s appointment. If you keep giving those hours away, the system in this course will stay theoretical. Write the protection rule on the same card as your one thing, and look at next week’s calendar before Monday starts.
Worked example
Example. Alex marks Tuesday 9:00 to 10:30 as busy on the booking calendar, offers Wednesday afternoon for vendor calls, and shortens the Friday wrap to 15 minutes with an agenda. Jordan sets Thursday morning as a no-meeting block, publishes 11:30 as a questions window for the bookkeeper, and declines a standing Thursday call that had no decisions, with a short note and an offer to meet monthly instead.
Copy-paste templates
CALENDAR PROTECTION No-meeting or focus holds already on the calendar: [ ] A default meeting length I will offer (for example, 25 minutes): [ ] Office hours or a questions window, and who knows about it: [ ] A standing meeting I will change or drop if it has no decision: [ ] A slower-yes plus two alternative times, in a sentence I can paste: [ ] An edge of the day I will stop giving away (first clear hour, last deep-work hour): [ ] I will look at next week's calendar before Monday: Y / N
Do this now
Put a no-meeting or focus hold on the shared calendar, set a default 25-minute meeting length where you can, and offer a questions window instead of an always-open door.
Key takeaways
- Protected blocks should be as real as a customer appointment, with alternative times offered when something must move.
- Short, purposeful meetings and published office hours beat an always-interruptible day.
- Guard the edges of the day, and look at next week’s calendar before Monday.
Module 3 · Quick check
Module 3 Quiz: Protect Your Attention
Three quick questions to lock in what you learned in Module 3. Pick an answer to get instant feedback; answer all three correctly to complete the quiz.
1. A capture system works when:
2. Email and chat are least damaging when you:
3. The interruption-cost number is meant to:
Module 4 · Lesson 16 · About 4 min
Energy, Sleep, and Breaks
Attention is not only a calendar problem. It is also an energy problem. This lesson is general information about sleep, pacing, and breaks. It is not medical advice, a diagnosis, or a treatment plan. If sleep, mood, or fatigue is a serious problem, talk to a qualified health professional.
Put the hard work where you already have energy
Most people know, if they are honest, whether they think more clearly in the morning, mid-afternoon, or evening. Put deep work in the better window, and put batches, errands, and many meetings in the worse one, when you can. Fighting your own pattern with a 5 a.m. routine you cannot sustain is usually worse than a slightly later, kept block. A short walk, a meal, or a few minutes away from the screen between blocks is ordinary pacing, not a luxury. You do not need a perfect ‘ultradian’ theory; you need to notice when quality drops and to stop pushing the same demanding task for hours without a pause.
Sleep is strongly tied to attention, memory, and mood. That is well established in a large body of research, and it is something you can observe in your own week: after a short night, the same quote or close takes longer and feels harder. This course will not prescribe hours, supplements, or a sleep protocol. It will say: treat chronic sleeplessness or exhaustion as a health issue, not as a productivity puzzle you should solve with a stricter timer. MagnÜron’s notes on health as a leader and self-care in a home business are here as practical companions, not as medical guidance.
Breaks are part of the work
A break is a stop, not a switch to a second screen that leaves the same residue. Step away if you can. A few minutes is enough between two demanding blocks; a real meal helps more than a keyboard lunch every day. If you use a focus timer in Lesson 19, the break is there on purpose. None of this replaces care for anxiety, depression, pain, or a sleep disorder. If those are in the picture, a worksheet is the wrong tool. Get help, and use this course only for the calendar habits that still make sense around that care. Burnout is covered more fully in Lesson 22; the early warning is often energy you cannot recover over a normal weekend.
Worked example
Example. Alex already knows the first job of the day is physical and the office thinking is better at 9:00 than at 8:00 after a late clean. The Tuesday block stays at 9:00, and Alex eats lunch away from the phone. A week of 5-hour nights is treated as a reason to call a clinician, not as a reason to add a 5 a.m. writing habit. Jordan does the hardest analysis late morning, batches email after lunch, and takes a ten-minute walk between the block and the inbox. Neither pretends a timer will fix a sleep problem.
Copy-paste templates
ENERGY MAP This page is general information, not medical advice. My clearer thinking window (and the work I will put there): [ ] A lower-energy window I will use for batches or shallower work: [ ] A break I will actually take between demanding blocks: [ ] Sleep or fatigue I can improve with ordinary habits (a more regular wind-down, less late work): [ ] A sleep, mood, or fatigue issue that belongs with a clinician, not with a stricter timer: [ ] A 5 a.m. or late-night routine I will not start because I already know I will not keep it: [ ]
Do this now
Place this week’s deep-work block in a window when you already think more clearly, plan a real break after it, and do not use a worksheet to replace care for a serious sleep or health issue.
Key takeaways
- Put demanding work in the part of the day when you already have more energy, and use lower-energy hours for batches.
- Sleep is strongly tied to attention; chronic problems belong with a clinician, not with a stricter productivity system.
- This lesson is general information, not medical advice. Breaks should be actual stops, not a second screen.
Module 4 · Lesson 17 · About 4 min
Habits and Routines
A focus system sticks when it is a small routine, attached to a time and a place, not a burst of motivation on Monday. You already have the pieces: a weekly plan, a daily card, a block, a batch. The habit is doing them on ordinary weeks.
Make it small, obvious, and easy to repeat
James Clear’s Atomic Habits, summarized on MagnÜron here, is useful on this point: design the cue, shrink the starting step, and let identity follow the repeats (‘I am a person who plans the week on Friday’). You do not need to adopt every tactic in the book. You do need a cue for each core habit (Friday 4:00, calendar opens; morning, daily card already written; Tuesday 9:00, phone in a drawer). If the starting step is ‘write a perfect weekly plan,’ you will skip it. If it is ‘open last week’s card and write the one thing,’ you will start.
The Seinfeld strategy (don’t break the chain) can help you mark a simple weekly streak: did I run the planning slot, yes or no; did at least one focus block happen, yes or no. Misses happen. The rule is to start again the next day or the next Friday, not to declare the system dead and wait for January. Two kept weeks beat a colorful tracker you abandon.
Routines at the edges of the day
A short start-up (card, calendar, first MIT) and a short shut-down (capture inbox emptied, tomorrow’s card, one look at the calendar) close loops so work does not follow you around the house. Ten minutes is enough. If you work from home, the shut-down is also how you leave the business for the evening. If you work on site, it may happen in the van or at the kitchen table. Keep it boring. A dramatic morning routine that depends on a 5 a.m. workout, a journal, and a cold plunge is not required, and it is often a form of perfectionism dressed up as discipline. Build the smallest routine you will still do on a messy Tuesday.
Worked example
Example. Alex’s cues are Sunday 6:30 (weekly plan, same chair), a nightly five-minute card, and the phone in the glove box when the Tuesday block starts. A week with a late job still gets a shortened Sunday plan, so the chain does not break. Jordan’s cues are Friday 4:00 and a ten-minute shut-down: capture list processed, Thursday block confirmed, laptop closed. Jordan tried a 12-step morning routine and dropped it after four days; the Friday slot survived because it was small.
Copy-paste templates
HABIT CUES Weekly plan: cue (day, time, place) and the smallest starting step: [ ] Daily card: cue and the smallest starting step: [ ] Focus block: cue (including where the phone goes): [ ] A yes/no streak I will mark (weekly plan happened / at least one block happened): [ ] A 12-step routine I will not start, because I will not keep it on a messy Tuesday: [ ] A shut-down I can do in ten minutes (capture, tomorrow's card, calendar): [ ] If I miss a day, I will start again at the next cue, not in January.
Do this now
Write a cue and a smallest starting step for your weekly plan, your daily card, and one focus block, and decide a simple yes/no streak you will actually mark.
Key takeaways
- Attach each core habit to a time and place, and shrink the starting step so you can do it on a messy Tuesday.
- A simple weekly streak helps; after a miss, start at the next cue rather than abandoning the system.
- Short start-up and shut-down routines close loops; an elaborate morning ritual is not required.
Read more on MagnÜron
Module 4 · Lesson 18 · About 4 min
Procrastination, Without the Shame
Procrastination is often a response to a task that feels vague, hard, or judged, not a proof that you are lazy. The useful moves are to shrink the start, decide the first two minutes, and notice when perfectionism is dressed up as ‘not ready yet.’
Start smaller than you think you should
If you are putting off a piece of work, write the first visible step (open the file, write the ugly outline, set out the supplies) and attach a start time. Research on implementation intentions, associated with Peter Gollwitzer and colleagues, finds that a simple if-then plan (‘If it is 9:00 on Tuesday, then I open the standard and write the first heading’) can make it more likely you will start. You do not need an effect size to use the idea: decide the cue and the first move in advance, while your judgment is better than it will be at the moment of avoidance.
Work for a short, timed stretch if the full block feels too heavy (Lesson 19). A messy first draft or a rough checklist is progress. Perfectionism often looks like research, extra formatting, or waiting for a clearer week. Set a ‘good enough for this week’ bar in writing, and stop when you hit it. If the delay is really a decision you are scared to make, name the decision and use a decision process, rather than circling the task for a month.
Look at the feeling, then start anyway
Boredom, fear of a messy job, fear of a client’s reaction, or simple dislike are allowed to be named. Naming them is not the same as waiting for them to disappear. After you start, many tasks shrink. If you still cannot start after a two-minute entry, the task may be too big (break it), in the wrong time of day (move the block), or not actually yours (decline it). Do not add a shame lecture. Shame is a poor manager and a worse timer. A short, kind, started draft will do more than a long diagnosis of your character.
Worked example
Example. Alex has postponed the first-visit page for a month because it should ‘look professional.’ The if-then plan is: if it is Tuesday at 9:00, then I write a messy bullet list of what a first visit always includes, for 25 minutes, and I stop. That list becomes the page. Jordan has postponed a difficult client recap. The first step is to open last month’s file and write the three numbers, not to write the perfect letter. After ten minutes, the letter is easier, and ‘good enough’ is a clear recap by Friday, not a masterpiece.
Copy-paste templates
START CARD
The work I have been putting off:
[ ]
What I am telling myself ('not ready,' 'need to research,' 'next week'):
[ ]
The feeling under that (vague, hard, judged, boring, scary), in one word:
[ ]
If-then plan (If it is [time], then I [first two-minute move]):
[ ]
A 'good enough for this week' bar:
[ ]
If I still cannot start, I will (break it / move the block / decline it):
[ ]
I will not: add a shame lecture, or wait to feel like a different person.Do this now
Pick one postponed task, write an if-then start plan and a ‘good enough’ bar, and do the first two minutes at the time you named.
Key takeaways
- An if-then plan and a two-minute start beat a vague intention to ‘get to it later.’
- Perfectionism often looks like research or waiting for a better week; set a good-enough bar in writing.
- Name the feeling, then start anyway, without a shame lecture.
Read more on MagnÜron
Module 4 · Lesson 19 · About 4 min
A Focus Timer
A timer turns a block into something with a beginning and an end, which is often enough to start. A common pattern is 25 minutes of focus and a short break, known as the Pomodoro Technique, developed by Francesco Cirillo. Use a length you can actually keep.
Start, work, stop, step away
Choose a focus length (25 minutes is a default, not a law; 45 or 50 is fine if you are already in stride). Start the timer, work on one task, and when it ends, take a short break away from the work if you can. After a few focus blocks, take a longer pause. The timer is a boundary, not a score. If a genuine fire arrives, pause or reset, handle the fire, and start once. If you finish early, you can stop, or start the next small piece. You are not required to fill the minutes with busywork.
Focus timer
25:00
The timer runs in this browser tab; keeping the tab open works best. A common pattern is 25 minutes of focus and a 5-minute break (Pomodoro Technique, Francesco Cirillo). This is a timer, not a medical device, and nothing is sent anywhere.
Use it on the work you have been avoiding
The timer is especially useful at the start of a deep-work block, or on a task from Lesson 18 that you keep postponing. Combine it with a written next step and a closed phone. Do not use it to ‘crush’ twelve cycles after a short night, and do not treat a broken streak as a failure of character. Two honest blocks, with breaks, will do more than a performance of eight. If you prefer to work 50 minutes because you already have momentum, that is still a timer used well. The method is a servant. Deep work can live inside one longer block or a few timed cycles; pick the shape that gets you to start.
Worked example
Example. Alex uses a 25-minute cycle to start the first-visit page, then a five-minute walk around the van, then a second cycle to add examples. Two cycles are enough for Tuesday. Jordan prefers a 50-minute focus and a 10-minute break for reconciliation work, and uses 25 minutes only for the client letter that was being postponed. Both keep the tab open, and both pause if a real customer call comes in, then start once rather than abandoning the morning.
Copy-paste templates
TIMER PLAN The task I will use the timer on today: [ ] Focus length I will actually keep (25, 45, 50, or another): [ ] Break length: [ ] How many cycles I will attempt, as a modest maximum: [ ] The next step I will write before I press Start: [ ] Where the phone will be: [ ] If a fire arrives, I will pause, handle it, and start once, not abandon the morning. I will not: stack a huge number of cycles after a short night, or treat a miss as a character verdict.
Do this now
Run one timed focus cycle today on a real task, with a written next step and a short break after, and stop at a modest number of cycles.
Key takeaways
- A timer gives a block a beginning and an end; 25 minutes is a common default, not a requirement.
- The Pomodoro Technique (Francesco Cirillo) is one version: focus, short break, and a longer pause after a few cycles.
- Use the timer to start honest work, not to perform a huge streak or to replace rest after a short night.
Module 4 · Lesson 20 · About 4 min
Using AI and Tools Without More Busywork
A tool should save a step you have already decided is worth doing. If you add an app, an automation, or an AI assistant before you have a priority, a calendar, and a capture list, you will usually get a busier day, not a clearer one.
The work first, then the tool
Write the job (a first draft, a summary of notes, a checklist, a batch of similar emails) and the definition of done, then choose the smallest tool that helps. For some work, that is still a document and a timer. For some, a short prompt in an AI assistant is a genuine speed-up, especially on a first draft you will edit, or on admin you have already standardized. MagnÜron’s guides to starting with AI and asking better questions are practical here, as is the free AI for Small Business course if you want a fuller walkthrough. The rule in this course is narrower: do not let the tool become the project.
Watch for fake work: retuning a dashboard, comparing five apps, or generating ten drafts you never use. If a tool needs a weekly maintenance ritual, that ritual has to earn its time against the one thing. AI for bookkeeping and admin can be a good fit when the process is already clear; it is a poor fit when the process is a mess and you hope the software will decide for you. The same is true of project tools, new inboxes, and ‘second brain’ setups. Start boring. Upgrade when volume clearly breaks the boring version.
A five-minute test
Before you adopt something new, write: what step it replaces, how you will know it worked in 14 days, and what you will shut off if it does not. If you cannot name the step, you are shopping. Keep customer data and private information out of tools you do not trust; safety and judgment still apply. And do not automate a message or a decision you are not willing to stand behind. A faster bad email is still a bad email. Tools stay in their place when you already have a block, a batch, and a review, and you are using the tool inside those, not instead of them.
Worked example
Example. Alex is tempted by a new all-in-one app. The five-minute test fails: it does not replace a named step, and the first-visit page is still unfinished. Alex uses a document and the timer instead, and later uses a short AI prompt only to turn the messy bullet list into a cleaner first draft, which Alex edits. Jordan tries an AI summary of a long client thread, checks it against the file, and keeps it, because it replaced a 20-minute reread. Jordan does not migrate bookkeeping tools in the same week as the coding guide.
Copy-paste templates
TOOL TEST The tool or AI habit I am considering: [ ] The specific step it would replace: [ ] How I will know it worked in 14 days: [ ] What I will shut off if it does not: [ ] A fake-work pattern I will not start (app shopping, dashboard tinkering, ten unused drafts): [ ] A data or judgment line I will not cross: [ ] I will not: let a new tool become the week's one thing, or automate a message I would not stand behind.
Do this now
If you want a new tool or an AI habit, write the step it replaces and a 14-day test; otherwise, finish this week’s one thing with the tools you already have.
Key takeaways
- Choose a tool after you can name the step it replaces, and give it a short test with a shutoff.
- AI can speed a first draft or a clear admin process; it will not decide a messy process for you.
- Do not let app shopping become the week’s work, and do not automate a message you would not stand behind.
Module 4 · Quick check
Module 4 Quiz: Energy, Habits, and Getting Started
Three quick questions to lock in what you learned in Module 4. Pick an answer to get instant feedback; answer all three correctly to complete the quiz.
1. The energy and sleep lesson in this course is:
2. A timer is most useful when you:
3. A new AI tool or app should be adopted when:
Module 5 · Lesson 21 · About 4 min
A Weekly Review
A weekly review is the habit that keeps the rest of the system honest. Once a week, you compare the plan to what actually happened, name next week’s one thing, and look at the calendar before Monday, not after the week has already filled itself.
A short slot, the same day each week
Thirty to forty-five minutes is enough. Put it on the calendar on Friday afternoon or Sunday evening, and treat it as a real appointment. Open last week’s weekly plan and daily cards, your capture list, and next week’s calendar. The questions are simple: what did I say would matter, and what actually got time? What slipped, and was that a good trade or a default? What is next week’s one thing? Where will the deep-work block and the batch live? What will I decline, shorten, or move? If you skip the calendar look, you will write a beautiful plan that Monday already contradicts.
You do not need a perfect score. You need a written adjustment. If the important, not-urgent work never got a block, that is the first change, not a longer to-do list. If interruptions ate the mornings, the change may be a later block, a closed channel, or a shorter meeting default from Lesson 15. A light look at a few numbers can belong here if they tell you whether the week served the business, but a dashboard is not a substitute for the plan-versus-actual question. The weekly streak from Lesson 17 is a yes-or-no: did the review happen?
Weekly review checklist tracker
Default numbers are an example of a review in progress, not a grade. A finished list still has to show up on next week’s calendar. Nothing you type here is sent anywhere.
Keep the list short enough to finish
A useful review list is about ten items, not thirty. A workable set is: clear the capture inbox, compare last week’s plan to actual, name the one thing, place the deep-work block, place the admin batch, check email and chat rules, look at meetings you can decline or shorten, check energy and recovery in ordinary terms (not as a medical assessment), write three daily MITs for the first days, and put the next review on the calendar. If you run out of time, shrink the list next week rather than skipping the slot. Time management without a review is usually just a busier calendar.
Worked example
Example. With the starting numbers above, 4 of 10 weekly review items are done (40.0%). Alex has cleared the capture list and named next week’s one thing (the first-visit page), but has not yet placed Tuesday’s block or looked at a Thursday meeting that could be an email. The remaining work is the calendar, not a new system. Jordan’s Friday slot is 4:00 to 4:40. Last week’s plan said ‘coding guide,’ and only an hour happened; Jordan keeps the same one thing, protects a Thursday morning block, and declines a standing status call that has no decision. Both mark the review as a yes on the streak, even when the week was messy.
Copy-paste templates
WEEKLY REVIEW Date: [ ] Slot (day, time, minutes): [ ] Last week's one thing: [ ] What actually got protected time: [ ] A good trade I made, or a default I fell into: [ ] Capture inbox cleared: Y / N Next week's one thing: [ ] Deep-work block (day, start, end, where the phone goes): [ ] Admin batch (day, time): [ ] Meetings or requests I will decline, shorten, or move: [ ] Channel rules I will keep (email, chat, phone): [ ] Energy and recovery, in ordinary terms (not a medical assessment): [ ] First daily MITs: [ ] Next review is already on the calendar: Y / N The test: next week's calendar actually shows the priority I named.
Do this now
Put a weekly review on the calendar, run it once with last week’s plan and next week’s calendar open, and place next week’s one thing and at least one focus block before you close the slot.
Key takeaways
- A weekly review compares the plan to what happened, names next week’s one thing, and looks at the calendar before Monday.
- Keep the list short enough to finish; a tidy to-do list is not a review if the calendar does not change.
- Mark a simple yes-or-no streak, and shrink the slot in a busy week rather than skipping it.
Module 5 · Lesson 22 · About 4 min
Avoiding Burnout
A focus system that only adds pressure will not last. Burnout is more than a busy month: it is prolonged overload with too little recovery, often joined by cynicism and a shrinking sense that the work still matters. This lesson is general information, not a diagnosis or medical advice.
Watch for a week you cannot recover from
Busy seasons happen in a small business. A useful early warning is that a normal weekend, or a normal day off, no longer returns you to a workable baseline, and the next week starts already thin. Other ordinary signs people report are a shorter fuse, a duller interest in work that used to matter, and a sense that even a finished job does not count. None of those, by themselves, is a diagnosis. If mood, sleep, anxiety, or exhaustion is serious or persistent, talk to a qualified health professional. A planner is the wrong tool for that job. MagnÜron’s notes on burnout in a small business and on self-care in a home business are practical companions, not clinical guidance.
The course-level response is boring and useful: fewer yeses, a real off switch, a deep-work block that is not stacked to the edges of every day, and a weekly review that is allowed to cut work, not only to rearrange it. If you have been treating rest as a prize you earn after inbox zero, reverse that. Recovery is part of the work of attention, the same way a break in Lesson 16 is part of a block. Sleep problems and a ‘hustle through it’ story should not be solved with a stricter timer. Health as a leader matters here even if you lead only yourself.
Change the load, not only the slogans
A motivational quote will not fix a calendar that has no slack. Decline or postpone a class of work. Shorten a standing meeting. Hand off a batch, or drop a project that was never the one thing. If money is tight, you may not be able to drop billed work, but you can still drop unpaid theater, late-night email, and the extra ‘just in case’ projects. A short walk, a meal away from the screen, or an evening without the work phone is ordinary care, not a personality makeover. If you work at home, a shut-down ritual helps the business leave the house. If you already feel unsafe, hopeless, or unable to cope, get help now, and use this course only for the calendar habits that still make sense around that care.
Worked example
Example. Alex has had three Saturdays in a row of leftover quotes and a shorter fuse on Monday. The change is not a 5 a.m. routine. Alex cuts Thursday evening email, keeps one Sunday job off the calendar for two weeks, and books the already-late physical. The first-visit page stays the one thing, but the second marketing idea is dropped. Jordan notices that even a finished close does not feel like it counts, and that Sunday no longer resets the week. Jordan talks to a clinician about sleep, shortens Friday meetings, and stops treating the weekly review as a chance to add more. Both treat this as a load problem, not as a character problem.
Copy-paste templates
LOAD AND RECOVERY This page is general information, not medical advice, and not a diagnosis. A recent week I did not recover from over a normal day off: [ ] Work I am carrying that is unpaid theater, or not the one thing: [ ] A yes I will decline, shorten, or postpone this week: [ ] A real off switch (evening, day, or window without the work phone): [ ] Ordinary recovery I will actually take (a meal away from the screen, a walk, a shut-down): [ ] A sleep, mood, or exhaustion issue that belongs with a clinician, not with a stricter timer: [ ] If I feel unsafe, hopeless, or unable to cope, I will get help, and I will not use this worksheet as a substitute.
Do this now
Name one yes you will drop or shorten this week, put a real off switch on the calendar, and if recovery or mood is a serious problem, talk to a qualified health professional rather than tightening the system.
Key takeaways
- Burnout is more than a busy month; a week you cannot recover from is an early warning, not a prompt to hustle harder.
- Change the load: fewer yeses, a real off switch, and a review that is allowed to cut work.
- This lesson is general information, not medical advice. Serious sleep, mood, or exhaustion belongs with a clinician.
Module 5 · Lesson 23 · About 4 min
When the Week Blows Up
Some weeks will break the plan: a sick child, a broken van, a client emergency, a job that runs long. The skill is not a perfect calendar. It is a fast triage that protects one priority and one short block, without throwing out the system.
Triage, then a smaller plan
When the week blows up, stop adding new work for a few minutes and write three lists: must happen in the next 24 to 48 hours, can move, and can wait or be declined. The one thing from Monday may still be the one thing, in a shorter form, or it may be deferred in writing until a named day. What you should not do is silently drop it and also keep every meeting, then call the system a failure. A 45-minute block, or a single timed cycle from Lesson 19, is still a block. A two-item daily card is still a plan. A short decision about what can wait will do more than a late-night attempt to catch up on everything.
Tell the people who need to know. A client, a teammate, or a family member can often absorb a moved time; they cannot absorb a silent miss. If you lead other people, Lesson 24 is the longer version of this. If you work alone, a short note and a new date is enough. Then protect a small restart: the next focus block, even if it is tomorrow, and the weekly review, even if this week’s plan was a wreck. The review’s job in a blown week is to record the trade and to reset dates, not to punish you with a longer list.
Do not burn the system down
A common pattern is to abandon time blocking, channel rules, and the capture list the moment a fire starts, and to live in the inbox until exhaustion. That turns one emergency into a second, quieter one. Keep the capture inbox, even if you only park items. Keep the off switch if you can, especially if the fire is already a long day. Time-efficient growth still depends on not letting every week become a special case. If blown weeks are the default, the work is Lesson 5 and Lesson 15 (fewer yeses, a protected calendar), not a tougher pep talk. One messy week is data. A messy month is a load problem.
Worked example
Example. Alex’s Tuesday block is lost to a no-show and a same-day add-on. The triage: the add-on happens, the first-visit draft moves to a 45-minute Wednesday morning block, and a non-urgent quote is postponed with a text. Alex still shuts the phone down at the usual evening hour. Jordan’s Thursday is lost to a software outage. The must-happen list is two client filings; the coding guide waits until Friday’s shortened block. Jordan writes the deferral on the weekly card so the review does not treat it as a vanished intention. Neither throws out the calendar for the rest of the month.
Copy-paste templates
BLOWN-WEEK TRIAGE What broke the plan, in one sentence: [ ] Must happen in the next 24 to 48 hours: [ ] Can move, with a new time or date: [ ] Can wait, or can be declined: [ ] The one thing, in a shorter form, or a named deferral date: [ ] The next short focus block I will still protect: [ ] Who I need to tell, and by when: [ ] The weekly review stays on the calendar: Y / N I will not: silently drop the priority and also keep every meeting, or burn the system down until January.
Do this now
If this week is already a mess, write a three-line triage (must / move / wait), protect one short block or a named deferral, and keep the weekly review on the calendar.
Key takeaways
- A blown week needs a fast triage and a smaller plan, not a silent drop of the priority and a pile of leftover meetings.
- A short block and a written deferral keep the system alive; abandoning the calendar turns one fire into two.
- If blown weeks are the default, the work is fewer yeses and a protected calendar, not a tougher pep talk.
Module 5 · Lesson 24 · About 4 min
Focus When You Lead Other People
If you lead even one person, your calendar and your interruptions become the team’s calendar and interruptions. Protecting your own deep work is not enough; you also have to stop being the main source of other people’s attention residue.
Your habits leak onto the team
A manager who sends late-night messages, drops by every half hour, and calls last-minute meetings teaches the team that deep work is not actually allowed, no matter what the handbook says. If you want people to think in blocks, give them blocks: a question window or office hours, a default meeting length of 25 minutes when a full hour is not needed, and a norm that a Teams or Slack ping is not an emergency unless it is labeled as one. Put your own focus hold on a shared calendar so people can see it, and honor theirs. MagnÜron’s free First-Time Manager course is the fuller walkthrough of one-on-ones, delegation and a weekly rhythm; this lesson is only the focus slice.
Delegation is also an attention tool. Work you keep ‘just to be sure’ is work that will interrupt you later. A clear standard, a named person, and a check at a planned time (not a running commentary) cuts both of your context switches. The same is true of a huddle that has a job versus a standing status meeting that could have been a written update. Remote and hybrid teams need this in writing, because they cannot see you thinking and will otherwise fill the silence with pings.
If you do not lead anyone yet
The same manners apply upward and sideways. You can still ask for a question window, batch your own updates, and decline a meeting that has no decision, with a written alternative. You can still stop training people that you answer in thirty seconds. A small-business owner who ‘does not really manage’ but has a helper, a contractor, or a family member in the operation is already leading, and the calendar still leaks. Keep the system from Lessons 12 and 15, and add one team rule you will actually keep: for example, no pings during a published focus block except a true emergency, and a daily or twice-daily window for everything else.
Worked example
Example. Alex now has a part-time helper. Alex puts the Tuesday 9:00 to 10:30 block on a shared calendar, asks the helper to collect questions for a 10:45 window, and stops texting job notes after 7 p.m. The Monday huddle stays at 15 minutes with one decision. Jordan’s Friday one-on-ones stay, but the mid-week ‘got a minute’ habit is replaced by a written question list and a 3:00 office hour. A contractor who works remotely gets the same window in writing. Both still protect their own deep-work block, and both treat a late-night message as a last resort, not a style.
Copy-paste templates
TEAM FOCUS RULES People I lead, help, or regularly interrupt (including a helper, contractor, or family member in the work): [ ] A focus hold I will put on a shared calendar: [ ] A question window or office hour, instead of a running commentary: [ ] A meeting I will shorten, make written, or drop: [ ] A late-night or always-on habit I will stop modeling: [ ] The one team rule I will actually keep (for example: no pings during a published block except a true emergency): [ ] If I do not lead anyone: the upward or sideways ask I will make (a window, a written update, a declined meeting). [ ]
Do this now
If you lead anyone, publish one focus hold and one question window, and stop one always-on habit you have been modeling. If you do not, make one written ask for a window or a shorter meeting.
Key takeaways
- A leader’s late-night messages and drop-in pings become the team’s operating system, whatever the handbook says.
- Shared focus holds, a question window, and planned checks cut interruptions for everyone.
- The First-Time Manager course covers the wider leadership rhythm; this lesson is the focus slice of that work.
Module 5 · Quick check
Module 5 Quiz: Review, Burnout, and Recovery
Three quick questions to lock in what you learned in Module 5. Pick an answer to get instant feedback; answer all three correctly to complete the quiz.
1. A weekly review is most useful when it includes:
2. If you are not recovering over a normal day off, a useful first move is:
3. When a week blows up, you should:
Module 6 · Lesson 25 · About 4 min
Write Your Own Focus Rules
A system you cannot remember is not a system. Write a short list of personal rules, on one page, in language you will still understand on a messy Tuesday. The rules should name your defaults, not every lesson in the course.
Fewer than ten rules, written in your own words
Useful rules sound like decisions already made: one thing for the week, a daily card with no more than three MITs, a focus block on named days with the phone out of reach, email at named times, a capture inbox that is emptied in the weekly review, a default no to meetings without a purpose, and a real off switch. They should be specific enough to follow (’email at 12:30 and 4:30, not all morning’) and few enough to reread in two minutes. If you need a handbook, you will not use it. Keep the course for reference; keep the rules on a card or at the front of the planner.
Include one rule about load, not only about effort: for example, ‘if I do not recover over a normal day off, I cut work before I add a timer,’ or ‘I will not stack a new tool and a new marketing idea in the same week as a missed block.’ That is how this course stays honest about burnout without turning the card into medical advice. Include one rule about tools: a new app has to replace a named step, or it does not get in. Rework is useful here in spirit: subtract before you add. You can change a rule, in writing, at a weekly review. You should not renegotiate it in the moment a ping arrives.
Post the rules where the work happens
A rule in a notes app you never open is decoration. Put the card on the desk, in the planner, or on the first page of the calendar. If you work from a van or a kitchen table, a paper card in the place you actually sit is enough. Share a shorter version with anyone whose interruptions you have already negotiated (a helper, a partner, a teammate), so the question window is not a surprise. Reread the card at the start of the weekly review. If a rule has been quietly broken for three weeks, either shrink it until you can keep it, or admit it was theater and write a smaller one. The goal is a kept default, not a perfect manifesto. Simple beats elaborate on an ordinary week.
Worked example
Example. Alex’s card has seven rules: one weekly thing, a nightly three-line card, Tuesday 9:00 to 10:30 with the phone in the glove box, email after lunch and at 4:30, a notebook capture inbox, no Thursday evening work phone, and no new app in a week that already missed a block. The card lives on the clipboard with the weekly plan. Jordan’s card has six, including a Friday 4:00 review, Thursday morning deep work, and ‘office hours at 3:00, not all afternoon.’ Jordan drops a rule about a 5 a.m. start that was never kept, and writes a smaller one about a ten-minute shut-down instead.
Copy-paste templates
PERSONAL FOCUS RULES Date: [ ] Rules I will actually keep (aim for fewer than ten): 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] 6. [ ] 7. [ ] 8. [ ] A load rule (cut work before adding a stricter timer, if I am not recovering): [ ] A tools rule (a new app must replace a named step): [ ] Where this card will live, so I will see it: [ ] The shorter version I will share with a helper, partner, or teammate (if any): [ ] I can change a rule in writing at the weekly review. I will not renegotiate it in the moment a ping arrives. A rule I am dropping because I already know I will not keep it: [ ]
Do this now
Write a one-page list of fewer than ten focus rules, including a load rule and a tools rule, and put the card where you will see it at the weekly review.
Key takeaways
- Personal rules should be few, specific, and written in language you will still follow on a messy Tuesday.
- Include a load rule and a tools rule, so the system does not only add effort.
- Post the card where the work happens, and change a rule in writing at the review, not in the moment of a ping.
Module 6 · Lesson 26 · About 4 min
A 30-Day Focus Experiment
Thirty days is long enough to make a weekly review and one focus block feel normal, and short enough that you can commit without redesigning your life. Treat it as a dated experiment with a yes-or-no test, not as a personality overhaul.
Pick a few habits, and date them
A workable 30-day experiment has a start date, a midpoint check around day 15, and a day-30 review. Under those dates, write only a few bets you can see:
- A weekly plan and a weekly review, already on the calendar.
- A daily card with at most three MITs, written the night before or first thing.
- At least one focus block each week, with a named task and a home for the phone.
- Named email or chat windows, not an always-on inbox.
- A capture inbox that is emptied in the review, not a new second brain.
Each bet needs a yes-or-no test: did the review happen four times; did at least four focus blocks happen; did I keep the phone out of the block? Use a simple streak, like the Seinfeld chain, and start again at the next cue after a miss. Do not add a new tool, a new marketing campaign, or a dramatic 5 a.m. routine in the same 30 days, unless that already is the one thing. Atomic Habits is useful here as a reminder to shrink the starting step, not as a homework pile. If focused hours on one skill are the real aim, put those hours inside the focus block, and let the rest of the experiment protect them.
Day 15 and day 30
At day 15, look only at what actually happened. If the block never landed, move it or shorten it; do not add a second block as punishment. If the review is being skipped, shrink it to twenty minutes. At day 30, decide what to keep as a default, what to drop, and what to carry into a 90-day plan in the next lesson. A kept, small system is a successful experiment. A colorful tracker you abandoned at day 11 is information: the cue or the starting step was too big. Write that down, and start a smaller 30 days rather than waiting for January.
Worked example
Example. Alex’s 30 days start next Monday: Sunday weekly plan, a nightly card, Tuesday 9:00 block, email after lunch, and a notebook inbox. The day-15 test is whether two Tuesday blocks actually happened. Alex will not start a new website project in the same window. Jordan’s experiment is a Friday review, a Thursday 90-minute block, office hours at 3:00, and no new bookkeeping tool. At day 15 Jordan has missed one Thursday and shortens the block to 50 minutes rather than cancelling the experiment. Both put the dates on the calendar before they start.
Copy-paste templates
30-DAY FOCUS EXPERIMENT Start date: [ ] Day 15: [ ] Day 30: [ ] Weekly plan and weekly review, already on the calendar: [ ] Daily card (when I will write it, and the cap of three MITs): [ ] Focus block each week (day, time, task type, where the phone goes): [ ] Email or chat windows: [ ] Capture inbox, emptied in the review: [ ] Yes/no tests I will use at day 15 and day 30: [ ] What I will not start in these 30 days (a new tool, a second transformation, a 5 a.m. routine I will not keep): [ ] If I miss a cue, I will start again at the next one, not in January.
Do this now
Date a 30-day experiment with a day-15 check and a day-30 review, write a few yes/no tests, and list what you will not start in that window.
Key takeaways
- Thirty days is for making a review and one focus block normal, with dated yes-or-no tests.
- Do not stack a new tool or a second transformation on a system that is not yet real.
- At day 15, shrink or move what is failing; at day 30, keep the defaults that actually happened.
Read more on MagnÜron
Module 6 · Lesson 27 · About 4 min
A 90-Day Plan
Thirty days starts the habits. Ninety days is long enough to make the weekly review ordinary, to finish one deep piece of work, and to notice whether your load is sustainable. Write the plan as dated aims, not as a hope to ‘be more focused.’
A few named bets, with review dates
A workable plan has a start date, a day-30 check, a day-60 check and a day-90 review. Under those dates, write only a few experiments:
- The weekly plan, weekly review, and at least one standing focus block, already on the calendar.
- One important, not-urgent project that will get those blocks (a page, a process, a product, a learning aim).
- Channel rules you will still keep at day 90 (email windows, a question window if you lead anyone).
- A load rule you will actually use, including a real off switch.
- Anything you will not start in these 90 days: a new platform, a second marketing overhaul, a stack of apps.
Each aim needs a yes-or-no test. If you cannot say what ‘done’ looks like, it is not a plan. SMART goals can help you date the aims without turning this into an offsite. If cash, pricing, customers, or a first team rhythm is still the tighter constraint, you can run this plan alongside earlier MagnÜron courses without mixing all the homework into one pile. The opportunity cost of a 90-day stretch is real: every extra project you add is a project the focus block will not finish.
Day 30, day 60, day 90
At day 30, you should have a kept weekly review and at least a few honest focus blocks. Decide what to keep and what was theater. At day 60, look at the project: is it actually moving in the blocks, or only living on a list? At day 90, reread your personal rules, update the one thing, and only then consider a new tool or a bigger aim. If life gets in the way, shift the dates in writing, the same way you would in a blown week. A slipped plan with a new date is still a plan. A silent stall is not. Do not stack a software migration, a rebrand and a hiring spree on top of a rhythm that is not yet real. Steady, protected time beats a dramatic quarter you cannot recover from. The energy and sleep cautions from earlier lessons still apply: this is a calendar plan, not medical advice.
Worked example
Example. Alex’s 90-day plan starts next Monday: Tuesday blocks, a Sunday review, the first-visit page shipped by day 60, email windows kept, Thursday evening off, and no new website platform. Day 30 is a yes/no on whether the reviews and blocks actually happened. Day 90 is a reread of the rules and a decision on a second page, not a new app. Jordan’s plan is the coding guide in Thursday blocks, Friday reviews, office hours, a real Sunday off, and no tool migration. Day 60 is whether unusual cases are actually easier. Both write what they will not start, and both put the four dates on the calendar.
Copy-paste templates
90-DAY FOCUS PLAN Start date: [ ] Day 30: [ ] Day 60: [ ] Day 90: [ ] Rhythm already on the calendar (weekly plan, review, standing focus block): [ ] The important, not-urgent project those blocks will finish, and what 'done' looks like: [ ] Channel rules I will still keep at day 90: [ ] Load rule and off switch: [ ] What 'done' looks like at day 90, in yes/no terms: [ ] What I will not start in these 90 days (a new platform, a second overhaul, a stack of apps): [ ] How I will shift these dates, in writing, if life gets in the way: [ ] This is a calendar plan. It is not medical advice.
Do this now
Date a 90-day focus plan with day-30, day-60 and day-90 checks, name a few aims with yes/no tests, and write what you will not start in that window.
Key takeaways
- Ninety days is for making the review and one focus block ordinary, and for finishing one important project inside those blocks.
- Each aim needs a yes-or-no test, mid-point reviews, and a list of things you will not start yet.
- Shift dates in writing if you have to. This is a calendar plan, not medical advice.
Read more on MagnÜron
Module 6 · Lesson 28 · About 5 min
Focus and Productivity Planner Checklist
This last lesson is a single checklist for the system you have been building: a chosen priority, a week and a day you planned, protected blocks, quieter channels, a capture list, a weekly review, and a 30-day or 90-day plan. Tick what is genuinely in place. Then keep using the planner after you close the course.
Tick only what exists in real life
A completed checklist does not make you a finished person. It means the habits have a home in your week. Download the Focus and Productivity Planner if you have not already, and keep a paper copy of this list next to your weekly review card. The energy, sleep and burnout items are a reminder to get care when you need it, not a claim that this course is medical advice.
What to do after you close this tab
Fill the first open tick, then the next. Run this week’s review even if the only decision is to leave the plan as it is. If you still need a cleaner offer, a first set of customers, or a first-team rhythm, the MagnÜron courses on pricing, getting customers, thinking tools, and first-time managing remain useful neighbors. You need one named priority, one protected block, and a weekly card you will actually keep.
Choose what matters, protect time for it, and review the week on purpose. Get help when a health issue is real. That is the system. This course is general education, not medical advice.
Worked example
Example. Alex ticks twelve boxes and leaves six open, including the 90-day dates and a cleaner Thursday evening off switch. The first open tick is to put Sunday’s review on the calendar, not to reread a chapter. Jordan ticks the Thursday block, the Friday review, office hours, and the tools rule, and leaves the team-hold item alone until a contractor is actually in the week. Both download the planner and put the paper checklist on the same clipboard as the weekly card. That is a finished course and an unfinished, useful month.
Copy-paste templates
FOCUS AND PRODUCTIVITY PLANNER CHECKLIST Date: [ ] Open ticks I still owe, in order: 1. [ ] 2. [ ] 3. [ ] The first one I will close this week: [ ] Weekly review slot: [ ] 30-day or 90-day review date: [ ] The energy, sleep and burnout items are a reminder to get care when you need it, not a claim that this course is medical advice. The one sentence I want on the front of my weekly card: [ ]
Do this now
Tick only what is genuinely in place, write the first open item you will close this week, and keep a paper copy of the checklist with your weekly review card.
Key takeaways
- The planner checklist is a system check, not a second theory course, and it is not medical advice.
- Tick only what exists in real life, keep a paper copy, and work the first open item next.
- After the course, the work is the weekly review, the protected block, and the 30-day or 90-day dates you already wrote down.
Read more on MagnÜron
Module 6 · Quick check
Module 6 Quiz: A System You Can Keep
Three quick questions to lock in what you learned in Module 6. Pick an answer to get instant feedback; answer all three correctly to complete the quiz.
