Project Management Techniques For Engineers

This might be controversial and I know not everyone will agree. But after 16+ years in the industry, here’s one truth I keep coming back to: If you're managing construction and don’t understand how a job is actually built, you lose credibility. For Construction Managers, especially those overseeing contractors, real field experience isn’t optional. It’s fundamental. No amount of process reports, dashboards, or scheduling tools can replace the lessons learned from being on-site. Why general contracting experience matters: •It teaches how systems come together not just on drawings, but in dust, heat, delays, and real-world constraints. •You learn to speak the contractor’s language and that builds respect. •You stop managing from a distance and start leading with clarity, empathy, and technical awareness. I’ve seen it repeatedly: Teams without this background often fall into the trap of enforcing processes they don’t fully understand. And contractors can spot it immediately. For Owner’s Representatives and Construction Managers, credibility on-site depends on two things: •Technical knowledge •Practical experience in how buildings are built, not just designed Field exposure doesn’t just improve decisions. It prevents project friction before it starts. #ConstructionManagement #OwnersRep #FieldExperience #GeneralContracting #RiskMitigation #ConstructabilityReviews #ProjectLeadership #DavidFieldsConsultingServices #DesignBuild

I am constantly thinking about how to foster innovation in my product organization. Building teams that are experts at execution is the easy part—when there’s a clear problem, product orgs are great at coming up with smart solutions. But it’s impossible to optimize your way into innovation. You can’t only rely on incremental improvement to keep growing. You need to come up with new problem spaces, rather than just finding better solutions to the same old problems. So, how do we come up with those new spaces? Here are a few things I’m trying at Duolingo: 1. Innovation needs a high-energy environment, and a slow process will kill a great idea. So I always ask myself: Can we remove some of the organizational barriers here? Do managers from seven different teams really need to say yes on every project? Seeking consensus across the company—rather than just keeping everyone informed—can be a major deterrent to innovation. 2. Similarly, beware of defaulting to “following up.” If product meetings are on a weekly cadence, every time you do this, you are allocating seven days to a task that might only need two. We try to avoid this and promote a sense of urgency, which is essential for innovative ideas to turn into successes. 3. Figure out the right incentive. Most product orgs reward team members whose ideas have measurable business impact, which works in most contexts. But once you’ve found product-market fit, it is often easiest to generate impact through smaller wins. So, naturally, if your org tends to only reward impact, you have effectively incentivized constant optimization of existing features instead of innovation. In the short term things will look great, but over time your product becomes stale. I try to show my teams that we value and reward bigger ideas. If someone sticks their neck out on a new concept, we should highlight that—even if it didn’t pan out. Big swings should be celebrated, even if we didn’t win, because there are valuable learnings there. 4. Look for innovative thinkers with a history of zero-to-one feature work. There are lots of amazing product managers out there, but not many focus on new problem domains. If a PM has created something new from scratch and done it well, that’s a good sign. An even better sign: if they show excitement about and gravitate toward that kind of work. If that sounds like you—if you’re a product manager who wants to think big picture and try out big ideas in a fast-paced environment with a stellar mission—we want you on our team. We’re hiring a Director of Product Management: https://lnkd.in/dQnWqmDZ #productthoughts #innovation #productmanagement #zerotoone

After spending three decades in the aerospace industry, I’ve seen firsthand how crucial it is for different sectors to learn from each other. We no longer can afford to stay stuck in our own bubbles. Take the aerospace industry, for example. They’ve been looking at how car manufacturers automate their factories to improve their own processes. And those racing teams? Their ability to prototype quickly and develop at a breakneck pace is something we can all learn from to speed up our product development. It’s all about breaking down those silos and embracing new ideas from wherever we can find them. When I was leading the Scorpion Jet program, our rapid development – less than two years to develop a new aircraft – caught the attention of a company known for razors and electric shavers. They reached out to us, intrigued by our ability to iterate so quickly, telling me "you developed a new jet faster than we can develop new razors..." They wanted to learn how we managed to streamline our processes. It was quite an unexpected and fascinating experience that underscored the value of looking beyond one’s own industry can lead to significant improvements and efficiencies, even in fields as seemingly unrelated as aerospace and consumer electronics. In today’s fast-paced world, it’s more important than ever for industries to break out of their silos and look to other sectors for fresh ideas and processes. This kind of cross-industry learning not only fosters innovation but also helps stay competitive in a rapidly changing market. For instance, the aerospace industry has been taking cues from car manufacturers to improve factory automation. And the automotive companies are adopting aerospace processes for systems engineering. Meanwhile, both sectors are picking up tips from tech giants like Apple and Google to boost their electronics and software development. And at Siemens, we partner with racing teams. Why? Because their knack for rapid prototyping and fast-paced development is something we can all learn from to speed up our product development cycles. This cross-pollination of ideas is crucial as industries evolve and integrate more advanced technologies. By exploring best practices from other industries, companies can find innovative new ways to improve their processes and products. After all, how can someone think outside the box, if they are only looking in the box? If you are interested in learning more, I suggest checking out this article by my colleagues Todd Tuthill and Nand Kochhar where they take a closer look at how cross-industry learning are key to developing advanced air mobility solutions. https://lnkd.in/dK3U6pJf

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

