Lunch And Learn
Lunch and Learns provide an effective way to share new technology, new learnings, and new ideas. They cross-pollinate the orgaization so it can grow. Usually a developer leads the Lunch and Learn.
- A different language/framework/stack shows great promise and would make the work easier and faster, but no one knows it
- Teams are too busy with “real work” to take time to learn
- Improvement activities are only local within the team, and don’t propagate to other teams or departments
- No one knows whats happening in other parts of the company
- Knowledge is treated as a precious commodity, no one is willing to share with others
- Developers become more comfortable presenting to their peers
- Developers get to share new technologies and learnings
- Opportunity to improve employee engagement
- Information flows informally through the company.
- Innovation results from ideas and information intertwining and cross pollinating, which will increase the company’s effectiveness and overall capabilities.
- Lunch and Learns are held consistently and provide meaningful, relevant content that helps to increase the team’s capabilities (100pts)
- Lunch and Learns are occasionally held, and sometimes provide something valuable (10pts)
- No one volunteers to present a topic (-25pts)
- Lunch and Learns are never held (-100pts)
- Lunch and Learns are consistently canceled due to higher priorities (-150pts)
❑ Critical ✓ Helpful ❑ Experimental
Steps to first adopt this practice:
- Announce Lunch and Learns will be held for the next 3 - 6 months as an experiment to share information and ideas between teams
- Have the potential participants pick a starting topic
- Started holding Lunch and Learns
- Track topics/presenters and participation
- Repeat for 3 - 6 occurences
- Do a quick exit poll on value to the participants. A Return on Time Invested chart can gather this type of data.
- Has participation remained about the same? If so, how might you increase the number of participants?
- Have the topics covered both theorectical and practical aspects of the job?
- Are the participants interested in keeping the Lunch and Learns active?
What Does it Look like?
Knowledge doubles every 12 months or less. Knowledge doubles even faster in software development where we deal with both theoretical knowledge and the practical / application of that theoretical knowledge. Even if we practice intentional learning, we’re losing ground. By not learning at all, we’re planting the seeds of destrution. Specifically, ours.
Lunch and Learns offer an avenue for people to get together and share new information, ideas and to innovate. Some companies chose to support Lunch and Learns by paying for the food. After all, the person participating in the Lunch and Learn is dontating some personal time. Formats vary, but there’s generally an assembling time (to find food, get seated, do some chit chat). The program/presentation and a few questions.
Start with asking participants what they’d like to cover during the Lunch and Learns. Have several ideas to suggest should the participants be reluctant to initially add items. They’ll be happy to let you know what interests them. Find someone (preferablly in the company) who can share ideas and experiences with the session material. Anchoring the meeting time (second Tuesday of the month) and location (conference Room B) make the Lunch and Learns easier to remember.
- Vendors line up to present at your Lunch and Learn
- The same people present at the events
- Participation starts high, and eventually dwindles to the organizer and presenter
- You come up with the list of topics
Lunch and Learns start the path to larger organizational peer-to-peer meetings such as internal open space conferences, hackathons and more in-depth presentations and workshops.
How to Fail Spectacularly
- One person decides all the topics
- The meeting location and time changes every Lunch and Learn
- Someone from HR sits in and takes attendance
- Lunch and Learns regularly get canceled due to “higher priority” tasks.
- Lunch and Learns become “religious wars” such as Vi vs Emacs, AWS vs Azure, OO vs FP etc
←Prev (Schedule Skills Improvement)(Share The Secrets) Next→