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

🚧🚧🚧 Project running late? Don’t panic. Every planner, engineer, or PM has faced this moment: 👉 The deadline is slipping. 👉 The client is asking tough questions. 👉 You need a rescue plan—fast. Good news: you’ve got two weapons in your toolkit. ⏱️ Fast Tracking or 💸 Crashing. But the trick is knowing when to use which. 🔹 Fast Tracking ✔️ Run activities in parallel instead of sequentially ✔️ No extra cost, but you risk rework ✔️ Perfect when time is the top priority and scope is stable ✔️ Example: Overlapping design & construction phases 🔹 Crashing ✔️ Throw in extra resources to speed things up ✔️ Cost goes up, but time goes down ✔️ Best for critical path activities where resources are available ✔️ Example: Adding shifts or doubling manpower on key tasks 🧠 Pro Tip: Don’t just throw money or effort at the schedule. 👉 Always analyze the critical path first. Otherwise, you’re just “crashing” non-critical work while the delay stays untouched. 📌 Bottom line: Fast Tracking = Time over Risk Crashing = Cost over Time Choose wisely. That’s the difference between a controlled recovery and a budget disaster. #ProjectManagement #Construction #PrimaveraP6 #Scheduling #DelayAnalysis #Planning #ProjectControls #PMO #ProjectEngineer #CareerGrowth #FromSiteToOffice #ConstructionLife #PlanningEngineer #EngineeringJourney #RealTalk #KeepLearning #ProjectManagement #SiteToProject #pmp #pmi

People often ask how we manage complex projects as a team of 100 people in 35 countries, and since I'm currently revamping our documentation on this subject, that info is top of mind. Here's 29 pages of content condensed into 1 LI post for a sneak peek into our DO (Doist Objectives) System 👀 It starts with our annual roadmap, which the leadership team builds in Q4 of the prior year. To execute that plan, we organize our work into four areas of priority (Strategic Priorities, aka SPs), each running multiple initiatives simultaneously in quarterly "cycles", and overseen by a Directly Responsible Doister (DRD): • Brand (DRD: CMO): Marketing campaigns, brand evolution, growth initiatives • Product (DRD: Head of Product): New features, user experience improvements, product strategy • Engineering (DRD: CTO): Platform stability, performance optimization, technical infrastructure • Doist (DRD: 🙋🏻♂️): Internal tools, company operations, team effectiveness Planning kicks off four weeks before each quarter when the CXOs provide the DRDs with general guidance and goals. We respond by proposing general plans for DOs (Doist Objectives; projects/initiatives) in line with our annual roadmap. Two weeks before the new quarter begins, the DOs are agreed upon and the team Heads assign team members to cross-functional "Squads" as "Squad Leaders" and "Squad Members". **See photos below to illustrate the squad infrastructure. Each SP typically runs 2-5 major DOs per quarter, meaning we're executing 12-16 significant projects at any time. The quarter begins with a two-week "Foundation Phase", where squads: • Deep dive into the challenges and opportunities their squad faces • Conduct user research • Create comprehensive specs detailing their proposed solutions • Align on execution approach • This phase ensures we have the space to avoid diving too deep into the upcoming cycle while working on the current cycle From there, squads maintain momentum for the following 10 weeks in the "Execution Phase" through established rituals: • Weekly "snippets" in Twist for progress updates and transparency (our version of an async standup meeting) • Bi-weekly recorded demos to showcase work in-depth • Monthly retrospectives on squad health for continuous improvement • Monthly companywide updates on each strategic priority's DOs • Monthly strategic reviews/adjustments by the leadership team • Expectation = each squad should "ship" something weekly Of course, we manage most of this using Twist for communication and Todoist for project management, but more so than the tools, this system works for us because we emphasize clear ownership/autonomy, transparent communication, and just enough processes to stay coordinated without slowing the team down. That was a lot to digest, but I hope it's helpful. Let me know if I can expand on anything or answer any other questions 👇

