Managing Time and Energy

01 Title

On screen "Managing Time and Energy" · Module 7 · Facilitation Foundations

I drove from Scotland back down south in one go once. Left about four in the afternoon, decided somewhere around Carlisle that I'd push on rather than stop, and got home some time after midnight.

And here's the thing I remember. I missed my junction. Not a subtle one. The big obvious one I'd taken a hundred times.

When I finally pulled off, twenty minutes out of my way, I realised I'd been a genuinely worse driver for about two hours. And at no point had I felt like one. I felt fine. I felt like someone making good time.

That's the whole problem with energy. You don't notice getting worse.

Hold onto that drive.

0:46 · then: an energy line falling off a cliff after lunch

The room version.

The morning's gone well. Genuinely well. Good discussion, real progress, slightly ahead of schedule.

Then lunch. At ten past two you start the block you'd earmarked as the important one, the actual decision, and the room is just gone. Answers are shorter. Two people are on laptops. You push through, because it's on the agenda, and you get a decision out of them with all the enthusiasm of a hostage statement.

That decision won't survive the week. And the mistake wasn't made at two o'clock. It was made on Tuesday, when you put the hardest thinking of the day into the worst slot of the day.

Almost everything in this module works like that. It looks like a live problem and it's a design problem showing up late, which is good news: live problems need nerve, design problems need twenty minutes and a pencil.

02 Timeboxing, out loud

On screen "Every activity gets a stated duration, announced before it starts."

Start with the basics, because they hold everything else up.

Every activity gets a duration, and you say it before the activity starts. 'Four minutes.' 'Twelve minutes.' Not 'let's spend a bit of time on this.'

A timebox is permission to work fast and badly, which is exactly what early divergence needs. Given no time limit, people polish. Given four minutes, they produce. The constraint isn't a restriction, it's an instruction about what standard you're asking for, and it's kinder than watching people agonise over a sticky note.

0:35 · then: "Four minutes" that turns into nine

And then hold it, which is the part people don't.

Announce four minutes, give them nine, and you've taught the room your numbers are decorative. By the afternoon they're worth nothing.

So either hold the number or change it out loud. 'That's your four minutes. This is going well, so I'm giving you three more and taking them off the next block.' That's a visible decision, and the room reads it completely differently.

03 The two-minute warning

On screen "Two minutes left." · a countdown where the room can see it

Before every transition, two minutes' notice. That's the whole technique.

What it buys you is that people finish a thought instead of having one amputated. Cut a group off mid-sentence and they spend the next five minutes still in the last activity, or quietly resentful, or both. And it puts a floor under the pace: a room that knows the warning is coming works right up to it.

Then put the clock where they can see it. A timer on the screen, or the finish time on the flipchart. Without it, the only person who knows how long is left is you, so you're the one interrupting rather than the clock. With a visible timer the room paces itself, and you get to be the person helping rather than the person hurrying everyone.

04 Running to time versus running to the outcome

On screen two clocks

An important distinction, because 'keep to time' on its own is bad advice.

Running to time means the session ends when it said it would. That matters. People have made arrangements around it.

Running to the outcome means the group leaves with the thing. That matters more.

When they conflict, the outcome wins and something else gets cut. What you must not do is let both slip quietly, which is the default: you overrun by twenty minutes, still don't get the outcome, and now you've broken the promise and wasted the extra time.

05 The energy arc

On screen a curve across a day

Now the part almost nobody plans for.

Attention is not flat across a session, and treating it as flat is why the last hour of most workshops is worth so much less than the first.

Three practical rules. Hardest cognitive work in the first ninety minutes, because that's the best thinking you'll get all day and it should be spent on something that deserves it. Something physical or social after lunch. And never, ever schedule the key decision for quarter to five.

0:32 · then: "Practitioner rule of thumb, not a measured finding."

That ninety-minute figure gets quoted with more confidence than it deserves.

It comes from ultradian rhythm research, Kleitman's work on cycles of sleep and alertness. It is not a study of meetings, so treat it as a practitioner rule of thumb rather than a measured finding.

What is well supported is the shape: sustained attention degrades, and it degrades faster than the person experiencing it notices. That's the motorway.

06 The post-lunch slump is a design problem

On screen "Solve it in the agenda, not with enthusiasm."

Everybody knows about the post-lunch slump, and almost everybody tries to solve it with personality. More energy from the front. A rally. A joke.

