Knowledge in one head, and steps done by hand

When only one person knows how to sort something out, kanman offers that person a short walkthrough and keeps what they confirm. When someone repeats the same step after the same event, kanman offers to take it over.

Every team has topics where one person always knows what to do, and nothing written says how. When that person is on holiday, the next incident takes three times as long. kanman notices these topics and helps write the knowledge down, without ever putting anyone on the spot.

This is switched on per team. Ask your workspace admin if your team does not have it yet.

What the team sees

kanman tells the team about a topic, never about a person:

kanman: IVR routing has no written procedure and little shared practice. I am collecting what is known so the next incident there does not depend on who is around.

kanman never ranks people, never shows who resolved how many incidents, and never tells the team who holds the knowledge. In a team of two it says nothing at all, because there “one person” would be a name.

The walkthrough: about ten minutes

The person who sorted out the last incidents of that topic gets a private card in their own chat. It shows their own last incidents and a few specific questions, for example:

  • In the incident “Calls land on the wrong queue”, how did you recognise what it was?
  • What did you check before you acted?
  • What exactly did you do, step by step?
  • How did you see that it worked?

Choose Let’s do it to answer in the card, or Not now to decline. A declined topic is never offered again, and an offer nobody answers closes on its own after a few weeks.

From the answers kanman drafts a procedure: when it applies, what to check first, the steps in order. It keeps only what you said, in your own words, and adds nothing. Check it, then choose That’s right or drop it. Only a procedure you confirmed is kept.

What happens next:

  • The next incident on that topic comes with your procedure, for whoever is on duty.
  • The team gets the steps as a page draft. kanman never writes the page itself: someone on the team publishes it in your wiki.

Steps you repeat by hand

kanman also notices when the same person does the same thing after the same event, for example a restart after every Monday deploy, or a rerun after a job fails. It only uses what your connected tools record, and only for steps someone did through kanman. Something that happened twice by coincidence does not count.

The person who does the step gets a private card with the times it happened and two choices:

  • Take it over: kanman drafts a habit that does the step after the event. You change it and start it, with your own rights, like any habit.
  • Fix the reason: kanman opens a story on the board to remove the reason the step is needed, with the times listed.

Not now declines for good.

Try this in the chatIn your team's chat

  • What do we only know in one head?

Last updated: January 1, 0001

Open kanman