Glen Palmer, PSP, CFCC, FAACE and I are honored by AACE publishing another of our Top Ten series of papers in the Cost Engineering Journal. Resource management sits at the heart of project success—and, too often, at the root of costly construction claims. Why Focus on Resources? Most construction schedules are built on assumptions about production rates, durations, and quantities. But when resource planning falls short—whether due to unrealistic manpower peaks, lack of skilled labor, or poor coordination—projects risk delays, cost overruns, and disputes. Rather than waiting for claims to arise, Palmer and Carson argue for a proactive approach: plan, validate, and monitor your resources from day one. Key Takeaways from the Top Ten Approaches: 1. Validate Resources by Discipline: Go beyond surface-level schedule checks. Detailed resource validation—using field-experienced personnel—can identify unrealistic resource peaks and prevent unachievable schedules. 2. Formalize Punch and Warranty List Management: Avoid never-ending completion and warranty periods by developing comprehensive, early punch lists and using structured warranty management systems. 3. Check Resource Earning Curves: Ensure planned progress is actually achievable by comparing planned manpower curves and production rates to real-world constraints. 4. Manage Schedule Compression: When compressing schedules, understand the risks and costs of acceleration and recovery. Use structured analysis and documentation to avoid disputes. 5. Review General Conditions Labor: Monitor and budget field overhead costs carefully, and avoid relying on variable, hard-to-track level-of-effort activities. 6. Use Constructability Reviews: Always have experienced field experts review “fast-tracked” project schedules to spot resource and constructability problems early. 7. Address Trade Stacking and Overcrowding: Analyze crew concurrency and area usage to prevent inefficiencies from too many workers or trades in the same space. 8. Specify Resource Requirements in Schedules: Include resource histograms and percent curves in scheduling specifications to enable thorough schedule reviews. 9. Plan for Resource Availability: Evaluate the availability of skilled labor and specialty resources, especially on large or geographically constrained projects. 10. Minimize Inefficiencies from Disrupted Trade Work: Align procurement, sequencing, and trade starts to reduce disruption, and use targeted planning to ensure work is completed efficiently on the first attempt. Conclusion: Resource-related claims are often avoidable with disciplined planning, honest schedule validation, and ongoing monitoring. By following these ten approaches, project teams can dramatically reduce the risk of disputes, keep projects on track, and protect both profit and reputation.

I don't class conflict as a "waste" because not all conflict is bad...but unresolved conflict can be VERY wasteful in organizational improvement efforts. As a Lean and Leadership Coach, I have worked with companies to develop systems and skills to reduce harmful conflict, in order to make continuous improvement a reality. People ask me - how do you know there's conflict in the first place? Do we have to assess it in some way? Short answer yes. The problem has to be visible. My own approach is to ask questions that help me understand it through my 1:1 interviews as part of my Discovery phase. Here's what I (and many studies) see as the 5 of the main causes of workplace conflict...and how to resolve them 👇 👉 Communication Conflict: Studies have found that 39% of workplace conflicts arise from communication differences. I coached 'Joan' who told me that she and her direct report ('Jim') only interact when there's a problem. They both want the same results, but they don't spend time together proactively figuring out how to get them. Resolve it through: ✔️ Holding regular 1:1 and team check-ins ✔️ Reviewing communication and information flow as part of process improvement efforts ✔️ Improving meeting management 👉 Values Conflict: Research indicates that 18% of conflicts are due to clashing values. I see it in teams all the time- 'Mark' valued speed and 'Greg' valued precision. It turned into personal conflict as they were both too set on their own values, to try and understand where the other is coming from. Resolve it through: ✔️ Focusing on shared goals and common ground. ✔️ Respecting different viewpoints ✔️ Investing in people and leader development, to develop these skills in everyone. 👉 Resource Conflict: Studies found that 33% of workplace conflicts are due to too much work without enough support or a clash over differing cross- departmental priorities. A simple example- the Sales team rush orders to hit targets but Operations burns out trying to deliver. Resolve it through: ✔️ Being fair and transparent about resources. ✔️ Prioritizing tasks when resources are limited. ✔️ Working together to find creative solutions. 👉 Personality Conflict: One study found that a whopping 49% of workplace conflicts are attributed to clashes between personalities or egos. This comes down to how people behave, how they judge others and their level of EQ. Resolve it through: ✔️ Learning about different work styles. ✔️ Investing in personal development ✔️ Investing in team EQ development and team bonding 👉 Role Conflict: Unclear roles and responsibilities can cause confusion and disputes. Approximately 22% of workplace conflicts is said to stem from unclear roles. Resolve it through: ✔️ Clearly defining roles and responsibilities. ✔️ Reviewing job duties regularly and using them in 1:1's. ✔️ Discussing and fix any role overlaps. How should we be dealing with conflict in our organizations? Leave your thoughts below 🙏

