Effective Team Leadership In Engineering Projects

When I first asked my team for feedback, the room went SILENT. Why? Because speaking the truth felt too risky. This isn’t just my story, it’s the reality in countless workplaces. Here’s the truth: feedback is a minefield. 🔴 Done wrong? It breeds tension and mistrust. 🟢 Done right? It fixes problems—it transforms teams. Here’s how to get it right: 1/ Timing Is Everything ↳ Feedback during chaos? Disaster. Wait for a calm moment. ↳ A private 1-on-1 works best. 💡 Pro Tip: Start with a positive comment—it sets the tone. 2/ Lead With Solutions ↳ Complaints without fixes = noise. Solutions = action. ↳ Try this: “We could avoid confusion with more clarity upfront. What do you think?” 💡 Pro Tip: Frame solutions as support for the team’s success, not criticism. 3/ Be Clear, Not Cryptic ↳ Instead of “Communication could be better,” say: ↳ “Inconsistent updates slow me down. Weekly check-ins might help.” 💡 Pro Tip: Use examples to back it up—clarity builds trust. 4/ Use “I” Instead of “You” ↳ Feedback isn’t a blame game. Stick to “I” statements to share your perspective. ↳ Example: “I feel I don’t have enough autonomy to contribute fully.” 💡 Pro Tip: Highlight how solving the issue benefits the whole team. 5/ Know When to Let It Go ↳ Pick your battles. Save your energy for what really matters. ↳ Does this impact the team or my work? If not, let it go. 💡 Pro Tip: Focus feedback on what aligns with team goals. 6/ End With a Vision ↳ Great feedback doesn’t just fix problems—it builds something better. ↳ Paint the big picture: “Here’s how this change could help the team hit the next level.” 💡 Pro Tip: Vision-driven feedback inspires action. The takeaway? Feedback isn’t about proving you’re right, it’s about progress. Master these steps, and you’ll not only solve problems, but you’ll also earn respect and trust. What’s your biggest feedback fail (or win)? Share it below. 👇 ♻️ Repost to help your network get better! ➕ And follow Shulin Lee for more.

Accountability Nearly every organization I work with at the moment is focused on some version of creating a "high-performance" culture. Alongside this goal is a push for greater speed of decision-making, efficiency, and accountability. However, a common mistake many organizations make is treating accountability as a binary attribute—individuals are either seen as accountable or not. In reality, accountability is more nuanced. Understanding accountability as a spectrum is critical for cultivating a high-performance culture. The Accountability Ladder illustrates this concept by mapping out various levels at which individuals engage with their responsibilities, ranging from unaware or indifferent to becoming proactive and inspiring others. Those familiar with the Leadership Circle Profile will note that accountability transforms as leaders pivot from an external to an internal locus of control. This move from a Reactive to Creative mindset is a critical prerequisite. Here is a summary of each step on the ladder: Unaware: At this level, individuals are not aware of the issues or their responsibilities. They lack the knowledge necessary to understand what needs to be done. Blaming Others: Individuals recognize the issue but choose to blame others rather than taking any responsibility. They see the problem as someone else's fault. Excuses: At this step, individuals acknowledge the problem but offer excuses for why they can't address or resolve it. They often cite external factors or limitations. Wait and Hope: Individuals here are aware of the problem and hope it gets resolved by itself or that someone else will take care of it. There is recognition but no action. Acknowledge Reality: This is a turning point on the ladder. Individuals acknowledge the reality of the situation and their role in it but have not yet begun to take corrective action. Own It: Individuals take ownership of the problem and accept their responsibility for dealing with it. They start to commit to resolving the issue. Find Solutions: At this step, individuals not only take ownership but also actively seek solutions. They explore various options to resolve the problem. Take Action: Individuals implement the solutions they have identified. They take concrete steps to resolve the issue. Make It Happen: Individuals not only take action but also follow through to ensure that the solutions are effective. They monitor progress and make adjustments as necessary. Inspire Others: Leaders inspire and encourage others to take accountability, creating a proactive problem-solving culture. As a team exercise, try writing the steps of the accountability ladder on a whiteboard and ask: What level of accountability do we see across the organization? What level do we exhibit as a team (to each other and our stakeholders)? And finally, where would I place myself?