It doesn't work. And being the only energetic person in a flat room is an unpleasant place to stand, which you'll discover about ten minutes in.

Solve it on paper instead.

0:22 · then: wall work, small groups, mid-afternoon decision

The slot after lunch gets movement, or something social, or something with a physical artifact people have to get up for. Wall work rather than table work.

And put your decision block either before lunch or mid-afternoon, once they've come back up: there's usually a genuine second wind around half past two.

The slump is a known property of humans at one o'clock, and designing around it costs nothing.

07 Break, change, or push

On screen three options, three signals

So the room's flagging. Three options, and they're not interchangeable.

Break, if it's been more than about ninety minutes, or people are restless, or you're about to start something needing real concentration. Ten minutes that buys back an hour of attention is the best trade available to you all day.

Format change, if attention is drifting but people aren't tired. Same content, different shape.

And push on, if what you're seeing is the Groan Zone rather than fatigue.

0:31 · then: sitting, standing, wall, pairs

Those two live levers, in a bit more detail. Both are cheaper than a break.

Movement. Get people out of their chairs. Do the clustering on a wall instead of a table, or ask people to go and stand next to the option they prefer. Bodies wake up faster than minds do, and the mind follows the body.

Format change. Forty minutes of the same shape, change the shape, even if the content is going fine. Plenary to pairs. Talking to writing.

And notice: the change itself does work, separately from what you change it to. Novelty buys attention. You don't need the new format to be better, only different.

08 Tired or Groan Zone

On screen withdrawal vs effort

Back to that third option, because tired and Groan Zone is the distinction that catches people, and getting it wrong is expensive in both directions.

A room that's frustrated and arguing is not a tired room. Give it a break at that moment and you break the very thing it was about to work through. You come back from coffee to find the argument politely abandoned.

The tell. Tired looks like withdrawal: shorter answers, less eye contact, quick agreement, phones. Groan looks like effort: talking over each other, repeating themselves, visibly frustrated but still leaning in.

Withdrawal, break. Effort, hold.

And if you can't tell, ask. 'Is this a break, or do you want to push through this?' Rooms are usually right about themselves, and asking costs you fifteen seconds.

0:52 · then: "Useful, and not today."

A specific time problem: the conversation that's genuinely interesting and is not what you're here for. Harder than a boring tangent, because a boring one dies on its own and an interesting one recruits people.

So give it thirty seconds. If new information is entering, it might be the real conversation in disguise, which happens more than you'd think. If people are enjoying themselves and nothing new is arriving, it's a tangent, and you park it with the objective as the reason. Module eight does the parking lot properly; the timing judgement is the part that belongs here.

09 Cutting under pressure

On screen four half-done things vs three finished things

You will run late. So decide how you cut.

The instinct is to speed everything up slightly. Trim two minutes off each activity, talk faster, keep everything. Don't. Half-doing four things frustrates everybody and produces four things nobody can use. And rushing is contagious: a hurried facilitator makes a hurried room, and hurried rooms make shallow decisions.

Cut whole activities instead. Drop one, do the other three properly.

And say the cut out loud. 'We're twenty minutes behind, so I'm cutting the second round and going straight to prioritising.' Nobody minds that. They mind being rushed, and they mind the creeping sense that you're behind and pretending not to be, which they can feel anyway. Announcing the cut converts a failure into a decision.

0:49 · then: COMMIT and CLOSE, ringed

And what you protect when you cut, always, is commit and close. They carry the value out of the room, and they sit closest to the clock running out, which is why they get eaten. The ten percent you built in back in module four is what you're spending here.

So the rule is simple and slightly counter-intuitive: when you're behind, cut from the middle. Take it out of the generating, or take out a whole convergent round. Never out of the end.

A session that generated less and committed properly is a good session. A session that generated brilliantly and ran out of time to decide anything is a wasted day, and it's the more common of the two by a distance.

10 When an activity flops

On screen "Name it, then move."

Sometimes you'll run something and it just won't land. Blank faces, thin output, an energy that says this isn't working.

Don't pretend. The room already knows, and carrying on cheerfully as though it went fine costs you credibility you'll need later in the day.

Name it plainly and move. 'That one didn't land the way I hoped. Let's try it differently.' Then switch format and go again. Thirty seconds, no apology, no post-mortem.

The only genuinely bad move is defending it. Or worse, implying the room did it wrong. It was your instruction, your format, or your timing. Nobody thinks less of a facilitator who adjusts. They think less of one who insists.

