Effective Team Leadership In Engineering Projects

"If you want something done right, do it yourself." - I used to believe this but I was wrong! I learned the hard way that this mindset holds everyone back—including me. Real growth happens when you build a team you can trust. That's when it clicked: The strongest leaders aren't the ones with the tightest grip—they're the ones who know when to delegate. My approach? I'm not their supervisor—I'm their mentor. When a team member makes a bold decision in a client meeting, they know I've got their back. When they face challenges, I'm their shield, not their critic. Here's how we make this work: > Smart goal setting: We kick off each year by breaking down targets from HQ, involving teams in shaping their goals for ownership, and conducting quarterly reviews to stay agile and realistic. >  Real Independence My team has the freedom to travel when needed to meet clients, the authority to make decisions, and the space to innovate—and occasionally fail. >  Balance is key Clear accountability, regular check-ins (not checkups), and support when needed, with space to thrive. Their targets are my targets. Their success is my success. If they don't achieve, I don't achieve. We're in this together, but I'm behind them, not over them. As a result, they’re a team that doesn't just meet targets—they crush them. Because empowered people will always outperform controlled ones. How do you balance guidance with independence? #LeadershipLessons #TeamManagement

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?

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.

As I continue exploring what makes high-performing teams tick, I've covered key topics like group dynamics, trust, cohesiveness, and psychological capital. In this post, I want to dive deeper into a crucial aspect of team dynamics: conflict. Conflict is inevitable in any team, even in high-performing ones. However, the difference lies in how these teams handle it. They don't shy away from conflict; instead, they have established rules of engagement and cultural practices for navigating it effectively. They embrace conflict, using it as a tool for growth and innovation—often with the support of a skilled facilitator. Here are some common types of conflict that can arise in the workplace: Conflict in Vision: Example: Disagreement over the company's long-term direction. Impact: Misaligned vision can fragment efforts and lower morale. Resolution: Facilitate discussions to align on a shared vision and involve all stakeholders in the vision-setting process. Conflict in Goals: Example: Differing objectives between departments. Impact: Can create competition rather than collaboration, leading to inefficiencies. Resolution: Establish clear, unified goals and ensure they are communicated across the organization. Conflict in Communication Styles: Example: Misinterpretations due to different communication preferences. Impact: Misunderstandings can escalate into larger conflicts. Resolution: Promote awareness of diverse communication styles and encourage adaptive communication techniques. Conflict in Values: Example: Clashes over ethical decisions or cultural values. Impact: Can lead to deep-seated animosity and ethical dilemmas. Resolution: Create a values-based culture and ensure organizational policies reflect shared values. Conflict in Resource Allocation: Example: Competing demands for limited resources. Impact: Can result in feelings of unfairness and hinder project progress. Resolution: Implement transparent and fair resource allocation processes. Conflict in Roles and Responsibilities: Example: Overlapping or unclear job roles. Impact: Can cause confusion, redundancy, or gaps in task completion. Resolution: Clearly define roles and responsibilities, and regularly review them to avoid overlap. Conflict in Work Styles: Example: Differing approaches to completing tasks or managing time. Impact: Can cause friction and reduce team cohesion. Resolution: Encourage flexibility and understanding of diverse work styles, and find common ground. Conflict in Power Dynamics: Example: Power struggles between employees or teams. Impact: Can lead to a toxic work environment and hinder collaboration. Resolution: Foster a culture of mutual respect and equitable power distribution. What other types of conflict have you encountered in teams? How did you resolve them? Share your thoughts and experiences in the comments! #teambuilding #communicationskills #peopleskills

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

🎨🖊️ "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

𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐄𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭: 𝐌𝐞𝐞𝐭 𝐓𝐡𝐞𝐦 𝐖𝐡𝐞𝐫𝐞 𝐓𝐡𝐞𝐲 𝐀𝐫𝐞 Enterprise Architecture abhors a vacuum—it thrives on stakeholder engagement. Often, architects jump into collaboration without first assessing one critical factor: • 𝐖𝐡𝐚𝐭 𝐝𝐨 𝐬𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫𝐬 𝐤𝐧𝐨𝐰, 𝐚𝐧𝐝 𝐛𝐞𝐥𝐢𝐞𝐯𝐞, 𝐚𝐛𝐨𝐮𝐭 𝐄𝐀? Before strategy, frameworks, or roadmaps, 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝 𝐭𝐡𝐞𝐢𝐫 𝐚𝐰𝐚𝐫𝐞𝐧𝐞𝐬𝐬, 𝐩𝐞𝐫𝐜𝐞𝐩𝐭𝐢𝐨𝐧𝐬 and 𝐞𝐱𝐩𝐞𝐜𝐭𝐚𝐭𝐢𝐨𝐧𝐬. This will shape how you approach, gain buy-in, and drive outcomes. Here are 𝐭𝐡𝐫𝐞𝐞 𝐞𝐬𝐬𝐞𝐧𝐭𝐢𝐚𝐥 𝐦𝐨𝐯𝐞𝐬 for aligning EA with stakeholders: 𝟏 | 𝐆𝐚𝐮𝐠𝐞 𝐄𝐀 𝐀𝐰𝐚𝐫𝐞𝐧𝐞𝐬𝐬 𝐁𝐞𝐟𝐨𝐫𝐞 𝐄𝐧𝐠𝐚𝐠𝐢𝐧𝐠 EA means different things to people, how can you align? Approach: * 𝐀𝐬𝐬𝐞𝐬𝐬 𝐞𝐱𝐢𝐬𝐭𝐢𝐧𝐠 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞. What do leaders think EA does? What experiences shape their view? * 𝐏𝐨𝐬𝐢𝐭𝐢𝐨𝐧 𝐄𝐀 𝐢𝐧 𝐭𝐡𝐞𝐢𝐫 𝐥𝐚𝐧𝐠𝐮𝐚𝐠𝐞. If a product saw EA as 'overhead,’ shift the conversation to ‘rapid decision-making.’ * 𝐓𝐚𝐢𝐥𝐨𝐫 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐛𝐲 𝐚𝐮𝐝𝐢𝐞𝐧𝐜𝐞. Finance, operations, and IT leaders have different concerns. Meet them on their terms. 👉 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: When you shape EA’s role based on their reality, it becomes relevant, not theoretical. 𝟐 | 𝐀𝐥𝐢𝐠𝐧 𝐄𝐀 𝐭𝐨 𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐏𝐫𝐢𝐨𝐫𝐢𝐭𝐢𝐞𝐬 EA isn’t all architecture, it’s solving business problems. Approach: * 𝐒𝐭𝐚𝐫𝐭 𝐰𝐢𝐭𝐡 𝐊𝐏𝐈𝐬. Growth? Efficiency? Risk? Align EA contributions to what leadership interests. * 𝐂𝐨𝐧𝐧𝐞𝐜𝐭 𝐭𝐞𝐜𝐡𝐧𝐨𝐥𝐨𝐠𝐲 𝐭𝐨 𝐢𝐦𝐩𝐚𝐜𝐭. Show architecture driving go-to-market, savings, or agility—over compliance. * 𝐀𝐧𝐭𝐢𝐜𝐢𝐩𝐚𝐭𝐞/𝐫𝐞𝐦𝐨𝐯𝐞 𝐫𝐨𝐚𝐝𝐛𝐥𝐨𝐜𝐤𝐬. If EA was a bottleneck, demonstrate accelerated decision-making instead. 👉 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: EA is a strategic enabler, not afterthought. 𝟑 | 𝐁𝐮𝐢𝐥𝐝 𝐄𝐀 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐂𝐨𝐧𝐯𝐞𝐫𝐬𝐚𝐭𝐢𝐨𝐧 EA works best in collaboration, not isolation. Approach: * 𝐄𝐦𝐛𝐞𝐝 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬 𝐢𝐧𝐭𝐨 𝐛𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐝𝐢𝐬𝐜𝐮𝐬𝐬𝐢𝐨𝐧𝐬. Decision-making improves when EA is a proactive presence. * 𝐒𝐡𝐢𝐟𝐭 𝐟𝐫𝐨𝐦 ‘𝐩𝐫𝐞𝐬𝐞𝐧𝐭𝐢𝐧𝐠 𝐄𝐀’ 𝐭𝐨 ‘𝐜𝐨-𝐜𝐫𝐞𝐚𝐭𝐢𝐧𝐠 𝐬𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬.’ Stakeholders engage when architecture is a tool for their success. * 𝐂𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭, 𝐧𝐨𝐭 𝐨𝐧𝐞-𝐨𝐟𝐟. EA isn’t a pitch—it’s a dialog evolving with business. 👉 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: EA shaping decisions early rather than reacting later. 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐞𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐬𝐭𝐚𝐫𝐭𝐬 𝐰𝐢𝐭𝐡 𝐮𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠. Before pushing frameworks or models, assess 𝐰𝐡𝐚𝐭 𝐄𝐀 𝐦𝐞𝐚𝐧𝐬 𝐭𝐨𝐝𝐚𝐲—and how to reshape that narrative to unlock its full potential. How do align EA stakeholders? Let’s discuss.👇 --- ➕ 𝐅𝐨𝐥𝐥𝐨𝐰 Kevin Donovan 🔔    👍 Like | ♻️ Repost | 💬 Comment    🚀 𝐉𝐨𝐢𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬’ 𝐇𝐮𝐛 👉 https://lnkd.in/dgmQqfu2

