Effective Team Leadership In Engineering Projects

Should you try Google’s famous “20% time” experiment to encourage innovation? We tried this at Duolingo years ago. It didn’t work. It wasn’t enough time for people to start meaningful projects, and very few people took advantage of it because the framework was pretty vague. I knew there had to be other ways to drive innovation at the company. So, here are 3 other initiatives we’ve tried, what we’ve learned from each, and what we're going to try next. 💡 Innovation Awards: Annual recognition for those who move the needle with boundary-pushing projects. The upside: These awards make our commitment to innovation clear, and offer a well-deserved incentive to those who have done remarkable work. The downside: It’s given to individuals, but we want to incentivize team work. What’s more, it’s not necessarily a framework for coming up with the next big thing. 💻 Hackathon: This is a good framework, and lots of companies do it. Everyone (not just engineers) can take two days to collaborate on and present anything that excites them, as long as it advances our mission or addresses a key business need. The upside: Some of our biggest features grew out of hackathon projects, from the Duolingo English Test (born at our first hackathon in 2013) to our avatar builder. The downside: Other than the time/resource constraint, projects rarely align with our current priorities. The ones that take off hit the elusive combo of right time + a problem that no other team could tackle. 💥 Special Projects: Knowing that ideal equation, we started a new program for fostering innovation, playfully dubbed DARPA (Duolingo Advanced Research Project Agency). The idea: anyone can pitch an idea at any time. If they get consensus on it and if it’s not in the purview of another team, a cross-functional group is formed to bring the project to fruition. The most creative work tends to happen when a problem is not in the clear purview of a particular team; this program creates a path for bringing these kinds of interdisciplinary ideas to life. Our Duo and Lily mascot suits (featured often on our social accounts) came from this, as did our Duo plushie and the merch store. (And if this photo doesn't show why we needed to innovate for new suits, I don't know what will!) The biggest challenge: figuring out how to transition ownership of a successful project after the strike team’s work is done. 👀 What’s next? We’re working on a program that proactively identifies big picture, unassigned problems that we haven’t figured out yet and then incentivizes people to create proposals for solving them. How that will work is still to be determined, but we know there is a lot of fertile ground for it to take root. How does your company create an environment of creativity that encourages true innovation? I'm interested to hear what's worked for you, so please feel free to share in the comments! #duolingo #innovation #hackathon #creativity #bigideas

How to compare your eng team's velocity to industry benchmarks (and increase it): Step 1: Send your eng team this 4-question survey to get a baseline on key metrics: https://lnkd.in/gQGfApx4 You can use any surveying tool to do this—Google Forms, Microsoft Forms, Typeform, etc.—just make sure you can view the responses in a spreadsheet in order to calculate averages. Important: responses must be anonymous to preserve trust, and this survey is designed for people who write code as part of their job. Step 2: Calculate your how you're doing. - For Speed, Quality, and Impact, find the average value for each question’s responses. - For Effectiveness, calculate the percent of favorable responses (also called a Top 2 Box score) across all Effectiveness responses. See the example in the template above. Step 3: Track velocity improvements over time. Once you’ve got a baseline, you can start to regularly re-run this survey to track your progress. Use a quarterly cadence to begin with. Benchmarking data, both internal and external, will help contextualize your results. Remember, speed is only relative to your competition. Below are external benchmarks for the key metrics. You can also download full benchmarking data, including segments on company size, sector, and even benchmarks for mobile engineers here: https://lnkd.in/gBJzCdTg Look at 75th percentile values for comparison initially. Being a top-quartile performer is a solid goal for any development team. Step 4: Decide which area to improve first. Look at your data and using benchmarking data as a reference point, pick which metric you believe will make the biggest impact on velocity. To make this decision about what to work on to improve product velocity, drill down to the data on a team level, and also look at qualitative data from the engineers themselves. Step 5: Link efficiency improvements to core business impact metrics Instead of presenting these CI and release improvement projects as “tech debt repayment” or “workflow improvements” without clear goals and outcomes, you can directly link efficiency projects back to core business impact metrics. Ongoing research (https://lnkd.in/grHQNtSA) continues to show a correlation between developer experience and efficiency, looking at data from 40,000 developers across 800 organizations. Improving the Effectiveness score (DXI) by one point translates to saving 13 minutes per week per developer, equivalent to 10 hours annually. With this org’s 150 engineers, improving the score by one point results in about 33 hours saved per week. For so much more, don't miss the full post: https://lnkd.in/grrpfwrK