11 Decide your cuts on Tuesday

On screen a run of show with a "cut if behind" column

And here's the version of all of this that works in practice: decide your cut order before the day, in the run of show, in a column.

What goes first. What goes second. What never goes.

Because at three o'clock, twenty minutes down, tired, with a room looking at you, you will decide worse than the calm version of you did on Tuesday afternoon.

Let Tuesday decide. That's the whole technique. Almost everything experienced facilitators appear to do gracefully in the moment is something they settled in advance.

0:35 · then: ninety minutes, one dip

Most of the sessions you'll actually run are sixty or ninety minutes, and the arc is still there, compressed. In ninety minutes the dip lands around the fifty-minute mark, and it's usually format fatigue rather than tiredness.

So one format change at around the forty-minute mark, even if things are going fine. Thirty seconds, and it buys you the second half.

12 The steel-man

On screen "Rigid timeboxing kills good conversations."

The objection, and I have some sympathy with it.

It goes: the best moments in workshops are the unplanned ones. The conversation that runs twenty minutes over because it's finally the real conversation. Cut that off at your timebox and you've served your agenda and lost the session.

That's true, and I've cut off a conversation I should have let run. A real cost.

Two things I'd hold, though. First, you can tell the difference more often than you think. A conversation that's going somewhere has new information entering it. One that's overrunning has the same three points restated with increasing conviction.

And second, extending is fine. Extending silently is not. 'This is the real conversation, so I'm giving it fifteen more minutes and cutting the next block.' Now it's a decision with a price on it, and the room helps you pay.

0:57 · then: five short lines

Five to watch for.

One. You announce timeboxes and don't hold them, and by lunchtime your numbers mean nothing to anybody.

Two. You solve a flat room with enthusiasm instead of a format change.

Three. You mistake the Groan Zone for fatigue and call a break in the worst possible minute.

Four. You cut evenly across everything instead of dropping whole blocks.

Five. You let the end get eaten, because it's at the end. Protect commit and close in the plan rather than in the moment.

13 The practice

On screen This week's practice · a supplied all-day agenda, nine sessions

Here's your one thing.

On the page, an all-day agenda. Nine sessions, breaks marked, one decision block at three in the afternoon that is clearly carrying too much.

Two passes. First, mark where the energy will be lowest, before you look at the answer key. You already know roughly where it is. It's after lunch, or it's the third activity in a row where people sit and talk.

Second, cut twenty minutes out of that day without touching the commit or close blocks, and write one line on what you'd cut and why.

Then compare against the model answer. You're checking whether you dropped a whole activity or shaved everything, and whether you protected the end.

And if you've got a real agenda of your own sitting in a drive somewhere, run the same two passes over it afterwards. Optional.

14 Callback close

On screen the motorway, a missed junction

I'd been a worse driver for two hours and I never felt like one.

And the decision that cost me wasn't made at midnight. It was made at Carlisle, hours earlier, when I felt fine and chose to push on. By the time I missed the junction I was just paying the bill.

Rooms are identical. They don't tell you they've gone flat. They give you shorter answers and easier agreements, and if you're not watching you'll take those agreements at face value and wonder in a fortnight why nothing stuck.

So plan the stops before you set off.

0:39 · then: Next: Module 8 - Reading the Room and Closing Well

Next, module eight, and it's the last one.

Design, participation, pacing: that's what this path has built in you so far. Module eight is the live skill. Reading what's actually happening in front of you, deciding when to leave a plan, and landing the end properly.

## The practice (recap)

A supplied all-day agenda: nine sessions, breaks marked, one overloaded decision block at three in the afternoon. Mark where the energy will be lowest before you look at the answer key. Then cut twenty minutes out of the day without touching the commit or close blocks, and write one line on what you cut and why. Compare against the model answer, checking whether you dropped a whole activity rather than shaving everything, and whether you protected the end. Optional: run the same two passes over a real agenda of your own.

## Callback

The decision that cost me was made at Carlisle, hours before I missed the junction, at the point where I still felt fine. Rooms are the same. They don't announce that they've gone flat, they just start giving you easier agreements.

## Sources

Kleitman, N. Work on ultradian rhythms (basic rest-activity cycle). The ninety-minute figure is extrapolated from sleep and alertness research, not from studies of meetings, and is used here as a practitioner rule of thumb. Beat 8 states this out loud.

The cut-from-the-middle rule is mine, from practice. Beat 16.