Balancing Innovation And Practicality In Engineering

It’s easy as a PM to only focus on the upside. But you'll notice: more experienced PMs actually spend more time on the downside. The reason is simple: the more time you’ve spent in Product Management, the more times you’ve been burned. The team releases “the” feature that was supposed to change everything for the product - and everything remains the same. When you reach this stage, product management becomes less about figuring out what new feature could deliver great value, and more about de-risking the choices you have made to deliver the needed impact. -- To do this systematically, I recommend considering Marty Cagan's classical 4 Risks. 𝟭. 𝗩𝗮𝗹𝘂𝗲 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗦𝗼𝘂𝗹 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 Remember Juicero? They built a $400 Wi-Fi-enabled juicer, only to discover that their value proposition wasn’t compelling. Customers could just as easily squeeze the juice packs with their hands. A hard lesson in value risk. Value Risk asks whether customers care enough to open their wallets or devote their time. It’s the soul of your product. If you can’t be match how much they value their money or time, you’re toast. 𝟮. 𝗨𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗨𝘀𝗲𝗿’𝘀 𝗟𝗲𝗻𝘀 Usability Risk isn't about if customers find value; it's about whether they can even get to that value. Can they navigate your product without wanting to throw their device out the window? Google Glass failed not because of value but usability. People didn’t want to wear something perceived as geeky, or that invaded privacy. Google Glass was a usability nightmare that never got its day in the sun. 𝟯. 𝗙𝗲𝗮𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗔𝗿𝘁 𝗼𝗳 𝘁𝗵𝗲 𝗣𝗼𝘀𝘀𝗶𝗯𝗹𝗲 Feasibility Risk takes a different angle. It's not about the market or the user; it's about you. Can you and your team actually build what you’ve dreamed up? Theranos promised the moon but couldn't deliver. It claimed its technology could run extensive tests with a single drop of blood. The reality? It was scientifically impossible with their tech. They ignored feasibility risk and paid the price. 𝟰. 𝗩𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗥𝗶𝘀𝗸: 𝗧𝗵𝗲 𝗠𝘂𝗹𝘁𝗶-𝗗𝗶𝗺𝗲𝗻𝘀𝗶𝗼𝗻𝗮𝗹 𝗖𝗵𝗲𝘀𝘀 𝗚𝗮𝗺𝗲 (Business) Viability Risk is the "grandmaster" of risks. It asks: Does this product make sense within the broader context of your business? Take Kodak for example. They actually invented the digital camera but failed to adapt their business model to this disruptive technology. They held back due to fear it would cannibalize their film business. -- This systematic approach is the best way I have found to help de-risk big launches. How do you like to de-risk?

Prototypes aren't for testing your product. They're for testing your assumptions. Most teams get this backward, and it costs them weeks of wasted effort and a product nobody wants. A prototype isn't a tiny product; it's a medium for learning. It's a tool designed to ask a specific question and test a core assumption with the right audience. An unintentionally designed prototype is a flawed input, and even with advanced teams and tools, flawed inputs only amplify flaws. The true power of a prototype isn't in its polish, but in the intentional "message" it sends. To unlock this power and truly accelerate collective learning across your organization, you must design with intent: ✺ Low-Fidelity Prototypes: These are for asking foundational, "Does this even solve the right problem?" questions. They signal that everything is up for debate. The intentional message is: "Let's explore the idea, not the pixels." ✺ Medium-Fidelity Prototypes: Use these to test core user flows and information architecture. The intentional message is: "Is this journey intuitive?" By keeping them a little rough, you prevent stakeholders from getting fixated on visual design. ✺ High-Fidelity Prototypes: Reserve these for the final stages to test things like micro-interactions, brand consistency, or subtle emotional responses. The intentional message is: "We're almost there. What are we missing?" This is how you turn prototyping from a simple task into a strategic lever for change and Team Learning. It ensures your team isn't just building things, but is learning together and making better decisions about what to build and why. It's how you break down silos and create a "Holding Environment" for generative dialogue. What's a time you intentionally used a low-fidelity prototype to prevent a high-stakes meeting from spiraling? Let’s discuss in the comments below. #ProductDesign #SystemsThinking #StrategicDesign #UXStrategy #DesignLeadership #ComplexSystems #TeamLearning #Prototyping #OrganizationalDesign #Innovation

