What a Phoenix GC’s calendar taught me about makers, managers, and the 30-minute gap that is worth nothing
“We need six bids a week out and we’re getting three.”
That is how a principal at a well-run Phoenix GC opened a leadership meeting I was attending. We were in his conference room, the one with the framed aerial of their first ground-up job from the nineties, and he was talking to his lead estimator. We will call him Marcus.
Marcus was in the meeting and was not complaining or disagreeing. He responded with what he had already done, three bids out the door the last few days, scope letters and all in the gaps in time he could find. Then he asked the question the way a guy asks who is trying to solve a problem, not create one.
“How am I supposed to get six out when I’m in meetings and site visits half the week?”
The principal looked around the room. I looked at Marcus and offered the only useful thing I could think of, which was, “Could we open your calendar?” With one raised eyebrow he agreed and we put it on the big screen. All three of us walked through it like a schedule of values.
The Calendar Math
Monday: the weekly ops meeting, a go/no-go review, and a precon kickoff on a job they had just been awarded. Four and a half hours.
Tuesday: three hours of meetings, plus a request to sit through ninety minutes of training videos on the new estimating platform they rolled out in the spring.
Wednesday: three hours of meetings, but spread across six hours of calendar. A thirty-minute gap between each one.
Thursday: needed on a qualifications package for a healthcare pursuit.
Every one of those was legitimate. The go/no-go needs the estimator in the room. The quals package had a real deadline. Nobody was wasting his time on purpose.
Then we did the other side of the ledger.
A real takeoff on a mid-size commercial job, the kind where you read the specs, catch the alternates, get sub coverage, and write a scope letter that will hold up in a buyout meeting, takes four to five hours of uninterrupted attention. Minimum. Six of those in a week is a full week of nothing else.
Six was never an aggressive number. It just did not fit. And nobody in that business had ever sat down and added it up.
“If the number does not fit on the calendar, you have a math problem, not a performance problem.
The principal was quiet and then smiled. Then he admitted, “I put most of those meetings on there.” Which, to his credit, is exactly the right thing to notice.
Paul Graham Wrote This Down in 2009
Here is the reframe, and it is the whole piece.
Paul Graham co-founded Y Combinator, the startup accelerator behind Airbnb, Stripe, and Dropbox. In 2009 he published a short essay called Maker’s Schedule, Manager’s Schedule. It takes five minutes to read and I have sent it to more contractors this year than any article about AI.
Managers run on an appointment book. The day is cut into one-hour boxes, and any box is interchangeable with any other. Something needs discussing, you find an open slot and drop it in. The cost of a meeting is one hour. That is it.
People who make things run on a completely different clock. They need time in half-day units. As Graham put it, “You can’t write or program well in units of an hour.” It takes time to warm up, get into the work, and the real results show up thirty, sixty, ninety minutes in.
Drop a couple of thirty-minute meetings into the first half of the day and that half is largely gone. Not because the meetings were long. Because the pieces left over are too small to build anything in.
And the manager cannot see it. From his seat, every slot is equally valuable. He has no idea that ninety minutes of meetings just took out four hours of production.
Graham was writing about programmers. If you have been in construction in Arizona for more than about fifteen minutes, you already know who he was describing.
Who Is a Maker on Your Jobsite
Here is the exercise I now recommend with each leadership team that will sit still for it. Go role by role and ask one question: does this person create value in a room with other people, or alone with a screen and a set of drawings?
The makers are the estimator mid-takeoff. The VDC coordinator working through a clash report. The architect or engineer in design development. The project manager writing an RFI that actually gets answered, or reviewing a submittal against the spec instead of skimming it. The superintendent building the three-week lookahead. And every single person doing closeout, because a punch list does not sort itself in fifteen-minute pieces.
The managers are the principal, the ops lead, the OAC meeting, the pull plan session, sub coordination, the safety stand-down, the weekly L10. That work is real. It is also interchangeable in a way maker work is not. Your L10 can move to Tuesday. The takeoff cannot be done in the cracks.
Now here is the twist that makes construction harder than a software company. Most of your people are both, on the same day. Your super is a maker at 5:30 in the morning with the lookahead and a cup of gas station coffee, and a manager by 9:00 when the first sub walks up in boots with a question. Your PM is a maker with a submittal at 7:00 and a manager on an OAC call at 10:00.
The meetings that make you money are not the internal ones. A principal creates value in meetings with his own team. An estimator creates value alone with a set of plans. Both are real work. They just cannot happen in the same hour, and the P&L only shows one of them.
Why Thirty Minutes Is Worth Nothing
Think about what actually happens in a thirty-minute gap between meetings on Marcus’s Wednesday.
He opens Bluebeam. He finds the sheet he was on. He reads his own notes to remember which alternate he was carrying and which sub still owes him a number. He gets about twelve minutes of real takeoff done. Then he glances at the clock, sees ten minutes to the next meeting, and decides it is not worth starting the next sheet. So he answers email until the meeting starts.
Marcus can move through an entire drawing set in a protected half-day. In a thirty-minute gap he gets a page and a half, badly, and spends the meeting thinking about the page he did not finish.
The research on this is not new, and it is not flattering. Here is what the credible sources say.
- Construction professionals spend roughly 35 percent of their time, more than 14 hours a week, on non-optimal activities, according to the FMI and PlanGrid Construction Disconnected study of nearly 600 construction leaders. About 5.5 of those hours go to hunting for project information, 4.7 to conflict resolution, and 3.9 to mistakes and rework.
- Microsoft’s 2025 Work Trend Index, built on telemetry from Microsoft 365, found that knowledge workers are interrupted roughly every two minutes during core hours by a meeting, email, or chat, and that about 60 percent of meetings are ad hoc rather than scheduled.
- Gloria Mark, the UC Irvine researcher who has followed office workers around with a stopwatch for two decades, has put the time to fully regain focus after an interruption at around 23 minutes. Which means a thirty-minute gap is, for practical purposes, seven minutes of work.
None of that is a construction-only problem. But a missed alternate on a takeoff does not show up as a bad quarter. It shows up as a change order with your name on it.
I Am the Guy Booking the Meetings
I want to be honest before I hand out advice. This piece hit close to home not because of Marcus, but because I opened my own calendar afterward and found myself on the wrong side of it. I run our SDR team at Dimensions, and I am the one who drops a 2:00 check-in on a Tuesday because I have an open slot and want to see how the week is going. I am the one who says “grab ten minutes” and takes twenty-five. Nobody in that story is trying to hurt anybody. I am a manager solving a manager problem with a manager tool, and every time I do it I take a call block away from somebody whose whole job is the call block. If you are the owner reading this, I would bet money you are the same. The manager in you keeps booking over the maker in you, and then booking over the makers who work for you.
DO THIS MATH OUT LOUD
Pick one person on your team who makes something: an estimator, a PM, a VDC coordinator, a designer. Then fill in three numbers.
- The number you asked for. Six bids a week. Forty submittals reviewed. A punch list closed in ten days.
- The hours that number actually takes. Not the hopeful version. The real one. A takeoff on a mid-size commercial job is four to five hours of uninterrupted attention.
- The hours left on their calendar after everything you assigned. Count only blocks of two hours or more. A thirty-minute gap counts as zero. Yes, zero.
If line two is bigger than line three, you do not have a performance problem. You have a math problem. And you are the one who can fix it, because you are the one who built the week.
The Move
Sit down with your maker and do the arithmetic out loud, the way we did with Marcus. Then do four things, and keep them small.
- Stack the internal stuff. Put your meetings back to back on designated days instead of sprinkling them across the week. Graham’s own fix at Y Combinator was to cluster everything into office hours and leave the rest of the day alone. Monday and Tuesday heavy, Wednesday through Friday protected, works fine for most GCs I know.
- Block the maker time and mark it busy. Get the takeoff block, the submittal block, the lookahead block on the calendar, and protect it like a meeting with an owner. Pick the hours when that person is sharp, not the hours that happen to be left over.
- Move to weekly targets instead of daily. Marcus suggested this one himself. Six a week turns every meeting-heavy Monday into a failure. Thirty a month lets him load the back half of the week and hit the number.
- Agree out loud on what breaks a block. An owner escalation, sure. A sub who cannot find the gate detail, probably. Somebody wanting to grab time, no. A blocked calendar that everyone ignores adds exactly nothing.
And if the meetings are really about trust, meetings will not fix it. You do not call a meeting to find out if a ticket got closed. You open the dashboard. Your bid log and your closeout tracker should work the same way.
Which brings me to Thursday.
Closeout is maker work. Sorting forty-seven punch list items to the right sub, figuring out which of two drywall contractors owns an item, drafting the email to each one, that is half a day of a project manager’s uninterrupted attention on every single job, and it lands at the exact moment his calendar is fullest. On Thursday we are going to show you one way to give that half-day back.
THE PUNCH LIST AGENT- SESSION 3 OF THE AI IN CONSTRUCTION SERIES
When: Thursday, September 10, 2026 at 11 AM Arizona
Featuring: Nate Kappler, President, Kappcon Construction
Live Build: A Claude-based Punch List Agent on real Kappcon documents
Hosted by: Dimensions and Smartbuild, sponsored through the Arizona Builders Alliance
Cost: Free. 60 minutes. Recording available to all registrants.
Register Here: AI In Construction – The Punch List Agent
It is not a silver bullet. It is a few hours handed back to the person who needed them most.
What bothered me about that conference room in Phoenix was not the number. It was that the business had asked for six, then built a week where six could not fit, and if we had never opened the calendar, the story would have been that Marcus was not hustling. Nobody in that story was trying to miss the target.
Do the math on your estimator. Do it on your PMs. Then open your own calendar and do it on yourself, because I would bet money the maker time in there is whatever survived after everyone else got a turn.
Nobody books over a meeting that is already there. They book over white space.
Your calendar already decided how much you are going to build this quarter. Somebody built it. Make sure it was you.
For over 20 years, Dimensions has been the trusted IT partner for Arizona’s architecture, engineering, and construction industry. We help AEC firms communicate better, collaborate smarter, and actually use the technology they’ve invested in. Because in construction, the tools only work if your team does.
IT Built For Builders.
