Managing Culture and Processes in Engineering Projects

Rethinking Requirements in Hardware Engineering Requirements management isn’t just about checklists—it’s the difference between effective collaboration and costly missteps. Here are once-unconventional approaches to requirements now embraced by top teams 1. From “Requirements��� to “Design Criteria” Early systems engineers were part engineer, part lawyer. Someone had to create “techno-legal documents” to manage external contracts. These evolved into requirements. Many cultural issues stem from using requirements incorrectly–as a weapon rather than tool for collaboration. Not all requirements need to be treated as commandments. Reframing lower-level requirements as design criteria reduces resistance among engineers, empowering them to see requirements as flexible guidelines open to questioning and adjustment. This is what you want to inspire. 2. Culture of Ownership and Accountability Drives Agility A strong requirements culture is built when engineers “own” their work. Engineers must take responsibility for the requirements they design against, creating a culture of ownership, responsibility, and systems-mindedness. Assigning a clear, single-point owner for each requirement, even across domains, encourages each engineer to think critically about their area’s requirements, establishing ownership and trust in the process. Encouraging information flow between teams helps engineers see how their work impacts others, leads to reduced and stronger system integration. Requirements should be viewed as evolving assets, not static documents. You want engineers to push back on requirements and eliminate unnecessary systems rather than add more requirements, complexity, or systems. 3. Requirements as Conversations, Not Just Checklists Requirements aren’t just specs or checklists—they’re starting points for cross-functional discussions. Every problem is a systems problem, and to solve complex challenges, engineers must be systems thinkers first and domain experts second. In traditional settings, requirements stay isolated in documents. But when teams understand why requirements exist, where they come from, and who owns them—and engage in continuous dialogue—they blur the lines between domains and foster a systems-oriented mindset. This collaborative environment accelerates problem-solving, enabling engineers to align quickly and tackle challenges together. Instead of siloed requirements for each subsystem, drawing dotted lines and encouraging information flow between teams helps engineers understand how their work affects others. This cross-functional awareness leads to fewer misalignments and stronger system integration. When you see engineers make sacrifices in their own area to benefit the overall system, you know you are on the right track. There you have it. The full guide goes into specifics on how to start implementing these ideas in tools.

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

Post-mortem your projects. For a team I coached, post-mortems were non-negotiable. After every project, they would sit down and unpack the process and the outcome, celebrating the hits without tiptoeing around the misses. Because it was expected and just a regular part of their process, no one took it personally. There was no blaming and shaming, but there was accountability and learning. Through these sessions, giving and receiving feedback became something each person owed the team. This meant that with each project, whether it went well or otherwise, the organisation sharpened its skills and systematically got better at what they did. You can imagine how that kind of progress compounds over time. When you build a culture of improvement, growth is inevitable. But that culture has to be built intentionally and purposefully. The best teams don’t just deliver projects. They learn from them. 💯 Do you post-mortem your projects, or leave them to become skeletons in your closet?

Project management is 10% process and 90% people. Teams often chase better tools, tighter workflows, and cleaner dashboards. But the real leverage sits somewhere else. Here is how the 90% shows up in real project environments: → Communication creates clarity long before any template does. → Trust speeds up decisions that workflows cannot touch. → Conflict resolution keeps delivery moving when tension builds. → Alignment removes delays that no software can fix. → Culture drives ownership, momentum, and follow-through. When the people side is strong, the process side becomes straightforward. That is why the best project outcomes start with relationships, not tools.

Recently, I heard a manager demand his team "run it again." Those three words destroyed their experimentation culture. Here's what happened: His hypothesis: Faster changeovers would increase throughput by 15%. They ran the experiment for three weeks. Measured everything. Results: 3% improvement. Within normal variation. His response? "Run it again." ❌ Not the values poster in the lobby about "innovation and learning." ❌ Not the strategic plan promising "data-driven decisions." That single sentence told his team everything they needed to know. Then I watched a different leader handle the same situation last month. Her team tested a material substitution she'd been championing. Data showed 4% increase in defect rates. She pulled everyone together: ❓ "What does this tell us about our process constraints?" ❓ "Where else might we be making similar assumptions?" Then she thanked them. Publicly. And shifted budget to test three alternative approaches. THE REAL DIFFERENCE When we treat contradictory data as gold rather than treat it as a threat, → WeThey run experiments again → We find flaws in methodology → We explain why "this time was different" THE MOMENT THAT DEFINES YOUR CULTURE We don't build experimentation when data confirms our genius. We build it when results prove us wrong: • Our pet theory fails • The new engineer's method beats ours • Three weeks of testing reveals we optimized the wrong variable That's when our team is watching. Do we ask "What did we learn?" Or demand "Run it again?" Every time we dismiss contradictory data, we teach our team: "Don't bring me learning. Bring me validation." Then we wonder why: → Experiments slow down → Innovation stalls → People stop challenging assumptions The culture we want lives in how we respond to being wrong. What contradictory data are you sitting on right now? How will you respond? 👇 I help engineering and manufacturing leaders build experimentation systems where contradictory data drives breakthrough insights, not defensive reactions. If your teams keep confirming what you already believe, let's connect.

