Episodes / Founder Freedom / No. 675

Count Your Real Work Days Before You Plan the Quarter (Ryan Deiss Had Only 16)

Ryan Deiss went back through his calendar and journal and found he worked only 16 real days in the third quarter, down from 43 in Q2 and about 60 in Q1.

Roland Frasier and Ryan DeissNovember 5, 2026 · 26 min
Read

Listen instead and the audio keeps playing while you browse the site.

In this episode

The write up

Ryan Deiss came into this episode with a number that surprised him. He went back through his calendar and his journal and found he had worked only 16 real days in the third quarter, down from 43 in Q2 and about 60 in Q1. The question on the table was what to do with that. Ryan's first answer was to count the days you really have before you plan the quarter. My push was a little different. If the important work still got done in 16 days, then maybe the number of days was never the real issue, and the better move is to plan for fewer days than you have, on purpose.

Where we landed was a combination of the two. Count the real capacity first, then decide what has to get done, then rank it, then say, let's try a 30 day thing instead of a 90 day thing and see whether that constraint makes you better.

The count that started it

I'd like to admit that my blindness about time is really the first thing. I opened by telling Ryan I thought we had done our last episode two weeks ago. I asked my son at lunch to check what we covered, and he gave me the date, and it was almost a month ago. So I'm not in any position to lecture anybody else on knowing where the time goes.

Ryan does a quarterly review and preview, and this time he did something he said he had never done before. He put his calendar into Claude and his journal into Claude and asked how many real work days and full weeks he had worked. The answer was 16 work days and only one week uninterrupted by travel across July, August and September. He said a lot of that time away was vacation, which was very good, but the rest was just personal chaos, both for him and for Richard, our business partner. I said my chaos has been running about a month and a half too.

Then Ryan ran the math forward. He said that if he goes out from Monday, October 5th, to the end of 2026, there are 88 calendar days left. There are 64 weekdays. There are 61 working days if you take out the time around Thanksgiving. There are 52 if you take out the end of December. After a few other days off, he ends up with 40 days to work. His argument is, I think I plan as though I have 90 days and that's why I've overplanned for as long as I can remember.

Efficient, or just more time

That's where I pushed back. What if you're just terribly inefficient and this is the first time that it's actually coming to light? Ryan said he got so much done in Q1 because he had more time. I said, was it more efficient? Or was it just more days? And if you had three times as many days, did you get three times as much done in value?

Ryan thought about it and said that, from an impact perspective, he bet they were pretty equal. That to me was the most helpful admission in the episode. The way that I framed it was that there are three separate questions here: availability, efficiency and effectiveness. If you're just counting days, you're only addressing the first one.

I brought up music because a lot of artists talk about this. You have older gear that gives you maybe three seconds of time to work with, or one instrument instead of a whole bunch. They seek out those older instruments because in that constraint environment, they find that they're able to create better. That's where I was coming from, and Ryan said he agrees with the principle, but 16 days is probably too much of a constraint and there is a happy medium somewhere above it. My guess would be somewhere between twenty and forty. Ryan said, "Yeah, I think you're right." Then he said he takes a 30 day vacation every summer and he's very productive in that season anyway.

Then Ryan drew the distinction that I think explains everything about the quarter. Do you know about the constraint on the front end and then plan for it, or do you not know about it and then you're reacting to it? The vacation he had prepared for was fine. The time that he had to be gone without warning was what was bad.

Deciding ahead of time what falls off

My objection to simply counting days is that it's still subject to massive interruption. With what Ryan had last month, there was no possible way to plan for that. So my suggestion would be that we use a budgeting model. Let's say that it's 30 days in the quarter of real focus on work, because we should be able to get 30 out of a quarter, and we budget 30 days of must do work. Then we have another 14 days that is contingency for the things that are important but not urgent. We know that in that 14 days, time can be interrupted because life happens.

Ryan's answer was that you can't decide ahead of time exactly what you're going to do because "life gonna life." What you can decide ahead of time is what falls off. His system is a big 3 for the quarter. I think he said that came from a story. He said he doesn't know if it's apocryphal or not, but it was about how Steve Jobs would have all of the leaders of the company rank the top ten things. Then he would draw a line under 3, and that was the big 3. Within that, Ryan keeps one thing that is the right next thing. In Q3, the things that were not the right next thing didn't get done. He said that was okay.

