Culture in Practice
Show inclusion through a concrete decision: what was planned, who was missing, what changed and what remains unresolved.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Technology and software · Healthcare · Financial services · Retail and hospitality
Overview
Culture in Practice is a focused editorial page about a fictional equipment-trial decision at Northstar Services. The schedule originally suited the day shift. An evening-shift lead challenged the plan, contributed a voice note and helped move one trial. The page preserves the cost and uncertainty of that response: other trials remain in daytime and night-shift participation is still unresolved.
The structure makes an abstract value visible through a specific scene, a before-and-after account, a quotation and discussion questions. Use it to publish a permissioned story, not a catalogue of value definitions or a claim that every decision works this way. Keep approved policies and company values at their maintained sources.
Standards & compliance context
- Use permissioned real accounts or clearly labeled fiction.
- Do not expose confidential project or personal information.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
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
Follow the original plan, challenge and response.
-
What the team planned, what was said, and what they did instead. Before: the schedule worked for the people who built it 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. The pause: a colleague speaks up at shift handover 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. After: one trial moved, and the reasoning was published 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. What changed 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. What stays open 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
-
Day-shift equipment project team We treated "nobody objected" as "everybody knew." Those aren't the same thing, and it took someone not in the room to show us. Project lead Northstar Services (fictional)
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.
How to use this template
- Select one decision where a value affected the outcome.
- Verify the original plan, affected roles, contribution route and actual response with participants.
- Write the story in three moments: before, the conversation and after.
- State both what changed and what remains unresolved.
- Obtain permission for attributed words and images, then confirm the route for future stories.
Best practices
- Make the affected shift, location or role visible.
- Show a tradeoff rather than claiming effortless consensus.
- Explain what happened to employee input.
- Keep the story separate from official policy or procedure.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does Culture in Practice include?
One fictional equipment-trial story told in three moments, a comparison of what changed and what remains open, a project-lead quotation and questions readers can apply to their own decisions.
Is this a directory of all company values?
No. It is a focused editorial story showing a behavior in one decision. Link to the company’s approved values and policies where relevant instead of duplicating their wording.
How should we adapt the example?
Choose an actual decision and obtain the participants’ agreement. Explain who was affected, how their views were heard, what changed and what remains unsettled. Verify details and quotations before publishing.
Why keep the unresolved questions?
They make the tradeoff understandable and avoid presenting a perfect outcome that the evidence does not support. In this example, some trial timing and night-shift participation remain open.
Who should maintain the page?
A communications or people-team editor can coordinate with the participants and decision owner. Review it if the outcome changes or the story no longer reflects the current situation.
Can managers use it for discussion?
Yes. The closing questions help a team identify who is absent from a decision, offer ways to contribute outside a meeting and explain afterward what changed. It is a discussion aid, not a substitute for employment policy or an operating procedure.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
-
Compare clinical communication platforms and workforce apps for hospitals. Learn how to reach frontline healthcare staff without EHR logins in 2026.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
-
Clinical Staff Engagement with MangoApps: unify schedules, training, and HR self-service in one mobile app for frontline healthcare teams.
-
Healthcare employee engagement ideas to reduce burnout, boost retention, and improve patient outcomes in your health system.
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Culture in Practice ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
