Weekly challenge strategy: solve one business problem a week
Short answer Each Monday, ask your team what slowed the business most last week. Pick one problem you can fix in five working days, give it one owner and one number to move, and fix it together. On Friday, check the number, keep what worked, and pick next week's problem. Small fixes add up because each one stays fixed.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callHow does the weekly challenge strategy work?
One problem, one week, one number. You don't write a yearly plan and hope. You run a short loop every week:
| Day | What happens | Time |
|---|---|---|
| Monday | The team names last week's biggest slowdown; you pick one | 30 minutes |
| Monday | Write the fix plan: owner, steps, the number to move | 10 minutes |
| Tuesday–Thursday | Do the fix; the owner checks in daily | Normal work |
| Friday | Check the number; keep, change or drop the fix | 15 minutes |
This loop isn't new. Hospitals and software teams both use a version of it. The Institute for Healthcare Improvement, a nonprofit that trains health systems, builds its method on three questions. They work word for word for a shop, a law office or a cleaning crew:
"What are we trying to accomplish?" "How will we know that a change is an improvement?" "What change can we make that will result in improvement?" (Institute for Healthcare Improvement: Model for Improvement)
Its test cycle, Plan-Do-Study-Act (PDSA), is the weekly challenge in short form:
"The Plan-Do-Study-Act (PDSA) cycle is shorthand for testing a change on a small scale (e.g., one patient, one day) in the real-world setting — by planning it, trying it, observing the results, and acting on what is learned." (Institute for Healthcare Improvement: Model for Improvement)
What makes it a *team* method: the people who hit the problem every day help name it and fix it. The owner doesn't pick it alone.
How do you find this week's biggest problem?
Ask the people closest to customers. On Monday, give everyone the same three questions and two minutes to write answers:
- What wasted your time last week?
- What did a customer complain about, or ask about twice?
- Where did a job, sale or lead get stuck?
Then check a few numbers you already have. Most small businesses lose money in the same places:
| Where to look | What a problem looks like |
|---|---|
| Phone and inbox | Missed calls, slow replies to new leads |
| Quotes and estimates | Sent late, or never followed up |
| Calendar | No-shows, empty slots, double bookings |
| Invoices | Bills going out late, overdue payments piling up |
| Reviews | The same complaint in two or more reviews |
| Website and ads | Visits but no calls or form fills |
If you track nothing yet, start with calls and lead replies. A missed call is often a lost job; see what missed calls cost and how fast to answer a lead.
How do you pick one when everything feels urgent?
Pick the problem that costs the most and can be fixed in five working days. Score each candidate quickly:
| Problem | Cost if ignored | Effort to fix | Pick? |
|---|---|---|---|
| Nobody follows up on quotes | High | Low | Yes: high cost, low effort |
| Website looks dated | Medium | High | Not this week; break it up |
| Break room is messy | Low | Low | Just do it, don't make it the challenge |
| Need a new booking system | High | High | Pick one slice: compare three options this week |
A good weekly challenge passes four checks:
- One problem. Two problems means neither gets fixed.
- Fits in a week. If it can't, cut a slice that can. "Fix the website" becomes "add a click-to-call button to the homepage."
- Has a number. "Reply to every web lead within an hour," not "better follow-up."
- Serves a bigger goal. If this quarter's goal is more booked jobs, the challenge should move booked jobs, not office tidiness.
If you're choosing between bigger bets, like which marketing channel to fund, a scoring sheet helps more than gut feel. See RICE scoring.
How do you fix it as a team?
Give the problem one owner and the whole team a part. The owner isn't the person who does all the work. They make sure it's done by Friday.
Write the plan in five lines anyone can read:
- Problem: what goes wrong, in one sentence.
- Number: what you'll measure, and today's value.
- Fix: the change you'll try.
- Who does what: names next to steps.
- Friday check: who reports the number.
The hard part is getting honest answers on Monday. People won't name a problem if naming it gets them blamed. Google studied 180 of its own teams and listed psychological safety first among five things that made a team effective. Its guide defines it with researcher Amy Edmondson's words:
"a shared belief held by members of a team that the team is safe for interpersonal risk taking" (Google re:Work: Understand team effectiveness)
Google's engineers run their failure reviews the same way. Their rule is to look at what caused the problem, not who:
"If a culture of finger pointing and shaming individuals or teams for doing the 'wrong' thing prevails, people will not bring issues to light for fear of punishment." (Google SRE book: Postmortem culture)
In practice: thank whoever names the problem, talk about the process, and never ask "whose fault was this?" on Monday.
How do you know it worked?
Compare one number from before and after. If you wrote down "web leads answered within an hour: 4 of 10" on Monday, count again Friday. Then decide:
| Friday result | Next step |
|---|---|
| Number moved, fix is easy to keep | Make it the new normal; write it in your checklist |
| Number moved, fix is hard to keep | Keep it a second week and find an easier way |
| Number didn't move | The fix was wrong, not the problem. Try a different fix or pick the next problem |
| Couldn't measure it | Next time, choose the number before you start |
Scrum, the way many software teams work, ends every work cycle with the same kind of review. The Scrum Guide says:
"The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness." (The Scrum Guide)
Keep a one-line log of every week: problem, fix, before, after. After three months you'll have about 12 fixes, and a record of which ones lasted.
Some problems take longer than a week to show results. Search rankings often take months (how long SEO takes). For those, the weekly challenge is the step you finish, like publishing one service page, and the number is checked monthly.
Does fixing small problems really add up?
Yes, if each fix stays fixed. A problem solved once and kept stops costing you every week after. Twelve kept fixes a quarter change how the business runs.
It also helps the team. Teresa Amabile and Steven Kramer studied nearly 12,000 diary entries written by hundreds of employees at several organizations. Their book, *The Progress Principle*, says leaders who want motivated people must create "forward momentum in meaningful work". A visible weekly win is that kind of momentum.
Two limits:
- It doesn't replace a direction. You still need a goal for the quarter or the year. The weekly challenge decides what to fix next on the way there.
- It can't fix a problem you can't see. If you don't track leads, calls or sales, the loudest complaint wins, not the costliest. See marketing analytics for a small business.
Example
A plumbing company, 6 people
Monday: the office manager says callers often hang up when nobody answers during jobs. Last week, 20 of 80 calls were missed. Challenge: forward calls to the office line when a tech is on a job, and text back every missed call within 5 minutes. Friday: 8 missed, every one texted back. Kept.
A dental office, 10 people
Monday: the front desk counts 12 no-shows in a week. Challenge: call or text every patient two days before their visit. Friday: 7 no-shows. The team keeps the reminder and next week tackles same-day cancellations.
A small accounting practice, 3 people
Monday: 15 invoices are over 30 days late. Challenge: send all invoices the day work finishes, with a pay-by-card link, and email reminders for the overdue ones. Friday: 6 still late, US$9,000 collected. Kept, plus an automatic reminder at 14 days.
FAQ
What if my team is just me?
The loop works the same: pick the problem Monday, note one number, check it Friday. For a second view, ask a customer or contractor.
What if the biggest problem takes longer than a week?
Cut it into weekly steps; the first step is this week's challenge. "Hire a technician" becomes "write and post the job ad" in week one.
Should we do more than one challenge a week?
Start with one. Once the habit holds, a larger business can give each team its own challenge, all serving the same company goal.
What if nobody names a problem on Monday?
Name one of your own mistakes first. Then ask narrower questions: what wasted your time, what did a customer ask twice? Blame keeps people quiet.
How long before we see results?
Fixes like faster replies or reminders often show in that week's numbers. Search and ads changes can take weeks or months to show.
Different for you?
- The weekly problem is leads that don't turn into customers: missed calls, speed to lead, and conversion.
- The problem is not enough leads at all: compare channels with RICE scoring, then look at paid ads or SEO.
- The website gets visits but no calls: start with the website.
- You can't tell which problem costs most: set up basic marketing analytics first.