Do you also feel your roadmap planning is a counterproductive waste of time? Change that to a productive exercise that will set your success 12 months ahead with the following 10 pieces of advice: 1) Start too early The earlier you start, the more time you have to align with stakeholders and refine priorities. October might feel early, but having a draft ready before the year ends allows for feedback and stressless adjustments. 2) Clarify goals and strategy A roadmap without a clear purpose is just a wish list. Tie it to business goals, customer needs, and your overarching strategy. This gives your roadmap direction and credibility. 3) Allow everyone to chip in Your roadmap will be stronger if it includes diverse perspectives. Devs will ask for essential technical investments, sales understand customer pain points, and support hears complaints daily. Use their input to ensure your roadmap addresses real needs. 4) Double-check with legal Don't overlook this! Legal compliance can make or break your plans, especially in industries like fintech, healthcare, or data-heavy products. A quick legal review now can save you from costly setbacks later. 5) Organize a brainstorming workshop Bring stakeholders together for a focused brainstorming session. Use sticky notes, whiteboards, or virtual tools to encourage creativity. Workshops help uncover ideas you might not have considered and build alignment early. 6) Put an effort estimate on the most promising items Prioritization isn't just about impact; effort matters too. Collaborate with your devs to estimate the time and resources needed for each initiative. This helps balance quick wins with high-impact projects and helps choose the actual roadmap items during prioritization. 7) Ask your designer to put some quick visuals for the selected initiatives A picture is worth a thousand words. Having simple visuals for key roadmap items can help stakeholders grasp the vision faster and ensure everyone is aligned on what success looks like. 8) Organize work by quarters, not months, and especially not sprints Quarterly planning gives enough flexibility to adapt while still maintaining structure. Monthly plans can feel too rigid, and sprint-level roadmaps are operational, not strategic. Keep your roadmap focused on the big picture. 9) Leave room to breathe Don't overload the roadmap. Unexpected challenges will arise, and new opportunities will pop up. Leaving 20-30% of capacity unplanned ensures you can adapt without derailing the entire roadmap. 10) Be careful with your comms Communicate clearly that the roadmap is a direction, not a commitment. You’re agile, not waterfall. Keep flexibility baked into your messaging to avoid frustration later. So, does your roadmap planning feel like it produces something meaningful? Let me know in the comments! #productmanagement #productmanager #roadmap P.S. If you liked this read, be sure to catch more with my free newsletter. Subscribe at: www. drbartpm. com :)

Autonomy is often wrongly confused with independence. This mistake negatively affects accountability. People sometimes mistakenly think that giving people autonomy means leaving them completely to their own devices (this is independence). In the organizational sense, autonomy is not the opposite of structure—it’s the freedom to operate WITHIN a structure that supports continuous improvement and accountability. A Lean mindset and approach helps leaders to understand how to foster BOTH accountability and autonomy. Lean leaders do this by intentionally moving away from making people feel like they are "being held accountable" (which feels imposed) and inspiring them to "take accountability" (a sense of ownership that naturally fosters autonomy). Here’s how you can adopt this approach in YOUR team: 🟢 Be clear about goals, roles, and responsibilities: Use tools like RACI charts or visual management boards to clarify who does what. 🔴 Define success together: Involve the team in setting performance standards or KPIs so they have a say in what they’re working toward. 🟣 Encourage regular 1:1 check-ins and team huddles: create spaces for discussing challenges without fear. 🟡 Engage people in problem-solving: Use structured techniques and Kaizen to involve the team in addressing inefficiencies. 🔵 Ask for their ideas first: Instead of directing what needs to change, coach them with powerful questions like, “What do you think is the best next step?” 🟤 Use visual management: Team dashboards or Kanban boards make progress visible, reduce micromanagement and highlight areas needing attention. 🟠 Review metrics as a team: Make this part of regular meetings, so progress and accountability are a collective effort. ⚫ Own your commitments: If you make a mistake or miss a deadline, acknowledge it openly. ⚪ Model humility: Admit when you don’t have all the answers and seek input from the team. (This makes people feel valued!!) 🤔Reflection time for leaders... Are you balancing structure and flexibility in your team? Which of the above could you act on to shape a culture of autonomy?

