Nobody in the Room Had a Time Problem

September 04, 2026•13 min read

Three people took the hot seat on this week's accountability call. One could not find the hours to build the systems he knew he needed. One had her working week compressed down to a single protected day. One had spent a good week holding boundaries and then watched every reclaimed hour refill by Friday. Three different businesses, three different stages, three versions of the same opening sentence: I do not have enough time. By the end of the call the room had rejected that diagnosis three times out of three. Not one of those was a time problem. They were all the same problem wearing different clothes.

The Automation Story Was Not the Point

I opened the call with something I was frankly proud of. While I was away with family for a weekend, I had an agentic AI system running against my own portfolio operations. It pulled the resident communications, audited the property management software for gaps and for paid features we had never switched on, wrote a full report of what could be improved, and then started making the improvements. When I logged in the next morning it was like a different piece of software. A leasing agent function that calls a prospect the moment they dial in. A restructured phone tree routing to a leasing coordinator and to a back office maintenance team we had been paying for and never plugged in. None of that existed until the night before. In parallel I ran a swarm of cheaper agents on market rent research across 429 units and had the output written back into the system automatically.

Then I did the math out loud, because the math is the interesting part. Maybe I saved myself forty hours. Those were low level hours. I could have handed them to a VA for a few hundred dollars. Measured in money, it is not much of a story.

The reason it mattered has nothing to do with the money. It is that nobody had to be taken off the work only a human can do, and I did not have to spend management attention delegating it. That is the actual return, and it reframes the whole conversation the room was about to have. The scarce resource in a small operation is not hours and it is not dollars. It is attention. Every one of the hot seats that followed was a story about attention leaking somewhere the operator had not looked.

Eliminate Before You Automate

The first hot seat was an ambitious operator with a long list of things he wants to build, who cannot find the time to build the things that would give him the time. He is not confused about what to build. He is stuck upstream of that.

The room gave him a sequence, and the order is load bearing: systematize, eliminate, automate, delegate. You cannot eliminate a step you have never made explicit, so writing the process down comes first. Then you strip out everything in it that does not need to exist. Only then do you automate what is left, and only then do you hand it off. The metric for choosing what to work on is not return on equity and it is not return on effort. It is return on time.

I added the filter I actually use, because it cuts hard against the current reflex to point AI at everything. Do not build a system unless there is already somebody, or something, that could take it over. We have developed an addiction to the idea that AI will build any system. Building an elaborate process around work that should simply have been deleted is not leverage. It is a more efficient version of the wrong thing. Focus on the systems that cost you the least to hand off, or that pay you the most when you do. That is the same sequencing argument behind building the system before you hire the person, applied one layer earlier.

Two tools got named for narrowing the list. The Buffett approach of writing down twenty five goals and killing the bottom twenty, and then the question of which one of the survivors makes the rest easier or unnecessary. Sometimes the answer is that the goal itself is wrong, and once you fix that, a large share of your task list turns out to be side quests that never pointed at the destination anyway.

A member closed that segment with the line the room kept coming back to. Having too many priorities has the same effect as having none at all. If your list for today has thirty eight things on it, you are not being effective. Your daily list should be two or three items, all of them pointed at one priority. Everything else belongs to a system.

A Private No Is Just a Wish

The best coaching of the night came from a member who deliberately skipped the systems conversation. His argument: this is not a time problem, it is a saying no problem, and you cannot solve it privately.

He walked through his own case. When he committed to a demanding multi year program, he did not simply decide and hope. He had what he called an enrolling conversation with the people affected. The script was roughly this. Here is what this is going to take. Here is what I am saying yes to. Here is what I have to say no to. For this period of time, not forever. Are you okay with that?

Then he ran a small trap on the hot seat member. He asked what the second component was, got the answer "sticking to it," and corrected it. Everybody forgets the enrolling conversation. People decide privately what they will say no to, tell nobody, and then wonder why it collapses. Declaring it out loud does two things at once. It converts the people around you from obstacles into supporters, and it converts them into the people who hold you accountable to it.

The time boundary is what makes the ask acceptable. "For the next four months" is a request a spouse can say yes to. "Forever" is not. And he allowed for drift honestly, because life is messy and plans get adjusted. The point is not perfect adherence. The point is that an undeclared boundary has no enforcement mechanism at all.

That same move showed up in two other places on the call without anybody pointing it out. When a member had to ask a tenant to accept a safety change on a porch, the coaching was to state it plainly and stop over explaining. This is what needs to happen, I know it is inconvenient, thank you. And then say it again, and again, because you will have to. And when the conversation later turned to declining requests, the tactic that worked was pre declared scarcity: announcing in advance, publicly, that a thing is not available, so you are not refusing people one at a time forever.

Cut the Loss and Go Get a Better Deal

