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

𝑻𝒉𝒆 𝑩𝒍𝒖𝒆𝒑𝒓𝒊𝒏𝒕 𝒇𝒐𝒓 𝑺𝒕𝒓𝒐𝒏𝒈 𝑾𝒐𝒓𝒌 𝑹𝒆𝒍𝒂𝒕𝒊𝒐𝒏𝒔𝒉𝒊𝒑𝒔: 𝑻𝒓𝒖𝒔𝒕, 𝑹𝒆𝒔𝒑𝒆𝒄𝒕, 𝒂𝒏𝒅 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒄𝒂𝒕𝒊𝒐𝒏 Creating healthy work relationships is vital for a positive and productive work environment. Key strategies include #effective #communication, which involves active listening, clear and concise expression, and promoting open dialogue. Mutual respect is another cornerstone, requiring respect for diversity, professionalism, and regular appreciation of colleagues' contributions. Building trust is essential, achieved through consistency, maintaining confidentiality, and being transparent in actions and intentions. Empathy and #emotionalintelligence also play crucial roles, as they help in understanding colleagues' feelings, managing one's emotions, and resolving conflicts constructively. Collaboration and #teamwork strengthen relationships by encouraging joint efforts, valuing contributions, and aligning with shared goals. Personal connections are important; getting to know colleagues and participating in social interactions foster #rapport. Supporting colleagues during challenging times further solidifies these bonds. Maintaining boundaries is crucial to ensure professionalism and respect for personal space and work-life balance. Continuous improvement in relationships can be achieved by seeking #feedback, reflecting on behavior, and engaging in professional development. 𝑲𝒆𝒚 𝑺𝒕𝒓𝒂𝒕𝒆𝒈𝒊𝒆𝒔 𝒇𝒐𝒓 𝑩𝒖𝒊𝒍𝒅𝒊𝒏𝒈 𝑯𝒆𝒂𝒍𝒕𝒉𝒚 𝑾𝒐𝒓𝒌 𝑹𝒆𝒍𝒂𝒕𝒊𝒐𝒏𝒔𝒉𝒊𝒑𝒔 ✅ 𝑬𝒇𝒇𝒆𝒄𝒕𝒊𝒗𝒆 𝑪𝒐𝒎𝒎𝒖𝒏𝒊𝒄𝒂𝒕𝒊𝒐𝒏: ✔️ Active Listening: Focus fully on colleagues when they speak, showing that you value their input through engagement and feedback. ✔️ Clear and Concise Communication: Articulate thoughts and expectations clearly to avoid misunderstandings; use straightforward, respectful language. ✔️Open and Honest Dialogue: Cultivate an environment where transparency in sharing thoughts and feelings is encouraged. ✅ 𝑴𝒖𝒕𝒖𝒂𝒍 𝑹𝒆𝒔𝒑𝒆𝒄𝒕: ✔️ Respect Differences: Embrace diversity by acknowledging and respecting different perspectives, backgrounds, and ideas. ✔️Professionalism: Treat everyone with courtesy and professionalism, irrespective of their position in the organization. ✔️Appreciation and Recognition: Regularly acknowledge colleagues' contributions, reinforcing their value within the team. ✅ 𝑩𝒖𝒊𝒍𝒅𝒊𝒏𝒈 𝑻𝒓𝒖𝒔𝒕: ✔️Consistency and Reliability: Build trust by being dependable and following through on commitments. ✔️Confidentiality: Keep sensitive information private, which helps foster trust among colleagues. ✔️Transparency: Be open about intentions and actions to eliminate suspicion and strengthen trust. In short, healthy work relationships are built on respect, trust, empathy, and effective communication. These relationships contribute to a supportive and unified workplace where everyone feels valued. What would you like to add more?

