tech·nic·al·ly agile

The Limits of Self-Taught Learning: Why External Perspectives Matter

Discover the pitfalls of self-taught learning and the power of diverse insights in consulting. Embrace continuous learning for better solutions!

Published on
5 minute read
Image
https://nkdagility.com/resources/DvW-xwxufa0

In today’s fast-paced digital landscape, the concept of self-taught learning is more prevalent than ever. However, as we dive deeper into the realms of software development, DevOps, and organizational transformation, it’s crucial to recognize the limitations that come with learning in isolation. While self-taught knowledge has its merits, there are significant benefits to bringing in external expertise. This post explores the importance of diverse knowledge and how it can help organizations break through the barriers that self-taught learning often creates.

The Reality of Self-Taught Knowledge

When working with new customers, one of the first things we make abundantly clear is that we’re not here to solve all your problems. The messes, the challenges—those are yours to tackle. But what we can do is help you see the problem, shine a light on it, and keep your focus on the areas that need improvement.

  • Shining a light on the problem: We often liken our role to bringing torches into a dark room, illuminating those dusty corners where issues have been swept under the rug. These hidden problems are often the ones slowing down your progress and costing you money.

  • Focusing on solutions: By highlighting these areas, we empower organizations to address their problems, offering guidance on potential solutions that they might not have considered.

The Gap in Training

One of the most interesting observations we’ve made over the years is the lack of formal training that many engineers and professionals receive.

  • Limited opportunities for growth: In many organizations, engineers aren’t sent to coding courses, product development workshops, or security training. They aren’t exposed to structured learning environments that could vastly improve their skills.

  • Self-taught limitations: As a result, almost every engineer is self-taught, learning within the narrow bounds of what they’ve explored. The problem with this approach is that we tend to stop looking for answers once we find one that works.

Imagine you’ve lost your keys. You search your house, and as soon as you find them, you stop looking, right? You don’t continue searching just in case there are more keys hidden somewhere. The same principle applies to knowledge acquisition—once we find a solution, we often stop exploring. But what if there are five better solutions out there?

The Power of External Expertise

This is where external expertise becomes invaluable. Bringing in someone from the outside—someone with a wealth of experience and a different perspective—can help you see beyond the solutions you’ve settled on.

  • Years of experience: I’ve been involved in DevOps (before it was even called DevOps) for over 20 years. During this time, I’ve seen the evolution from application lifecycle management to the modern practices we see today.

  • Diverse exposure: As a software engineer and Scrum coach, I’ve worked with numerous organizations, observing what works and what doesn’t. This diverse exposure allows us to bring a variety of ideas and tools to the table—solutions that you might not have considered.

Encouraging Broader Exploration

Our goal isn’t to hand you a one-size-fits-all solution. Instead, we aim to provoke thought, encouraging you to explore alternatives:

  • Providing tools: We might suggest a tool to get you started, and if that doesn’t work, we’ll point you towards the type of tool you should be looking for.

  • Fostering innovation: This approach often leads to organizations finding their own unique solutions—ones that are even better than what we initially proposed.

But remember, the process of discovery and improvement is something that you and your team must undertake. We can guide you, but the work has to be done by your people.

The Evolution of DevOps: Continuous Learning and Institutional Knowledge

When it comes to DevOps, our role is to help you understand where you are, determine where you want to go, and keep you moving in that direction. However, the actual work—the learning and application of new methods—must be done by your team.

  • Institutional knowledge: Every organization has its own institutional knowledge, the collective understanding that your team builds over time. When new people join your team, they bring fresh ideas, but they also absorb this institutional knowledge. It’s crucial that this knowledge aligns with the direction you want to go.

  • Progressing effectively: True progress isn’t about accumulating unfinished work or refining processes endlessly. It’s about doing the right things and doing them well.

The Role of External Guidance

External guidance plays a vital role in ensuring that your team’s progress aligns with your goals. By providing an outside perspective, we help you:

  • Identify roadblocks: Shine a light on the areas that are holding you back.

  • Explore new possibilities: Introduce new tools, methodologies, and approaches that you might not have considered.

  • Maintain momentum: Keep your team focused on the right direction, ensuring that your institutional knowledge grows in alignment with your goals.

The Takeaway: Balancing Self-Taught Learning with External Expertise

While self-taught learning fosters independence and innovation, it’s essential to recognize its limitations. By bringing in external expertise, organizations can break free from the constraints of their existing knowledge and explore new, more effective solutions.

