Before the trials were booked, who hadn't been asked?
Fictional example from Northstar Services. Three equipment trials were due to run on the production floor, and the schedule had been agreed entirely during day-shift hours. The people who would run the equipment through the evening hadn't seen it yet. This is the story of the week a colleague asked the team to stop and check, and what the team did next.
One decision, in three moments
What the team planned, what was said, and what they did instead.
The project team planned three trials of a new pallet-wrapping unit over two weeks. They booked each one in the same window, mid-morning to mid-afternoon, because that's when the team and the vendor's technician were all on site. The schedule went out on the project page and in the day-shift huddle notes.
- All three trials were set between 9:30 am and 2:30 pm.
- The evening shift would use the unit daily if it was adopted, but no one from that shift was invited.
- No one had raised an objection. The team read that as agreement.
An evening-shift lead read the schedule at handover and found the project lead before leaving. She said: "I'm not asking you to cancel anything. I'm asking you to wait until the people who'll run this at 6 pm have seen it. We'd find the problems you can't see at 10 in the morning." The project lead said the vendor's technician was only booked for that week and a delay would cost time. They agreed to hold the decision for two days while the team asked for comments properly.
- The evening-shift lead recorded a short voice note with her concerns, because she couldn't attend a day-shift meeting.
- The project lead played the note at the next team stand-up, so the team heard it in her words rather than as a summary.
- Some of the team were frustrated about the vendor's tight window. That was said out loud and not smoothed over.
The team moved the second trial to the start of the evening shift so the people who'd use the unit could run it themselves with the vendor's technician. The other two trials stayed where they were. The project lead then posted a short note on the project page that said what changed, what didn't and why.
- The vendor's technician extended one visit by a few hours to cover the evening slot.
- The published note named the decision, who made it and the two questions still unanswered.
- The trial results will be reviewed with both shifts present.
What changed, and what's still open
This didn't resolve neatly. Here is the honest account the team posted, lightly edited.
Specific changes the team made after the pause:
- Trial two moved from late morning to the start of the evening shift.
- The evening shift ran it hands-on, and their findings go into the same review as the day-shift trials.
- Voice notes are now accepted as comments on project decisions, alongside written comments.
- The project page lists the shift each trial runs on, so a gap is easy to spot.
Questions the team hasn't settled:
- Trials one and three still run in day-shift hours. The team isn't sure that's enough coverage.
- The night shift hasn't been consulted. The team hasn't decided how to reach them before the review.
- The two-day pause was a judgement call. There's no agreed minimum notice for comments yet.
- The vendor's schedule limited the options. Nobody knows whether a longer pause would have been possible.
In the project lead's words
“We treated "nobody objected" as "everybody knew." Those aren't the same thing, and it took someone not in the room to show us.”
Try it with a decision of your own
A few questions to take to your next team huddle
The team didn't have a special process. They noticed who wasn't part of a decision, asked them, and said plainly what they did with the answer. You can try the same on something you're planning now.
Questions to ask before you lock a plan
- Which shift, site or role will live with this decision but wasn't in the room when it was made?
- How could they comment without attending a meeting? A voice note, a message or a conversation at handover would all do.
- If you hold the decision, what does it cost, and who needs to know about that cost?
- What will you publish afterward: what changed, what didn't, and what's still unanswered?
If you'd like to share a story like this
Stories work best when the people in them have agreed to be included and have read the final text. Talk to your site's internal communications partner or your team lead about adding yours. Include what was hard, not only what went well.