Sustainability = Innovation 🌎 Integrating sustainability into business strategy requires continuous advancements in technology, processes, and resource management. At the same time, sustainability challenges drive research, development, and operational efficiencies that lead to new market opportunities and competitive advantages. Resource constraints drive material and process innovation. The need for alternatives to finite or harmful materials has accelerated the development of advanced composites, circular economy models, and energy-efficient production systems, improving cost efficiency and resilience. Addressing sustainability challenges requires systems-level innovation. Reducing emissions, optimizing resource use, and minimizing waste require advancements in supply chain management, product lifecycle design, and industrial processes, reshaping entire sectors. Cross-functional collaboration is critical. Sustainability initiatives require input from engineering, data science, regulatory compliance, and finance to develop integrated solutions that meet environmental targets while maintaining operational and commercial viability. Data-driven approaches enhance sustainability performance. Measuring environmental impact enables companies to identify inefficiencies, optimize resource allocation, and refine business strategies based on quantifiable sustainability metrics. Long-term sustainability targets drive investment in research and technology. Businesses are accelerating development in areas such as AI-driven resource optimization, carbon capture, and next-generation materials to align with regulatory requirements and market expectations. Nature-based solutions provide scalable innovation opportunities. Biomimicry has led to advancements in self-healing materials, passive cooling systems, and regenerative agricultural techniques, improving efficiency and resilience across industries. Sustainability is reshaping business models. The transition to circular economy principles, service-based models, and regenerative supply chains is driving competitive differentiation and long-term value creation. Innovation is fundamental to achieving sustainability objectives. The convergence of regulatory frameworks, technological advancements, and market shifts is reinforcing the role of sustainability as a driver of industrial transformation and business resilience. #sustainability #sustainable #business #esg #climatechange

Interview Conversation Role: RTE in #SAFe framework Topic: Conflict Management 👴 Interviewer: "Imagine the Product Manager and System Architect disagree over feature priorities, with the PM focusing on customer needs and the Architect concerned about tech debt. As the RTE, how would you handle this?" 🧑 Candidate: "I’d remind them to focus on the PI objectives and find a middle ground." 👴 Interviewer: "Say this disagreement is slowing decision-making, impacting team alignment, and morale is dipping. What specific actions would you take to mediate?" 🧑 Candidate: "I’d encourage both of them to think about the project’s overall goals." What a skilled Release Train Engineer should say: ------------------------------------------------------ In cases like this, it’s crucial to foster open, constructive discussions without losing sight of both customer value and technical stability. 🌟 I’d start by facilitating a conversation with the PM and Architect to unpack their priorities and establish a shared understanding. 📅 In a similar situation, I scheduled a conflict-resolution workshop with both roles, focusing on ‘value vs. sustainability’ using the Economic Framework. 🏹 We assessed the impact of each priority on the PI objectives, assigning weights based on business and architectural needs. The workshop helped clarify the ROI of tech improvements and immediate features, allowing them to make informed trade-offs. 🛠 To make it concrete, we identified one high-priority feature to advance and a critical refactor for the next PI. By reaching a balanced decision, we addressed urgent customer needs while setting a feasible path for addressing tech debt. 🚩 Impact: This approach helped restore team alignment, fostered trust between the PM and Architect, and improved the ART’s overall efficiency. ✍ As an RTE, my role is to mediate these discussions by grounding decisions in shared values and structured prioritization, ensuring both immediate and long-term value are achieved.

