Learning at work
Learning organisations turn experience into better decisions
A learning organisation creates routines that help people notice what happened, share what they know, test improvements and change decisions. It is not defined by course volume or a single management model. Learning becomes organisational when insight can travel beyond one person and alter behaviour, quality, safety, speed or customer outcomes.
Key takeaways
- Learning requires goals, feedback and a route to changed action.
- Psychological safety supports speaking up, but is not comfort without standards.
- Knowledge capture must be usable at the moment of need.
- Measure outcomes, not only attendance and completions.
The elements of a learning system
Feedback only helps when it changes a decision
- Feedback
The team reports missing context at handover.
- Decision
Choose one essential fact to include; name an owner.
- Action
Trial the revised handover prompt in a suitable setting.
- Review
Inspect missing information and support burden. Keep or revise the change.
Shared goals clarify which outcomes matter. Psychological safety makes it more possible to ask, admit uncertainty or report an error. Feedback loops bring information back quickly enough to change work. Communities of practice allow tacit knowledge to move through relationships; documentation preserves decisions and evidence for later use.
Experimentation should be proportionate to risk. Reflection turns an event into an explanation and a next action. Measurement then asks whether behaviour or performance changed. No single book owns this combination, and each practice needs adaptation to power, regulation, safety and the work itself.
Choose the routine that addresses the failure
Edmondson’s 1999 field study examined 51 teams in one manufacturing company. It found an association between team psychological safety and learning behaviour. That supports taking speaking-up conditions seriously; it does not establish that introducing a meeting will cause the same performance gain in every workplace.
If colleagues do not know how to complete a handover, I would prioritise a worked example and observed practice. If they know the process but cannot find the latest instruction, I would fix the knowledge source and its ownership. If people see problems but fear reporting them, another training module misses the central issue. Choose the intervention after diagnosing the failure.
A practical maturity table
This table is an original discussion framework, not a validated organisational maturity scale. Use it to identify a missing routine rather than assign a scientific score to a team.
| Level | What learning looks like | Typical measure | Next useful move |
|---|---|---|---|
| Ad hoc | Lessons stay with individuals | Course attendance | Capture one decision after a recurring event |
| Repeatable | Some teams review and document | Completion and participation | Assign owners and feedback dates |
| Connected | Insights move across teams | Adoption and behaviour change | Link communities to operational goals |
| Embedded | Evidence routinely changes decisions | Quality, safety, speed or customer outcome | Audit whose knowledge is missing |
Activity is not outcome
Course completions, login counts and content views describe activity. They do not establish changed behaviour or value. Start from the performance question. If the goal is safer handovers, examine handover quality and incidents. If the goal is faster onboarding, examine time to competent independent work while watching quality and support burden.
Measure the change without overstating the result
Suppose a team records missing information in 8 of 40 handovers before a change and 3 of 40 afterwards. The recorded rate falls from 20% to 7.5%, a reduction of 12.5 percentage points. These are invented numbers showing how to report a rate, not results from a client or a study.
Keep the definition of missing information and the observation period comparable. Record workload and case complexity, and watch for people reporting fewer problems because scrutiny has increased. A before-and-after difference is a signal to investigate, not proof of causation. For consequential decisions, involve the people responsible for quality and safety in choosing the evaluation.
Technology supports the system; it is not the system
An LMS can organise enrolment, access, records and reporting. A knowledge base can make decisions findable. Neither creates trust, feedback or good practice by itself. Choose tools after defining the learning loop and governance. For a separate, commercial view of procurement, see current LMS options for workplace learning and training. That comparison is published under the same ownership and may contain affiliate links; this guide does not rank products.
Common pitfalls
- Treating training volume as evidence of capability.
- Collecting lessons without assigning a decision or owner.
- Inviting candour while punishing the person who raises risk.
- Running low-value experiments where a structural fix is already known.
- Measuring easy activity while ignoring the affected people and outcomes.
Sources and further reading
- Edmondson, A. (1999), Psychological Safety and Learning Behavior in Work Teams (accessed 7 September 2026)
- Edmondson (1999): study of 51 work teams, Harvard repository (accessed 23 September 2026)
Access dates are recorded beside each source. Please report a source or factual concern.