Reading a franchise network through its WhatsApp groups

01

The work lives in the chat

I would compare the formal operating system with the messages people use to get work done. The manual may describe the approved route while a chat group reveals an unresolved question or an unclear owner. Read that difference as a process question before treating it as a personnel judgement.

Nobody designed the second one. It grew because a message to a group gets an answer faster than a ticket does, and because the person who knows the answer is in the group and not in the ticket queue. Head office tends to treat this as a compliance problem to be tidied away. I think that misreads what the groups are. They hold the only complete record of what the network asks, decides and improvises, written by the people doing the work, with a timestamp on every line.

Most organisations never read that record. They read the dashboard built on the formal system, which sees only the fraction of the work that was routed through it.

02

What surgical teams showed

Use an appropriately governed transcript to identify recurring operational questions, then test those patterns with the team. A message is evidence of what was written; it is not a complete account of what happened.

Map who asks, who answers, who makes the decision and where the exchange stops. The useful output is a pattern of work, with identities removed from the report unless there is a defined and authorised reason to retain them.

Include the channels used for practical coordination in the review scope, with appropriate permission and privacy controls. Count unanswered questions and unclear decisions rather than assuming that a busy group is an effective one.

A franchise network is the same thing at a greater distance. Swap the junior doctor for a new clinic coordinator and the senior surgeon for a regional lead, and the transcript will tell you who really carries the network's knowledge.

03

The four reads

I read a month of one group with four questions in mind, one pass for each. It is slower than trying to do all four at once and far more accurate.

Questions. Mark every message that asks something, then group them by what they ask about. The recurring ones are the interesting ones. A question asked once is a question. The same question asked by four clinics in a month is a missing paragraph in the standard, and every answer given in the group instead of in the manual guarantees that the fifth clinic will ask again.

Routes. Record the role that answers and the role authorised to decide. Test the route when a frequent responder is absent. If a clinical question is settled by someone without the relevant clinical remit, refer that governance gap to the responsible clinical lead.

Silences. Look for the questions that got no reply, or got sympathy without a decision. Then look for the clinics that have stopped posting. A quiet clinic reads as a well run clinic on a dashboard. In a transcript it often reads as a clinic that has decided asking is not worth the wait.

Workarounds. Search for the phrases people use when they improvise, such as "we did it like last time", "just for today" or "until the stock comes in". Each of those is a place where the lived process has already moved away from the written one. Most are harmless and a few are sensible enough to adopt across the network. You cannot tell which until you have found them.

04

Patterns, not people

Whether the exercise helps or poisons the groups for good gets decided here.

Before reading staff messages, define the purpose, access, retention and reporting method with the responsible privacy and legal owners. Tell the people affected what is being reviewed. Use only the information necessary for the stated task, and do not repurpose patient or staff details for article writing.

In operating language, that gives me three rules. I tell the network, in the group itself, that I am reading a month of messages to find gaps in the standard. I strip names and replace them with roles before any analysis leaves my desk. And nothing found in the reading goes into anyone's appraisal, including the message that made me wince.

That last rule has a cost. Now and then you will read something that shows a person doing what they should not. Fix the process that allowed it. If it was genuinely unsafe, it goes through the clinical safety process like any other report, openly. What it never becomes is a performance note built on a quoted message. Use the transcript against one person and you lose the record for everyone.

The first time a chat message turns up in a performance review, the real conversation moves somewhere you cannot read.

05

Three kinds of change the reading should produce

A month of reading should end in a short list, and every item on it should be one of three kinds of change. A paragraph added to the standard, for each question that recurs. A routing change, where one person is carrying answers that belong to a role. Or a named owner, for each type of question that currently dissolves into agreement.

If an item cannot be written as one of those, it is an observation, and observations are how these exercises end up forgotten in a slide deck.

I repeat the reading every quarter. The second pass on the same group is the one that earns its time, because it tells you whether the questions you wrote into the standard have stopped being asked.

06

Living with the groups

You will not stop a network running on chat groups, and you should not try. The groups exist because they are faster than anything head office has built. Ban them and the traffic moves to private messages, where nobody can learn from it at all.