Conflict gets a bad rap in the workplace. Early in my career, I believed conflict had no place in a healthy workplace. As I progressed, I realized that it was quite the contrary. The lack of conflict isn't a sign of a healthy work culture, rather it is an indication that important debates, discussions and differing viewpoints are being disregarded or suppressed. This insight revealed another key aspect: high-performing teams do not shy away from conflict. They embrace it, leveraging diverse opinions to drive optimal outcomes for customers. What sets these teams apart is their ability to handle conflict constructively. So how can this be achieved? I reached out to my friend Andrea Stone, Leadership Coach and Founder of Stone Leadership, for some tips on effectively managing conflict in the workplace. Here's the valuable guidance she provided: 1. Pause: Take a moment to assess your feelings in the heat of the moment. Be curious about your emotions, resist immediate reactions, and take the time to understand the why behind your feelings. 2. Seek the Other Perspective: Engage genuinely, listen intently, show real interest, and ask pertinent questions. Remember to leave your preconceived judgments at the door. 3. Acknowledge Their Perspective: Express your understanding of their viewpoint. If their arguments have altered your perspective, don't hesitate to share this with them. 4. Express Your Viewpoint: If your opinion remains unswayed, seek permission to explain your perspective and experiences. Remember to speak from your viewpoint using "I" statements. 5. Discuss the Bigger Objective: Identify common grounds and goals. Understand that each person might have a different, bigger picture in mind. This process can be taxing, so prepare beforehand. In prolonged conflict situations, don't hesitate to suggest breaks to refresh and refuel mentally, physically, and emotionally. 6. Know Your Limits: If the issue is of significant importance to you, be aware of your boundaries. For those familiar with negotiation tactics, know your BATNA (Best Alternative to a Negotiated Agreement). 7. Finalize Agreements: Once an agreement has been reached, continue the engagement to agree on responsibilities and timeframes. This ensures clarity on the outcome and commitments made. PS: Approach such situations with curiosity and assume others are trying to do the right thing. 🔁 Useful? I would appreciate a repost. Image Credit: Hari Haralambiev ----- Follow me, tap the (🔔) Omar Halabieh for daily Leadership and Career posts.

Most change initiatives don't fail because of the change that's happening, they fail because of how the change is communicated. I've watched brilliant restructurings collapse and transformative acquisitions unravel… Not because the plan was flawed, but because leaders were more focused on explaining the "what" and "why" than on how they were addressing the fears and concerns of the people on their team. People don't resist change because they don't understand it. They resist because they haven't been given a compelling story about their role in it. This is where the Venture Scape framework becomes invaluable. The framework maps your team's journey through five distinct stages of change: The Dream - When you envision something better and need to spark belief The Leap - When you commit to action and need to build confidence The Fight - When you face resistance and need to inspire bravery The Climb - When progress feels slow and you need to fuel endurance The Arrival - When you achieve success and need to honor the journey The key is knowing exactly where your team is in this journey and tailoring your communication accordingly. If you're announcing a merger during the Leap stage, don't deliver a message about endurance. Your team needs a moment of commitment–stories and symbols that anchor them in the decision and clarify the values that remain unchanged. You can’t know where your team is on this spectrum without talking to them. Don’t just guess. Have real conversations. Listen to their specific concerns. Then craft messages that speak directly to those fears while calling on their courage. Your job isn't just to announce change, but to walk beside your team and help your team understand what role they play in the story at each stage. #LeadershipCommunication #Illuminate

Teams are often dysfunctional. For six reasons, not five. In his 2002 book "The Five Dysfunctions of a Team," Patrick Lencioni suggested that genuine teamwork is rare, and that organizations often unknowingly fall prey to five interrelated dysfunctions that hinder team effectiveness. These dysfunctions form an inverted pyramid, each one leading to the next: - Absence of Trust: Team members are unwilling to be vulnerable, leading to... - Fear of Conflict: Inability to engage in unfiltered, passionate debate of ideas, leading to... - Lack of Commitment: Feigning agreement during meetings, leading to... - Avoidance of Accountability: Hesitation to call peers on actions and behaviors that seem counterproductive, leading to... - Inattention to Results: Putting individual needs above the collective goals of the team. Lencioni emphasizes that while these concepts are simple in theory, they require significant discipline and persistence to overcome in practice. He also writes that the leader plays a crucial role by demonstrating vulnerability first, setting the tone for the team to follow. I very much agree with his take. Based on my experience working with diverse teams across the globe, though, I would add another dysfunction: 6. Misunderstanding the Power of Difference: Diverse teams bring unique perspectives and strengths, but misunderstanding or underestimating these differences can lead to missed opportunities and great resentment. Here's how to address this dysfunction: - Acknowledge, understand and value differences. - Foster inclusive, candid communication. - Don't blame difference when things go wrong (since difference is usually not to blame). Whatever the line of difference—identity, role, or geographical location—effective teams manage differences proactively and thoughtfully. When they don't, misunderstandings and misinterpretations due to differences in language, cultural norms, and communication styles can hinder their effectiveness. When we recognize and harness differences, we unlock the full potential of teams, driving exceptional results. #Collaboration #Teams #HumanResources #Leadership #Innovation #Difference #Communication

