Fictional sample article for template testing. The timings below are part of the invented scene, not research findings.
The invitation said “Quick catch-up”. It had a fifteen-minute slot and no agenda, which gave everyone the freedom to arrive with entirely different ideas about why they were there.
Jo brought a notebook. Chris brought a problem. Morgan brought the first of several sentences beginning, “While we’ve got everyone here”.
At ten o’clock, the meeting began with a discussion about whether the screen was visible. The screen was visible to everyone except the person sharing it, who understandably wanted further reassurance.
A reassuringly small objective
The team needed to choose a date for a modest internal announcement. There were two possible dates. Both were weekdays. No specialist equipment was required.
Jo suggested Thursday.
Chris wondered whether Thursday might be too soon. Morgan wondered whether Friday might be too late. Someone asked what had happened last time, and the meeting acquired a historical dimension.
How the morning developed
By the time the original slot ended, the conversation had reached the following stages:
| Time | Subject | Outcome |
|---|---|---|
| 10:00 | Choose an announcement date | Two dates remain available |
| 10:08 | Recall the previous announcement | Three versions of events |
| 10:15 | Discuss who needs consulting | Another meeting suggested |
| 10:26 | Review the wording | Document opened |
The document contained a sentence that everyone broadly liked. This was unfortunate. A sentence everyone broadly likes can sustain a remarkable amount of discussion about whether it should be slightly different.
The word “soon”
“Soon” sounded friendly but imprecise. “Shortly” sounded formal. “In the coming days” sounded as though the announcement might involve a national address.
The team tried removing the sentence. The paragraph then needed an opening sentence.
The person who was not in the room
Eventually, someone mentioned a colleague whose opinion would settle the matter. This colleague was not attending because the invitation had described the meeting as a quick catch-up.
A message was sent. While waiting for a reply, the group discussed what the colleague would probably say.
Actions were captured
Jo had been taking notes. There were several underlined headings and one small drawing of the meeting-room plant.
The agreed actions were:
- Confirm the preferred date.
- Check the wording with the absent colleague.
- Circulate the final version.
- Arrange a short follow-up if required.
These were reasonable actions. They were also, on closer inspection, the work the meeting had been arranged to complete.
“Let’s take this offline,” said Morgan, from a room in which everyone was already physically present.
Back to the actual work
Chairs moved. Laptops closed. Someone collected three mugs while maintaining that only one was theirs.
Outside, the morning had continued without supervision. Jo returned to the desk, opened the original task and found a reply from the absent colleague.
“Thursday works. Wording looks fine.”
Jo added the date, sent the announcement for scheduling and crossed something off the list. It took less time than finding the meeting room had taken.
A new invitation appeared before lunch. Fifteen minutes. Just to close the loop.
