Workshops

For engineering leaders, the word "workshop" can sometimes evoke a sigh. Too often, they’re seen as fluffy, time-consuming exercises that generate more heat than light. But I’ve learned over 20+ years that well-designed workshops are a crucial component of knowledge management – and can be a powerful force multiplier for your team. They’re not just about sharing information; they’re about building understanding, fostering collaboration, and driving impactful change.

Consider this: studies show that employees spend an average of 5-7 hours per week in meetings – a significant investment. If a portion of that time is dedicated to ineffective workshops, the cost of lost productivity and innovation is substantial. Let's dive into how to run workshops that genuinely move the needle for your engineering organization.

Why Workshops are a Key Knowledge Management Tool

Before we get into how, let’s reinforce why workshops matter in the context of knowledge management. Engineering knowledge isn't just codified in documentation (though that’s important!). A huge amount resides in the heads of individual engineers. Workshops provide a structured mechanism for:

• Externalizing Tacit Knowledge: Getting those "tribal knowledge" nuggets out into the open. What shortcuts do senior engineers use? What are the common pitfalls to avoid?
• Cross-Pollination of Ideas: Breaking down silos and enabling engineers from different teams to learn from each other.
• Shared Understanding: Aligning the team on complex topics, architectural decisions, or new technologies.
• Collective Problem-Solving: Tackling challenges that are too complex for any single engineer to solve.
• Building a Learning Culture: Demonstrating a commitment to continuous improvement and fostering a growth mindset.

Types of Workshops That Deliver Real Value

Not all workshops are created equal. Here are a few types I’ve found particularly effective:

• Post-Incident Reviews (Blameless Postmortems): These are arguably the most important workshops you'll run. Focus on what happened, not who made a mistake. The goal is to identify systemic issues and prevent future incidents. (I recommend the "5 Whys" technique –to get to the root cause.) For example, at a previous company, a post-mortem revealed a lack of automated testing for a critical service. Implementing automated tests during the next workshop reduced similar incidents by 40% in the following quarter.
• Architecture Deep Dives: Unpack a complex system or architectural pattern. Invite the engineers who built it to walk others through the design, trade-offs, and key considerations. This is invaluable for onboarding new team members and fostering a shared understanding of the system.
• Technology Brown Bags: Dedicated sessions where engineers share their knowledge of a specific technology, tool, or framework. This is a low-pressure way to encourage learning and experimentation. These sessions can spark new ideas and expose team members to innovative approaches.
• Design Workshops (Problem Framing): Before diving into coding, facilitate a workshop to collaboratively define the problem you're trying to solve. This helps ensure everyone is on the same page and prevents wasted effort on building the wrong thing. A well-framed problem definition can save weeks of development time.
• Skill-Sharing Sessions: Have engineers teach each other skills – maybe a new testing technique, a powerful command-line tool, or a specific design pattern. This fosters a culture of continuous learning and helps build internal expertise.

Making Your Workshops Effective: Practical Tips

Here’s where the rubber meets the road. Running a truly effective workshop requires planning and facilitation skills.

1. Define a Clear Objective: What do you want participants to know, understand, or be able to do by the end of the session? This will guide your agenda and ensure you stay focused.
2. Target the Right Audience: Who needs to be in the room (or on the video call)? Don't invite people just for the sake of it. A smaller, focused group is often more effective.
3. Prepare a Detailed Agenda: Outline the topics you’ll cover, the activities you’ll do, and the time allocated to each. Share this with participants in advance.
4. Facilitate, Don't Lecture: Your job isn't to tell people things; it's to guide the conversation and encourage participation. Ask open-ended questions, encourage debate, and actively listen to different perspectives.
5. Use Interactive Activities: Break up the monotony with hands-on exercises, brainstorming sessions, or group discussions. Tools like teamwork.com or contriber.com can help manage these activities. For remote sessions with a small group (up to 5 attendees) Showtime – which allows for detailed screen sharing and recording – can be useful for capturing key insights.
6. Document Key Takeaways: Assign someone to take notes and capture the key insights, decisions, and action items. Share these with participants after the workshop. Shortcut can be helpful here as you can use it to manage tasks coming from workshop sessions.
7. Follow Up: Don't let the knowledge gathered in the workshop gather dust. Assign owners to action items and track progress. Integrate the insights into your team's processes and documentation.
8. Embrace Remote Collaboration: Remote workshops are perfectly viable. Leverage tools like video conferencing, shared documents, and online whiteboards to facilitate interaction and collaboration.

Measuring Workshop Effectiveness

Workshops are an investment, and it's important to demonstrate their value. Consider tracking these key metrics:

• Reduced Incident Rates: Following post-mortems, monitor whether the frequency of related incidents decreases.
• Faster Onboarding Times: Measure how quickly new team members become productive after participating in architecture deep dives.
• Increased Team Innovation: Track the number of new ideas generated during workshops, or the number of features implemented based on workshop discussions.
• Participant Feedback: Collect feedback after each workshop to identify areas for improvement.

Beyond the Workshop: Sustaining Knowledge Sharing

Workshops are a powerful tool, but they’re not a silver bullet. To truly build a learning organization, you need to foster a culture of continuous knowledge sharing. Encourage engineers to:

• Write documentation: Even a few minutes of documentation a day can make a huge difference.
• Share learnings in code reviews: Use code reviews as an opportunity to share knowledge and best practices.
• Contribute to internal knowledge bases: Create a central repository of information that everyone can access. Dev.to is a good external resource to show them how to share learnings.
• Pair program: Pair programming is a great way to transfer knowledge and improve code quality.

Final Thoughts:

Well-executed workshops aren't just time well spent; they are an investment in your team’s collective intelligence. They help externalize critical knowledge, foster collaboration, and drive meaningful innovation. Don’t think of them as interruptions to the work; think of them as how you get work done and ensure your engineering team continues to grow and thrive.

To get started, schedule a 30-minute team discussion to identify one knowledge gap that could be addressed through a workshop.