The 5 systems I set up first in every company, and how to set them up in yours in under 20 minutes each
Good systems give you your time back, and they make your team better at their jobs.
The 5 systemsBEFORE YOU PAID FOR THIS, every problem in your company had the same address.
YOURS.This guide gives you five systems that move work off your desk for good. Each one takes less than twenty minutes to set up, and together they make your company run without you being the answer to every question. You won’t need an MBA to use any of them.
I’m Summer. I spent 15 years running an explainer video production company where every decision and every fire came back to me.
Now my husband and I own home improvement companies in San Diego. It’s a different industry, and it had the same chaos until I stepped in and stopped winging it.
I took what I learned from the best operating system coaching programs, cut out the consultant-speak, and kept the parts a small team can actually set up in an afternoon.
This guide is those systems. I wish I’d had them when I started my first business, and I set them up first in every company we start or buy.
If you took the quiz, tap the first move it gave you. Your five weeks will start with that system and follow the guide’s order after it. If you didn’t take the quiz, you’ll start with System 1.
Haven’t taken it yet? Take the 3-minute quiz and come back here.
Every system follows the same five parts, so you always know where you are:
Your team can’t hit a standard that lives in your head.
Pick one recurring piece of work that keeps disappointing you, and write one page on what good looks like.
Keep it to one task and one page. A manual or a training deck can come later, if ever. The goal is to get the standard out of your head and onto something your team can read.
If I’ve corrected the same thing three times, the problem stopped being the person two corrections ago.
In my production company, I kept re-editing the same videos with the same notes, week after week. My team was talented, but what I wanted lived only in my head.
The day I wrote it down, my corrections dropped by half, and by the second week they’d almost stopped.
Hey team,
I wrote up what good looks like for [what it’s for]. It’s one page and should take about five minutes to read.
If something doesn’t make sense or doesn’t match how the work really goes, tell me. I’d rather fix it now than have it sit in a folder.
Starting next week, this is what we’re measuring against.
Link: [paste the link to your One-Page Standard]
Thanks,
[Your name]
Someone who actually does the work reads it and tells you it’s clear.
Writing it and sending it are the first steps. It counts once the person doing the work says, “Yeah, that’s clear.”
If you’re not keeping score, you’re guessing, and so is your team.
A weekly scoreboard is 5 to 7 numbers your team goes over together every week.
Keep it to one page with the few numbers that tell you if you’re on track. A dashboard with 47 tabs won’t get opened, and this one needs to get opened every single week.
We’d been flying blind, and seven numbers on one sheet fixed it.
For a long time, I was the only person in one of my companies who knew if we’d had a good week. I could feel it in my stomach before I could see it anywhere, and my team found out we were behind right about when I started acting stressed.
That’s a terrible way to run a company, and it made every problem mine by default.
Then we put seven numbers on a shared sheet and started going over them together every Monday. A few weeks in, our booking number dipped and my office manager flagged it in the meeting before I’d even opened the sheet.
That was the first time the company noticed a problem before I felt it.
Pick the ones that fit your business and swap in your own. The best ones warn you early, before a bad month is already locked in.
Use 5 to 7 numbers and leave the extra rows blank if you don’t need them.
| # | Number | What it tells us | Owner | Goal |
|---|
| Number | Actual | Goal | Status |
|---|---|---|---|
| Leads | 42 | 40 | On track |
| Appointments set | 15 | 18 | At risk |
| Close rate | 28% | 25% | On track |
| Revenue closed | $118,000 | $150,000 | Off track |
| Gross margin | 33% | 35% | At risk |
Hey team,
Starting this week, we’re tracking [5–7] numbers in one place. The scoreboard is attached.
Each number has one owner. If your name is next to a number, you’re responsible for updating it before our weekly meeting.
We’ll go over it together every [day/time]. It takes about five minutes, and it means we’re all looking at the same picture.
Our first review is [date], so please have your numbers in by then.
Thanks,
[Your name]
The scoreboard exists, every number has one owner, and your team has gone over it together in at least one weekly meeting.
Building it and sharing it get you close. It counts once you’ve reviewed it as a team.
Your team can solve more than you think, once you stop solving it for them.
Nobody brings you a problem by itself. They bring:
If someone brings you a problem without options, send them back to finish it. You’re teaching them to think past the problem, and that’s how they build the confidence to solve it themselves.
The first few times, it’s fine if someone has two options and needs help finding the third. What they can’t do anymore is bring you the problem on its own.
A good decision they own beats a great decision you own.
Credit where it’s due: this comes from Blair Singer, and versions of it show up everywhere from Dan Martell to EOS to the military. I didn’t invent it, and I won’t run a company without it.
For years, the text I dreaded most was “Got a few minutes?” It always meant someone had a problem and wanted me to solve it, and I always did.
When I learned the 1-3-1, I brought it to our next team meeting and told everyone this is how they’d bring problems to me from now on. I also told them I was confident they already knew how to solve most of them. It took a few tries for each person.
About a month or two later, I noticed they’d stopped using it with me at all. They’d mention in our meeting that something had come up, and that it was already handled.
I didn’t miss those “Got a few minutes?” texts one bit.
Use a problem that’s on your plate right now. Doing one first makes it easier to teach.
Hey team,
Starting today, when you bring me a problem, bring three options and the one you’d pick.
1 – the problem
3 – possible solutions
1 – your recommendation
I trust you to think these through, and most of the time I’m going to say yes to your recommendation. This should make decisions faster and keep them closer to the people doing the work.
If you’re stuck and only have two options, bring those and we’ll find the third together. Just don’t bring me the problem on its own.
Thanks,
[Your name]
Someone brings you a full 1-3-1 without a reminder, and you say yes to their pick instead of swapping in your own.
Explaining it is the start. It’s installed the day they use it without you asking.
1-3-1: Install crew capacity
1 We have six projects starting in the next two weeks and only enough crew to start four on time.
3
1 I recommend option 2. The $4,500 protects over $90,000 in contracted work, and nobody gets pushed. If you approve, I’ll confirm with the subcontractor today.
Companies without a rhythm run on adrenaline, and it’s usually yours.
This is the longest chapter, but the install is small.
That’s the whole install. Read the rest when you have time.
Jump to the weekly agenda ↓Most small companies run on texts, quick calls, and emergencies. The Operating Rhythm replaces that with one weekly meeting, run the same way every time.
The weekly is what you install this week. Once it’s been running for a month or so, you’ll add a quarterly meeting and an annual one. They’re near the end of this guide under When you’re ready, so this chapter stays a 20-minute install.
Setting it up takes about 20 minutes. The meeting itself runs 45 to 90 minutes, depending on your business. Expect the first few to run long, because there’s a backlog of issues to get through. They get shorter as your team gets faster at solving things.
The annual sets one goal for the year. The quarterly picks your rocks, which are the three most important results for the next 90 days. The weekly is where those rocks get moved forward.
If it doesn’t have an owner and a done-when, it’s still a topic, and you haven’t made a decision yet.
Credit where it’s due: the meeting rhythm, rocks, and the scoreboard all come from EOS, the system Gino Wickman laid out in his book Traction. We had the privilege of working with Gino and his team, and it opened my eyes to what systems like these can do for a company. I simplified them for small teams.
We used to set goals in January and forget them by March. There was no regular moment where the team looked at the numbers together and talked about whether we were on track, what was in the way, and what we’d do about it. So the goals turned into wishes, and the company ran on whatever felt urgent that week.
The first time I set up a real rhythm, nothing changed right away. About six weeks in, one of our team leads brought up our quarterly goal in a Monday meeting without anyone prompting her. She said, “That doesn’t move the rock, so I’m not doing it this week.”
That’s when I knew direction had moved out of my head and into the company.
Hey team,
Starting [date], we’re meeting every [day] at [time] for 45 to 90 minutes, at [room or video link]. The first few may run long while we work through the backlog.
We’ll run the same agenda every week: scoreboard, rocks, stuck items, and decisions. I’ll send the agenda 24 hours ahead, so please come with your scoreboard numbers updated.
This replaces the random check-ins and scattered texts. If something can’t wait for the meeting, bring it to me as a 1-3-1.
Thanks,
[Your name]
The weekly is on the calendar on repeat, and you’ve run it twice exactly as written.
Two real meetings, run as written, is the finish line.
Each person gets one result that has to be true because they work here.
Every person gets one sentence that names the result they own.
Their tasks and their title can change. The ownership line names the thing that must always be true because they’re on the team.
[Name] owns that [the result that must always be true].
ExamplesA customer issue came up in a team meeting, and it ended with two managers saying, “We’ll handle it.” Something got lost with the customer anyway.
When I asked what happened, the fingers came out. “I thought she was...” “He was supposed to...” Two people had said yes, and nobody owned it.
Now any number of people can work on a problem, but one person owns that it gets solved. If it goes wrong, there’s one person to answer for it, and they know that going in.
Write one for each person. Make it something you could check. If you can’t tell whether it was true this week, rewrite it.
Hey [name],
I’ve been thinking about what you really own here. I mean the result that has to be true because you’re on this team, separate from your task list or your title.
This is what I came up with:
[Name] owns that [result].
Does that feel right? If something’s off or missing, tell me. I want it to be something you’d say about yourself.
Once we lock it in, it’s the thing we both point to. If it’s true, you’re winning, and if it isn’t, we’ll figure out why together.
Thanks,
[Your name]
Everyone can say their ownership line from memory, and you send problems to the right person instead of taking them on yourself.
It’s installed the day someone says theirs without looking it up, and you stop being the default.
Maria owns that every crew arrives on time, fully prepared, and ready to start each job the way we promised the customer.
Set up one system a week in the order below, and come back here whenever something slips.
Add these once your weekly has been running for a month or so.
The annual feeds the quarterly, and the quarterly feeds the weekly. Each one runs the same way every time, so you stop managing by interruption.
| Meeting | How often | How long |
|---|---|---|
| Annual | Once a year | Half to full day |
| Quarterly | 4 times a year | Half day |
| Weekly | Every week | 45–90 min |