Thursday has been running since September. Eight regulars, fifteen semi-regulars, a bounded-context diagram on the wall, a markdown file Priya refuses to turn into a Confluence page. Nobody has named it. Lee has decided it is time.
It is Charlotte who corners him about it, not the other way around.
They are at the cafe two doors down from the office. Charlotte is leaving for the airport in forty minutes. She has been running most of Greenbox’s sense-making for a year and she has been thinking about Thursday on planes.
“You know what Thursday is,” she says. It is not a question.
Lee stirs his coffee. “Yes.”
“Why haven’t you said so?”
“Because the moment I say it, somebody tries to do it again on purpose.”
Charlotte laughs, a short one. “That happens either way. Maya’s going to tell the board about Thursday at some point. If she names it wrong, we get six of them with charters by Q2.”
Lee looks at her. “Fair.”
“Say it.”
“Community of practice. Wenger, 1998. Thursday is a textbook example and the textbook is nearly thirty years old.”
Charlotte drinks her coffee. “Right. So how do we name it without killing it?”
The problem with the word
Lee raises it in the Monday leadership meeting. He has one sheet of paper and he keeps it in his lap.
“Thursday has a name. I have been sitting on it. The name is community of practice. It is older than everyone in this room’s career, it describes exactly what Priya accidentally built, and if we say it out loud in the wrong way the whole thing stops working by Easter.”
Maya blinks. “Start with what it is.”
“Three pieces. A shared concern people care about. The people who show up because they care. A set of ways-of-doing that develops between them, words they use, diagrams they draw, stories they tell each other when the new person joins. All three, or it is something else.”
Tom: “Thursday’s got all three.”
“Thursday’s got all three.”
“So what’s the bit that breaks it?”
Lee folds the paper. “The second you give it a charter, a chair and a quarterly KPI, it stops being a CoP and becomes a meeting nobody wants to be in. Which is what happens at every company that reads the Wikipedia page and decides to have twelve of them by Christmas.”
Maya: “Thursday doesn’t have a charter. Why would we give it one?”
“Because every quarter somebody from the board is going to ask you how Thursday works and what it produces and how you know it’s working, and you are going to want to answer in a way that sounds like a proper answer. The proper answer ruins it.”
Charlotte, who has seen this in three companies: “The proper answer is a stewardship line and a page of observations and the phrase we are deliberately not measuring it, and you have to be willing to say that to Patricia Osei with a straight face.”
Maya considers this. “Can I say that to Patricia with a straight face?”
Charlotte: “You can if you mean it.”
Priya, over coffee, the next day
Priya catches Lee at the kettle on Tuesday.
“You named it.”
“I named it.”
“Are we going to start calling it a CoP now? Am I supposed to put it on my LinkedIn?”
“Please don’t.”
She laughs. “Okay. But the pattern. What do I do differently now that it has a name?”
Lee thinks. This is the question he has been waiting for somebody to ask.
“Two things. One, when you see the same shape somewhere else, you will recognise it. Which means if Kai comes to you next week with an invite for a Tuesday thing about models, you can look at it and say this is a community of practice that wants to exist, let me stay out of its way. Two, when somebody more senior than you, me, Charlotte, a board member, a new VP we hire next year, comes at Thursday with a suggestion that would kill it, you will have language to explain why. Because a CoP without voluntary attendance is a working group, and a working group is a different shape, and Thursday does work as a CoP that it would not do as a working group. That’s a sentence you can say to a VP.”
Priya: “That’s also a sentence that sounds like someone has read a book.”
“I know. That is the cost of the name. You trade the ability to protect it for the risk that people start waving the word around.”
She pours the coffee. “I’ll take the trade. I’ve spent five months not being able to explain why I get angry when anyone suggests making it efficient.”
The list that isn’t a charter
Jas takes it on, because Jas has been writing about Thursday in her notebook since week one and everybody knows this without having been told.
She writes it fast. Half an hour after the Monday meeting. She doesn’t run it past anyone, which is also deliberate.
A Thursday is easier to start than to design.
It has a steward, not a chair. The steward sends the reminder. The meeting runs without them.
It has a domain you can say in a sentence. If you need a paragraph, it is two Thursdays.
It has pain in the room. Real, recent, specific. The pain is what makes it a Thursday and not a seminar.
Its artefact is a record, not a report. Nobody reads it except the people who were there, and that is correct.
It has the right to refuse the agenda. Including from me.
It can have a name. It does not need one. If it has one, the name is descriptive, not aspirational.
It is measured by whether people in different rooms mean the same thing by the same words. Not by anything else.
She pins it to the board outside the big meeting room. She does not tell anyone she has pinned it. By Thursday afternoon three people have photographed it. By the end of the following week it is in the engineering onboarding doc, which Jas has strong feelings about but has decided not to litigate.
Patricia, four weeks later
The board meeting is in early March. Maya has her deck. Patricia has her notebook. Somewhere between the pause-rate slide and the Sydney operational update, Patricia says:
“Tell me about the Thursday meeting. I keep hearing about it from people who are not you.”
Maya has been waiting for this question for a month. She has rehearsed several answers. She uses none of them.
“It’s a community of practice. Priya started it after the allergen incident. We do not measure it, we do not charter it, and when we interviewed a senior engineer for the Brisbane squad last month, the candidate heard about it on the tour and asked if she could observe one. She starts Monday. I did not make Thursday happen. I am carefully not making it not-happen. That is the entire management strategy.”
Patricia writes something. She looks up.
“Good. Keep doing that.”
It is, Maya thinks on the drive home, the first board question she has answered exactly right.
What Priya sent on Tuesday
Tuesday afternoon, four-thirty. Five people. Subject line Modelling Thursday. No body text. Tuesday at four, small meeting room, bring a broken model or a draft you do not trust.
The first session has three people in it. Priya, Kai, Anika dialling from Melbourne with her laptop propped on a cookbook. Priya brings the pause-risk impact map from last week’s session with Lee. Kai brings a question about how you evaluate a thing when you do not yet know what good looks like. Anika brings a problem she does not know how to phrase.
They argue for forty minutes. Priya writes a gist. The gist has a different filename from the original Thursday gist, which she has stopped updating because it is no longer the only one.
Kofi messages on Thursday: Is there a second Thursday now?
Priya writes back: Too soon to say. Come if it’s still on next week.
She closes Slack. She does not tell anyone she has sent the second invite. She goes home on time for the first Wednesday in a month.
The pause-risk work continues: what counts as preventable, and where the model could quietly hurt someone.