Key Points to Remember:

  • Self-taught knowledge is limited by the scope of exploration. Most people stop looking once they find a solution, missing out on potentially better alternatives.

  • External expertise offers diverse perspectives and solutions that can help organizations overcome challenges and improve processes.

  • Continuous learning and institutional knowledge are crucial for long-term success. External guidance can help ensure that your team’s progress aligns with your organizational goals.

🚀 Final Thoughts: Embrace the balance between self-taught learning and external expertise. By doing so, you can unlock new possibilities, drive innovation, and achieve your goals more effectively.

When we’re engaging with customers, especially new customers, one of the things we try and be 100% clear on is that we’re not going to solve your problem. All of the messes, all of the issues are yours to fix. But what we can do is help you see the problems and keep a little bit of focus on those problems so that you can solve them. Right? We’re bringing the torches so that we can see what’s going on, shine a light in those dirty corners, under the rug where we’ve been sweeping the dust, and point at that and say, “Look, we need to resolve this. This is causing you problems. This is slowing you down. This is costing you money.” Right?

We help those organisations get better by helping them figure out what their options are. Quite often, I think it’s really interesting how many organisations and engineers—I’m going to include engineers in this because I think it’s true there too—we tend to not get a lot of training. Right? I don’t see organisations sending their engineers on coding courses. I don’t see them sending them on product courses. I don’t see them sending them on API courses. I don’t see them sending them on security courses. They don’t do that. So almost every one of your engineers is self-taught.

Right? And when you’re self-taught, you learn something within the bounds of what you looked at, and we stop looking when we find an answer. Right? It’s like when you’re looking for your keys in your house. Right? If you’ve lost your keys and you’re looking for them, you don’t find your keys and then keep looking. Right? You don’t find them and go, “I think I’ll look a little bit more in case I find more keys.” No, I found them, so I’m going to stop looking. Right? So they’re always in the last place you look, and that same is true for knowledge. When we find an answer, most of us stop looking and use that answer. But perhaps there are five better answers. Perhaps there are five progressively better answers that we could be finding.

And that’s the value of bringing in sometimes somebody from the outside to look at what it is you’re doing and how you can be more effective at it. It’s that experience, knowledge, and experience. I’ve been doing DevOps—probably the best way to describe it—doing DevOps before it was called DevOps. It was called application lifecycle management before then, and I’ve been looking at that for 20 years. I’ve been a software engineer for 20 years. I’ve been a scrum coach and consultant for 10 years, seeing what all of these organisations out there are doing and seeing the things that work for them and the things that don’t. Because not every organisation does everything well. They might do some stuff well and other stuff not so much. Right?

That means that we can bring a whole bunch of ideas. Have you thought about this? Have you looked over here? Here’s a tool that you could use to get you started in the space. Oh, if that tool doesn’t work for you, here’s the type of tool you’re looking for. Right? And that provokes people to go look for alternatives, look for other ways to do things, look for solutions, and perhaps they’ll find their own ones that are even better than the ones that we came up with. But that process is something that you and your people have to do.

So when you’re engaging, as for DevOps, we’re going to help you understand where you are right now, help work with you to understand what direction you want to go, and help you keep moving in that direction. But it’s you and your people that have to do the work because it’s you and your people that have to learn the things—institutionally, you know, that institutional knowledge that an organisation gets. When you bring in new people, although they come in with their own ideas, they learn that institutional knowledge. You want that institutional knowledge to be moving in that direction. Right? The weight of progress is in the direction that you want to go, which is not building up a whole bunch of refinement and work you’ve not done. It’s doing those things and doing it properly and not actually doing things well.

And we can help you keep progress in those directions.

People and Process Discovery and Learning Pragmatic Thinking
Comments

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Bistech Logo
Illumina Logo

NIT A/S

Big Data for Humans Logo

CR2

Xceptor - Process and Data Automation Logo
Slicedbread Logo
Qualco Logo
Philips Logo
Boeing Logo
Jack Links Logo
Genus Breeding Ltd Logo
YearUp.org Logo
Deliotte Logo
ALS Life Sciences Logo
DFDS Logo
Graham & Brown Logo
Healthgrades Logo
Washington Department of Transport Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Ghana Police Service Logo
Department of Work and Pensions (UK) Logo
Washington Department of Enterprise Services Logo
Akaditi Logo
Jack Links Logo
DFDS Logo
Boxit Document Solutions Logo
SuperControl Logo
Cognizant Microsoft Business Group (MBG) Logo