The employee survey results are in, and a clear majority agrees with the statement “Learning is a priority here”. In the same week, a team lead asks whether next month’s training can be dropped. The quarter is tight.
Both are sincere. That is exactly what makes learning culture so hard to pin down. It shows in what people do when nobody is asking, while a survey mostly captures what they think about it.
This article comes at it from the other side. It describes the everyday scenes that give a weak learning culture away, the causes behind them, and a way to read your current state without another survey, using traces your systems already store. The phase model behind that reading is covered in full in the white paper “Corporate Learning Culture”, which you can download free of charge.
Five scenes every L&D lead will recognise
None of them is alarming on its own. Together they form a pattern.
- Learning time is the first thing cut when a project falls behind.
- Business units order training from L&D as if from a supplier, with a preferred date and no contribution of their own.
- Questions on a topic end up with the same three people, usually by direct message.
- The lessons-learned session after a project is postponed, then forgotten.
- Whoever solved a tricky problem talks about it at the coffee machine and nowhere else.
The last scene looks harmless and costs the most. The fix exists. It has no place where it can reach the next person with the same problem. Panopto (2018) put a number on the waiting: employees spend 5.3 hours a week on average waiting for information that someone else holds. A good share of that is probably knowledge of exactly this kind, said out loud once and never written down.
Why appeals fall flat here
The obvious reflex is communication from the top: a mission statement, a campaign, a learning day in the calendar. None of that hurts, but it works on the wrong lever. A learning culture in which everyone learns and teaches cannot be ordered into existence, because its decisive step is voluntary: someone who knows something records it and shares it without anyone requiring them to. That willingness grows out of wanting to help colleagues, and it disappears surprisingly fast when sharing is cumbersome, when nobody notices, or when the person’s own manager never does it. An appeal changes none of those three things. At most it adds to the guilt of the people who wanted to share anyway.
The causes lie elsewhere. In most organisations there are two.
The route from knowing to recording is too long
Picture a shift supervisor who has just fixed a fault on a production line that no manual covers. What would she have to do so the next shift benefits? In a typical organisation the answer is a request to L&D, a briefing, an alignment meeting, a follow-up question and a sign-off. Weeks later there might be a training module. By then she has explained the fault twice over the phone.
This is where learning culture fails on tools built for specialists. If a short explainer video requires training in an authoring tool first, the circle of authors stays small however motivated the workforce is. The white paper sets a strict benchmark: producing a video should take a few minutes, or nobody will share. What it looks like when subject experts produce their own content, and where it gets sluggish after the first weeks, is described in our article on expert-generated content.
Learning has only one address
The second cause is structural. In many organisations learning belongs to L&D in the same way payroll belongs to HR. That creates order. It also has a side effect that rarely gets said out loud: everyone else sees themselves as a customer. And customers wait for delivery.
Where learning happens in the flow of work, the work is divided differently. L&D steers, sets standards and keeps the infrastructure running. Content comes from the teams that hold the knowledge, and the shared pool belongs to everyone who contributes to it. Leadership shows that this is wanted by recording what it knows itself. Without that last part, the first two do not get far.
Reading the traces your systems already hold
You do not need to ask anyone whether your organisation lives a learning culture. The answer sits in systems you already run. Each of them records, in passing, who creates knowledge, who uses it and where it gets stuck. Four places are worth a look.
The author field in your LMS
Sort the content on your learning platform by creator. The number of courses matters less than the number of different names and the departments they belong to. If nearly every name is from L&D or HR, learning is a central service. If names from sales, operations or IT appear, the organisation is writing along. If the platform is well stocked but people open little beyond mandatory courses, the article on building a corporate academy goes into that problem.
The edit history of your wiki or intranet
What counts here is when a page was last edited and by whom. Pages nobody has touched in years are an archive. The circle of editors is just as telling: two editors at head office, or the people who run the process every day?
The path a question takes in team chat
Search open channels for phrases such as “does anyone know how” or “who knows about”. Two observations are worth making:
- Is the question answered in the channel, where others can read along, or does the conversation move to a direct message?
- Do the same people always answer?
If it moves to private messages, the answer is lost to everyone else. If the same people always answer, you are looking at a single point of knowledge well before anyone calls it that.
Meeting agendas and minutes
The least obvious place. Take the agendas of a quarter’s recurring team and department meetings and check whether there is ever a slot where someone shows what they learned or solved. A slot like that costs a few minutes and tells you more about a department’s culture than any brochure on staff development.
None of these places needs a new tool or a new data collection exercise. If you plan to analyse anything at the level of individuals, clear it with your data protection officer and any employee representatives before you start. For a diagnosis, department level is enough anyway.
What the traces say about your phase
The white paper describes four phases on the way to a learning culture in which knowledge moves through everyday work. Reading the traces places you in it fairly reliably:
- In the classroom-training phase, the LMS mainly manages dates and attendance lists. The wiki barely moves, and direct messages dominate the chat.
- In blended learning there is digital content, but as preparation and follow-up for seminars, and all of it comes from L&D.
- In the e-learning phase, individual subject experts appear in the author field, usually commissioned by L&D. The wiki is alive in some departments.
- With knowledge sharing in the flow of work, you find many names in the author field, current wiki pages, answers in open channels and a fixed place in meetings for what was learned.
Hardly any organisation lands cleanly in one phase. A typical picture is a sales team that has been making its own explainer videos for a while, next to an operations unit whose knowledge travels only through shift handovers. Those differences are the real finding. They show where role models already exist for other departments to follow, and where the next step will take the least persuading.
Where reading the traces falls short
One objection is fair: a lot of learning never touches a system. The shift supervisor who shows her successor something at the machine leaves no trace. In areas where people have no desk of their own, the traces can paint too bleak a picture. How large that effect is, we do not know, and we are not aware of any study that quantifies it properly.
The employee survey also deserves more credit than this article has given it so far. It is quick, comparable from year to year, and gives the board a number that fits in a report. Anyone who has to defend a learning budget knows what that is worth. It answers a different question. Laid side by side, survey and traces say more than either alone, especially where agreement is high and the traces are thin.
That leaves one question you can only answer after reading the traces: if a name from a business unit is soon to appear in your LMS author field, whose name would it be, and what is stopping that person today?
The phase model, with characteristics and examples for each phase, and the three pillars for moving into the next one, are in the white paper. It arrives by email once you have filled in the form.