As an advisor to tech scaleups, and a former CTO and SVP of Engineering,  I've often encountered a familiar CEO complaint: "Our engineering team is too slow!" However, focusing solely on increasing individual productivity is rarely the solution. Sometimes the answer is changing the organizational structure. 🔍 The Issue with Flat Structures: Time to market was a major problem in a scale-up I advised, even though they had a flat structure where 40+ engineers reported directly to the VP of engineering and all of them shared equal accountability to the delivery of the software. 🚧 The Consequences: Major overcommitment.  People raised their hands to take on work even if the group was super extended. There was nobody that fully understood the team’s capacity vs the actual workload they took on. This approach led to a lack of predictability, chronic delays, unhappy customers, and ultimately, a tarnished reputation. 🛠️ The Solution: Transitioning to a hierarchical structure with focused teams and accountable experienced leaders was the game-changer. This shift brought in clarity, accountability, and much-needed structure. 📈 The Results: Predictable schedules, improved customer satisfaction, and a thriving engineering culture. ✅ Takeaways for Your Organization: Examine your organization with critical eyes: Is your ownership and accountability structure clear? Are your teams sized and focused appropriately? Do your leaders have the authority to deliver effectively? For more on the case study and about building a sustainable, efficient, and customer-centric engineering team in the blog post. 💭 I'm curious to hear your thoughts: Have you faced similar challenges? How did you address them? Let's share insights and grow together! #EngineeringManagement #Leadership #Productivity  _______________ ➡️ I am Talila Millman, a fractional CTO,  a management advisor, and a leadership coach. I help CEOs and their C-suite grow profit and scale through optimal Product portfolio and an operating system for Product Management and Engineering excellence.  📘 My book The TRIUMPH Framework: 7 Steps to Leading Organizational Transformation will be published in Spring 2024 https://lnkd.in/eVYGkz-e

One of the most important lessons I’ve learned in leadership is that you don’t have to be the expert. In fact, often, not being the expert can be an advantage in pulling together a great team that delivers fantastic outcomes. For someone who has spent much of my life in engineering businesses, I have a rather unusual background - I’m not an engineer nor a distribution expert. My degree is in food sciences and agriculture, and I trained as an accountant. Before stepping into industry, I spent 12 years as an investment banker in London and New York. What this background has taught me is the value of building a diverse team and trusting them to deliver… whilst providing a bit of coaching along the way. I have never believed I could engineer anything better than the engineers I’ve had the privilege to work with, nor make better people judgements than the people team . Instead, my role has always been about facilitating success - creating an environment where diverse talent can work effectively together as an aligned team, allowing everyone to contribute by empowering them doing what they do best in pursuit of common objectives. In engineering and beyond, the key to success lies in empowering people. It’s about enabling teams to recognise and truly understand the needs of the customers they serve and to develop efficient and effective solutions to the problems they and other stakeholders face. As leaders, we don’t need to have all the answers. Our job is to make sure we create the right culture and ask the relevant questions, and then provide the space, resources and support to let talented individuals work effectively together to find the best solution. No matter your industry or discipline, success is never about the contribution of one person. It’s about trust, collaboration, and creating a space where everyone can contribute to their full potential. #Engineering #Leadership #Trust #WeAreRS

