5 Ways to Energise Your Team Before a Big Project

A major project is coming. The stakes feel higher than the last one. Your team is competent, capable, and quietly running out of gas. Here's how to change that in the two weeks before launch — without a two-day offsite, without a budget you don't have, and without the pep talk everyone secretly hates.

Most managers, when a big project hits the calendar, do one of two things. They call an all-hands, walk everyone through the Gantt chart, and end with a variation on "let's do this." Or they say nothing at all — heads down, we've got work to do, no time for morale.

Both approaches leak energy at exactly the moment you need it most.

Because energy, in a team context, isn't caffeine. It's the felt sense that this matters, I know my part, and the people around me have my back. When those three things are in place, teams sprint. When even one is missing, they grind. Big projects don't fail because of skill gaps. They fail because energy runs out somewhere around week three, and nobody notices until the slip becomes obvious.

Here are five things you can do in the two weeks before launch to build a reservoir of energy your team will actually draw on when the pressure comes.

1. Name the "why" before the "what"

The kick-off deck almost always starts with scope, timeline, and deliverables. Those are important. They also energise nobody.

Before you walk your team through any of that, spend fifteen minutes on a different question: why does this project matter, and to whom? Not the strategic-plan version. The human version. Whose day gets better? What breaks if we don't ship? Who's counting on us that we haven't named?

Research from Wharton's Adam Grant shows that even brief exposure to the beneficiary of the work — a customer story, a testimonial, a letter — can produce measurable increases in effort and persistence weeks later. You don't need a big production. You need a single, specific, human reason the work matters, and you need to say it out loud before you say anything else.

2. Make roles unambiguous — even if it feels obvious

In our experience running team building across dozens of South African corporates, the single most common energy leak is not disagreement. It's role ambiguity. Two people quietly think they own the same piece. One person quietly thinks they own something nobody has actually given them. Someone else is doing work that nobody knows about — and won't know about until it's late.

Before you start, write down every meaningful role for the project. Not job titles — decisions. Who signs off on scope changes? Who talks to the client? Who breaks ties when engineering and design disagree? Circulate the list. Ask people to challenge it.

You'll get one of two responses: "yes, that's right," which builds confidence, or "actually, I thought I was doing that," which surfaces a landmine before it detonates. Both outcomes are energy in the bank.

3. Run one short, purposeful team building session — not a full-day offsite

Here is the counter-intuitive truth about team building before a big project: short is better than long, and specific is better than general.

A two-hour session focused on one thing — communication under pressure, problem-solving in ambiguity, decision-making with incomplete information — will outperform a full-day general offsite almost every time. It signals to your team that this project is different without pulling them away from actual work. It builds a shared reference point they can call back to when things get hard. And it gives you, as the manager, a live look at how your team functions before the stakes are real.

Our Creative Collision and Leadership Development formats are designed exactly for this pre-launch window. Two to three hours, one clear outcome, and a debrief that leaves the team with a shared language for the weeks ahead.

4. Schedule the celebration before the launch

This one sounds strange, and it works.

Before the project starts, put a date on the calendar — three days after the delivery milestone — and tell the team you're marking the finish, whatever the outcome. Not a huge production. A team lunch. A Friday afternoon off. A dinner at a spot people actually want to go to.

Two things happen when you do this. First, your team stops treating the finish line as an abstraction. It becomes a real event on a real day. Second, and more importantly, you signal that you value their effort — not just the result. That signal, given before the work starts rather than after, changes how people show up on the hard days. It says you're not disposable, and this isn't just another project. Small gesture, big compound effect.

5. Ask one honest question, then listen

In the week before launch, sit down with each person on your team individually. Ten minutes. Not a status update, not a planning conversation. One question:

Then be quiet. Don't defend. Don't solve. Don't schedule a follow-up. Just listen and take notes.

Most of what you hear will be small — a tool they need, a decision that hasn't been made, a person they haven't been able to reach. Some of it will surprise you. Fix what you can fix. Acknowledge what you can't. Come back to each person within a week and tell them what you heard and what you're doing about it.

That single conversation, done well, does more for team energy than any offsite, any pep talk, and any all-hands. Because it says: I see you, I take you seriously, and I'm on your side. Teams that feel that way don't run out of energy — they generate it.

Before the sprint, fill the tank

A big project is a marathon disguised as a sprint. You will need every unit of energy your team can produce, and then some. The two weeks before launch are your best — and cheapest — chance to top up the tank.

None of the five ideas above require a big budget. None of them require a consultant. All of them require a leader willing to spend a few hours on the things that don't feel urgent but always turn out to be the ones that mattered.