Skip to content

Blog

Time management4 min read

The Schedule Nobody Kept

A field-service electrical shop tried to timebox every task into a shared calendar. Six weeks and roughly €807 in rebooking time later, the calendar was scrapped.

  • #Zeitmanagement
  • #Timeboxing
  • #Kleinbetrieb
  • #Terminplanung
  • #Handwerk
Updated

AI-assisted · editorially reviewed Details

Text size
Also asMarkdownJSON

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. What follows is an imagined scenario, not a field report: 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 management argued that scheduling logic reshapes how people weigh relationships against efficiency — worth taking seriously even paraphrased rather than quoted here. Inside the imagined 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. A freundin.de piece on what German coverage calls time wealth describes people with a stronger sense of having enough time as tending to feel less stress — in the scenario, stress rose over those six weeks instead.

What Six Weeks Actually Cost

The direct cost is roughly calculable if a few assumptions are stated plainly. Assume the office manager spends an extra four hours a week re-slotting the calendar, 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.

ItemAssumptionCost
Extra office manager time4 hrs/week at €28, over 6 weeks€672
Follow-up visits after double booking2 × 1.5 hrs at €45€135
Total€807

Not counted: the hours technicians spent ignoring and re-negotiating blocks among themselves — even within the scenario, there's no reliable figure to put on that. 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 names customer calls that knock a block over as the limit of timeboxing. It follows that 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.

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

Responsible: Yusuf Senel. Written with AI assistance and editorially reviewed after publication. How wischtig.de works

Read next