🎨🖊️ "Draw two circles under a rectangle…" "Now, make the circles connect to the rectangle" - some of the instructions that were given to me by our Head of Architecture during a recent offsite. We engaged in an exercise that underscored the importance of clear and effective communication. Each participant paired up, with one partner facing a screen displaying an image and the other facing a blank wall with a pen and paper. The challenge? The partner facing the screen had to guide their teammate in drawing the image using only directional and descriptive language. This exercise was a powerful reminder of how crucial it is to be clear, descriptive and thoughtful when sharing requirements, feedback or instructions. In the world of technology, we often fall into the trap of using complex language, acronyms, and omitting details we assume are "obvious." This can lead to confusion, misunderstandings, rework, and ultimately, wasted time. The key takeaway? Being specific doesn't always mean being overly detailed or long-winded. There's a beautiful balance between being specific and descriptive. It's about conveying the right amount of information in a way that's easily understood. Here are some common pitfalls to avoid when striving for specificity in communication: - Overloading with Details: Focus on the most relevant information to avoid overwhelming your audience. - Using Jargon and Acronyms: Consider your audience and provide explanations when necessary. - Assuming Shared Knowledge: Provide necessary context to ensure understanding. - Being Vague: Use precise language to prevent misunderstandings. - Neglecting the Audience's Perspective: Tailor your communication to the needs and understanding of your audience. I am reminded of a quote by Mark Twain: "I apologize for such a long letter - I didn't have time to write a short one." Concise communication takes time and effort, but it's always worth it. In our fast-paced world, mastering the art of effective communication is essential. It not only enhances collaboration but also drives efficiency and innovation. #Communication #Leadership #EffectiveCommunication

When I work with teams, I don’t just ask “do you trust each other?” I look for three specific capabilities: 1. Psychological Safety 💬“I feel safe to speak up.” This is the most studied predictor of team performance. Teams with psychological safety voice concerns earlier, catch problems faster, and bring their full thinking into the room. It creates intellectual openness. 2. Vulnerability 💬“I can ask for help.” Trust isn’t built through independence, it’s built through interdependence. When team members admit uncertainty, say “I don’t know,” or ask for support, they create a signal loop that says: we grow together. This is where openness emerges as a habit. It humanizes the team and makes learning possible. 3. Shared Accountability 💬“We’re in this together.” Even the safest, kindest team fails without this. Shared accountability turns a group of individuals into a collective. It’s where courage kicks in to follow through, own outcomes, and hold each other to a shared standard. This is what transforms trust from a feeling into a performance structure. We often talk about trust like it’s a mood. Like it appears when people “click” or when culture is “nice.” But in high-performing teams, trust isn’t chemistry. It’s architecture. Built not on feelings, but on behaviors, signals, and systems.

If you think overcommunication is annoying, wait until you have to redo your work because of a simple misunderstanding. Guess which one is worse. As an entry-level engineer, you might feel that overcommunication is unnecessary. You might think, "This could be straightforward, why bother bringing it up?" But here’s the truth: overcommunication can save you time and effort. I learned this the hard way. 💬 I was working on a ticket and followed its description to the letter. I shared my approach during the team standup, got inputs, and started implementing. Everything seemed fine. But as I was close to completing it, I realized the planned outcome wasn’t possible. When I raised this, my manager stepped in and explained that we needed a completely different approach. It turned out she wasn't in the standup where I shared my plan. I assumed approval from the team was enough, but in hindsight, a quick confirmation from my manager could have saved me a lot of rework. This wasn’t a high-priority task, so there was no major impact. But it taught me that overcommunicating isn’t a burden, it’s a safety net. ✅ Takeaway: How to avoid this situation in the future 💡 Use Team Channels. If you’ve shared your approach verbally, follow up in the team’s messaging channel. Write something like: “Here’s how I’m planning to approach Ticket #123. Please let me know if there’s anything I should reconsider or if this doesn’t align with expectations.” 💡 Document Assumptions. When you’re not 100% sure about something, spell it out. This invites corrections early. 💡 Confirm with Stakeholders. If someone wasn’t part of the discussion, proactively loop them in with a summary. 💡 Don’t Be Shy. Remember, you’re not being annoying, you’re ensuring success for the entire team.

I urge you—please take them away from their desks! Last month, my team and I spent a day at Lohagarh Farms, away from screens, meetings, and the usual work routine. No emails, no targets, just time spent together outside the office. On the surface, it might seem like just another team outing. But here’s what actually happened: [1] We connected beyond work Conversations shifted from deadlines and strategies to real-life stories. Team members who barely spoke in the office suddenly had endless things to talk about. [2] We saw different strengths.  Someone who’s quiet in meetings turned out to be fiercely competitive in outdoor games. Another, who’s usually reserved, took charge in organizing activities. You start seeing people in a completely different light. [3] We learned to collaborate without pressure.  In the workplace, collaboration is often tied to performance. But here, teamwork was effortless, whether it was completing challenges together or simply sharing a meal. The bonds built in those moments carry over when we’re back in the office. [4] A workplace functions best when the team works for each other, not just with each other. And that happens when relationships go beyond work. Many leaders think of team outings as an expense or a break from work. But the truth is, the best ideas, the strongest teams, and the highest productivity often stem from environments where people feel comfortable, connected, and valued. After this, I know one thing for sure that investing in a team doesn’t only mean training programs and appraisals. It also means creating shared experiences that make people feel like they belong. How do you build strong connections in your workplace? #teambuilding