Trust is not something you have, but something you do. 6 proven ways to build unshakeable trust with your team, TODAY: (Sample situations and scripts are included) 1. Say what you do. Minimize surprises. ➜Why: Consistency in communication ensures everyone is on the same page, reducing uncertainties and building reliability. ➜Situation: After a meeting, promptly send out a summary of what was agreed upon, including the next steps, owners, and deadlines. ➜Script: "Thank you for the productive meeting. As discussed, here are our next steps with respective owners and deadlines. Please review and let me know if any clarifications are needed." 2. Do what you say. Deliver on commitments. ➜Why: Keeping your word demonstrates dependability and earns you respect and trust. ➜Situation: Regularly update stakeholders on the project's progress. Send out a report showing the project is on track, and proactively communicate any potential risks. ➜Script: "Here's the latest project update. We're on track with our milestones. I've also identified some potential risks and our mitigation strategies." 3. Extend the bridge of trust. Assume good intent. ➜Why: Trust grows in a culture of understanding and empathy. Giving others the benefit of the doubt fosters a supportive and trusting environment. ➜Situation: If a team member misses an important meeting, approach them with concern and understanding instead of jumping to conclusions. ➜Script: "I noticed you weren’t at today’s meeting, [Name]. I hope everything is okay. We discussed [key topics]. Let me know if you need a recap or if there's anything you want to discuss or add." 4. Be transparent in communication, decision-making, and admitting mistakes. ➜Why: Honesty in sharing information and rationale behind decisions strengthens trust. ➜Situation: Be clear about the reasoning behind key decisions, especially in high-stakes situations. ➜Script: "I want everyone to understand why we made this decision. Here are the factors we considered and how they align with our objectives..." 5. Champion inclusivity. Engage and value all voices. ➜Why: Inclusivity ensures a sense of belonging and respect, which is foundational for trust. ➜Situation: Encourage diverse viewpoints in team discussions, ensuring everyone feels their input is valued and heard. ➜Script: Example Script: "I'd really like to hear your thoughts on this, [Name]. Your perspective is important to our team." 6. Be generous. Care for others. ➜Why: Offering support and resources to others without expecting anything in return cultivates a culture of mutual trust and respect. ➜Situation: Proactively offer assistance or share insights to help your colleagues. ➜Script: "I see you’re working on [project/task]. I have some resources from a similar project I worked on that might be helpful for you." PS: Trust Is Hard-Earned, Easily Lost, Difficult To Reestablish...Yet Absolutely Foundational. Image Credit: BetterUp . com

A man with a watch knows what time it is. A man with two watches is never sure. ~ Segal’s Law More data doesn’t mean better decisions. In fact, it often leads to paralysis, over-analysis, and slower execution. So ... how do you filter out the signal from the noise? While AI cannot replace your instincts and judgment, nor make a high-stakes leadership call on your behalf, it can be a valuable thought partner in decision-making. Here are AI prompts to challenge your own thinking: CLARIFY THE CONTEXT 💭 What is the core problem we’re solving, and how has it evolved over time? 💭 What data or evidence suggests this is the right priority right now? 💭 What are the second- and third-order consequences of this decision? 💭 What does success look like in 12 months? What about failure? 💭 If we had to explain this decision in one sentence, what would it be? MODEL SCENARIOS 💭 What are the best-case, worst-case, and most likely scenarios if we move forward? 💭 How would this decision play out in different competitive conditions? 💭 What factors would make this decision a game-changer or a massive failure? 💭 What are the opportunity costs of choosing this path over others? 💭 If we succeed beyond expectations, what new risks or constraints will emerge? STRESS TEST ASSUMPTIONS 💭 What assumptions are we making that could be flawed or outdated? 💭 What evidence would immediately prove this decision wrong? 💭 What are the hidden risks or unintended consequences we aren’t considering? 💭 Are we making this decision based on past success, or future relevance? 💭 What is the hidden downside of being right? PRIORITIZE SPEED 💭 What is the ONE critical insight that makes this decision 80% clear right now? 💭 If we had to make this decision within 24 hours, what would we prioritize? 💭 Are we optimizing for certainty, or are we delaying out of fear? 💭 If we delay this decision by 6 months, what are the risks and missed opportunities? 💭 What’s the smallest action we can take to test this decision before fully committing? BUILD FEEDBACK LOOPS 💭 What are the top 3 leading indicators that will signal whether this decision is working? 💭 What biases might cause us to ignore early warning signs of failure? 💭 If this decision needs to be reversed, what’s the fastest and least costly way to do it? 💭 How will we ensure that feedback is acted upon, not just collected? 💭 What questions should we be asking 6 months from now to reassess this decision? #leadership #AI #innovation

