Coach Yourself: 25 Weekly Questions That Keep Your Business Moving

Use weekly questions to collect evidence

Open your calendar, published links and work notes. Pick a week with a clear start and end. Review what you made, who saw it and what they did next. Use counts where you have them, and mark where you are missing a number. A reply, test result or clear example is useful evidence even when the number of readers is small.

Use the questions in order the first time. Later, you can choose the section that fits the week. For each answer, try writing one sentence about an observation and a second sentence about a possible cause. “Two people asked where to confirm” is an observation. “The sender name may be hard to recognise” is a possible cause. The second line gives you something to test.

Questions 1–5: Check what reached the field

1. What did I publish, send, deliver or test this week?
2. Which piece of work could a reader use without my help?
3. What did I finish that made another task possible?
4. Which task took longer than I expected, and which part took the time?
5. What did I leave unfinished, and what is the exact next action?

Use specific verbs. “Tested the signup in a private tab” tells you what happened. “Worked on email” makes the next step harder to remember. If an unfinished task has no next action, open it for five minutes and write the first thing you need to see. Stop after you have a clear handoff.

Questions 6–10: Listen to the reader

1. Which question did a real person ask?
2. Where did someone pause, click, reply or ask for an example?
3. What words did a reader use that differ from mine?
4. Who seems to be using the resource, and in what situation?
5. What would help a reader take the next step they already want?

You can listen in replies, comments or a simple walkthrough. Ask a friend to use a page and say what they think will happen next. Leave out personal details from your review notes. Record one point of confusion and one line they understood. Both belong in the evidence because you want to keep the parts that are working.

Questions 11–15: Follow the route

1. Where did visits come from, and did I label those sources clearly?
2. Which main action did I ask a visitor to take?
3. Did the page, form, confirmation and email work in a fresh test?
4. Where does the earliest visible gap appear?
5. What is one small change that would help me investigate the gap?

A route can be a funnel from a useful article to a signup and a welcome email. Compare visits, submissions and confirmations from the same dates and sources. Keep test addresses separate. If counts are too small to interpret, use a walkthrough and record what you can actually verify. A blocked download deserves attention even if nobody has reported it yet.

Questions 16–20: Review time, attention and gear

1. Which work block was easiest to start, and what made it easy?
2. Which interruption happened more than once?
3. Which tools or courses served the current project this week?
4. Which idea or expense can wait without blocking the next test?
5. What would I change about next week’s schedule to fit my real hours?

Put the answers beside the calendar. If the middle of the afternoon regularly gets interrupted, try a smaller task there or move the block. If a course taught you one useful action, write down the action you applied. Record upcoming renewal dates in a place you will see. Decide based on the work the tool has to support.

Questions 21–25: Pick one move for next week

1. What should I keep doing because I have seen it help?
2. What single change is worth testing next?
3. What am I willing to pause so I can complete that test?
4. When will I do the work, and what should I have at the end?
5. When will I review it, and what result will I record?

Write the next move in one sentence. “On Tuesday, shorten the thank-you page and test confirmation with a fresh address.” Give the review a date too. “On Friday, compare the new walkthrough with the old one and check whether a test reader knows which message to open.” Save any longer ideas in a separate parking note.

A worked example with a small amount of data

Suppose you published one tutorial and six people visited the resource page. Two submitted an address and one confirmed. Those numbers describe the route for that period. They do not explain the other person’s choice. Run a fresh test and see whether the confirmation arrived with the sender name you promised. Then ask a friend to read the thank-you screen before they open the inbox.

If the message arrived and your friend still didn’t know which subject to look for, change that instruction. If the file link asks them to sign in, fix that first. Write the date and the one change you made. Next week you can compare the new route with the previous one without guessing which of several changes came first.

Common fouls in a weekly review

• Counting activity without saying what it produced.
• Treating a hunch as an explanation for a reader’s choice.
• Comparing two numbers from different dates or sources.
• Bringing too many new projects into the next week.
• Picking an action without reserving time for it.

Keep a review sheet you can compare next month

Use a dated page with five lines: finished, observed, guessed, next test and review date. Under finished, name one artifact you could show. Under observed, write a fact from a test, reply or report. Under guessed, explain one possible cause in words you can test. Under next test, write a task with an owner and a stop point. Then put the review date on your calendar. You can answer the long list of questions in a separate note and use this sheet to keep the decision visible.

Use the same evidence format across weeks. If you record two tracked links, label the source and dates each time. If you collect questions from readers, note the topic and what they were trying to do. Leave out names and private details. After a month, look for repeated tasks and repeated obstacles. A pattern can justify a bigger change, such as moving an explanation earlier in your guide or scheduling a different time for recording.

Review a week that didn’t go to plan

Suppose you scheduled three sessions and only got one. Look at what made that session possible. Maybe you had the draft already open, or you had a quiet half-hour before dinner. Use that observation to schedule one more block like it. Move a smaller action into the time that gets interrupted. An honest calendar gives your next plan a better chance of working.

If nobody tried the page you made, your next test may be to ask a suitable person to open it. If the page was never published, make a private test or publish it only when ready. If it was published but nobody knew about it, put one useful answer where the reader already looks. Choose the first missing step. Then book the time to do it and write down the result you’ll check.

End the review with a short note for tomorrow

Finish with a line such as “Open the published form on a phone, submit a new test address and save the sender name I see.” Leave the public page address next to the line. If the task is too big to finish in one block, separate the first test from the repair. Tomorrow’s work can start from a real observation instead of another open-ended review. Close the notes after you have booked that action. Come back on the date you wrote down and compare the result with your earlier observation.

FAQ

Keep practicing

• Free Traffic That Still Works in 2026
• Sales Funnel Basics: Free Gift, Small Offer, Bigger Offer
• The One-Hour-a-Day Business: Time Blocking for Side Hustlers
• Try Day 30 in the 30-Day Playbook
• Visit the Gear Room