BookNotes: The Octopus Organization #3: Talent Development Isn't a Nice-to-Have

Welcome to the Manager Lab, where we delve into the increasingly dynamic world of talent management.

In each episode, we will unravel key insights, break down the most relevant books and articles, and provide actionable tips to optimize your approach in developing and retaining top talent. Stay tuned for a deep dive into the art, science, and strategy of unlocking your team's full potential. Let's enter the Manager Lab.

Hello, everyone. Welcome back to the lab. Today, we are in part three of our book note series on a wonderful new book I just finished, The Octopus Organization, A Guide to Thriving in a World of Continuous Transformation. And today, we're going to cover the tip in the book called Talent Development Isn't a Nice-to-Have. Now, as a talent development specialist in my role. This is right up my alley, if you will. So think about these types of questions.

Does your organization downplay talent development? Well, I can honestly say in my organization, we really put a big emphasis on talent development. It's at the forefront of how we think about succession planning and things like that. So I feel very, very fortunate to be in the role that I'm in. When companies neglect or minimize their employees' growth, treating it secondary to real work, the consequences are real.

So critical skills gaps that hinder productivity appear, disengaged workers, low retention, reduced innovation, all of those things lead to competitive vulnerability.

The Octopus Organization, according to the book, mitigates these risks by treating talent development as a critical continual investment. So here's how to model this type of idea in your organization. So number one, make learning the work. Embed training exercises into your projects. This could be a two to three day sprint at the beginning of an initiative to learn new tools or learn new techniques.

Maybe you consider creating time for retrospective reflection on skills learned, such as structured debriefs after a project, after action reviews. Journaling prompts for leaders that just help people encapsulate the learning that's happened on a particular project or work initiative. Okay, that was number one. Number two, create micro learning content. So you don't need intensive, long training modules. Those are sometimes important and necessary, but you don't need those all the time.

Sometimes short videos, articles, book chapters, or just book paragraphs that explain a point or maybe interactive exercises are all your employees really need to get the main points across. Three, strategically plan skills development. So proactively identify near future skills that you need based on organizational goals and then conduct regular skills gaps analysis. Link learning to career progression opportunities and then incorporate skills development goals into your performance reviews.

Next, enable self-organized curiosity groups. So encourage employees to create groups around topics of shared interest. For instance, one of the operating companies in my region has every fourth Friday of the month has manager tools, and it's exactly what it sounds like. There's an article or a book chapter or an interview with managers that just help them get better at what they do. They have 15, 20 people on there every month, and they just get better at a specific competency.

These groups can discuss how they're learning and experimenting with new tools, new technologies. Maybe a system upgrade, whatever it might look like. You might also develop a skill swap marketplace. I like this idea, where employees can list skills they have and want to teach, as well as the skills they don't have and want to learn. And so maybe you can pair people up accordingly.

The last thing they talk about in the book is to create space for regular development conversations. Use regular one-on-one meetings as dedicated development conversations. So the rule of thumb that I've used for, gosh, 20 years now, you know, I have weekly one-on-ones with my direct reports, but I take one of those meetings every quarter or so and completely devote that to their own development conversations. So what's in their IDP? What are they thinking about career-wise?

Are they on the right path? Are they satisfied with where they are? What stretch opportunities can we look for? So, you know, it should come up periodically anyway, but if it doesn't, if you get kind of wrapped up in your own, you know, sort of tactical, you know, humdrum, if you will, make sure that at least one of your one-on-ones every quarter is totally devoted to their development.

This shifts your role from taskmaster to coach, and that's a good thing, making development a continuous part of the work cadence.

All right. I hope this is being helpful to you. It's good for me to go back and review this wonderful book. And until next time we meet in the manager lab, do good work.