How do you keep technicians motivated during slow periods?

From a leadership perspective, slow periods are an operational investment opportunity. We reallocate 20% of field labor hours to three priorities:

1. Process improvement projects — technicians lead root cause analysis on our top five callback drivers

2. Customer retention touchpoints — proactive maintenance calls to existing accounts, not revenue-generating but relationship-building

3. Cross-functional exposure — dispatch shadowing, parts inventory management, safety committee participation

The key is structure. Unstructured downtime breeds uncertainty. Structured development maintains engagement and typically yields measurable improvements in our fall peak season.

We also use this period for compensation planning and career pathing conversations. Technicians who see a future stay longer.

From a leadership perspective, slow periods are an operational investment opportunity. We reallocate 20% of field labor hours to three priorities:

1. Process improvement projects — technicians lead root cause analysis on our top five callback drivers

2. Customer retention touchpoints — proactive maintenance calls to existing accounts, not revenue-generating but relationship-building

3. Cross-functional exposure — dispatch shadowing, parts inventory management, safety committee participation

The key is structure. Unstructured downtime breeds uncertainty. Structured development maintains engagement and typically yields measurable improvements in our fall peak season.

We also use this period for compensation planning and career pathing conversations. Technicians who see a future stay longer.

Keiko's structure is solid, though I'd add — let your techs propose projects too. We got a fantastic van organization system because a technician was bored and mocked up a whole new layout in CAD (turns out he used to do kitchen design).

Another thing: slow periods are when you fix those annoying little workflow issues everyone complains about but nobody has time to address. We did a "pain point sprint" where techs pitched their top three daily friction points and we knocked out the quick wins. Took two weeks, massive morale boost.

And honestly? Sometimes the right move is reduced hours with retained benefits. We piloted this last winter — voluntary 4-day weeks, same healthcare, prorated pay. 60% of the team opted in, burnout dropped, and we had zero voluntary turnover in Q1. Expensive but worth comparing to replacement costs.

Reduced hours sounds nice until your best techs find second jobs and don't come back.

We just stay busy. Maintenance agreements, equipment audits, quote follow-ups from six months ago. There's always work if you look for it.

Another way to think about Mike's point — the work is there, but it requires sales and marketing investment that some ops teams haven't built out yet. Maintenance agreements are an excellent bridge, as are proactive system health checks for existing customers.

We found that framing these as "complimentary seasonal tune-ups" rather than "we're slow, can we come look at your system" made a significant difference in customer receptiveness and technician comfort with the soft-sell aspect.

lmao we played bingo

dispatcher made cards with squares like "customer offers you coffee" "dog tries to bite you" "unit is older than you" etc. dumb but we were all screenshotting our wins in the group chat

sometimes you just need something to talk about ngl

• Skill audits — 2 hours, assess what gaps exist
• Pair weak/strong on actual jobs when available
• Document everything for fall onboarding rush

Skip the team building activities. Techs hate forced fun.

Sorry if this is a silly question, but how do you handle the techs who *want* the team building? We have a couple younger guys who are really social and I think they'd actually be disappointed if we canceled our summer BBQ, but I also don't want to make everyone else feel like they have to attend...

Also I'm not sure if this is relevant but we're a smaller team, only 8 technicians, so maybe that changes things? I really appreciate any insight — this is my first time managing through a slow season and I want to get it right!

Hi Lindsey! Not a silly question at all — this is exactly the kind of nuance that makes each team's situation unique.

With 8 technicians, you probably know individual preferences pretty well. What we've seen work is making social events truly optional with a small twist: give the social folks a way to opt "in" more meaningfully. Maybe they help plan the BBQ, or it's framed as a recognition event for a specific win rather than generic "team building."

The key is reading the room — if two people organically want to organize something, support them. If you're the one pushing it because you think you "should," that's when it backfires.

Happy to chat more about your specific team dynamics if helpful. We're here to make sure you're set up for success!

Honest communication... right. That's the answer that sounds good in a forum post.

Try telling a tech with two kids and a mortgage that "things will pick up in September" and see how motivated they are.

We do guaranteed minimum hours. Written into employment agreements. No games, no optimistic projections. They know exactly what to expect. Makes the "development opportunities" actually land instead of feeling like a consolation prize.