Here is my latest post for Simple Programmer…
For success, it isn’t the programming knowledge you or your team members have at present that matters most. Nor is it how many years of experience we have.
It’s how we work together, how we approach problems, and most importantly, how we learn. Michael Gerber said in the most eloquent way I have seen in his book The E-Myth: “Contrary to popular belief, my experience has shown me that the people who are exceptionally good in business aren’t so because of what they know but because of their insatiable need to know more.”
A workplace learning culture is not only for fun (although it can be!); it allows for better business.
A workplace learning culture enables us to be more adaptable. If the market changes, so can our teams and our business. If a new technology launches, we can capitalize on it. By being adaptable, we can keep our companies relevant and delight our customers.
With a workplace learning culture, our company can become what Nassim Taleb would call: Antifragile. Antifragility is beyond resilience or robustness. The resilient resists shocks and stays the same; the antifragile gets better.
Many companies make excuses as to why they cannot embed a workplace learning culture. These companies often cite reasons such as: We don’t have the budget or the time to train our employees. This thinking is very much about what we don’t have, rather than what we do have. This thinking pervades because often we haven’t utilized our workforce’s knowledge. We’re all sitting on top of a goldmine.
Mountains of knowledge and energy are trapped in the heads of our colleagues and fellow programmers; all they need is an appropriate forum or framework for sharing their knowledge. They need a workplace learning culture.
In my experience, teams with a learning culture are better prepared, more flexible, and are close-knit. They operate like a well-oiled machine, instead of merely a collective of people that have divided up tasks on the same project.
As programmers and developers in this fast-paced, ever-changing world of technology, we must find ways to build a learning environment within our companies, for the success of our teams and for our own long-term success.
If your company doesn’t have an existing workplace learning culture, it’s up to you to create one. There are a few simple things you can do to bring your coworkers together; all they require is a bit of time, attention, and a leader to step up and get things going.
Ways to Foster a Workplace Learning Culture
To promote a workplace learning culture, we don’t need to wait for the mythical management team to tell us that it’s okay to do so. We can (and should) begin now. Seth Godin said it best in Tribes: “The secret of leadership is simple: Do what you believe in. Paint a picture of the future. Go there. People will follow.”
All we need is some inspiration and some structure on the how.
The following are different initiatives that you can use to start to build a working learning culture in your own company. Feel free to change, adapt, and update them to suit you.
I present the following ideas in a progressive order. So if you want to try them, I would suggest this order as each idea builds on the last. That said, the only rule is: There are no rules, so get creative!
1) Kata Sessions.
A kata is a series of movements, choreographed and practiced frequently. Used most often in martial arts (think of the forms in karate or judo), you can use kata in the workplace, too.
Katas are a great way to get started on the journey of building a workplace learning culture. A Kata is a very non-intrusive practice, as all it takes is 15 minutes per session. Which makes it quite hard for a company to say no.
Wikipedia has a great way of describing the concept of kata and how it can be used in the workplace: “The goal is to internalize the movements and techniques of a kata so they can be executed and adapted under different circumstances, without thought or hesitation.”
In other words, take a small amount of time daily to practice ideas, so that they become a part of how we work.
To organize a kata, you need to get together a group of your colleagues with similar learning goals. This can be a group of colleagues interested in a certain aspect of programming, or a new framework or app.
I would suggest doing this every day for a week or two, for around 10-15 minutes per day. I’ve found in the past that practicing just before lunch is a good time. Everyone has got through plenty of work already, so there’s no nagging I-should-be-working guilt and usually no meetings.
Instead of being the type of physical motion you learn in martial arts, these type of katas are programming related, such as a code challenge. Or they can be small lightning-type talks / show-and-tell from individual team members. The themes don’t have to always be the same, and they don’t have to run forever.
Katas can be run as a series; you can do this by picking a single topic and approaching it from different angles. For example, use a kata session to go through a piece of code. Discuss each part and the respective pros, cons, alternatives, and motivations for different techniques and styles of code. These types of sessions will usually last longer than the 15 minutes, but you can keep coming back and picking up where you left off last time. This also eases the pressure on those delivering them as they don’t have to create a new topic each day.
Don’t be afraid to invite senior programmers to the sessions. They won’t get bored; in fact, quite the opposite. Often the most knowledgeable team members relish the opportunity to learn more.
The side-effect (and true power) of kata sessions is how they encourage interactions. It creates a sense of cohesion that is then reflected in our everyday work. Practicing kata means that our team will be able to act without hesitation because we have internalized important techniques and thought processes.
2) Lunch & Learns.
One of the great advantages of katas is that they are hard for a company to push back on because they are so short and simple. Lunch and learns leverage this same thinking.
As with Kata’s, a lunch and learn is where individuals get together to discuss an area of shared interest. The difference is, a lunch and learn is more infrequent and is on ad-hoc topics, rather than short, intense practice sessions on the same topic.
If you’ve got enough ideas to share, once a week is usually good. The topic could be a book someone recently read or a new technology they are using. Kick off the lunch and learn by having someone speak for a few minutes on the topic, and then open it up to discussion.
To help establish lunch and learns, you will need a schedule of topics. Pick a day of the week, and then send out a message requesting topic areas. Let people know the list of topics in advance; you could send out a note on a monthly basis with the topics or you could work on a longer lead time if that’s better for your team. When you get into the swing of it, you can ask people what general things they would like to see discussed, then create a more curated list of topics that focuses more on what people want to learn.
The secret to good lunch and learns is keeping up the cadence. The group should never run out of topics to discuss.
If your colleagues feel like they don’t have anything profound to share, either as a topic or within the discussion itself, it helps to remind the group that perfection isn’t the goal of the discussion. As author of Experts Secrets Russell Brunson says, “You don’t have to be the most knowledgeable person in the world, you just have to be one chapter ahead of the people you’re helping.”
Building a workplace learning culture is not about waiting until we know everything. It’s about sharing ideas that excite us or ones we’re curious to discuss.
3) Communities of Practice (CoP).
When running katas or lunch and learn sessions, we may start to witness patterns emerging. Our colleagues have shared interests that they would like to take further. We can add structure to our workplace learning with a community of practice, or CoP for short.
This group is a collective of individuals who are exploring a topic of shared interest.
How a CoP runs is flexible. The way we run CoPs at AND Digital is that we meet every few weeks for usually an hour. This hour is often dedicated to a presentation and followed with discussion. To support the discussion, we have dedicated channels on Slack, open to the entire company.
If you’re wondering which disciplines work for CoP’s, the answer is: all of them. At AND Digital, we have (amongst others) CoPs for: analysis, front-end development, and coaching and mentoring.
Other companies use different names for the idea of a CoP. Spotify calls them guilds/chapters, and they use it as a way to share knowledge between areas of expertise that don’t usually have the chance to talk in depth, such as quality assurance engineers, who are often distributed with one member in each team.
4) Actively Promote “Mastery”
Mastery is a long-standing commitment from an individual to go deep on a single topic area. We want to encourage Mastery within our organizations as this allows for the deep knowledge to be shared. Some good examples are Martin Fowler for general programming or Troy Hunt for security.
But companies are still slow to officially capitalize on this trend. They don’t often have official support systems for employees who are interested in speaking, blogging, or building a mastery.
Paul Irish is a great example of how Google is helping an individual advocate and share their Mastery. Irish has become the poster-boy for this movement because the company has directly supported his growth as a master in the field. His talks have hundreds of thousands of views on YouTube, and he is the go-to guru of browser tooling. Irish is responsible for a large amount of the buzz around Google, which has, in turn, led to Google’s reputation (for many) as the peak example of a software developer’s employed career.
Fostering Mastery can be hard without the right environment and support. Most companies have a promotional scheme of some kind, so I would suggest speaking to your company about adding Mastery as part of this and getting the topic out in the open. Once the conversation about it has begun, you can continue to support the idea by creating communities of practice for those wanting to better their public speaking or writing skills. You could also speak to your company about running a blog series about your Mastery.
These four ways (katas, lunch and learns, communities of practice, and actively promoting mastery) are only a few of the ways that we can begin implementing a learning culture.
The real secret to success in implementing a workplace culture of learning is by promoting values such as inquisition, transparency, and sharing. To embed these values, we need to put the wheels in motion.
As programmers and developers, we need to find ways to take action for the success of our teams and to build our own successful careers.
We don’t need permission because sharing our knowledge should be a part of what we do, naturally. What we really need, for a better culture for all, is a little courage and action.