How Engineers Master Skills Through Collaborative Learning

Back in 2017, my team had a simple but powerful ritual. We held "I have a design challenge" meetings, where someone would bring a project they were working on, and we’d workshop it together. These sessions weren’t just about fixing problems. They helped us grow our skills as a team and learn from each other’s perspectives. In 2024, I wanted to bring that same energy to learning designers looking to level up their skills in a fun and engaging way. This time, I turned to Tim Slade’s eLearning Challenges but took a different approach. Instead of just participating, we started doing live reviews of the challenge winners. How It Works One person drives the meeting, screensharing the challenge winner’s eLearning project while recording the session. We pause at each screen and ask two simple but high-impact questions: ✅ What worked well and why? ✅ What would you do differently and why? This sparks rich discussions on everything from instructional design and accessibility to visual design and interactivity. Everyone brings their unique expertise, turning the meeting into a collaborative learning experience. Want to Try It? Here’s What You Need ✔️ A web conferencing tool with recording capabilities ✔️ Adobe Premiere Pro or a transcript tool (optional, but helpful) ✔️ A generative AI tool like ChatGPT, Gemini, or Claude (optional for extracting themes from discussions) After the session, we take the recording and import it into Adobe Premiere, which generates a transcript in seconds. Then, using GenAI, we pull key themes, quotes, and takeaways, turning raw discussions into actionable insights. Why This Works This approach takes learning from passive to interactive. You’re not just seeing best practices. You’re critically analyzing them with peers, learning through feedback, and refining your own instructional design instincts. Would you try this with your team? Have you tried something similar? What worked well? #InstructionalDesign #GenAI #LearningDesign #eLearning #AIinLearning #CourseDevelopment #DigitalLearning #IDStrategy #EdTech #eLearningDesign #LearningTechnology #InnovationInLearning #CustomerEducation

Learning never stops — especially for engineering teams solving real-world problems. Technology stacks change, edge cases grow more complex, and expectations evolve faster than ever. But the real differentiator is not tools it’s how teams think, adapt, and keep improving. In rooms like this, learning is not formal. It happens through discussion, peer review, shared debugging, and challenging decisions that don’t feel right. Whether it’s rethinking a DB schema, reworking an endpoint, or questioning a tradeoff these moments are where engineering excellence is shaped. Upskilling is not a training module. It’s baked into the culture. It happens in stand-ups, in whiteboard sessions, in quiet nods of agreement when someone explains something better than documentation ever could. The best teams grow by staying curious — together. #learningneverstops #engineeringexcellence #teamgrowth #techleadership

How to Create a Continuous Learning Culture for Your Engineering Team In today’s fast-evolving landscape, the success of any organization depends not only on innovation but also on how well its people continue to learn. Frameworks change, technologies evolve, and customer expectations rise — making continuous learning a strategic necessity rather than a nice-to-have. Creating a culture of continuous learning empowers engineers to stay current, think creatively, and solve complex problems with agility. Here’s how to make it part of your team’s DNA. 𝐋𝐞𝐚𝐝 𝐛𝐲 𝐄𝐱𝐚𝐦𝐩𝐥𝐞 Culture starts at the top. Engineering leaders who openly share what they’re learning — whether it’s a new architecture pattern, leadership concept, or emerging tool — send a powerful message that growth is valued at every level. 𝐁𝐮𝐢𝐥𝐝 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠 𝐈𝐧𝐭𝐨 𝐭𝐡𝐞 𝐖𝐨𝐫𝐤𝐟𝐥𝐨𝐰 Learning shouldn’t feel like a side project. Encourage micro-learning opportunities — 15-minute daily reads, pair programming sessions, or code reviews that focus on teaching moments. Allocate dedicated “innovation time” every sprint or month for engineers to experiment with new frameworks, libraries, or cloud tools. 𝐑𝐞𝐜𝐨𝐠𝐧𝐢𝐳𝐞 𝐚𝐧𝐝 𝐑𝐞𝐰𝐚𝐫𝐝 𝐂𝐮𝐫𝐢𝐨𝐬𝐢𝐭𝐲 A learning culture thrives when curiosity is rewarded. Celebrate engineers who share knowledge or propose new approaches, even if the ideas are still evolving. Recognition programs, or simple acknowledgments during retrospectives can go a long way in reinforcing positive behavior. 𝐈𝐧𝐯𝐞𝐬𝐭 𝐢𝐧 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞𝐬 𝐚𝐧𝐝 𝐀𝐜𝐜𝐞𝐬𝐬 Provide access to quality learning platforms and budget for certifications, conferences, or hackathons. Pair this with internal mentorship programs so knowledge spreads horizontally, not just top-down. The goal is to make continuous learning easy and accessible. 𝐄𝐧𝐜𝐨𝐮𝐫𝐚𝐠𝐞 𝐊𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 𝐒𝐡𝐚𝐫𝐢𝐧𝐠 Learning sticks when shared. Host internal tech sessions, brown-bag lunches, or lightning talks where engineers discuss lessons from recent projects or new technologies. Create dedicated Slack channels or Confluence spaces where learning moments can be documented and revisited. 𝐅𝐨𝐬𝐭𝐞𝐫 𝐏𝐬𝐲𝐜𝐡𝐨𝐥𝐨𝐠𝐢𝐜𝐚𝐥 𝐒𝐚𝐟𝐞𝐭𝐲 For learning to flourish, team members must feel safe to experiment — and fail. Encourage experimentation as part of innovation cycles and frame mistakes as learning opportunities. A psychologically safe environment allows engineers to ask questions and challenge assumptions without fear. 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 𝐚𝐧𝐝 𝐄𝐯𝐨𝐥𝐯𝐞 Finally, treat learning like any other key initiative: measure it. Track engagement in learning programs, the number of internal knowledge-sharing sessions, or the adoption of new tools. Use feedback to continuously refine your learning approach. In the end, the best engineering teams aren’t just building products — they’re building better engineers every day. #leadership #engineering #learning #culture