Tyre recycling stands as a powerful reminder that innovation is not always about creating something new, but about seeing hidden value in what the world has already discarded. In a time where landfills continue to expand and natural resources are stretched thin, transforming end-of-life tyres into engineering-grade materials reflects a shift in mindset—from waste management to resource intelligence. Through carefully designed mechanical and thermal processes, what was once an environmental burden is re-engineered into resilient components for roads, infrastructure, and landscape systems, quietly supporting the very foundations of modern life. This is not just recycling; it is a form of engineering redemption—where rubber becomes resilience, steel finds a second purpose, and fibers regain structural relevance. The true impact lies beyond materials; it lies in the philosophy it promotes—that sustainability is not a compromise, but an upgrade. When industries begin to design systems that reuse, reintegrate, and regenerate, they don’t just reduce damage—they build smarter, longer-lasting solutions. Tyre recycling, therefore, is more than a process; it is a blueprint for a future where progress and responsibility move in the same direction, proving that even the most overlooked waste can become a cornerstone of sustainable development.

PROTOTYPES ACCELERATE DISCOVERY, NOT DELIVERY Prototypes are powerful tools for the discovery phase — helping teams quickly explore product directions, validate concepts with customers through high-fidelity experiences, and align executives around tangible visions. The leverage they provide in answering "what's the right experience to build?" is remarkable. However, I frequently see PMs expecting to hand prototypes directly to engineering teams for production implementation. This approach consistently leads to disappointment. Here's why: prototype code isn't built to meet the security, reliability, robustness, and maintainability standards that production systems require. Your engineering team rightfully prioritizes these critical attributes. And that's perfectly fine. The value of prototypes lies entirely in discovery. Even when engineering teams ultimately rebuild from scratch, prototypes have already delivered tremendous ROI by: - Accelerating team alignment on product direction - Validating customer demand with realistic experiences - Securing executive buy-in through tangible demonstrations The code was never meant to ship — the insights were.

Are you trying to boil the ocean with your A.I. initiatives? In the construction industry, business value is often scattered across complex processes and value chains. As much as we'd like to believe in a magical one-size-fits-all solution, they don't exist. A.I. is definitely the latest hot topic and it's easy to get swept up in the excitement. Once that excitement wins the collective imagination, there's often a corresponding enthusiasm to embark on wildly ambitious A.I. plans. But here's the thing: many A.I. initiatives fall flat because we're asking them to solve problems that might just be too big, too complex, or maybe even the wrong fit for A.I. I’ve seen this happen in large construction companies with big R&D or IT budgets. What starts as a bold plan to merge all of a company's financial data, project performance metrics, and/or project documents can end up as a tool that no one uses or trusts. So, how do we avoid this? Here’s what I’ve been thinking: First, I’m a big believer in starting small and focusing on what matters most. Instead of boiling the ocean, why not start with the workflows that really move the needle? These are incremental wins that prioritize A.I. use cases fitting high-value workflows in the field and at the project level. Another thought—how are we evaluating feasibility early in the process? It's crucial to involve technical experts from the start to ensure we're solving the right problems and not just chasing the latest trends for the sake of it. Both of those involve a deep understanding of your company's use case prioritization, similar to the one walked through in the latest Placer Solutions industry research. Finally, A.I. requires time and patience. Not every problem can be solved with A.I. and leaders should avoid treating it as a magic solution to every challenge. Are we focusing on problems that really deserve long-term commitment? If a project feels like it's more about hitting the latest trend or trying to impress with jargon, maybe it's worth reconsidering. I'm curious—what challenges have you faced when it comes to A.I. initiatives? How do you decide which projects are worth the investment and which ones might be too ambitious? #construction #buildingconstruction #ai #digitaltransformation #constructiontechnology #constructiontech #technologyexcellence #organizationalexcellence #builtenvironment

