How do you keep technicians motivated during slow periods?

We've been through this a few times. Pro tip: never let your senior techs sit idle for more than a couple days. They get restless and start looking elsewhere.

What works for us is pairing senior guys with newer techs for shadowing sessions that don't feel like "training." We frame it as "quality reviews" — they ride along, spot-check past jobs, talk through what they would've done differently. Keeps the veterans feeling valued as mentors, and the rookies get better without being in a classroom.

Also: maintenance days. Deep cleaning vans, reorganizing parts, updating documentation. Sounds boring but we gamify it — fastest organized van gets lunch on the company.

In my experience, the worst thing you can do is invent busywork. Techs smell that from a mile away.

We pay for certifications during slow periods. Electrical code updates, manufacturer training, safety refreshers. It's real work, they know it matters, and they can put it on their resume. Costs money but cheaper than losing someone.

Also give them honest communication. "It's slow, here's why, here's when we expect it to pick up." The silence kills morale more than the downtime.

yeah basically this lol

we had a slow stretch last spring and my manager was like "deep clean the shop" and everyone's standing around like... we cleaned it last week tho?? so what I did was I just started asking if I could shadow the estimator on some bigger commercial bids, learn how pricing actually works, and turns out that was way more useful than wiping down shelves again

turned into me getting trained on commercial work which is higher rate so win win tbh

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!