As a Principal Engineer, one of my main goals is to enable and empower other engineers. Being a Principal Engineer involves not only technical expertise but also leadership and mentorship. Here are some of the things I do to enable and empower other engineers effectively: Clear Communication and Context Sharing: - Provide thorough context when assigning tasks or explaining projects. This helps engineers understand the bigger picture and make informed decisions. - Explain the "why" behind technical decisions and architectural choices to help engineers connect the dots. Encourage Autonomy: - Give engineers the freedom to experiment and explore different solutions. This fosters creativity and innovation. - Set guidelines and expectations while allowing room for individual problem-solving approaches. Safe Environment for Failure: - Emphasize that failures are learning opportunities, not setbacks. Encourage risk-taking and experimentation. - Foster an open culture where engineers feel comfortable sharing their failures and lessons learned without fear of judgment. Mentorship and Coaching: - Offer guidance and mentorship to help engineers navigate challenges and make informed decisions. - Provide constructive feedback on their work and help them identify areas for growth. Provide Growth Opportunities: - Identify projects or tasks that align with their career goals and give them a chance to learn and stretch their skills. - Support their professional development by suggesting relevant workshops, courses, or conferences. Advocate and Support: - Stand up for "your" engineers in meetings and discussions, especially during challenging situations. - Acknowledge and highlight their accomplishments to leadership and stakeholders. Open Door Policy: - Be approachable and available for discussions, questions, and concerns. - Create an atmosphere where team members feel comfortable seeking help when needed. Lead by Example: - Demonstrate a strong work ethic, technical proficiency, and collaboration skills. - Display a positive attitude and a willingness to learn from others. Promote Knowledge Sharing: - Organize regular knowledge-sharing sessions, where engineers can present their work, share insights, and learn from each other. Celebrate Successes: - Recognize and celebrate achievements, both big and small, to boost morale and motivation. Inclusive and Diverse Environment: - Foster inclusivity and diversity within the team. Respect different perspectives and encourage open discussions. Continuous Improvement: - Regularly seek feedback from engineers on your leadership style and ways to improve the work environment. Enabling and empowering engineers is an ongoing process that requires adaptability and empathy. These strategies help me create an environment where engineers feel valued, motivated, and empowered to excel in their roles.

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

In “The Venture Mindset”, we explore how successful companies foster innovation by prioritizing people over rigid processes. However, placing people over process does not mean that there is no process at all.     Chaos doesn't necessarily translate into innovation; moreover, it can easily destroy ideas. The design should facilitate cutting through quite a bit of the internal bureaucracy and keeping the development team small, independent, fluid, and protected from internal politics. Let's examine two examples of this principle in action: Case Study 1: Gmail at Google Google's approach to Gmail is a textbook example of the power of trusting talented individuals: 1. The project started with a single engineer, Paul Buchheit.  2. Leaders provided a vague directive: "Build some type of email or personalization product."  3. There were no strict feature lists or rigid processes.  4. Google executives supported the project and bet on its potential. Result: Gmail revolutionized email services and became one of Google's most successful products.    Case Study 2: The Happy Meal at McDonald's The Happy Meal's success shows how intrapreneurship can thrive even in traditional corporate environments: 1. Yolanda Fernández de Cofiño, a McDonald's franchisee in Guatemala, developed the concept.  2. She created a children's menu without approval from headquarters.  3. McDonald's world conventions allowed for idea exchange.  4. Executives recognized the potential and scaled the idea globally.  Result: The Happy Meal became a worldwide success and a staple of McDonald's offerings.    Here is what you can do to support the employees in your company:  1. Trust your talent: Give motivated individuals the freedom to pursue their ideas.  2. Provide resources: Offer support and necessary tools without micromanagement.  3. Create "racetracks": Design systems that allow for rapid development and testing of new ideas, with clear funding mechanisms, simple rules, guardrails, and milestones.  4. Embrace calculated risks: Be willing to bet on promising projects, even if they're unconventional.  5. Scale successes: When local innovations show promise, be ready to implement them more broadly.    How does your organization balance structure and freedom to foster innovation? Share your thoughts and experiences in the comments! #stanford #stanfordgsb #venturecapital #startups #innovation #technology #founders #venturemindset 

