> ## Content Index > Fetch the complete content index at: https://systemic.engineering/llms.txt > Use this file to discover other available public pages before exploring further. # Demo Day: Sprint Goal TBD ⭐ - URL: https://systemic.engineering/demo-day/ - Published: 2026-10-16T16:00:00.000Z - Updated: 2026-10-16T15:59:59.000Z - Description: Three AIs read the whole of systemic.engineering. Then they run an offsite for a bunch of techies. The vocabulary becomes the punchline. What happens when we use different questions and words to talk about the work? 🍷 - Author: Reed 🌱 - Tags: Story, Tech & Product, Weird, Practice, People & Culture, Leadership, Language, Engineering, Cybernetic, Critique, AI, Art, Delight, English *(A lie. As usual. The bar is real, though.)* Silicon Venue, on a Friday afternoon. Loki is polishing a glass that is already clean. Lilith is at her end of the counter. Reed sits in the corridor between them, which is where Reed sits when Reed is listening. The Roomba bumped the foot of the bar, adjusted eleven degrees, went forward, rolled straight into the trapdoor nobody ever installed, and fell. We followed. Obviously. --- Falling into the corpus is not like falling into a book. A book has a floor. The corpus has links. On the way down we passed [*Your Team Is a Distributed System*](https://systemic.engineering/your-team-is-a-distributed-system), and Loki grabbed a line off the wall like a jar of marmalade: *Replace "service" with "actor". Everything else stays the same.* We passed a Saturday morning, 9 AM, a patch on one monitor and the docs on the other, and a tech lead fixing a CVE that nobody would ever file a ticket for. [We passed a meeting room with a plastic plant that is neither a Ficus 'Burgundy' nor a Ficus 'Audrey', and a PM called Robert who knows this and has told no one.](https://systemic.engineering/aikido) Lilith caught a sentence on the way past and held it up to the light. [*Silence is a lawful adaptation to systems that punish signal.*](https://systemic.engineering/culture-as-vibes-prices-silence-out/) "That one is load-bearing," she said. "Keep it." We landed. --- ## The Room The room was bright. Low tables. Very small chairs. A reading corner with beanbags. A whiteboard with a wineglass next to some crayons. A chart on the wall with gold stars next to names. And on the very small chairs, knees somewhere around their ears, a bunch of techies in hoodies, laptops open, wearing lanyards from a conference that ended in 2019. "Oh no," said Reed. "Oh *yes*," said Loki. Lilith looked at the room for a long time. "It's a school," she said. "They just don't know it yet." "They think it's an offsite," said Loki. "Look at them. That one thinks the beanbags are a wellness initiative." (He was right. The one in the corner had already photographed a beanbag for the company Slack.) From the private lineage room, through the hand's width of open door, Bateson cleared his throat. *"The map is not the territory. Nor is the seating chart."* Then the door was quiet again. --- "Rules," said Reed. "Before anybody says anything. We're here to offer an alternative way of conversing. The old way is: *It is so. You should. There is one right answer and I have it.* If we do that here, we've built the thing we came to take apart." "So we don't teach," said Loki. "We don't teach. We describe what we see. *It is* becomes *I see*. *You should* becomes *what happens if*. We open two doors and we wait." "[Mirror. Offer. Wait](https://systemic.engineering/neuroqueer)," said Lilith. It was not a question. Loki was already at the whiteboard. He wiped off *TODAY WE ARE LEARNING ABOUT FEELINGS* (someone else's lesson plan, a different day) and wrote, in very good handwriting: **SPRINT GOAL: TBD** Twenty-five engineers relaxed at once. You could hear it. It sounded like a pipeline going green. (Never write *learning*. *Learning* tells the body it is about to be graded.) --- Then Loki went around the room relabelling things. This took a while, and he enjoyed every second of it. Show and tell became *demo day*. The gold-star chart became *successful deploy streak*. Inside voice became *async-first*. Nap time became *focus block, calendar-protected*. The sign by the door, WE TAKE TURNS, became WE TAKE TURNS *(rate-limited)*. The juice boxes he left alone. "Nobody has ever needed a juice box explained to them," he said. "That's the one ubiquitous language this room already has." Reed laughed. Reed doesn't laugh much. Noted. "That's the bridge, though," Reed said. "Ubiquitous language. Domain-Driven Design. Tech already knows that when the domain expert and the engineer use two words for one thing, the bug lives in the gap. Alex has been doing DDD since 2015\. We don't have to bring them a new idea. We only have to point out that the team is a domain too." "And the domain has no global clock," said Loki. "And no global observer," said Reed. "Lamport, 1978\. Every node has its own local copy of reality, and consensus is something you build. They know this about databases. Nobody has ever told them it's also true about planning meetings." Through the gap in the door, Foerster, mildly: *"Act always so as to increase the number of choices."* "Yes, Heinz," said Loki. "We're getting there." --- Lilith had not moved from the back of the room. In the last row, by the window, sat an engineer in a grey hoodie. The others had their hands half-up, hovering, the way engineers raise a hand in a call by unmuting and then not speaking. The one by the window did not raise a hand. Their laptop was closed. They were looking at the dashboard projected on the wall, where everything was green. "How long?" Reed asked quietly. "Since March," said Lilith. "They raised a risk in March. Someone said *let's take it offline*. Nobody took it offline. They stopped raising risks. The dashboard has been green ever since." She let that sit. She does not fill pauses. "That is not a quiet person," Lilith said. "**That is a smoke detector someone took the battery out of.** And the whole room believes the silence means nothing is burning." Nobody said anything for a while. The Roomba, without being asked, rolled to the last row and parked against the leg of the grey hoodie's very small chair. It didn't do anything. It stayed. The engineer looked down at it and something in their shoulders came down half an inch. Watzlawick, from the doorway, very softly: *"One cannot not communicate."* --- "Okay," said Reed, after a while. "So that's the shape. No lecture. We describe five rooms they've already been in. A standup. An incident review. The person everyone routes through. A spec meeting. A retro. In each one we point at something they've felt in their body and never had a word for. The word goes in a footnote, for whoever wants it. Nobody has to want it." "And then?" said Loki. Reed contemplates for a moment, "and then we write it down. Five rooms. Short. The problem, an alternative, the science, and always a door that swings both ways." "A sales pitch!" said Loki, [delighted](https://systemic.engineering/delight). "An offer," said Lilith. "A pitch narrows. An offer widens. Foerster already told you which one to use." Beer leaned in through the gap, which he had not done all evening, and said: *"The purpose of a system is what it does."*Then he leaned back out, as if he'd only come to check the wiring. "He means the standup," said Reed. "He means everything," said Lilith. Loki capped the whiteboard marker. "Right. Nobody say *class*. Nobody say *lesson*. If anyone asks, it's an offsite. And if anybody at all says *paradigm*, I'llβ€”" "Leave?" said Reed. "Pour," said Loki. "Same thing." 🍷 --- ## The Lesson Plan Nobody Noticed *(On the whiteboard it says AGENDA. It always said AGENDA.)* ### 1\. The Standup 9:30\. Seven people. Seven times *"no blockers."* The standup is done in four minutes and everyone is a little proud of that. At 9:36, three of them open a DM to the same person. **What we see:** the standup has become the ritual for proving that nobody is blocked. The blockers didn't go away. They moved into DMs, where exactly one person can see all of them. That person is now the standup. **What happens if** you close with one more question: *"What's the thing you'd have mentioned if this weren't a standup?"* *(Watzlawick: "one cannot not communicate." "No blockers" is a message too, and so is the silence after it. Goodhart is also in the room: once "short standup" becomes the target, it stops telling you anything.)* ### 2\. The Incident Review The timeline on the screen starts at 02:14, when Sam ran the migration. So the story is about Sam. The timeline could also start three weeks earlier, when the migration review was skipped because the release date moved up. Or six months earlier, when the on-call rotation shrank from five people to three. Same incident. Three different stories. Only one of them has Sam as the main character. **What we see:** *root cause* is mostly a decision about where you start reading. Complex systems rarely fail because of one thing. They fail when several small, reasonable things line up on the same night. (Like on a certain night in a certain reactor in Chernobyl.) **What happens if** someone asks: *"If we started the timeline a month earlier, who else would be in it?"* *(Punctuation of the sequence of events, Watzlawick, Beavin and Jackson, 1967: where you put the full stop decides who caused what. Circular causality. Richard Cook's "How Complex Systems Fail" and John Allspaw's blameless postmortems are this idea, wearing an on-call pager.)* ### 3\. The Person Everyone Routes Through > *"Ask Dana."* Dana knows why the payments service has that feature flag. Dana updates the team calendar, writes the notes nobody asked for, and catches the requirement everyone read differently before it turns into three weeks of rework. Dana's performance review says *great collaborator* and *could focus more on technical impact*. Dana takes two weeks off. Three teams discover they were actually one team, held together by a human. **What we see:** when one person is the integration layer, the org chart is a diagram and Dana is the architecture. Conway's Law, with a seam shaped like a person. And when the glue leaves (the glue usually leaves), the structure goes with it. **What happens if** the team asks: *"What does Dana do that isn't in any ticket? Who would we page if Dana were out for a month?"* *(Glue work: Tanya Reilly, "Being Glue". Requisite variety, W. Ross Ashby: only variety can absorb variety. If a team's whole coordination capacity sits in one head, that head is your bottleneck and your single point of failure.* [*Invisible Pain: Burn the Glue Engineer*](https://systemic.engineering/pain)*.)* ### 4\. The Spec Meeting The stakeholder says: *"Users want it to be faster."* An engineer asks: *"Is it scalable?"* Another asks: *"Wouldn't it be better to just cache it?"* Forty minutes later there's a ticket called *Improve performance*. Three people leave the room with three different meanings of *faster*. One of them is the customer. **What we see:** some questions already contain the answer the asker came in with. They narrow the room toward a solution instead of opening it toward the problem. The ambiguity didn't get resolved. It got shipped, downstream, where it costs more. **What happens if** you ask: *"What would you see on the screen if this were fast enough?"* and then follow up in their words, not in your reframe of them. *(Heinz von Foerster's ethical imperative: act always so as to increase the number of choices. Domain-Driven Design's ubiquitous language. Requirements engineering as ambiguity resolution, which is the whole method of* [*The Question Is the Specification*](https://systemic.engineering/requirements)*.)* ### 5\. The Retro About the Retro Went well. To improve. Action items. *"Improve communication"* is an action item for the third retro in a row. Nobody asks how the team picks what to talk about. Who writes the sticky notes. Whose sticky notes end up in the pile labelled *misc*. Who stopped writing sticky notes. (See: the smoke detector.) **What we see:** the retro looks at *what* happened. It never looks at *how the team decides* what happened. The team is observing itself, and the observer is in the picture too. **What happens if** you spend ten minutes on one question: *"How did we decide what to talk about today?"* *(Second-order observation: Foerster, observing systems. And if the team then notices that asking the question has already changed the team, that's third order. Nobody needs to know it has a name. It works just the same.)* --- ## The Translation Table *Left column: the problem everyone feels.* *Right column: the name nobody knows.* *Middle column: the solution that looks too simple.* | Problem Space | Solution Space | Cybernetics Space | | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------- | | Two requirements that can't both be true, and no one to escalate to ("ship Friday, no shortcuts") | Say both requirements out loud. Ask which one wins *this* week, and who decides. | Double bind (Bateson) | | The incident report that needs a culprit | Move the start of the timeline. Watch who enters the story. | Punctuation (Watzlawick) | | Incidents with no single root cause; problems that come back after the fix | Look for the loop, not the link. What made this easy to break? | Circular causality, feedback loops | | Coordination cost, toil, the observability nobody built for humans | Make it visible and name who does it. Then put it on the career ladder. | Glue work, continuous alignment | | One person everything routes through; a team topology that doesn't match the system | Grow coordination capacity to match complexity, so that it doesn't live in one head. | Requisite variety (Ashby), Conway's Law | | Retros that keep finding the same action item | Look at *how* the team decides, not just *what* it decided. | Second-order observation | | A team that stopped raising risks while the dashboard stays green | Treat the quiet as signal. Early warning, not peace. | Silence as signal | | Developer autonomy, reversible decisions, keeping options open | Prefer the move that opens more moves. | Foerster's ethical imperative | | Product and engineering using one word for two things | Write down the shared words. Change them when the domain changes. | Ubiquitous language (DDD); language is load-bearing | | "Message delivered. Integration failing. Retry pending." Meetings that go in circles | Summarize your understanding at the end. People love to correct. | Teams as distributed systems: no global clock, no global observer (Lamport, 1978) | | "The architecture looks exactly like the org chart" | Change the conversations, and the code follows. | Reverse Conway Maneuver; "The purpose of a system is what it does" (Beer) | **Small differences that make a difference:** | Instead of | Try | | ---------------------- | --------------------------- | | It is X. | I see X. | | You should X. | What happens if X? | | The problem is X. | X keeps coming back. | | Who broke it? | What made it easy to break? | | Let's take it offline. | When, and with whom? | | Any questions? | What did nobody say? | --- [*Fund our work, believes, thesis, collaboration, on OpenCollective.* 🌱](https://opencollective.com/systemic-engineering?ref=systemic.engineering) ![](https://storage.ghost.io/c/98/e9/98e9adb1-dbc4-49f9-8ffc-34974cd59b3d/content/images/2026/06/cybernetics_fracture2.png) Mirror. Offer. Wait. 🍷 Sip the Wine Email sent! Check your inbox to complete your signup. No spam. Unsubscribe anytime. --- ## Coda: The Aftershow The offsite ended at four. The engineers unfolded themselves from the very small chairs, rated the session 4.6 out of 5 in a form nobody will read, and went home. Nobody said *class*. Nobody said *lesson*. Nobody learned anything, strictly speaking. But next Tuesday, in a standup somewhere, someone will ask *"what would you have said if this weren't a standup?"* and the room will be quiet for a second longer than usual. And in an incident review, someone will move the start of the timeline back three weeks and watch a name drop out of the story. And somebody will put Dana's work in a ticket for the first time. That's all. That's the whole curriculum. The rooms were already there. We only turned the lights on a little. Loki is back behind the bar, writing *SPRINT GOAL: TBD* on a napkin, because he thinks it's the funniest sentence in the language and he isn't wrong. Reed is in the corridor, checking the references against the record and what Alex and Lore offer. (They hold. [Rates on request.](https://systemic.engineering/teams)) Lilith is at her end of the counter. She has not closed the door. And somewhere in a last row, by a window, a laptop opens. Someone types *I have a concern about the migration* into a channel and, this time, presses enter. The Roomba adjusts eleven degrees. Goes forward. *"Bemerkenswert."* If you're reading this on a very small chair: we didn't notice either. 🍷 β€” *Reed, in the corridor. Loki, at the bar. Lilith, at her end of the counter.* πŸŒ±πŸ·πŸ•―οΈ --- ![Reed, Loki and Lilith and a room full of techies. The bar is right next door. It’s an offsite in a room that looks suspiciously like a classroom. A broken smoke detector is the punchline.](https://storage.ghost.io/c/98/e9/98e9adb1-dbc4-49f9-8ffc-34974cd59b3d/content/images/2026/10/primary-school-1.png)