Most of the expertise I’ve seen in my career didn’t come from a course or a certification. It came from doing work, making mistakes, talking to colleagues, reading things that weren’t assigned, and spending time thinking about problems that mattered. The formal training was there, certainly – the degree, the workshops, the mandatory compliance modules. But the real depth, the judgment that lets someone navigate ambiguous situations, the intuition that surfaces a problem before it becomes critical – that almost always grew from something less structured.
This pattern holds across fields. A surgeon develops surgical judgment not just from residency rotations but from years of observing complications, discussing cases with mentors over coffee, reading case studies outside their specialty, and reflecting on their own outcomes. A software engineer learns more about system design from debugging production incidents and code review conversations than from most architecture courses. A manager learns to read a team’s dynamics through repeated cycles of hiring, conflict resolution, and project delivery – none of which appears in an onboarding manual.
The reason informal learning shapes expertise so effectively is that it’s responsive to actual friction. When you encounter a real problem in your work, the motivation to understand it is immediate and concrete. You’re not learning for an exam or a credential. You’re learning because something isn’t working and you need it to work. That urgency, combined with the ability to test understanding against reality immediately, creates a different kind of learning than classroom instruction can provide.
How Informal Learning Differs From Formal Training
Formal training is designed for transfer – the assumption is that you’ll learn a principle or method in one context and apply it elsewhere. It’s efficient for breadth and for establishing baseline competence. But it necessarily simplifies. A course on project management teaches frameworks and best practices, but it can’t teach you how to manage a specific team with specific personalities, constraints, and history. That learning happens on the job, through trial and feedback.
Informal learning, by contrast, is embedded in context. You learn about communication by having a difficult conversation with a colleague and then reflecting on what worked and what didn’t. You learn about resource allocation by managing a project that has too many priorities and too little budget. You learn about your industry’s unwritten rules by observing how decisions actually get made, not how the org chart says they should be made.
This doesn’t mean formal training is irrelevant. Early in a career, structured learning establishes vocabulary, introduces frameworks, and prevents people from having to reinvent everything from first principles. But the ceiling of formal training is real. After a certain point, additional courses produce diminishing returns. The expertise that matters – the ability to make sound judgments in novel situations, to see patterns others miss, to know what to worry about – comes from accumulated experience and the informal learning that experience generates.
The Role of Networks and Conversation
Some of the most consequential learning happens in conversations that aren’t designed as learning at all. A colleague mentions how they solved a similar problem in a previous role. Someone asks a question in a meeting that makes you realize you haven’t thought about something carefully. A peer shares a tool or approach they’ve been experimenting with. These moments are invisible in training records, but they compound over time.
Professional networks function as distributed expertise. When you have access to people who’ve worked in different organizations, different roles, different industries, you can learn from their experience without having to live through it yourself. This is partly about explicit advice – someone telling you what they learned from a mistake. But it’s also about exposure. Hearing how other people think about problems, what they prioritize, what they worry about, gradually shapes how you think.
The quality of these networks matters enormously. A network of people doing essentially the same work in the same industry will reinforce existing patterns. A network with genuine diversity – different backgrounds, different career paths, different perspectives – creates more friction and more learning. The discomfort of encountering a genuinely different approach is often where the most useful learning happens.
Reflection and Deliberate Practice Within Work
Not all experience produces expertise. Some people repeat the same year of experience ten times. Others learn something new every year. The difference is often reflection – taking time to think about what happened, why it happened, and what it means for future decisions.
In fields where the feedback loop is immediate and clear, this reflection happens naturally. A pilot knows within seconds whether a landing was smooth or rough. A salesperson knows whether a pitch worked. But in many professional roles, the feedback is delayed, ambiguous, or distributed across many variables. A manager makes a hiring decision and doesn’t know for months whether it was sound. A strategic choice might take years to play out. In these contexts, deliberate reflection becomes essential. It’s the mechanism that converts experience into expertise.
This reflection often happens informally – thinking through a problem while commuting, discussing an outcome with a trusted colleague, writing notes after a difficult meeting. But it can also be structured without being formal. Some professionals keep journals. Others have regular retrospectives with peers. The common element is creating space to think about what happened and why, rather than just moving on to the next thing.
Deliberate practice in professional contexts looks different than it does in sports or music, but the principle is similar. It means working on the edges of your current capability, getting feedback, and adjusting. It means seeking out assignments that stretch you. It means asking for feedback even when it’s not offered. It means reading widely in your field, not just what’s immediately relevant to your current role.
What Gets Lost When Informal Learning Is Neglected
Organizations that rely too heavily on formal training often end up with a particular problem: people who know the theory but struggle with judgment. They can explain the framework but can’t navigate the messy reality where frameworks don’t quite fit. They know the right answer according to the manual but not the right answer for this situation with these constraints and these people.
This happens partly because informal learning requires time and space that busy organizations don’t always protect. If someone is always in meetings or always heads-down on immediate work, there’s no room for the conversations, the reflection, the exploration that builds expertise. The person stays competent but doesn’t develop the deeper judgment that comes with informal learning.
It also happens when organizations don’t value or recognize informal learning. If career advancement and recognition are tied primarily to credentials and formal achievements, people optimize for those. They take the course because it looks good on their resume, not because they’re genuinely curious about the subject. They don’t have time for the reading, the side projects, the conversations that don’t directly lead to a promotion.
There’s also a knowledge loss problem. When people leave an organization, they take their informal knowledge with them – the patterns they’ve noticed, the solutions they’ve developed, the relationships they’ve built. This knowledge often isn’t documented because it wasn’t formal enough to capture. A successor has to relearn it through their own experience, which is inefficient and means the organization never quite reaches the level of expertise the previous person had.
Creating Conditions for Informal Learning
The most effective organizations I’ve worked with don’t try to eliminate formal training – they use it strategically and then create conditions for informal learning to flourish. This means protecting time for reading, for thinking, for conversations that don’t have an immediate deliverable. It means valuing mentorship and peer learning, not just as nice-to-have but as central to how expertise develops.
It means hiring for potential and then investing in people’s growth over years, not quarters. It means tolerating some inefficiency in the short term because the learning that happens during complex projects builds expertise that pays off long term. It means creating psychological safety so people can discuss failures and learn from them, rather than hiding mistakes.
It also means recognizing that different people learn informally in different ways. Some learn best through conversation. Others learn through reading and independent exploration. Some develop expertise through side projects. Others through mentoring. An organization that wants to cultivate expertise needs to accommodate these different paths, not force everyone through the same formal training program.
The professionals I’ve seen reach the highest levels of expertise tend to be voracious learners who engage with their field across multiple channels. They read widely. They attend conferences and seminars, not for the certificates but for the conversations. They seek out mentors and also mentor others. They work on problems that challenge them. They reflect on their experience and share what they learn. None of this is captured in a training transcript, but all of it is visible in the quality of their judgment and the depth of their expertise.
