In the whirlwind of software development, success too often depends not just on what you know, but on who you know. Picture this scene:

A promising new hire, Maya, joins your team with solid fundamentals but limited experience in your specific tech stack. She tackles an assigned task, diligently studying documentation and online resources. Days turn into a frustrating week as Maya gets stuck on an integration issue that seasoned team members know is notoriously finicky. Meanwhile, across the office, another developer, Alex, breezes through a similar task, muttering, “Oh, the usual quirks with that library...” under his breath. Maya doesn't know to connect with Alex, and Alex hasn't been prompted to share the workaround. What unfolds?

• Wasted Effort: Maya's progress stalled, while precious time is spent reinventing the wheel.

• Missed Growth: A learning opportunity evaporates. This could have been a prime moment for Maya to master a tricky corner of the codebase and solidify a positive working relationship.

• Teamwide Impact: Frustration festers. Maya feels unsupported; Alex becomes the go-to person, soon overburdened with questions which could have been prevented by a better knowledge sharing accros teams.

Real-Life Story: The Cost of “I'll Figure It Out”

Early in my career, I was hesitant to “bother” senior engineers, assuming struggling through was a rite of passage. This led to weeks of spinning my wheels and missed chances to understand design rationale. While I eventually brute-forced the solutions, more was lost than just my time. This mentality fostered an aversion to asking for help, harming my progress long-term.

Beyond Missed Opportunities

As seen so many times, these issues can easily scale throughout your organisation:

• Knowledge Silos: Critical insights locked with individuals or teams impede agility and can jeopardize a project if someone leaves.

• Reinventing the Wheel: Lack of awareness of existing in-house solutions drains company resources and morale.

• Uneven Workload: A few “gurus” get swamped with basic questions, while the potential of less outspoken team members remains untapped.

The problem isn't about a lack of talent or documentation—it's about failing to create the channels through which knowledge, wisdom, and experience can flow seamlessly.

Why Traditional Approaches Fall Short

While onboarding documents and internal wikis are valuable tools, they often fall short of providing the depth and personalisation critical to true mentorship. Here's why:

• Onboarding documentation or wikis represent a snapshot of knowledge at a particular point in time. Technology, teams, and best practices evolve rapidly, rendering them quickly outdated. Mentorship, in contrast, is a dynamic, two-way process that flexes with evolving needs. A mentor can pinpoint what needs updating and address the “why” behind processes, not just the “how.”

• Boilerplate documentation lacks the nuanced, individualized context vital for deep understanding. Imagine a new engineer just out of school joining your heavily regulated industry. Onboarding docs tell them the company forms to fill out, but a mentor helps them grasp the underlying reasons for the strict compliance rules, fostering both adherence and innovation within the constraints.

• Wikis present facts but lack the interpretive layer a mentor provides. A new hire wrestling with code architecture benefits infinitely more from a mentor patiently explaining design choices and tradeoffs than a page describing abstract patterns.

My early days at a fast-growing startup were marked by frantic scrambling through the company wiki. There was always a page covering some technical process, but rarely addressing the edge cases I inevitably ran into. The breakthrough came when paired with an experienced developer. Turns out, half the wiki was outdated, filled with workarounds for since-fixed bugs! My mentor knew what to skip, the undocumented “tribal knowledge”, and crucially, was invested in helping me bridge those information gaps.

Beyond Technical Knowledge

It's crucial to stress that wikis and docs fall shortest in mentorship's “softer” aspects such as:

• Confidence Building: The simple act of a senior engineer dedicating time boosts a mentee's sense that they belong.

• Company Culture Navigation: How and when to escalate issues, who is truly the expert on 'X' technology, informal communication norms – a good mentor accelerates this decoding process.

• Career Pathing: Wikis won't provide honest insights into growth opportunities or challenges within the organization.

While documentation will always play a crucial role, the power of human connection in knowledge transfer and professional development shouldn’t be underestimated.

Key Elements of Effective Systems

Transforming good intentions into a true force for growth requires structure. What truly makes a mentorship program thrive? Let's dive into the key elements that separate well-meant initiatives from transformative programs:

1. ✅ Finding the Right Match

   Skillset is just a start for finding a good match but what sometimes gets overlooked are the other aspects such as: ways of working, personality, common aspirations etc.

   • Communication Match: An introverted mentee may struggle with an overly extroverted mentor, regardless of technical skills. Similar communication styles streamline interaction and reduce misunderstandings. For example, both being naturally direct benefits efficiency, while an introvert/extrovert pairing may require adapting to each other's preferences.

   • Personality Fit: Grumpy pessimist + eager optimist = potential frustration. Friction over clashing personality styles can dampen enthusiasm on both sides. A mentor who seems overly negative or dismissive can discourage the mentee, impacting their progress.

   • Career Path Honesty: Is the mentor in a position to truly help with the mentee's aspirations?

2. ✅ Setting SMART Goals and Keeping a Live Document

   SMART stands for Specific, Measurable, Achievable, Relevant, Time-bound. Don't just say “improve coding”, “get better at X“ - break that down into smaller focused and actionable goals. Goals shouldn't be set and forgotten. Regular check-ins allow mentors/mentees to celebrate progress and refine goals as the relationship evolves.

3. ✅ Mentoring on Values

   1. The Hidden Culture Code: Every company has unspoken ways decisions get made, what truly signals being a team player, etc. This can be harder to navigate than the tech stack itself!

   2. Ethical Compass: This is especially significant in fast-paced, 'move fast, break things' environments. A mentor showing when to push back, uphold quality standards despite deadlines – that models values in action.

4. ✅ Network Creation: Opening Doors and Breaking Invisible Barriers

   1. Advocate, Don’t Gatekeep: Simply knowing names gets a foot in the door, but true mentorship paves the way. (“May I intro you to Maya? Her work on X would be relevant to your team...”)

   2. Beyond Internal Networking: Mentors with broad industry connections become allies. Recommending the mentee for conference talks, open-source collaborations – this amplifies growth.

   3. “Paying it Forward” Loop: This isn't about indebted favors. Rather, the mentee, now armed with a wider network, is positioned to eventually open doors for others.

5. ✅ Keeping it Structured, but Flexible

   Guidance and autonomy should balance.

   • The Power of Suggestion: Offer templates for goal setting, sample agendas for early meetings, etc. This eases pairs into the process without a rigid script.

   • Mentorship Menu: Could have varying levels of engagement. Is there a 'quick question' channel AND an option for longer term pairing?

   • Adaptability Test: Mentor is NOT a crutch. If a mentee fails to prepare for meetings, repeatedly disregards agreed-upon goals, that's feedback for the program coordinators.

6. ✅ The Feedback Loop: Mentors Aren't Mind Readers

   • Safe Space: Emphasize to mentees they WON'T hurt their mentor's feelings by being honest about what's not working. This protects from passive resentment.

   • Org Level Feedback: How did this mentorship improve (or not) the mentee's onboarding? Their contributions?