You can spend millions on new tech, but without this one skill, you're part of the 70% that fail. Ever watched a child resist trying new food? That's exactly how most employees feel about new technology at work. I learned this the hard way while leading digital changes in my team. The game changer wasn't fancy software, it was understanding how my team felt. Here's the exact playbook that turned my team's tech fear into enthusiasm: 1. Listen first, act later. When team members worry about losing their jobs to automation, show them how the new tools will make their work easier, not take it away. Schedule dedicated 1:1 sessions to document concerns. 2. Keep talking, keep sharing. Set up structured communication channels, bi-weekly tech updates and anonymous feedback systems. 3. Take baby steps. No one learned to run before walking. Give your team time to learn new tools at their own pace. Break training into short, digestible 15-minute daily modules focusing on immediate-use features. 4. Celebrate small victories. Create a weekly "Tech Win" spotlight in team meetings to recognize progress. 5. Know yourself first. As a leader, if you're stressed about change, your team will feel it too. Use established change management frameworks to assess and manage your own readiness for change. The success of digital initiatives isn't measured by technological efficiency, but by how well teams adapt and thrive in their new environment. What's the biggest challenge you've faced when implementing new technology in your team? #Leadership #Growth #Change #Success

A knee-jerk reaction to team resistance might be: “Fire them all and start again.” But here’s the truth you probably don’t want to hear: Your team isn’t resisting change, they’re resisting you. That’s a tough pill to swallow, but let’s be honest, change rarely fails because the idea is bad. It fails because trust is broken and because you skipped the “why,” and fear filled the silence you left behind. When your team pushes back, here’s what they’re really saying: “I don’t trust where this is going.” “No one asked me.” “I’m scared, and I don’t feel safe saying that out loud.” “You’ve changed things before and left us to clean up the mess.” Change is emotional, human, and messy. So if you want real buy-in? Don’t start with a strategy deck, start with your people. Here’s how: 1️⃣ Ask Invite input early. Before rolling out a change, ask your team what they think. What are their worries? What would make this easier for them? Use open-ended questions like: “What do you see as the biggest challenge here?” “How do you think this change could help us?” 2️⃣ Listen Really listen. Don’t just nod along, take notes, ask clarifying questions, and reflect back what you’re hearing. Acknowledge the emotion: “It sounds like you’re worried about how this will impact your workload. That’s a valid concern.” 3️⃣ Validate Show you value their perspective. Even if you can’t act on every suggestion, let them know their voice matters. Be transparent about any constraints. Make the change with them, not to them. Co-create solutions. Let the team own parts of the process. When things get tough, solve problems together, not in isolation. And when things get bumpy? Because they will: ✅ Celebrate the tiny wins, because they matter more than you think. ✅ Talk about the challenges and fix them together. When leaders try to solve the bumpiness alone, they leave their team feeling lost at sea. And let’s be honest, that’s a tough place to be left alone. So bring your team into the journey, or at least keep them in the discussion. My rule is simple: If it impacts them, communicate, don’t hide. Want to drive change that actually sticks? Start with trust, not tactics.

I had a fascinating conversation with Steve Quinlan of NatWest Group recently, and it really highlighted a fundamental issue in how many product teams approach experimentation. Too often, "experimentation" is seen as something that happens after a feature is built. This is the cart-before-the-horse. You've already invested significant time and resources, and now you're hoping to validate if it was worth it. True experimentation should be about validating and developing ideas before they enter serious development and as they go through design. Steve sits with a 'prototyping' function at Natwest created with this purpose in mind. They focus on de-risking development by rigorously testing and iterating on ideas early in the process. This approach not only saves valuable resources but also ensures that the final product truly meets customer needs. Moreover, Steve's team's work disambiguates from the narrow view that experimentation is just about A/B testing. It's about a broader, more strategic approach to product research, discovery and validation. It begs the question: how many product teams are missing out on this critical early-stage validation? How often are we building features based on assumptions rather than solid evidence, even if they are 'tested' before release? Shifting our mindset to prioritize prototyping and early-stage experimentation can revolutionize how we build products and drive innovation. How does your team ensure that experimentation is integrated into the entire product development lifecycle, not just tacked on at the end? #experimentation #cro #productmanagement #growth #digitalexperience #experimentationledgrowth #elg