Here is a story from a small, made-up product reviews desk, the kind of team that tests gadgets and household gear and writes up what it finds. Picture four people in a shared flat-turned-office: an editor, two testers and a part-time layout helper. Their problem was not a lack of products or a shortage of ideas. It was that worries about the work kept leaking into every hour of it, and the fix they landed on was a ten-minute daily meeting with nobody but their own concerns.
The week everything felt urgent
It began with a dull Monday. A courier delay meant a pair of headphones would arrive late. A tester remembered that a charger had been left at the wrong port count on the comparison sheet. The editor was fretting about whether a newsletter would go out on time, and the layout helper wondered aloud whether the photo sizes would break the page again.
None of these was a disaster. Together, though, they produced a room that hummed with low-level alarm. Conversations were interrupted. Test sessions were cut short to check on parcels. By Wednesday, nobody had finished a full review, and the editor described the mood as “busy but going nowhere”.
The idea: give the worrying its own appointment
A tester had read about a habit sometimes called scheduled worry time. The rule is plain: fix one short slot each day for concerns, jot down any that appear outside it, and refuse to chew on them until the slot arrives. The team shrugged, then agreed to try it for two weeks.
They chose ten minutes at the end of the afternoon, just before the tea round. A single sheet of paper stayed on the shared table, with a pen tied to it by string. The ground rules were few:
-
Anyone can add a line at any time, in under ten words.
-
Nobody comments on a line until the meeting.
-
At the meeting, each line gets one of three marks: do, ask, or drop.
-
When the ten minutes end, the meeting ends.
What the first meeting looked like
The sheet had eleven lines. “Headphones late?” became an “ask”: someone would email the courier once, and that was that. “Charger ports wrong?” became a “do”, assigned to the tester who had noticed it. “Newsletter on time?” turned out to hinge on a single missing paragraph, so the editor wrote the paragraph there and then.
Four lines got the “drop” mark. One of them, a worry about whether a competitor might cover the same product first, had been quietly draining attention all week. Saying it out loud in the slot made it sound small. Nobody could do anything about it, so it was crossed out and left on the sheet as a small piece of history.
What changed in the second week
The room got quieter, which surprised everyone. The interruptions dropped because the question “should I mention this now?” had a ready answer: write it on the sheet. The testers reported longer unbroken stretches with the products. The layout helper said the nicest part was no longer being asked, three times an afternoon, “are the images sorted yet?”
There was also a subtle shift in what ended up on the sheet. Early entries were vague and emotional, such as “this might go badly”. By the second week, they had become concrete, such as “photo crop for the kettle review” or “confirm shipping address for the next unit”. Writing a concern briefly forces it to become specific, and specific concerns are far easier to act on.
One more effect showed up around day ten. The testers began estimating their own timelines more honestly, because the sheet showed how often a delay had been guessed at rather than known. A line such as “unit might not arrive” tended to resolve into a single email and a firm date. The editor started planning the publishing calendar with a little slack, and the Friday scramble largely disappeared. Nobody had planned these gains; they were by-products of giving concerns a fixed place to live.
Where reading fits in
The team kept a habit of reading around the craft. When the editor wanted a refresher on structuring a consumer write-up, they looked at a post on tracking down dependable, even-handed product write-ups, and added a “do” item: tidy the template. The point was not to chase that topic in the meeting, only to feed the list with practical tasks.
A different tester, deep in a travel-gear roundup, noted a worry about luggage logistics and pointed colleagues to a piece on a straightforward approach to hiring a vehicle as background reading for a feature idea. The idea went onto a separate “someday” notebook, so it would not pad out the worry sheet.
An aside on how others talk about attention
While discussing why the sheet worked, a team member mentioned having seen a gaming-flavoured website that introduces itself as an information and software company in a roundup of web tools. Nobody on the desk used it or planned to, and the aside ended there. The team returned to the point that a sheet and a pen were doing the job.
The hiccups they hit
No habit arrives perfectly. The team ran into three problems.
-
Meeting creep. In week one, the ten minutes stretched to twenty. They fixed it by putting a kitchen timer on the table.
-
Hidden worries. A tester kept a few concerns off the sheet out of embarrassment. The editor responded by adding some of their own, plainly worded, which made it easier for others to be honest.
-
Real emergencies. One afternoon a broken file needed fixing right away. The team agreed that true urgencies skip the queue, with one test: would waiting until the slot cause actual damage?
Taking the routine home
Four colleagues are optional. A solo reviewer, a family comparing appliances, or a student collecting notes for a project can use the same pattern.
-
Choose a slot that already exists in your day and keep it to ten or fifteen minutes.
-
Keep one sheet where you can reach it without opening anything.
-
At the slot, mark each line as do, ask or drop.
-
End on time and let the leftovers wait.
-
After two weeks, count how many lines mattered. That count is your evidence for keeping or changing the habit.
The desk in this story still holds its ten minutes. The sheet is now a pad, the string is a bit frayed, and the editor says the real product of the experiment was not a calmer office but a better backlog. The worries got written down, the useful ones turned into tasks, and the reviews, at last, got finished.