Your team isn't lazy. They're confused. You need a culture of accountability that's automatic: When accountability breaks down, it's not because people don't care. It's because your system is upside down. Most leaders think accountability means "holding people responsible." Wrong. Real accountability? Creating conditions where people hold themselves responsible. Here's your playbook: 📌 Build the Base Start with a formal meeting to identify the real issues. Don't sugarcoat. Document everything. Set a clear date when things will change. 📌 Connect to Their Pain Help your team understand the cost of weak accountability: • Stalled career growth • Broken trust between teammates • Mediocre results that hurt everyone 📌 Clarify the Mission Create a mission statement so clear that everyone can recite it. If your team can't connect their role to it in one sentence, They can't make good decisions. 📌 Set Clear Rules Establish 3-5 non-negotiable behaviors. Examples:  • We deliver what we commit to  • We surface problems early  • We help teammates succeed 📌 Point to Exits Give underperformers a no-fault, 2-week exit window. This isn't cruelty. It's clarity. 📌 Guard the Entrance Build ownership expectations into every job description. Hire people who already act like owners. 📌 Make Accountability Visible Create expectations contracts for each role. Define what excellence looks like. Get signed commitments. 📌 Make It Public Use weekly scorecards with clear metric ownership. When everyone can see who owns what. Accountability becomes peer-driven. 📌 Design Intervention Create escalation triggers: Level 1: Self-correction Level 2: Peer feedback Level 3: Manager coaching Level 4: Formal improvement plan 📌 Reward the Right Behaviors Reward people who identify problems early. (not those who create heroic rescues) 📌 Establish Rituals Conduct regular reviews, retrospectives, and quarterly deep dives. 📌 Live It Yourself Share your commitments publicly. Acknowledge your mistakes quickly. Your team watches what you do, not what you say. Remember: The goal isn't to catch people failing. It's to create conditions where:  • Failure becomes obvious  • And improvement becomes inevitable. New managers struggle most with accountability:  • Some hide and let performance drop  • Some overcompensate and micromanage We can help you build the playbook for your team. Join our last MGMT Fundamentals program for 2025 next week. Enroll today: https://lnkd.in/ewTRApB5 In an hour a day over two weeks, you'll get:  • Skills to beat the 60% failure rate  • Systems to make management sustainable  • Live coaching from leaders with 30+ years experience If this playbook was helpful... Please ♻️ repost and follow 🔔 Dave Kline for more.

At Amazon, two of my top engineers had a shouting match that ended in tears. This could be a sign of a toxic workplace or a sign of passion and motivation. Whether it becomes toxic or not all comes down to how management deals with conflict. In order to deal with conflict in your team, it is first essential to understand it. A Harvard study has identified that there are 4 types of conflict that are common in teams: 1. The Boxing Match: Two people within a team disagree 2. The Solo Dissenter: Conflict surrounds one individual 3. Warring Factions: Two subgroups within a team disagree 4. The Blame Game: The whole team is in disagreement My engineers shouting at each other is an example of the boxing match. They were both passionate and dedicated to the project, but their visions were different. This type of passion is a great driver for a healthy team, but if the conflict were to escalate it could quickly become toxic and counterproductive. In order to de-escalate the shouting, I brought them into a private mediation. This is where one of the engineers started to cry because he was so passionate about his vision for the project. The important elements of managing this conflict in a healthy and productive way were: 1) Giving space for each of the engineers to explain their vision 2) Mediating their discussion so that they could arrive at a productive conclusion 3) Not killing either of their passion by making them feel unheard or misunderstood Ultimately, we were able to arrive at a productive path forward with both engineers feeling heard and respected. They both continued to be top performers. In today’s newsletter, I go more deeply into how to address “Boxing Match” conflicts as both a manager and an IC. I also explain how to identify and address the other 3 common types of team conflict. You can read the newsletter here https://lnkd.in/gXYr9T3r Readers- How have you seen team member conflict handled well in your careers?