Making Friends with Engineering: A GRC Professional's Guide to Speaking Their Language 🗣️ Want engineering to actually implement your security requirements? Start by speaking their language. Or keep getting ghosted. The traditional GRC-engineering relationship is basically a corporate cold war: - You request evidence - They pretend your email doesn't exist - You escalate to their manager (nuclear option) - They send screenshots with the enthusiasm of someone filing taxes - Both sides retreat to complain about each other in Slack - Repeat next quarter with fresh resentment Let's break this dysfunctional cycle 🔄 💡 Understanding Engineering Priorities & Workflows Engineering time is usually tied to product roadmaps, deadlines, and planned work. Whether they're using Plan->Build->Ship, Agile or "whatever works this week," one truth remains: unplanned security requests compete directly with product deliverables they've already committed to. When you drop a "quick request" that takes 3 hours, you're essentially asking them to sacrifice time that's already allocated—and possibly jeopardise commitments they've made to product leaders. That's like someone stealing your coffee every morning and wondering why you're irritated. Instead, try: - "Who manages your team's roadmap? I'd like to discuss including security requirements." - "What's your process for handling unplanned work?" (Translation: How can I not wreck your schedule?) - "Can we add compliance as a recurring item in your planning process?" (Translation: Let's make this predictable) 💬 Key Technical Terms That Build Credibility Nothing earns respect faster than showing you understand their world. It's like learning basic phrases before visiting another country, except the country is Linux and everyone's annoyed. Don't say: "Please take screenshots of access controls" Say: "Can we create an IAM role report using the AWS CLI?" Don't say: "We need to verify our website security" Say: "I'd like to review the WAF configuration and Content-Security-Policy headers" Don't say: "How do we know code is secure?" Say: "Where in your build pipeline are you running SAST and dependency scanning?" If you speak like that, you might be invited to their remote lunch. 🤝🏽 Collaboration Tools Meet them where they live, because they're not coming to your GRC castle: - Get a GitHub/GitLab account (bonus points: actually use it) - Learn to create issues with proper formatting (no walls of text) - Master the art of Markdown (the language for docs that doesn't look like it was written by a lawyer) - Use their ticketing system instead of yours (revolutionary concept) - Join their Slack channels (and laugh at their memes, even if you don't get them) The perfect compliance program that engineers hate is just an expensive screenshot collector. Stop being the GRC professional devs warn each other about in Slack and start being the security partner they tag when they need answers. #GRCEngineering