Community of Practise
Build shared expertise. Apply better practice. Demonstrate value.
Improvement & pilot actions
Give each action an owner, due date and objective evidence. Completion and effectiveness are separate decisions.
Pilot performance & value
A trend chart supports review. It is not an SPC control chart; target lines are not statistical control limits.
Community review & health
The readiness check flags missing records. The reviewer must judge the quality and adequacy of the evidence.
Community working registers
Capture practitioners, conversations and reusable knowledge. Links are references to records; files and invitations are managed outside this app.
A community that improves practice
A Community of Practice (CoP) is a continuing learning partnership among people who share a field of work and learn through regular interaction. This app uses your title “Community of Practise”; “Community of Practice” is the usual noun form in published guidance.
Start and sustain a useful community
- Agree a domain and useful problems with practitioners. Establish boundaries and sponsorship without turning the community into a status-reporting forum.
- Invite a mix of experienced and developing practitioners. Enable questions, disagreement and respectful challenge.
- Set a workable rhythm: case clinics, process visits, demonstrations, peer reviews, mentoring and short experiments.
- Capture the knowledge that others can reuse, with an owner, evidence, review date and a clear approval status.
- Trial ideas through an authorised improvement project. Record what worked, what did not and what conditions mattered.
- Review participation, knowledge reuse and practical outcomes. Adjust activities and prepare facilitator succession.
Roles and healthy participation
The sponsor removes barriers and supports resources. The facilitator creates useful conversations. Practitioners contribute cases, questions and experience. Knowledge owners maintain reusable material; authorised process owners approve changes. Roles may be shared, and participants need not contribute in the same way.
Support quieter members with advance agendas and written contributions. Avoid blame, dominance by experts and compulsory attendance as the only measure of engagement. Use agreed communication channels and respect accessibility needs.
Turn conversation into controlled knowledge
Distinguish personal experience, a testable hypothesis, a reviewed lesson and an approved practice. Record applicability, evidence, limitations, ownership and revision. Review content at agreed intervals; retire obsolete guidance. Share restricted or customer information only through approved channels with the right access.
A lesson is not a controlled instruction. Transfer a validated practice through the organisation’s document, training and change-control processes. The community cannot approve deviations from contractual requirements unless separately authorised.
Measure value without rewarding busywork
Use a balanced set of measures: quality of interaction, useful knowledge created, application of that knowledge, and process outcomes. Attendance and document counts show activity, not impact. Capture a short value story: challenge → learning → application → observed result.
Compare like-for-like denominators and product mix. A positive trend after a community initiative does not prove causation. Look for competing explanations, evidence of adoption and sustained performance.
Community, project team or committee?
A community sustains learning and shared practice across time. A project team delivers a bounded objective. A governance committee makes formal decisions within its authority. A community can support a pilot project and feed governance without replacing either.
Worked process control example
The fictional Surface Engineering Community shares preparation and coating experience across Quality, Engineering and Operations. Its pilot addresses an 8% adhesion failure rate. Members compare cases, trial preparation controls, peer review the evidence and transfer an approved method through controlled documentation. The latest result is 0.5%; the community still requires lot-based evidence and follow-up before claiming sustained success.
Standards & specification references
Record the exact drawing, process specification, test method and revision for every application project. Approved practice must remain within those requirements.