📚 Takeaways from July's Book-Of-The-Month "Decisive: How to Make Better Choices in Life and Work" by Chip & Dan Heath 📚 Four Villains of Decision Making 1) Narrow framing We tend to have a Mental Spotlight so the things in the spotlight are highly visible and we miss the things outside of it. Any “whether or not to do X” or “should I do X or Y” framing should set off warning bells: you may be missing options. Widen your options. How can you expand your set of choices? Think “And” not “Or”. Consider opportunity cost: what else can I do instead of X?  Apply Vanishing Option test (what if the current option was unavailable?).  Multitrack - consider more than 1 option simultaneously. This helps you understand the Shape of a problem a lot more than Narrow Framing. Beware of “Sham options”. Find someone who’s solved your problem: look outside, look inside, ladder-up via analogies (“this problem I’m trying to solve has the shape of another problem that has been solved”). 2) Confirmation bias We develop quick beliefs about a situation then look for data to bolster it. Reality-test your assumptions. Ask disconfirming questions. How can you get outside your head and collect information you can trust? Consider the Opposite: what would have to be true for that option to be best?  Zoom out, Zoom in. Don’t trust the averages, understand the percentiles (what’s your p0 case? p100?). Find Base Rates for your decision (in the past how many people who did X succeeded?) Run small experiments to test your theory. Go out and try things! 3) Short-term emotion. Attain distance before deciding. Often an outside perspective without historical background or knowledge of politics is good. Our decisions are influenced by (a) mere exposure, things that are familiar to us, (b) loss aversion: losses are more painful than gains are pleasant. This leads to status-quo as a default decision. Hard decisions are often signs of a conflict among your Core Priorities. Identify and enshrine your Core Priorities to make it easier to resolve conflict. [ Side note: this is why at Amazon we use Tenets, as a decision framework ] 4) Overconfidence People think they know more than they do about the future. Prepare to be wrong. The future is not a “point”, a single scenario we must predict. It’s a range. Bookend it considering a range of outcomes, some positive, some negative. Lower bookend: “It’s a year from now. Our decision has failed. Why?” Upper bookend: “It’s a year from now. Our decision was a success. Were we ready to handle it and scale?” Set a Tripwire - snaps you from autopilot. Particularly important when change is very gradual. Add Deadlines or Partitions (“I’ll only spend $1MM out of my $10MM budget then reassess”). Tripwires can be triggered by patterns, not just metrics or dates. Decisions made by groups have an additional burden (careful with social cohesion) but bargaining may lead to a better, fairer decision overall. #bookofthemonth #carlosbookofthemonth

Stop trying to solve burnout with meditation apps. #Burnout at work is on the rise, and next year isn't likely to bring relief -- in fact the opposite. Under pressure to "do more with less," fears about #genAI and #RTO commands, it's not a surprise. Sharon Parker and Caroline Knight in MIT Sloan Management Review have put together a great framework for addressing a pressing issue that doesn't get glib about apps or just say "lighten their load." They also root it in a case for change: "58% percent of 18-to-34-year-olds said that their daily level of stress is overwhelming. Disengaged, stressed-out employees do not perform at their best." The SMART framework: 🔸 Stimulating work: Am I solving real problems that matter? Is there variety? 🔸 Mastery: Am I learning new skills, getting feedback and is it clear how my work contributes to broader goals? 🔸 Autonomy: Are the lines clear for what decisions I can make, and do I have flexibility to do work where and when I'm at my best? 🔸 Relational work: Am I engaged with a team, connected and feel a sense of belonging and support? 🔸 Tolerable demands: Is the work realistically scoped, so that I'm not in continual overload? Are there peaks and valleys? Their framework sounds easy, but anyone who's managed large teams knows how hard it is and how much design goes into making it happen. What I found historically with teams that helped were: ☀️ Frequent check-ins on how someone's feeling about the work, not just the status of the work: are you learning? Is it reasonable? Are you having fun? ☀️ Rotations of dreck and joy: routine work and doing the same type of project over again isn't fun; ensuring people get rotations in and out of "drudge" work. ☀️ Balancing autonomy and collaboration: Getting clear up front about shared goals, roles and levels of decision authority across the team. No swarm ball. ☀️ Taking breaks. Make sure people can step away from work, build and support boundaries and rest periods. Peak performance isn't "hustle culture." What works for you to relieve burnout? #Leadership #Management #Engagement #Productivity #culture