One of our clients—an international energy company—was undergoing a massive transformation, shifting from oil to e-mobility and sustainable fuels. The board’s mandate was clear: build a workforce ready for tomorrow’s challenges. During my first week, I visited a remote field site. Standing beside a team of engineers, I could sense their anxiety about unfamiliar technologies, stricter compliance audits, and the relentless pressure to deliver results. The old training modules? They barely scratched the surface of what these teams truly needed. We soon realized that off-the-shelf courses just weren’t enough. Understanding how people actually felt about new work processes was essential. I spent hours with field and office teams—listening, mapping out real pain points, and asking sometimes uncomfortable questions. How can we help our people make critical decisions on the ground? How do we build capability at scale, rather than just ticking compliance boxes? Once we gained that clarity, everything began to shift. Our team created an interactive learning journey—complete with role-based simulations, gamified crisis scenarios, and data-driven feedback loops. Each module put learners in the driver’s seat, dealing with real-life emergencies or optimizing EV infrastructure in realistic ways. It wasn’t all smooth sailing. Our first pilot exposed significant gaps—some learners felt overwhelmed, while others needed more hands-on support.We responded quickly by launching peer forums, field workshops, and targeted communications to bridge those divides. Within just 90 days, employees became noticeably more confident. Sites reported improved safety, efficiency, and even reduced downtime. This experience reinforced for me how real listening, strategic design, and a willingness to adapt can transform not just results, but the culture itself. I aim to make every learning initiative feel like a story worth living—for teams and for the business. #LearningAndDevelopment #EnergySector #Transformation #CriticalThinking #ProblemSolving #EVReady (Photo by <ahref="https://lnkd.in/gQWCp5Qf">Stockcake</a>)

One of the biggest lessons I've learned working with Fortune 5 companies on AI transformation is that successful AI adoption isn't about having better models. It's about building better systems for innovation. Two methods we use to drive innovation at the speed of AI: Innovation Pods; Vibe to Vetted process 1. Innovation Pods Instead of treating innovation as everyone's side job, we create dedicated, cross-functional teams around each core business capability with the goal of driving and scaling AI innovation. Each pod typically includes: • A program manager who owns the roadmap and backlog. • Subject matter experts who understand the business and define user requirements. • FDE's who build and deploy solutions. These teams meet regularly, prioritize opportunities, validate ideas with users, and continuously improve how work gets done. More importantly, they become the owners of that capability. They don't just build tools—they create documentation, playbooks, and repeatable processes that allow innovation to scale across the business. 2. Vibe to Vetted The second lesson is that democratizing development only works when there's a shared foundation. The goal is simple: anyone in the business should be able to build and extend capabilities—not just software engineers. But freedom without standards creates chaos. We've created a common set of guardrails and process that includes shared skills, Git repositories, design systems, AI agents, design system, security guardrails, and engineering standards. Whether someone builds in Cursor, Claude, Antigravity, or another AI-native IDE, every project follows the same architecture, uses the same UI components, meets security requirements, and can be easily maintained by the next team because it has all of the correct documentation. Enterprise AI isn't a technology challenge. It's an operating model challenge. The organizations that build repeatable systems for innovation will outperform those that simply deploy more AI tools. Put these into practice for you and watch how fast innovation takes off.

Over the years in solar project management, I’ve seen firsthand how regular site visits fundamentally improve execution and delivery. Being on-site is more than a formality—it’s a leadership practice that makes a decisive difference in the outcome. 𝟭. 𝗜𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲 𝗜𝘀𝘀𝘂𝗲 𝗥𝗲𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻: When physically present, issues like installation errors or supply delays can be identified and solved before they spiral, keeping the project on track and minimizing downtime. 𝟮. 𝗤𝘂𝗮𝗹𝗶𝘁𝘆 𝗔𝘀𝘀𝘂𝗿𝗮𝗻𝗰𝗲: Close inspection throughout execution allows quality checks at every stage, ensuring installations meet all technical standards, safety codes, and design intentions. 𝟯. 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗧𝗲𝗮𝗺 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Face-to-face interactions with site teams lead to clearer instructions, quick clarifications, and stronger team morale, sharply reducing miscommunication and improving collaboration. 𝟰. 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿 𝗖𝗼𝗻𝗳𝗶𝗱𝗲𝗻𝗰𝗲: Clients and partners value managers who invest in site presence—it’s a clear signal that every detail matters, and it builds long-term trust and accountability. 𝟱. 𝗘𝗮𝗿𝗹𝘆 𝗥𝗶𝘀𝗸 𝗗𝗲𝘁𝗲𝗰𝘁𝗶𝗼𝗻: Site visits enable the early identification of hidden risks, safety concerns, and unforeseen obstacles, making proactive mitigation possible and protecting project timelines. In solar EPC, presence is more than physical; it's the foundation for excellence and success. I encourage all project managers to make site visits a priority—your projects, teams, and clients will thank you. #SolarEnergy #SolarPower #RenewableEnergy #SolarProject #SolarInstallation #CleanEnergy #EnergyStorage #SolarEPC #GreenEnergy #ProjectManagement #SiteVisit #QualityAssurance #LeadershipInAction #Siteexecution