Team members are traditionally onboarded in one of two ways:
- The “Read This Pile” introduction: You are supposed to learn from a pile of papers or online documents.
- The “Apprentice” introduction: You shadow a team member for a while trying to pick up as much knowledge as you can.
The “Read This Pile” introduction results in information overload – it’s hard to know what’s important. It also results in information gaps – new members don’t learn about what is not documented.
The “Apprentice” introduction has its drawbacks too. You’ll learn a lot from your colleague, but only the things the team is working on right now. To cover all parts of a system might take months because there will be parts that the team rarely touches.
Luckily, there is a faster way – deliberate learning.
We are regularly asked if we know any DevOps or site reliability engineering (SRE) experts available for hire. Our answer is, invariably, "Not really." It's a tough market out there.
DevOps and SRE (for large-scale software, at least) are critical approaches for success in modern software delivery and operations, as widely demonstrated every year in the State of DevOps report or the array of presentations at the DevOps Enterprise Summit.
But if you think you can achieve DevOps by hiring "DevOps experts," you are missing some contextual awareness. What exactly are you trying to improve in the first place?
If your software delivery is slow because of work you're handing off among multiple teams with diverse schedules and priorities, will a new hire really help?
We're not suggesting that you not hire people with diverse skills and backgrounds—that can be quite valuable to bring in new perspectives and approaches.
But conventional hiring based on expertise alone is ineffective and prevents organizations from developing the "learning muscles" that can help teams traverse the latest trends (DevOps, SRE, etc.) to their benefit at the right time, and in the right context.
Hiring experts for every need is like engaging in palliative care for organizational health. Preventive care would be to incorporate the necessary team structures and interactions—as well as a focus on people growth and sufficient slack—to effectively take in process, technology, and business changes.
Learning organizations smoothly morph as they adapt to new challenges, and they unlearn existing ways of working when they become limitations rather than enablers.