The quality of your product is capped by the quality of your relationships. Specifically: Your relationship with engineering. You can have perfect strategy, brilliant insights, clear roadmaps. None of it matters if your eng team doesn't trust you. The trust markers nobody talks about: LOW TRUST: - Engineers ask for everything in writing - They push back on timelines defensively - They go silent when you ask for ideas - They build exactly what you spec, nothing more HIGH TRUST: - They tell you when your idea is bad - They proactively suggest better approaches - They ship things you didn't ask for that you needed - They protect you from your own mistakes Here's what most PMs get wrong: They think trust comes from being right. It doesn't. Trust comes from: - Admitting when you don't know - Taking responsibility when things go wrong - Defending eng decisions to stakeholders - Not throwing them under the bus when timelines slip The shift: Stop trying to be impressive. Start being reliable. The best PM-eng relationships feel like partnerships, not transactions. Your eng lead should feel comfortable saying “That's a terrible idea” to your face. If they don't, you don't have trust. You have compliance. And compliance doesn't build great products. What changed when your engineering relationship went from transactional to trusted? #ProductManagement #Engineering #Trust #Collaboration

In "The Venture Mindset", we explore how successful companies foster innovation by prioritizing people over rigid processes, without abandoning structure entirely. Effective innovation requires cutting through bureaucracy while keeping development teams small, independent, and shielded from politics. Gmail at Google started with just one engineer, Paul Buchheit. His bosses simply told him to "build some type of email product" – no detailed requirements, no rigid process. He ran with it and created something that changed email forever. The Happy Meal has a similar story. A McDonald's franchisee in Guatemala, Yolanda Fernández de Cofiño, came up with a children's menu on her own, without asking permission. The idea spread at a company convention and soon became a global phenomenon. Want to support innovation? Trust your people, give them resources but not micromanagement, set up simple systems for testing new ideas, take smart risks on promising projects, and be ready to scale up what works.

One of the clearest signals of whether a transformation is working isn’t in the plan - it’s in the conversations happening in your teams. So pay close attention to the frequency of healthy debate, constructive challenge and openness to new and divergent ideas that takes place. If the frequency is low… …there is the risk of creating the illusion of performance because people readily ‘understand’ each other, agree on everything, collaboration seems to flow smoothly and there is a collective sensation of progress. However, the opportunity cost is teams gets trapped in their own paradigms, opportunities get overlooked, risks ignored - and ultimately their output becomes derivative not innovative, performance diminishes as opposed to improving and compounding. If the frequency is high… …there is a level of psychological safety that allows for team members to be more objective, to speak up with relevant ideas, to constructively challenge each other, and bring their diverse perspectives and experiences to the table - in the knowledge it won’t be held against them. This opens up the opportunity of reframing the paradigm, and connecting different perspectives and ideas. Ingredients for creativity, innovation, resilience and performance. You see homogeneous teams might feel easier, but easy doesn’t translate into Performance. Here are a few ideas to experiment with your teams… 1. Intentionally foster a team environment that replaces scepticism with intellectual curiosity, an open and learning mindset.   2. Consider how you can create a ways of working that allows all ideas and perspectives from everyone in the room to be heard. 3. Encourage dissenting perspectives. Surrounding yourself with people who are willing to disagree with you and challenge your perspectives and each other. 4. Consider whether you may need to invite others to that creative or idea generation meeting to ensure you get a broader perspective. 5. De-stigmatise failure through sharing past mistakes and celebrating lessons learnt. 6. Institutionalise a team culture of healthy candour. Candour is one of the key attributes to improving the quality of output, levelling up creativity and enabling effective collaboration. What would you add? #transformation #culture #psychologicalsafety

Project managers - you need to speak the language of your stakeholders Effective communication isn't just about sharing updates. It's about knowing: → What to share → With who → When You may be tempted to think sharing more is better. But not always. Some stakeholders want all the deets. Others just want the status of the big picture. And some only want to be tagged if things are getting dicey. The key: adapt your message based on your audience Some examples: 👉 Executives may only want to know whether things are on-track 👉 Teams are looking for the technical details and the "how" 👉 Customers care about the end product and impacts Tailor your communication to each stakeholders needs. It builds trust. Keeps everyone aligned. And shows respect for their time and project role. So don't just deliver results. Deliver the right message to the right people at the right time. 🤙