Different industries, different risks, the same pattern: poor relationships, siloed departments, low trust, high social risk, knowledge held locally instead of shared freely. It was tempting to call these safety problems. They weren’t. They were signs the organisation wasn’t functioning as a community.
Community is not soft. It is performance architecture.
A community is a group of diverse people aligned around a shared purpose, willingly contributing their knowledge, effort and support so others can succeed. When contribution feels worthwhile, performance improves.
Seven conditions that shape contribution
Over time I saw seven conditions that decide whether people contribute. Not seven programmes, seven conditions, each with a question:
- Purpose (CoNexus), Is effort connected to something people believe is worth contributing to?
- Collaboration (CoSolve), Can departments solve shared problems together?
- Interaction (CoSense), Do everyday conversations and processes create contribution?
- Narrative (CoScript), What story do people believe will happen when they speak, share or try something different?
- Leadership (CoShift), Do leaders invite contribution, or increase the social risk of it?
- Insight (CoSteer), Do metrics help leaders know what to adjust, strengthen and scale?
- Capability (CoScale), Does everyday work grow the organisation’s ability to perform?
How contribution becomes capability
Capability grows through everyday work. We get better by solving real problems together and supporting each other’s success. Contribution becomes capability; capability strengthens performance.
These seven questions sit behind the case studies in The Invisible Script, and behind how I help organisations turn contribution into performance. Which of these seven would make the greatest difference in your organisation right now?