I wondered whether anything that was critical got missed or done less well in a 16 day quarter. Ryan said a few things weren't up to his own standards, but doubted it mattered to the outcome. He admitted he can be a little precious with his work. He also worked later than he likes. His default is start at nine, end at five, and when something blows up, in Ryan's words, "I work past five." He said, I feel no guilt about what did not get done because I did not swap the important things for unimportant ones.

I added one thing to that. A lot of times people do the unimportant stuff because they didn't take the time to start with deciding what the important things were in the first place. It doesn't have to be three. It could be five. I don't use Eisenhower as much as a box as I do the thinking behind it, and that is that you should know what must be done and then let that take priority.

Ranking the short list

Ryan's plan for Q4 is to be far more intentional about his real capacity and to ask how long each of those big three things takes. His view is that it's a sign of executive maturity: the more mature you are as an executive, the better you should be at budgeting how long things take and how many resources they require. So, he said, you might end up with a big two and the third one as a nice to have.

I think the ranking inside the list is as important as the list. If you have three things, then you want to know which one of them is most critical and which one of them is least. I think that's really what good time management under pressure is. If you don't do that, you're assuming that everything has to get done, and then one of two things is going to happen. One is you'll be overwhelmed and you won't do anything. The other is you'll do all of it about half as well as it deserved. If you do have the ranking, then you're going to do the one thing that has to get done. The others are going to wait because they could wait.

I also pointed out that the important things rarely line up neatly. What you'll find is that when you do everything that you can on one of those things, you're going to be waiting on other people. The gap while you're waiting on other people is where you handle the emergencies or the less urgent work.

Ryan gave credit to the team on this. He said there were a fair number of dumpster fires in the quarter and the team was good at figuring out which ones to put out and which ones to let burn, which is why the quarter was still pretty solid.

The experiment I would run

Ryan's own conclusion was kind of modest. He said most of Q3 was personal and could not have been planned. The main lesson, he said, is that stuff is going to happen and that's when you find out how resilient your business is.

My takeaway was different. He got done in 16 days what he thought he needed 90 for, and when he compared it to the longer quarters, he did not think he had gotten that much more done. That tells me to test a 30 day plan. He's got 40 days in Q4. I would not plan to fill those 40. I'd plan 30, have the artificial constraint, and then see if it gets done. If it does, you've got 10 more days for your family and your life that you didn't think you had. He said he wants to do it.

So you're going to count the days you really have, and then you're going to set your goals based on those days. Then you're going to pick the short list, rank it, and plan for fewer than the days you counted. And then see whether you needed the rest.

Written from the recording of this episode of Business Lunch.

Show notes

Ryan Deiss went back through his calendar and journal and found he worked only 16 real days in the third quarter, down from 43 in Q2 and about 60 in Q1. The surprise was that the important work still got done. Roland Frasier and Ryan Deiss turn that into a planning rule: count the days you actually have before you set the quarter's goals, pick a big three and a right next thing, budget time the way a mature executive budgets money, and try planning for 30 days instead of 90 so constraints work for you instead of against you.

Follow Roland Frasier:
Instagram: https://www.instagram.com/rolandfrasier/
LinkedIn: https://www.linkedin.com/in/rolandfrasier/
TikTok: https://www.tiktok.com/@rolandfrasier
Facebook: https://www.facebook.com/RolandFrasierPage/
Everything else: https://msha.ke/rolandfrasier/

Follow Ryan Deiss:
Instagram: https://www.instagram.com/ryandeiss/
LinkedIn: https://www.linkedin.com/in/ryandeiss/
X: https://x.com/ryandeiss

Visit: https://www.scalable.co

Free tools that go with this one

Keep going

More on this

Off the Org Chart

A weekly read for owners who think past the day to day.

You are subscribing to Off the Org Chart, a weekly email from Roland sent through Beehiiv. Unsubscribe anytime with one click. See the Privacy Policy.