Coachable

That Gary Keller is a pretty smart dude

Best advice my dad ever gave

Your time blocking system isn't failing.
You are.
But probably not for the reason you think.

Real estate operations run on chaos. (Many businesses do.) Contracts come in. Deals fall apart. Agents need answers now. The business is volatile by design.

Most calendars pretend that isn't true.

I had a call this week with a lead admin supporting a high-performing sales team. She was exhausted, felt unproductive, and couldn't figure out why she never finished what was on her calendar.

When I looked at her time blocks, I saw the problem immediately.

Every hour was assigned. Morning routine. Email. CRM work. Follow-up. Systems. Client touchpoints. The calendar was a monument to productivity.

But every time something urgent hit - and something always does - she had to break a block. And every broken block registered as a failure.

The issue wasn't her discipline. It was her design.

She had confused a time block with a to-do list. Her calendar was capturing everything she wanted to do instead of protecting the few things she was truly committed to doing no matter what.

Here's what I told her:

Your calendar should be mostly blank.

Time blocks aren't aspirations. They're commitments. If you're not willing to defend it when the business gets loud, don't block it.

She left with three protected blocks per week. Morning email triage. Friday client cards. One weekly systems session. Less than 10% of her available time.

The rest? Open. Responsive. Available for the actual job.

Now she knows what success looks like.

And it's not a full calendar.

What are *you* blocking time for that you're not actually committed to protecting?

Being kind doesn't mean you can't have standards.
Too many leaders believe it does.
That's why your businesses feel fragile.

Last week I worked with a team owner navigating the departure of two sales agents who left to start their own operation.

The conversation started where most do: reviewing what went wrong, dissecting loyalty, questioning culture.

But that wasn't the real issue.

The real issue was this: they had built a people-first culture without operational boundaries. And when people left, the structure felt brittle.

They believed that holding firm standards would contradict their relational strength. So they delayed hard decisions. They designed roles around people instead of outcomes. They let performance drift because addressing it felt unkind.

Here's what shifted:

Standards don't weaken culture. They create durability.

A business built on clear systems and unapologetic expectations survives departures. A business built on accommodating individuals doesn't.

We stopped talking about the people who left. We started designing the org chart from scratch - zero-based thinking. Not around current team members. Around the structure required to deliver on their goals for the next nine months.

Role clarity. Communication standards. Performance thresholds.

The team didn't resist it. They were relieved.

Most leaders don't realize this: your team wants to know where the lines are. Clarity isn't cold. Ambiguity is.

Are you building a durable business, or one that's just nice to be around?

One survives turnover. The other doesn't.

Success comes from making peace with the repetition (and boredom) from doing the right things, the right way, more often. Not 'novelty'

Set a clear goal. Choose your model. Spend the morning focused on the 20% tasks that model requires. Congratulations, you've just time-blocked effectively

Run a sales team? Your profitability problem isn't the expense you're staring at.
It's the revenue mix.
And it's costing you money every single month.

I worked with a real estate team doing $250K in monthly revenue - good agents, solid fundamentals.

But profitability was stuck.

They were carrying $18K/month in video production costs with zero current ROI. The instinct? Cut the video spend.

But that wasn't the constraint.

The real issue: the cost of sales had climbed because they were over-indexed on paid leads. Those paid leads felt like growth because they drove transaction count. But the math was brutal.

Meanwhile, their past client database - which should generate >65% of closed deals - was only producing 30%.

Not because the database was weak. Because no one owned it.

Agents cherry-picked who to call. The system depended on memory and motivation. Outreach was inconsistent. Relationships were treated as agent property, not team assets.

So we ran the numbers.

Reduce paid spend by 20%. Increase self-generated deals by 20%.

Cost of sales drops from 54% to 48%. Profitability jumped immediately. That 6-point swing covers two-thirds of the video investment - without cutting a dollar.

But the bigger unlock wasn't the math.

It was the shift from agent-led to operationally-led.

Past clients don't need to be sold. They need to be systematically remembered. Who bought. What they care about. Where they live. When life changes. Why they moved. How they make decisions.

Those six questions become the algorithm. The team builds the system. The operation owns the relationship. Agents execute at higher levels because the infrastructure supports them.

Most teams treat past clients like a list.

High-performing teams treat them like a system.

What percentage of your deals are coming from paid leads right now?

If it's over 40%, you don't have a growth problem - you have a dependency problem.

Repeat it with me - "Thinking differently = changing your results"

Don't Be Afraid to Let Them Go

This week, I kept hearing team leaders delay or dilute standards because they believe keeping every current team member is the safest path.

You know the situation: someone on the roster closes deals - but resists the CRM, misses follow-ups - and you choose to look the other way because losing them feels "risky."

That feeling is understandable; you’re balancing revenue, relationships, and the recruitment cost of a replacement.

The real problem? You believe that PEOPLE need to be guaranteed before SYSTEMS can be enforced.

In practice, that posture makes your systems fragile: standards become optional, onboarding becomes reactive, and successful outcomes hinge on a few individuals rather than repeatable processes.

Struggling how to explain it? Try this: "Systems give us certainty, provide consistent service, and generate predictable results. You can leave if you want, but the system isn’t changing.”

Saying that aloud forces you to decide whether standards are conditional or real. Once leaders can voice it, their focus shifts from preserving individuals to preserving outcomes.

And in practical terms, that changes what you measure and who you coach.

Instead of coaching to keep someone comfortable, you coach to meet the standards - response windows, listing intake steps, file completeness, etc.

The immediate implication for an agent: if your lead response, listing presentation, or client follow-up is being compromised to avoid churn, you’re trading short-term comfort for long-term instability.

This week's coaching challenge: Make *one standard non-negotiable. Hold to it; you’ll either get buy-in or get clarity.

Either outcome is preferable to pretending the system exists when it doesn’t.

We all need more exercise

Team leaders who struggle with consistency don't have a discipline problem. They have a rhythm problem.

I coach top-producing teams. The leader is capable, the team has talent, and the results are there - but only in bursts.

The assumption is usually that inconsistency is a people issue. Someone isn't motivated enough. Someone isn't following through. So the leader pushes harder, adds more meetings, raises the pressure.

But the actual problem is structural. There's no reliable coaching rhythm underneath the team - no predictable cadence where performance gets reviewed, skills get developed, and standards get reinforced. Without that, accountability becomes reactive instead of systematic.

When a team finally installs that rhythm - even something as simple as bi-weekly sessions tied directly to performance data - the energy in the room shifts. Not because people suddenly care more. Because they finally know what's expected and when it will be addressed.

The momentum was always available. The structure just wasn't there to hold it.

So the question worth sitting with: does your team have a coaching rhythm, or do you only coach when something breaks?

Weekly Signals - April 17, 2026. A recap of the most popular post from our Facebook Group, KLOUD Coaching, this week.