Team Knowledge Sharing

When the only person at Meridian Parts who understood the warehouse label printers went on honeymoon, the warehouse stopped shipping for a day and a half. The printers were not complicated. The knowledge was in one head, and the head was on a beach with its phone off, as it was entitled to be. The two technicians left behind spent the day and a half discovering, one wrong guess at a time, what their colleague could have told them. He could have done so in twenty minutes on any Tuesday of the previous four years. Nobody had asked. Nobody had thought of the label printers as a risk, because they had never gone wrong, because he had always fixed them.

This series is about the twenty minutes on a Tuesday. It covers the bus-factor audit, a one-hour grid of systems against people that shows where the single heads are. It covers cross-training rhythms that survive a busy month, which is the only kind worth setting up. It covers documentation as the sharing medium, starting with the runbook for the thing that breaks most. Then come the weekly huddle and the ticket of the week, fifteen minutes standing. It covers when the expert leaves, and the handover that gets what is in the head out of it. And it covers measuring how far knowledge has spread, so the next honeymoon is just a holiday.

Articles in This Series

• The Bus-Factor Audit: Finding the Knowledge Only One Person Holds
  The grid of systems against people, the single points of failure it exposes, and the quarterly audit in an hour. Covers the first three to fix and why, a five-person worked example, and the grid.
• Cross-Training Rhythms That Survive a Busy Month
  The weekly half hour, the ticket swap, the shadow day, the teach-back, what to cross-train first, keeping the rhythm when the queue is on fire, and the cross-training calendar.
• Documentation as the Sharing Medium: What to Write Down First
  The runbook, the known-error list, the internal note that says how, the how-I-fixed-it habit, documentation as the second person, what to write first, and the minimum runbook set.
• The Weekly Huddle and the Ticket of the Week
  Fifteen minutes standing, the ticket of the week walked through by whoever solved it, the known-error review, the rotating presenter, what the huddle is not, and the agenda.
• When the Expert Leaves: The Handover in the Notice Period
  The handover in the notice period, the brain-dump structure, the shadow weeks in reverse, the questions to ask before the last day, passwords and vendor contacts, and the handover plan.
• Measuring How Far Knowledge Has Spread Across the Desk
  How many people can resolve each category, the bus factor by system over time, reassignments because only one person could, articles per person as coaching, and the scorecard.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.