The reality

A founder makes a hiring decision at 11pm after a six hour client crisis. Three months later the hire is gone and the business has paid AED 35,000 (USD 9,530) in visa, salary, and ramp cost for nothing. The decision was not bad because the founder was bad. The decision was bad because the founder was empty. Energy is the constraint nobody sets a budget for. The team's salaries are tracked to the dirham. The founder's capacity is treated as infinite. Run it the same way for a year and the cost lands on the calls that mattered most.

Read this if

The founder is making the most consequential decisions of the week at the worst hours of the day
A 60 hour week feels heavier than a 70 hour week did three years ago
Weekends have become working time and the team has noticed
Decisions made tired keep coming back as problems made worse
The founder cannot remember the last full day off without a phone check
The team avoids bringing the founder good news because they sense the bandwidth is gone

What success looks like

When energy is treated as an operating constraint:

The founder runs a defined work schedule with start and end times that the team can predict
High-stakes decisions (hires, terminations, major spend, key client conversations) happen in defined windows when the founder is rested, never after hours under pressure
A weekly recovery block (one full day, no calls) is on the calendar and protected
Sleep, fitness, and a single non-work commitment per week are tracked and held
The team has explicit permission to defer non-urgent decisions to the next morning instead of catching the founder at 9pm
The founder can name the activities that restore energy and the activities that drain it without producing output

The framework

Energy as a discipline runs across four layers. Each layer is a system, not a willpower question.

Layer 1: The schedule

A founder who works whenever something feels urgent works always. The first move is naming the start and end of the working day, and the team-visible boundaries inside it. A 7am to 7pm working day with a 1pm deep-work block and a 6pm shutdown is a schedule. "Always on" is not.

The behaviour to adopt this week: write the working day. Communicate it to the team. Hold it for two weeks before evaluating.

Layer 2: The decision windows

Major decisions belong in defined windows. Hires get made on weekday mornings. Terminations get scheduled in the first hour of the day. Major spend approvals happen in the weekly review block, never in the WhatsApp thread at 10pm.

The behaviour to adopt this week: list the categories of decision the founder makes most often. Write down the window each one belongs in.

Layer 3: The recovery block

A weekly day without calls is the difference between a founder who lasts five years and one who lasts fifteen. The block is the reset that lets the next week happen at capacity, not a luxury item. The team has explicit permission to defer non-urgent decisions until the day after the block.

The behaviour to adopt this week: pick the day. Communicate it. Block the calendar. Tell the team the rule.

Layer 4: The energy ledger

Every founder has activities that restore energy and activities that drain it. Founders rarely name them in detail. The ledger names them. It also tracks the leading indicators (sleep hours, exercise sessions, non-work commitments kept) so the founder sees the deficit before it becomes a crisis.

The behaviour to adopt this week: write down the three activities that restore the founder's energy and the three activities that drain it. Notice which ones the calendar has already protected and which ones it has not.

A founder you might recognise

A founder runs a 30 person interior design firm in DIFC. AED 14M (USD 3.8M) last year. From 2023 through early 2026 the founder worked seven days a week. By Q1 2026 the senior coordinator had left, two clients had complained about response times, and the founder had made three hires that did not work. The founder's wife asked when the last full day off had been. The founder could not remember.

In April 2026 the founder made four changes. The working day became 7am to 7pm with a hard shutdown at 7. Saturday became a no-call day, with the team explicitly told to defer non-urgent decisions to Sunday morning. Major decisions (hires, spend above AED 25,000 (USD 6,810), key client conversations) moved into a Tuesday and Thursday morning block. Sleep and exercise went on a tracker the founder reviewed weekly.

By the end of the second month, the founder had passed three nights without checking the phone, taken two full Saturdays, and slept seven hours a night for 28 of 30 days. The team had absorbed the change without losing velocity. One client commented, unprompted, that the founder seemed sharper in the strategy session. The founder had not become a different person. The founder had simply stopped operating at half capacity.

Working through it

Write the working day. Start time, end time, deep-work block, shutdown. Communicate it to the team. Hold it for two weeks before evaluating.
Define decision windows. List the major decision categories. Assign each one to a window when the founder is rested. Communicate the windows to the team.
Schedule the weekly recovery block. One full day. No calls. Calendar entry. Team briefing. The team has explicit permission to defer non-urgent decisions to the morning after the block.
Build the energy ledger. Three activities that restore energy. Three that drain it. Three leading indicators (sleep, exercise, non-work commitment kept). A weekly review of the ledger sits in the same Monday review block as the time audit.
Hold the discipline for 30 days before adjusting. A new schedule that gets broken in week two becomes a schedule the team does not believe in. Discipline first, then iterate.

Common mistakes

Treating the schedule as a private commitment. A schedule the team does not know about is a schedule the team will accidentally break. Communicate it.
Making the most consequential decisions late at night. A hire decision made at 11pm has a worse outcome than the same decision made at 9am, every time. Move the windows.
Skipping the weekly recovery block when "this week is busy." Every week is busy. The block is what makes the next week possible.
Tracking work hours instead of energy. A 60 hour week of strategic work beats a 70 hour week of firefighting. Track the strategic share of the week.
Treating energy as a willpower issue. Willpower is the thing that runs out fastest. Systems (schedule, decision windows, recovery block, ledger) are what hold when willpower is gone.

Self-assessment

Y or N for each.

Does the founder run a defined working day with a start time, end time, and a hard shutdown?
Do major decisions (hires, terminations, major spend) happen in defined windows when the founder is rested?
Is there a weekly recovery block on the calendar with no calls, communicated to the team?
Are sleep, exercise, and a non-work commitment tracked weekly?
Does the team know the rule for deferring non-urgent decisions to the next morning?
Has the founder taken at least one full day off in the last seven days?
Could the founder name the activities that restore energy and the ones that drain it without producing output?

Five or more "yes" answers means energy is being treated as an operating constraint. Three or four is the band where the founder has named the discipline but has not held the line. Two or fewer means the next consequential decision is being made empty, and the cost of that decision will arrive later.

Protecting Your Energy