7. ✅ Celebrating Success & Recognising Contributions

   • Success Is Variable: Not all mentees become rockstars (that's okay!). Did they get unstuck on a blocker? First significant code contribution? Celebrate it to encourage the relationship.

   • Make it Visible: Internal newsletter, 'thank you' board, etc. Showcases that the company is serious about this, not just paying lip service to mentorship.

8. ✅ Fostering a Psychological Safe Environment

   1. Combatting Imposter Syndrome: Especially prevalent among new hires, the fear of appearing incompetent stifles questions. A mentor explicitly stating 'No question is stupid' is a start, but must be consistent in their response.

   2. Error as Opportunity: This takes more than words. Can a mentor show how they diagnose their OWN mistakes? This teaches more than perfect demos ever could.

   3. The Long Game: Psychological safety creates long-term loyalty. That sense of being 'seen' and supported can be the deciding factor on whether a mentee sticks with the company during hard times.

Common Pitfalls

If you've been involved in mentorship, chances are you've encountered a few stumbling blocks. In this section, we'll uncover the most prevalent pitfalls:

❌ Pitfall 1: The 'Hero' Mentor

Swooping in to solve problems instead of teaching problem-solving strategies. The mentee ends up reliant, the mentor burnt out. Mentoring is about giving a toolbox, not just building things for others. Empowering mentees is empowering for the long term.

❌ Pitfall 2: Assuming Interest

A 'passion project' mentorship match – brilliant engineer paired with someone just seeking stable paycheck. Mutual frustration ensues. Upfront discussion about goals and what excites the mentee prevents wasted time and potential resentment.

❌ Pitfall 3: Rigid 'By-The-Book' Mentorship

The program dictates all the focus areas, meeting frequency, etc., with no room for adaptation based on the pair's unique needs. Structure is good, rigidity is stifling. Allowing mentor/mentee input on format fosters both ownership and better matching in future iterations.

❌ Pitfall 4: Neglecting Mentor Development

We assume technical experts already possess all the skills needed to be effective mentors. An underdeveloped mentor may flounder when providing constructive feedback, navigating difficult conversations about the mentee's performance, etc. This directly impacts the mentee's growth and can even breed disillusionment with the concept of mentorship altogether. Beyond the tech side, mentors need to give feedback, motivate, and sometimes manage underperformance. This is skill, not inherent instinct.

Key Takeaways

Let's recap the essential lessons covered:

1. Be on the Lookout for Static Resources

   1. These risk leaving mentees feeling overwhelmed, misinformed, and frustrated.

   2. “Information overload” hinders progress more than lack of access to facts. Mentors serve as filters and navigators.

   3. Wikis can actually impede adaptation— they perpetuate legacy knowledge unless meticulously maintained.

2. Have Structured Mentorship Programs

   • Pairing: Match new hires or less-experienced team members with seasoned developers for focused knowledge transfer and ongoing support. This program can be formal (designated time each week) or more flexible as needed.

   • Goal Setting: Help mentor/mentee pairs define what success looks like for both parties, creating focus and increasing progress tracking.

   • Company-Wide Mentorship Culture: Leaders must model this behavior by mentoring within their teams and recognizing those who dedicate time to develop others. This prevents mentorship from being viewed as a mere 'extra' duty.

3. Put in place Knowledge-Sharing Incentives and Tools

   • Collaboration Hubs: Dedicated Slack channels, or other platforms designed for asking questions, offering tips, and recognizing team members for helping.

   • Celebration of “Eureka” Moments: Encourage developers to share their hard-won solutions publicly, whether a brief internal knowledge article or a 'lunch and learn' presentation. Normalises both asking and sharing.

   • Reward Structures (If Feasible): Public shout-outs for those actively spreading knowledge creates positive reinforcement.

4. Make Sure your Team’s Internal Documentation is always a “Living Document”: Set clear expectations for who keeps internal resources up-to-date. A version control system (like Git) allows seeing when modifications were made, aiding in trust of content.

Some time ago I finished watching the TV series The Bear, and some parts of it keep resurfacing in my brain. And yes, you’ve guessed it. In order to declutter my mind, I’ll obviously need to write about it.

As I watched the show, my mind couldn't help but dwell on the various aspects of it that I come across in my daily work. “Hey, I know a guy that behaves like that and I have the same issues working with him“, or “Hey, I’ve seen my manager do the same thing to resolve a similar conflict“. What I found really cool about the show is that each main character seemed to be represented as an accentuated archetype of the different people you might encounter in your work environment: the controller, the perfectionist, the slacker, the over-achiever, the challenger, and somehow (after a really long struggle) the team manages to make it all work. We’ll get into how in a second. I also found bits of myself in almost every character and made me realise the issues I might be dealing with myself.

So what I want from this article is to present a reflection of the different dysfunctions of a team, different conflict resolutions, and what leadership lessons we can get from the show.

But first things first, what is the show about? The Bear unfolds the story of Carmen (Carmy) a young chef who, following his brother's death, returns to his hometown of Chicago. He inherits not only his family restaurant but also his brother's co-manager and a team of disorderly cooks. With experience in some of the world's finest restaurants, he is confident in transforming his family establishment into a culinary landmark. Easy, right? But what Carmy’s journey will unravel is an endless road of blockers: tight deadlines, challenging budget, difficult stakeholders, endless milestones, the pain of legacy work (in this case his brother’s huge unpaid debts), a ton of dependencies, unknown risks, burn out, lack of alignment, no shared vision, others’ pursue of self-interest over the well being of the team, personal commitments and so on. These are all real issues we’ve been dealing with which the show exposes in a really well-crafted manner.

The Archetypes

I couldn’t help but analyse how well the characters fitted in the Enneagram’s classic archetypes roles.

Firstly, we have Tina, the Challenger, who is resentful of change and of new-comers. She likes to be independent and refuses any type of help, even if it’s needed. When Sydney is appointed chef de cuisine, she constantly undermines Sydney's authority and disregards her advice. Her respect is earned through reason and competency, and not through age or status.

Sydney is The Achiever, the innovator, passionate about cooking, and very hard-working. She is always open and pushes for change. And sometimes pushing for too much at once, especially when the team is already dealing with a lot, leads to conflicts, as we’ll soon see.

Carmy is The Enthusiast, the observant, focused, and experienced person but with high anxiety, a problem of expressing himself, and the deep frustration that comes when he fails at that. Carmy loses his temper quickly. He doesn’t know how to communicate with his team. Routine and control calm him down.

Ritchie is The Giver (you doubt it but listen to me), the stubborn, lazy guy who takes it out on every one out of fear and anger at his own life. But under the angry hood, he is the loving and caring guy who cares strongly for his family even if he doesn't show it in words.

Marcus is The Peacemaker and The Perfectionist, an emphatic and thoughtful person but his dedication to his passion as a baker sometimes stands in the way of seeing the bigger picture as he fails to put the team’s wellbeing first before his own. This can be seen when he decides to work on his special doughnut rather than keep up with Carmy’s orders and his work at the restaurant during a busy and stressful time.

Getting to know your teammates’ ways of working and needs is crucial to making the team work well together: develop a common language, identify strengths and weaknesses, and build an authentic culture that works for you and them.

Lessons

I can’t share and analyse all the things I really appreciated about this show in the hope that I can still keep this article fairly short. So this is just a compressed list of lessons that came out from the different situations the team dealt with.

1. Grow your team; hire for passion and invest in skills

   Later in the show Tina and Ebra are sent to culinary school. Marcus is sent to Copenhagen to learn from a well-known baker and Natalie (Carmy’s sister) is brought in as a project manager because she might be a good fit. Even Richie is sent to a restaurant called Ever because Carmy “believes in him“. This completely changes the team’s dynamics as this constant investment in their skills makes them feel seen and appreciated. So they improve and contribute, and most importantly learn to care and show up.

2. Don’t stop the learning
   Another aspect I appreciated about the show was presenting how the team got unstuck when they were blocked (mentally). How they found inspiration and new creative ways to move forward. They would go outside and look at architecture, they would taste different foods, try out new restaurants, and travel to new places.
   Now this sounds expensive, and the thing is growth is not only hard but it can also come with a price. This is where Carmy stepped in with his network. As a leader, you might not be aware of the different realities people come from. Not everyone has your network or resources.
   
   During the show we can see Syd reading “Leading with the Heart: Coach K’s Successful Strategies for Basketball, Business, and Life” which emphasises the importance of leading with passion, empathy, and integrity. I haven’t read it but this approach to leadership will be emphasised in a lot of scenes during the show.
   

3. Trust your team

   One of my ‘but why’s’ moments was when Carmy sent Richie to a high-end, three-Michelin-star Chicago restaurant called Ever, to learn about how fine dining establishments are run. At this point, I was wondering how Richie fit in all of that. He’s the last person who would understand the importance of order and discipline. But what I wasn’t getting at that time is that Richie was battling some pretty big demons around his own ability and self-worth, like all of us out here, with our ever-growing imposter syndrome voice reminding us every day that we don’t belong and that we’ll never be good enough. And this is where Carmy steps in, and tells the crew over at Ever that he believes in Richie and his ability to work with people. Yes, Ritchie was supported by multiple people to be able to develop and thrive but without the trust from the others, maybe he wouldn’t have been able to step in and help Sydney when the tickets started to back up on opening night. Maybe he wouldn’t have been able to step up and become the “Expo” on that same night.
   

4. Cultivate your shared rituals
   Do what works for you to solve the issues you’re dealing with.
   
   Another aspect that made me “I need this in my relationship with others. This is good advice.” was Carmy and Sydney’s hand gesture. One of the things Carmy learned when he worked for another chef was that when tensions were high and there was no time to smooth things out, they would do this heart hand gesture to tell each other that they were sorry and that they could readdress the issue later. Sometimes too many emotions or having more high-priority issues on your mind don’t let you have the necessary bandwidth to deal with yet another issue. Having a shared ritual in your team for communicating the “I’m sorry, we’re both well-intentioned, but this is not a good time so let’s come back to this later.” can save your situation from overflowing into an out-of-control mess. Later on, Carmy and Sydney’s gesture ritual turns into a lack of communication and avoidance problem but we won’t talk about it now. What’s important is that while developing your rituals, you also need to adapt them or get rid of them accordingly when they don’t make sense for your team anymore. So, don’t continue doing something just because it used to work in the past.
   
   Other communication rituals help them maintain safety, optimise their work and show each other respect, like “Behind!” - I'm walking behind you, so please don't back up or turn quickly because one of us probably has a piping hot pot of something., “Corner!” - I'm coming around the corner, so be aware., “Hands”: Someone, please come grab this food and deliver it to the customer while it's hot. “Thank you, Chef.”
   

5. Show respect

   Talking about respect, I really enjoyed the “Yes, Chef“ acknowledgment. Even if they didn’t agree with one another, they would say “Yes, Chef“ as a type of “No matter what you're saying or asking, I hear you” and I find it a nice and thoughtful way of showing respect.
   

6. Take Ownership

   Another important lesson is shown during Ritchie’s time at Ever. During a staff meeting, a member of the team asks who was responsible for a smudge on a plate during a past service. The problem was not the smudge but that no one owned it. No one stepped up. Haven’t we been in similar meetings at work? Realising that something as small as that detail shouldn't matter, but it does. It matters because it’s proof of the team’s culture - a lack of ownership where no one will try to improve a process they’re not responsible for.

   
   “We're not children. It's okay to make mistakes. We can smudge things, but we need to own up to them with immediacy, integrity, and honesty.” (scene)
   

7. Be customer-obsessed

   Yet another interesting subject presented during Richie’s time at Ever is how much emphasis an established luxury restaurant puts on attention to detail. Some customers were chatting at their table about how disappointed they were to leave Chicago without trying the deep-dish pizza. The servers listened to the guests and carried the message to the kitchen, where they tracked down a real deep-dish pizza, which the chef remixed and sent it out to be served. Why is this important? The end product is not only the food but also the customer experience. Isn’t it the same in the tech space? The attention to detail, going above and beyond to understand your users and make their journey more enjoyable is what sets apart a successful company from the others.

8. Experiment, build, and break into small iterations

   When Syd and Carmy were working together on setting up the menu, they would start small. Experiment. Fail. Try Again. Fail some more. Try something else. When something works, go from there. Iterate.
   

9. Discover and embrace your leadership style

   Not everyone has the same talents or skills, so we all have different ways of conquering a problem. As so beautifully presented in the show, Richie has a way with people, Carmy brings with him his expertise, and Syd is the relentless innovator. While they all struggled for power at the beginning, they learned when it was time to take the lead and when it was time to take a step back and let the others do their thing.

"The Bear" serves as a captivating reflection of the intricacies that make a team work together, their diverse personalities, and ways of working. What adds further to the show's brilliance is its portrayal of how the team manages to make it all work. It’s a journey full of frustration, high cortisol levels, and sometimes desperation but when everybody works towards the same goal, nice things start to happen.