"𝗪𝗲 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗲 𝗿𝗲𝘃𝗲𝗻𝘂𝗲 𝗯𝘆 15% 𝘁𝗵𝗶𝘀 𝘆𝗲𝗮𝗿." Many product teams hear this from leadership, and then immediately jump to brainstorming features.  𝗕𝘂𝘁 𝘄𝗵𝗮𝘁 𝗶𝗳 𝘄𝗲 𝘁𝗼𝗼𝗸 𝗮 𝗺𝗼𝗿𝗲 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲𝗱 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵? I came across this fantastic chart that perfectly illustrates how to connect high-level business goals directly to tangible customer opportunities and UX metrics. It’s a masterclass in building a coherent product strategy. Here’s the breakdown: 1️⃣ 𝗧𝗵𝗲 𝗚𝗼𝗮𝗹 𝗖𝗮𝘀𝗰𝗮𝗱𝗲: It starts with a broad 𝗖𝗼𝗺𝗽𝗮𝗻𝘆 𝗚𝗼𝗮𝗹 (e.g., Increase revenue with stable NPS) and narrows it down to specific 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗚𝗼𝗮𝗹𝘀. This provides clarity and focus. 2️⃣ 𝗜𝗱𝗲𝗻𝘁𝗶𝗳𝘆𝗶𝗻𝗴 𝗟𝗲𝘃𝗲𝗿𝘀: Instead of guessing, we identify the primary business impact levers. To increase revenue, do we need to focus on 𝗔𝗰𝗾𝘂𝗶𝘀𝗶𝘁𝗶𝗼𝗻 (more paying customers) or 𝗘𝘅𝗽𝗮𝗻𝘀𝗶𝗼𝗻 (increase average contract size)? This is a critical strategic choice. 3️⃣ 𝗙𝗶𝗻𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 "𝗪𝗵𝘆": This is where it gets interesting. We move from what is happening (e.g., low retention) to why it's happening. The chart points to crucial insights like "New users aren't reaching the 'aha' moment" or "New users aren't upgrading." 4️⃣ 𝗘𝗺𝗽𝗮𝘁𝗵𝗶𝘇𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗨𝘀𝗲𝗿: The framework forces us to translate business problems into 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗢𝗽𝗽𝗼𝗿𝘁𝘂𝗻𝗶𝘁𝗶𝗲𝘀. "New users aren't upgrading" becomes "Everything I need is in the free plan." This shift is vital for building products people love. 5️⃣ 𝗠𝗮𝗸𝗶𝗻𝗴 𝗶𝘁 𝗠𝗲𝗮𝘀𝘂𝗿𝗮𝗯𝗹𝗲: Finally, we connect these customer opportunities to concrete 𝗨𝗫 𝗠𝗲𝘁𝗿𝗶𝗰𝘀 like Engagement, Comprehension, or Visit Frequency. Now your design and engineering teams have clear, measurable targets that ladder all the way up to the company's top-line goal. This approach transforms product development from a feature factory into an impact-driven engine.

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