I’ve seen brilliant people build average teams. And average people build something amazing together. The difference is this: One group just came to work. The other came to grow. When teams learn together, they become smarter together. It’s called 𝗰𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝘃𝗲 𝗶𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲, where the group solves problems better than any one person could. In my experience, growing teams follow a few powerful habits. 𝗧𝗵𝗲𝘆 𝘂𝘀𝗲 𝘁𝗵𝗲 𝘁𝗲𝗮𝗰𝗵-𝗯𝗮𝗰𝗸 𝗿𝘂𝗹𝗲: when someone learns a new skill, they teach it to someone else within 48 hours. It’s simple, but it doubles retention and spreads knowledge fast. 𝗧𝗵𝗲𝘆 𝗮𝗹𝘀𝗼 𝗲𝗺𝗯𝗿𝗮𝗰𝗲 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝘃𝗲 𝗰𝗼𝗻𝗳𝗹𝗶𝗰𝘁: disagreeing on ideas while staying aligned on goals. They challenge the thinking, but always respect the thinker. And they track learning just as seriously as performance. Not just “What did we achieve?” but “What did we learn?” The best teams I’ve built weren’t just high-performing. They were high-learning. So here’s a small shift that changes everything: At your next meeting, ask “What did we learn?” before “What did we accomplish?” You’ll be surprised by what opens up. #Experience #CollectiveIntelligence #Skills #Learnings

In this episode of The Mob Mentality Show, we sit down with Joshua Aresty to explore how remote teams thrive through communication, collaboration, and creativity in modern software development: https://lnkd.in/gfi92tyR https://lnkd.in/gsuS2Hx2 Together, we unpack three powerful and practical topics shaping the future of agile engineering: 🔹 Remote Work Communication Patterns What makes remote collaboration work — and what breaks it? The discussion dives into real patterns that distributed teams can adopt to communicate more clearly, stay aligned, and maintain momentum without burnout. Learn how to balance synchronous and asynchronous teamwork for maximum flow and productivity. 🔹 Mobbing vs Pairing What’s the difference between mob programming and pair programming in practice? The conversation breaks down the strengths and trade-offs of each approach. Discover when a mob or a pair works best, how to transition between the two, and how these methods can build a culture of shared learning, faster feedback, and higher-quality code. 🔹 Voice Coding and Accessibility Joshua brings unique insights into coding by voice — an approach that challenges traditional ideas of how developers write code. Hear how voice coding improves ergonomics, accessibility, and inclusivity in software engineering. This segment highlights how diverse workflows and adaptive tools can unlock new levels of creativity and collaboration. Whether you’re an agile practitioner, developer, team lead, or engineering manager, this episode delivers practical takeaways you can apply immediately: - Strengthen communication in remote or hybrid teams - Choose between pairing and mobbing effectively - Foster inclusive, accessible engineering environments - Improve team learning and knowledge sharing through ensemble programming 🎧 Tune in to learn how collaborative coding techniques, like mobbing and pairing, can transform not just how software is written — but how teams connect, learn, and grow. Stay connected and join the conversation with the Mob Mentality community — where we explore the people, practices, and patterns that make software development more human, sustainable, and effective. Chris Lucian #MobProgramming #PairProgramming #Agile #AgileTeams #Collaboration #SoftwareEngineering #RemoteWork #Teamwork #ContinuousLearning #EnsembleProgramming #DevPractices #EngineeringCulture