The Schedule Nobody Kept

Suppose a six-person electrical contractor tries to plan every task in fifteen-minute blocks: one owner, one office manager, four technicians, one shared calendar, fixed slots for customer visits, drive time, parts orders, and breaks. Six weeks later, the calendar was scrapped.

The Plan: A Calendar Without Gaps

The idea followed a comparison of small-business time management methods already covered on Wischtig, weighing Pomodoro, the Eisenhower Matrix, and timeboxing against each other (in German). Timeboxing looked like the most disciplined option: every task gets a slot, nothing floats unscheduled. The office manager entered every customer appointment, every drive, every parts order into a shared Google calendar, gridded in fifteen-minute increments. Technicians received each block as a push notification. The goal was to stop the constant back-and-forth phone calls to the office and give customers a firmer arrival window. Two weeks were meant to be a trial run. It stretched to six, because nobody wanted to be the one suggesting it wasn't working.

What Cracked in the First Week

Field electrical work resists fifteen-minute grids. A customer isn't home, a part is missing, a detour on the bypass road takes forty minutes instead of ten — each disruption didn't shift one block, it shifted the rest of the day. After every deviation, the office manager had to manually re-slot everything downstream. By day three, technicians stopped checking the calendar altogether, since it no longer matched reality, and went back to calling the office directly — the exact behavior the calendar was supposed to eliminate. What one German time-management overview calls time thieves weren't missing structure here but unplannable interruptions from outside. A tight calendar doesn't remove those interruptions. It just passes them to the next person in line.

Why the Blocks Fell Apart

The second effect surfaced more slowly. Technicians increasingly felt scheduled like resources rather than treated as colleagues with judgment of their own. A psychiatrist interviewed for a German magazine piece on time wealth argued that scheduling logic reshapes how people weigh relationships against efficiency — worth taking seriously even paraphrased rather than quoted here. Inside the shop, that translated into small refusals: blocks got ignored, updates to the office manager stopped coming in, and by week four two technicians showed up at the same customer's address at the same time, because the second booking had never been logged. The customer got an apology and a free follow-up visit, which didn't make the mistake cheaper. The irony: the calendar was meant to create more control over time. Research on what German coverage calls time wealth links a genuine sense of having enough time to lower stress and stronger relationships — both moved in the wrong direction over those six weeks.

What Six Weeks Actually Cost

The direct cost is roughly calculable if a few assumptions are stated plainly. The office manager estimated an extra four hours a week re-slotting the calendar, assumed here at an hourly rate of €28. Add two follow-up visits triggered by the double booking, each roughly 1.5 hours of technician time, assumed at €45 an hour.

Not counted: the hours technicians spent ignoring and re-negotiating blocks among themselves — there's no reliable figure for that, only the office manager's sense that morale visibly dropped in weeks four and five. As a sanity check, running the same setup with three people instead of six wouldn't have cut the office manager's workload much, since the calendar needs upkeep regardless of headcount; fewer overlapping jobs would have made a double booking less likely, though, pushing the total closer to €700. Scale up to twelve people and the number of possible scheduling collisions grows faster than the headcount itself, because every shift touches several other blocks. Past a certain size, one office manager simply can't keep a manual calendar current — and the math stops being about higher cost and starts being about the system no longer working at all. Adding a second person just for calendar upkeep would have relocated the problem, not solved it.

What Would Have Worked Instead

Fixed time slots work where the disruption rate is low — at a desk, not on a job site. For field service with shifting customer appointments, a loose daily plan with fixed anchors and open buffer time in between would have held up better, backed by a simple priority list on a whiteboard instead of a calendar with no gaps. The method comparison of Pomodoro, Eisenhower, and timeboxing reaches a similar point: the less predictable the work, the coarser the time grid should stay. Only the genuinely fixed appointments — the 9 a.m. customer visit, the 1 p.m. parts pickup — belong on a calendar at all.

Anyone already reviewing internal workflows might as well check their website while at it — not because it has anything to do with calendars, but because technical weak spots creep in the same quiet way an overly tight schedule does. The free website check from Log-System Development reviews load time, basic SEO, and technical fundamentals in a few minutes and points out where a closer look pays off. For shops also weighing online booking or a dedicated app, Log-System Development builds directly with developers rather than routing the work through an agency with extra layers in between.

The calendar is gone. Whether a six-person field-service shop needs a formal schedule at all is still an open question.