One of the biggest lessons I’ve learned in manufacturing is that solving technical problems is only half the battle, managing people is just as critical. During a capacity increase project at Tesla, I led the installation of new equipment. Everything was on track....until it wasn’t. The controls engineers responsible for integrating the system hit a major roadblock: One was focused on conveyance controls. The other was working on the machine we were installing. Neither could agree on how to align their work, and progress came to a halt. As the PM, I knew this wasn’t a problem that could be fixed with technical knowhow. It required something else: people skills. Here’s What I Did: 🔍 Identified the Root Cause: I sat down with each engineer separately to understand their frustrations and concerns. 🤝 Facilitated Honest Communication: In a collaborative meeting, I encouraged both engineers to share their perspectives and find common ground. 🎯 Aligned Everyone on the Goal: I refocused the team on the bigger picture: increasing capacity and meeting the project deadline. The Outcome? The engineers not only resolved their differences but collaborated effectively to complete the controls integration ahead of schedule. The equipment was installed, tested, and operational, delivering the capacity increase we needed. What I Learned: 1️⃣ People > Processes: Technical skills alone can’t move a project forward when people are stuck. 2️⃣ Communication is Key: Creating space for open dialogue can unlock solutions faster than any manual. 3️⃣ Leadership is Listening: Sometimes the most valuable thing you can do is step back, listen, and guide the team toward resolution. This project reinforced that managing a successful install isn’t just about the machines—it’s about the people behind them. 📢 What’s a time when you had to step in as a mediator to keep a project on track? Let’s share our experiences and lessons learned! #Leadership #Manufacturing #ProblemSolving #Teamwork #ProjectManagement

Adopt a systems approach to engineering design before your next capital project slips.     The pain you live with, disconnected people, processes, and data, shows up as late surprises, change chaos, and compliance gaps. In large capital assets, that fragmentation has a real price: average projects see cost overruns near $1.2 billion with delays from six months to two years, while construction productivity has inched around 1% over two decades compared to 3.6% in manufacturing. Add the push toward modular construction (about $175 billion by 2025) and a once-in-a-generation surge in capital spending through 2027, and the stakes could not be higher.     Systems-driven design is the discipline that closes the loop. It moves requirements from scattered docs into a single source of truth connected to every design domain, electrical, mechanical, software, so changes propagate in real time and compliance can be checked as decisions are made, not after the fact. It brings end-to-end traceability, the voice of the customer baked into each step, and a repeatable way to manage change as regulations evolve.     Try this simple play on your next project:  • Make requirements your single source of truth across plant, process, and equipment data.  • Connect requirements to every design activity and validate continuously as changes flow.  • Classify and reuse sub-systems, requirements, history, and change included, to cut rework.     When this approach is in place, hidden design issues surface early, cross-functional collaboration improves, and re-invention gives way to reuse. That’s how assets are more likely to work the first time with minimal rework later. 

Culture isn't built in one offsite. Culture is being built in the 100 small decisions your team makes every day. 💌 Culture = Consistent behavior at scale When your leadership team uses 3 different tools, your IC teams will use 10. When your VP writes strategy docs one way and your Director does it differently, no one knows the template. The fix isn't a private message about using the right tool. The fix is leaders demonstrating the system, every single time. 👉 Here's what works: → Pick one source of truth for your knowledge or project management → Create standard templates for common docs (strategy, project briefs, post-mortems) → Leaders link to properly-formatted docs in every meeting The results: → New PM finds last quarter's strategy in 2 minutes, not 20 → Fewer "wait, where did we document that?" moments → Knowledge that scales instead of living in Slack threads Culture is just repeated behavior that becomes expectation. If you want aligned teams, start with aligned systems.