One member brought a harder problem. He had introduced friends to projects, and although the exposure is not technically his, he carries it as his own. One project has been delayed repeatedly by subcontractor failure, occupancy approvals have slipped by months, incorrectly installed windows caused water intrusion that forced finished walls to be torn out, and the general contractor now refuses to work with the original subs, so the same work has to be paid for twice. The carrying cost runs every month. The break even sale price sits above what comparable units in that market are trading at.

The room worked the options. Everything routes through the occupancy approval first, since no sale, no refinance, and no lease up is reachable without it. After that, three paths: convert equity into a down payment and hold some units, bring in a party whose actual need is a tax position rather than monthly income, or sell at a loss.

My view, and I said upfront that I am biased: do both of the last two. Get the current capital partners out, and let the asset go to whoever it actually suits. If break even is one number and the sale is somewhat below it, everyone takes a small hit. If we go deeper instead, we are all stuck talking about a deal nobody likes for another five or ten years. I would sleep better knowing it was off our plate. Sometimes a deal is just going to lose money, and you go get a better one.

The real diagnosis is worth separating from the drama, because it generalizes. The people whose capital sits in that project never had an asset performance problem. They had a holding period mismatch. They had exited the ownership business, they wanted to hold paper rather than property, and they were sitting in something illiquid, long horizon, and not throwing off income. No clever structure fixes a horizon mismatch. The only real fix is substitution: find the party whose time frame and tax position genuinely fit the asset, and move the original party into something that fits theirs.

Which, notably, is the same principle a member had described forty minutes earlier from a trading book. The best traders run something close to even win rates, so the edge is not in picking winners. It is in loss management, and human instinct does exactly the wrong thing. People add to their losers and cut their winners short because they are afraid of giving back a gain. He made the property bridge himself: sometimes a property should be let go rather than fed. Same principle, three different rooms of the same house. It also explains why your best performing asset gets the least of your attention. It causes no problems, so it never asks for any. Worth running the numbers on that honestly, which is what the return on equity calculator is for.

Do Not Amputate the Drive, Redirect It

The last hot seat was a member who cannot say no. She is a rigorous calendar blocker, and the block she sacrifices is always her own. The overflow runs into her sleep.

The room hit this from several angles. One member described his own recovery from people pleasing, which turned on a single question he heard once and never recovered from: if you are a people pleaser, show me the list of people who are pleased with you. That list does not exist, and even in theory it changes hourly. Once the behavior looked futile rather than virtuous, it lost its grip on him. Another member declined to accept the deflection that this was about reciprocity, and pointed at the sleep procrastination as the tell. He earned the right to push by confessing the same trait, and offered a test worth keeping: if a challenge stings, there is something there. If somebody calls you a blue tomato you can check the mirror and laugh. If the label lands and you want to argue, that is information.

My contribution went the other direction, and it is the part I would most want an operator to take away. I am one of those people who seeks validation. I seek it from the city, from my tenants, from the people I have served over the years. It is a large part of why I have been successful. The people who want to give the most usually have some dopamine attached to approval, and it drives a great deal of good work.

Every good trait has a shadow, and the work is identifying where this one is costing you, not removing it. So the answer is not to stop needing approval. It is to build structures that pay that need without spending your time on it. Another member described the cleanest version. People calling him do not want his hands, they want a solved problem. Now he refers instead of performing, and he still gets the full social credit for solving it. He is still the person you call. He just does not do the work.

The room left three phrases behind that are worth writing down. Your lack of planning does not constitute my emergency. Do not take other people's monkeys off their backs, because you can give direction without taking custody. And the one that makes refusal feel generous rather than cold: this may not be your fault, but it is your problem to solve, and how do you plan to do it? When people treat you as the crutch, you are not helping them.

The Takeaway

Five things carried across all three hot seats.

Every time problem in the room turned out to be a boundary problem. Nobody accepted time scarcity as a root cause once, all night.

Elimination comes before automation. Automating work that should have been deleted is the failure mode, and it is easier to fall into now than it has ever been.

Cutting losses fast applies identically to trades, to deals, and to commitments. The instinct to feed the loser and abandon the winner shows up in all three.

Declaration is the enforcement mechanism. The enrolling conversation, the pre announced scarcity, and the plain tenant script are the same move: say it out loud, in advance, without over justifying it.

And the drive that got you here does not need to be amputated. It needs somewhere better to go.

I will close on the observation I made at the end of the call, because it is the uncomfortable one. This gets harder as you succeed, not easier. When you have a job, "I have to go to work" is a complete sentence and nobody argues with it. Remove the job and the excuse goes with it. Everyone assumes you are available. You become your own worst boss. The more freedom you build, the more your time becomes purely a function of what you decide, and deciding turns out to be the hard part. Which is exactly why the room exists. It is a lot easier to catch somebody else's pattern than your own, and we practice out loud, together. If you want the longer version of what happens when structure replaces effort, three problems from a previous week's hot seat landed on the same conclusion by a different road.