plan.md
Your plan
What you learned and what you'll do, block by block, with ideas for the months ahead. Suggestions, not a schedule.
Updated 2026-11-18. Confidence in this plan: 97%. Confidence is calculated from the plan: evidence from other people on each block, reality checks done, and next steps and an exercise card to act on. It stays under 70% until the plan is ready to finish.
Your community is what it was when you started. What has changed is how well you understand it, and what you'll do about it.
- You know most about: Benefit
- Start with: Benefit
Topic by topic
Where your community is on each part of the pyramid, as you now see it, and what you could do next.
Benefit
Where we are: Your members are not short of interest so much as permission: nobody has approved their time out loud, and the call slot clashed with transport planning's cut-off. What you heard: Three members said the sessions rarely touched their own work: one gain came from a colleague, one from the sessions, and a warehouse licence gap blocks trying anything (Member interviews). None of four members and line managers had heard an explicit yes to working time, the sponsor has never said it to line managers, and one operations manager would agree one hour a month on conditions (Member interviews).
What we could do next: Move the monthly call off 13:00 and keep it as short news only, with questions going to the small group. Offer the warehouse operations manager one supervisor hour a month from January tied to shift handover notes or damage reports. Take the time and licence gaps to your sponsor together.
Trust
Where we are: Your members don't fear each other's behaviour. They feel exposed in a big channel of strangers and managers, and unclear data rules keep mistakes and questions private. What you heard: The customer service lead who still attends comes for the tips and doesn't really know the other members (Member conversation). Three members from three sites feel safe with how people behave, but the group is large, anonymous and mixed with managers, two asked for a smaller group, and one hid a Copilot mistake over unclear data rules (Member interviews).
What we could do next: Start three small groups by work area (office functions, customer service with transport planning, warehouse), five or six members each, no managers above team-lead level. Run 'Who we are' and one failure story there first, and get a written answer on what is allowed with personal data.
Sharing
Where we are: Your members will share, but only in small, bounded spaces: Excel answers, a failure story among five or six, talk with their own site, and not in the big channel. What you heard: Three members said what they'd share: Excel answers only, a failure story in a group of five or six but not in the channel, and talk with two other warehouse colleagues rather than the whole group (Member interviews).
What we could do next: Reply to private questions with 'good question, can you put it in your group so others can help', starting with Excel questions for the finance controller in the office group. Let a failure story open the small groups, and keep warehouse talk among the three warehouse colleagues. Use the big channel for news.
Purpose
Where we are: Your sponsor and your manager want different things, and neither has asked what members want, so the purpose is still nobody's own. What you heard: The sponsor's target is licence adoption, while your manager wants real examples of use, including one from operations by summer (Sponsor interview).
What we could do next: Treat your manager's ask for real examples, including one from operations, as the direction members can fill in. Keep the sponsor's licence target as one measure, not the purpose. Have each small group write its own idea of the purpose separately, then bring them together in spring, once one group has an example to point at.
Ownership
Where we are: Your members would take on small, bounded jobs now. What stops them is you fixing their work before they can get it wrong, and silence after an idea. It is not unwillingness. What you heard: Two of three active members would take on a bounded job now if they get no template, prep time in working hours and permission to post without a check; nobody wants a title (Member interviews).
What we could do next: Hand over three things: topics for the customer service and planning group go to the team lead, with 30 minutes of working time and no template. 'Prompt of the month' goes to the sales support coordinator, posted without your check. Call notes become five bullets from the finance controller. Offer jobs, not titles, and only follow up.
Identity
Where we are: Your real membership is about 20, not 34, and members stay for the tips and for their own area, not for a shared 'we'. Two members who work together weekly didn't know they were both in. What you heard: 27 of 34 answered the form: 11 keep me on, 9 yes but differently, 7 no, 7 silent; operations has 1 of 9 left, and nobody says 'we' (Survey).
What we could do next: Write to the 7 who said no, thank them and say they're welcome back. Tell the 20 who stayed the list is now 20, and send the three newest members a welcome asking what they expect. Put the customer service lead and the transport planner in the same small group.
Ideas for the months ahead
Suggestions, not a schedule. Your community and your organisation will have their own rhythm, quiet weeks and surprises. Take these up when they fit, change them, or drop them.
To start with:
- You could take the licence, the monthly hour and the handover notes pilot to your manager with your sponsor, using the Benefit block's findings on unapproved time and the licence gap.
- You could run the first customer service and transport planning session as a late-delivery case, with the 'Who we are' card as short written stories and ten minutes live.
- You could write to the seven who left and the 20 who stayed, so Identity starts from an honest number.
When that's moving:
- You could reply to private questions with 'good question, can you put it in your group', so Sharing moves into the small group.
- You could follow the first prompt of the month and the five-bullet call notes with only a thank-you, building Ownership with jobs rather than titles.
- You could share the data protection officer's one page with the coordinator as the check for tips, once it arrives.
Later on:
- You could start the office and warehouse small groups, then run the Purpose in plain sight card with each group writing separately.
- You could review whether the big channel should stay for news only, once you see where members actually talk.
Next steps from the coaching session
- Weeks 1-2: with your sponsor, tell your manager the real number is 20, no example exists yet, and ask for one licence and one hour a month from January for the handover notes pilot, with the measures agreed
- Weeks 1-2: ask the operations manager for the last few months of 'nobody told us' incidents, and the customer service lead for the Monday backlog times, as baselines
- Weeks 1-2: forward the fuel costs pivot question to the finance controller, chase the DPO page, and write to the seven who said no and the 20 who stayed
- Weeks 3-6: run the late-delivery case session with the customer service and planning group, with short written 'Who we are' stories and ten minutes live
- Keep the monthly call as short news at 14:30 for 30 minutes; leave the other two groups and the parked exercise cards until January
Reality checks still open
Nothing open.
Exercise cards from the coaching session
Activities to run with your community, if you wish. Your plan above says which come first.
- Challenge collection: see
exercise-cards/challenge-collection.md - Who we are: see
exercise-cards/who-we-are.md - Question-led session: see
exercise-cards/question-led-session.md - Purpose in plain sight: see
exercise-cards/purpose-in-plain-sight.md
Habits some leads find useful
Take or leave these.
- A short look at the warning signs in
method/community-pyramid.mdnow and then, or whenever something feels off. - Before a gathering, one focus and one member who runs part of it.
- After a gathering, one line in
evidence-log.mdabout what you noticed. - Every few months, answering the 12 community snapshot claims in
community-pyramid.mdagain.