In 1986, the Space Shuttle Challenger disaster shook the world. But what many don’t know is the story behind it. The night before launch, engineers at Morton Thiokol (the company that built boosters) were deeply worried. The temperature in the launch area was predicted to drop to -1°C — far colder than any previous launch. They knew the O-rings (rubber seals) might fail in cold weather. But then came the pressure cascade •NASA had already delayed the launch multiple times •Media coverage was high (a teacher was going to space!) •Management pushed: “When will you engineers stop being engineers and start being managers?” The engineers felt pressured to approve. The next morning, 73 seconds into flight, the Challenger exploded, taking seven lives and NASA’s reputation with it. In our tech world, the stakes might seem lower at first. Early-stage startup cascade: “It’s just 50 users, we can fix bugs quickly” “Ship now, refactor later” “Everyone’s wearing multiple hats anyway” “We need to move fast to survive” When we are small, we can get away with this. Quick fixes are manageable. The team knows all the workarounds. Customer issues can be handled personally. But here’s where it gets dangerous — as you scale: 10K users → 100K users → 1M users 10 engineers → 50 engineers → 200 engineers Suddenly: •That “temporary” workaround is now critical infrastructure •The “we’ll document later” code is maintaining core features •The “quick fix” culture is deeply embedded •New hires inherit unclear processes •Technical debt compounds exponentially •3 AM fixes affect thousands of users •Knowledge silos become organizational bottlenecks The real cost isn’t in the early shortcuts. It’s in the culture they create: •Good developers leave •Innovation slows •Team morale drops •Quality becomes “optional” •Work-life balance disappears The solution isn’t working longer hours or hiring more people. •It’s building scalable practices early: •Culture of raising concerns without fear •Processes that grow with your team •Documentation as part of development •Quality as a non-negotiable value •Tools that provide transparency at scale like Astravue Remember: A culture of pressure might help you sprint, but it will cripple your marathon. Richard Feynman, in the Challenger investigation report, wrote something that is eternal: “For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled.” Whether you’re launching rockets or shipping code, the same principle applies: No amount of schedule pressure can change technical reality. The only question is whether we acknowledge it before or after something breaks. How does your team balance speed with scalability? Have you seen “temporary” solutions become permanent problems? #astravue #scalability #app #projectmanagement #workplace #workforce #leadership #management

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>)

If there's conflict in your team, how can you resolve it without aggression or escalation? And also without people-pleasing or giving away your power as a leader? The key here is: establish psychological safety. If your first response is to blame them, their guards will go up, and they will get defensive, because they will detect a threat i.e., lack of psychological safety. That's the end of the conversation and maybe even the relationship in extreme cases. Here are some examples: What NOT to Do: Dismiss or Ignore Concerns: Example: A team member raises an issue during a meeting, but it's brushed aside by the team leader without any further discussion. Instead: Acknowledge the concern and encourage open dialogue to understand its root cause and potential impact. What NOT to Do: Blame or Shame Individuals: Example: When a mistake is made, publicly assigning blame to a specific team member. Instead: Approach errors as learning opportunities for the entire team, focusing on solutions rather than assigning fault. Give constructive feedback in private. What NOT to Do: Dominate Discussions: Example: A few outspoken team members monopolize discussions, making it difficult for others to contribute their perspectives. Instead: Facilitate balanced participation by actively encouraging quieter team members to share their thoughts and ensuring everyone has an opportunity to speak. What TO Do Instead: Encourage Open Communication: Example: Create regular opportunities for team members to share their thoughts, concerns, and feedback in a safe and non-judgmental environment, such as through regular team meetings or anonymous suggestion boxes. Model Vulnerability: Example: Leaders openly admit their own mistakes or uncertainties, demonstrating that it's acceptable to be imperfect and fostering a culture of trust and authenticity. Provide Constructive Feedback: Example: When addressing performance issues, focus on specific behaviours or outcomes rather than attacking the individual's character. Offer guidance on how to improve and support them in their development. Celebrate Diversity of Thought: Example: Encourage team members to bring diverse perspectives to the table, recognizing that differing viewpoints can lead to more robust solutions. Celebrate successes that result from collaborative efforts. Establish Clear Norms: Example: Set explicit ground rules for communication and conflict resolution within the team, emphasizing the importance of respect, active listening, and maintaining confidentiality. Did this help? Then give this post a 👍🏼