A one-hour-a-day business is a way to organise the time you have around a job, family or other commitments. It starts with a defined work block and a result you can see. You might finish an outline, test a form or publish one answer. This guide gives you a schedule you can adapt when your week changes.
Set up a one-hour-a-day business around one active project
Time blocking means reserving a period on your calendar for a specific job. Open the calendar you already use and find three realistic blocks. Give each a title that describes an output. “Test the welcome link on a phone” tells you how to start and how to stop. “Marketing” asks you to make those decisions during the block.
Choose one project for the week. If you’re building an email list, your project might be connecting one form, one download and one email. Keep tool research, logo changes and channel ideas in a separate note. Schedule them when they serve a current task. A small set of materials within reach makes it easier to start when the time arrives.
Make the hour in three parts
- Give five minutes to setup. Open only the files and pages needed for the task. Read your last note and name the finish line.
- Use about 45 minutes on the main work. When you encounter a side issue, write it down unless it prevents the task from continuing.
- Use the last ten minutes to test, save or publish. Write one line that tells you where to resume and what you should see.
You can change the split to fit the task. A writing block may need more setup and a short check. A page test may need several attempts and a little more time to record what happened. Protect the last few minutes either way. “Next: open the test email and tap the file” saves tomorrow’s session from a long search for context.
Choose work you can finish at the right size
Turn a broad project into a visible action. “Build the website” could become “draft the opening paragraph,” “publish one form” or “open the privacy link from the form.” Choose the action that makes another action possible. For example, confirm the file exists before polishing the email that delivers it.
A finish line can be a version ready for feedback. It doesn’t have to be your final publication. Label a draft with the question you want answered. If a friend is checking your page, ask what they expect after tapping the button. Ask once, listen and write the answer down. That gives the next block a concrete task.
Plan for a short day before it happens
Keep a fallback list of jobs that fit 10 to 15 minutes. Check one link, save a license, edit a subject or write a question for a reader. Pick a fallback that belongs to the active project. Use the rest of the time for the competing obligation. On the next ordinary day, continue from the notes you left.
If you keep missing the hour at the same time, look at what the calendar is telling you. A recurring family responsibility deserves its own slot. Try fewer longer blocks or two short sessions instead. A block works best when it fits the conditions you actually have. Leave a little time between tasks so a delayed meeting doesn’t take the entire slot.
Work an example week
Monday, write the name and one-page outline of your free resource. Tuesday, draft the first three steps and run them on a phone. Wednesday, finish the resource and test the public file link. Thursday, build the form and thank-you screen. Friday, send yourself through the process and record the first point that needs a change.
If Wednesday disappears, use a short session to list what’s left in the resource and prepare the test link. Shift the form setup to the next available block. At the end of the week, keep the work that’s ready and name the dependency that’s missing. You can ask someone to review the draft before the form is public. That feedback can make a later block easier.
Do a short weekly review
Open your Review note and count what you shipped, tested or learned. Record each as an action. “Tested the form in a private tab” is clear. “Worked on site” tells you very little. Write what helped you start, what interrupted you repeatedly and which task deserves the first block next week.
Ask if the work brought you closer to an answer. A sample that makes a buyer ask about a revision gives you something to clarify. A published tutorial that receives a question gives you a topic for the next session. A missed deadline may mean the project was too big for the hours you had. Resize the work before filling every empty space in the calendar.
Common fouls with a small schedule
- Treating a block as a place to choose among ten projects.
- Spending the whole session getting ready to work.
- Saving a draft without a note about the next action.
- Planning a week with no room for work or family changes.
- Calling research finished without a decision or a clear question left to answer.
Make a simple handoff card
Create a small note with four lines: project, current file, next action and check. For example, “Newsletter test. Draft in Welcome Email v2. Replace the old file link. Test from a private window.” Put the card where you open your work. Each finished block should update it. If the task changes, write why in one sentence so you remember the decision later.
You can keep the card on paper. Choose the method you’ll see at the start of the next session. Take it to the calendar and give the next action a real time. Leave a little space for the review so the week ends with a useful record.
Match the task to the kind of hour you have
Some work needs a quiet block. Recording a screen demo or thinking through a new offer may be easier when you can close the door. Other tasks fit a noisy or broken block. You can rename a file, verify a link or mark up a draft paragraph in shorter stretches. Keep both kinds of work visible. Put the demanding task where it has the best chance of being completed, and keep one smaller task nearby for a change of plans.
Take a week with four ordinary work blocks. Use the first to choose a deliverable and gather what it needs. Use the second to make a rough version. Use the third to test it and write down what went wrong. Use the fourth to repair the most important issue or share the result. If a fifth block opens, use it to read feedback. Give every block a small finish line of its own.
Put a limit on research and interruptions
Before searching, write the question and the decision it supports. “Which setting connects the capture form to my list?” gives you a stop point. Once you have an official explanation, test it. If you find several articles that disagree, check the provider and record the version or plan you use. Avoid spending the whole block comparing unrelated products. Write them in the parking note if they serve a later decision.
If an interruption takes half the session, reopen the handoff card and choose the highest-value action you can still finish. A test you can run in fifteen minutes might tell you exactly what to schedule next. If you can’t get to the main work, reserve a new block while the job is still clear. Keep the action on the calendar in the same words so you can resume without translating your notes.
Review the workload with a real constraint
Choose the constraint that most affected last week, such as a late shift or household commitments. Write down how many useful blocks you actually had. Plan the next week against that number. Leave one flexible slot for a missed action or an outside request. If the project can’t fit those blocks, reduce what the first version covers. A one-page checklist with a working delivery is enough to test. A full workbook can wait until the first reader tells you which part they need.
FAQ
Do I have to work every day?
Use the days and times your life allows. Spread the Playbook over more weeks if that helps you do the drills in order.
What if my work needs more than one hour?
Split it into checkpoints such as draft, test and publish. Give each checkpoint a block.
Where should I record ideas that come up while I work?
Use a single parking note. Review it later, after the current task reaches a checkpoint.