I've trained 600+ project managers over the last 3 years. From budding teams in start-ups to large-scale projects in multinational corporations. Hre are 9 challenges and recommendations frequently shared. 1) Scope Creep Management It's daunting when project deliverables keep changing. Without clear boundaries and pushback, projects will derail. Highly recommend reading "Scope and Requirements Management" and "Effective PM and BA Role Collaboration" to solidify your scope management strategies. 2) Time Management Effective PMs understand that every minute counts. Design an “Ideal Project Week” and schedule critical tasks. Risk assessment? Schedule it. Stakeholder meeting? Schedule it. Documentation review? Schedule it. 3) Stakeholder Engagement Project Managers need to skillfully manage stakeholder expectations. Instead of just updating on progress, send out agendas ahead of stakeholder meetings. Focus on critical discussion points, and be prepared to address the top concerns. 4) Resource Allocation It's tempting to bring in the best talents, but ensure they align with the project's current needs. Don’t bring in a high-level consultant when you need hands-on expertise on the ground. 5) Driving Team Accountability Inconsistent team updates and feedback loops can hurt a project's momentum. As the PM authority, establish regular checkpoints. Embrace the mantra: “Consistency is the heartbeat of projects.” 6) Clear Project Objectives If stakeholders or team members can't quickly summarize the project's goal and outcomes, there’s a clarity issue. Consider methodologies like SMART goals to crystallize your objectives. 7) Handling Conflicts Project disputes, if not addressed promptly, can escalate and impact delivery. Address conflicts head-on. Familiarize yourself with techniques from "Crucial Conversations" for effective resolution. 8) Budgeting Managing finances is critical. A well-told narrative about your project’s ROI and value proposition is invaluable. Understand your budget's narrative, including how resources are allocated, potential ROI, and long-term project benefits. This narrative informs future budgeting decisions. 9) Project Strategy Many project managers grapple with succinctly defining their approach. A clearly articulated strategy not only provides direction but aids in stakeholder buy-in. I highly recommend diving into the "Project Management Body of Knowledge (PMBOK)" to sharpen your strategic skills. How do you prioritize and balance stakeholder engagement with ensuring timely project delivery, especially when faced with conflicting interests?

The key to progress on hard, complex projects comes down to latency and bandwidth — the interfaces through which teams communicate. 1 / Latency is the delay. How long it takes for information to travel, decisions to be made, or problems to surface. High latency slows everything down — people wait, guess, or lose momentum. Strong leaders reduce latency by creating environments where: Feedback moves quickly. Problems are flagged early and acted on decisively. Communication loops are short, direct, and clear. 2 / Bandwidth is the capacity. How much information can flow between people. Low bandwidth leads to confusion, blind spots, and misalignment. Strong leaders increase bandwidth by ensuring: Teams share the right context at the right time. Communication is open, transparent, and efficient. People trust each other enough to exchange ideas freely. When latency is low and bandwidth is high, progress accelerates. Teams collaborate seamlessly. Small signals get noticed before they become big problems. Decision-making improves. Great leaders don’t just manage — they optimize the interfaces of communication within the team. They create systems where ideas flow, feedback happens in real time, and no one is stuck waiting for clarity. Because in the end, the speed and quality of progress aren’t just about individual talent — they’re about how well the team interacts. Thoughts??? If you’re building hard things and want signal over hype, subscribe to Per Aspera. 👉🏻 Join here: https://lnkd.in/gacTgUkh

The uncomfortable truths about high-performing teams that nobody talks about (and what to do about it). After two decades of coaching executive teams, I've discovered five counterintuitive truths about exceptional performance: 👉 High-performing teams have more conflict, not less. Teams engaging in intellectual conflict outperform peers by 40% in complex decisions. → Action: Schedule structured debate sessions where challenging ideas is explicitly encouraged. 👉 Top teams strategically exclude people. McKinsey & Company found that each member above nine decreased productivity by 7%. → Action: Create a core decision team while establishing transparent processes for broader input. 👉 The best teams often break company rules. MIT Sloan School of Management research shows 65% of top teams regularly deviate from standard procedures. → Action: Identify which processes truly add value versus those that add bureaucracy. 👉 Emotional intelligence can be overrated (but not overlooked). Teams with moderate EQ but high practical intelligence outperform by 23%. → Action: Balance empathy with pragmatic problem-solving in your team assessments. 👉 Effective teams experience productive dysfunction. 82% of top teams go through significant tension phases before breakthroughs. → Action: Recognize periods of dysfunction as potential catalysts rather than failures. In today's complex work environments, understanding these hidden truths is critical. Embracing these contradictions rather than fighting them positions you as a leader to build exceptional teams—even when the process looks messier than expected. Embrace the mess. Coaching can help; let's chat. Joshua Miller #executivecoaching #leadership #teamdevelopment