Iterative Project Management Processes

Stakeholder Engagement Map for Sustainability 🌎 Sustainability advances when companies move from speaking to stakeholders toward building solutions with them. Engagement becomes powerful when it shifts from information-sharing to participation and co-creation. Employees are not passive recipients of corporate policies. When positioned as innovators and ambassadors, they can drive cultural change that scales faster than top-down initiatives. Investors increasingly evaluate not only financial returns but also resilience and impact. Open dialogue and credible disclosures create the foundation for financing models that reward long-term value creation. Regulators and policymakers shape the boundaries of what is possible. Proactive collaboration ensures that emerging rules both protect society and enable business innovation. NGOs and civil society connect business with pressing social and environmental realities. Partnerships with them help translate global challenges into concrete, measurable corporate actions. Customers bring more than purchasing power. Through collaboration and product co-design, they accelerate the adoption of sustainable solutions and redefine what markets demand. Suppliers and partners extend responsibility beyond a single enterprise. Joint innovation in sourcing, standards, and technology transforms sustainability into a shared endeavor across the value chain. Communities ground sustainability in place. When businesses co-invest in local development, they secure trust and create ecosystems that benefit both society and the enterprise. Media and opinion leaders influence how actions are perceived. Transparent storytelling backed by evidence strengthens legitimacy and reinforces accountability. Academia and experts contribute the critical lens of science and independent validation. Engaging them ensures that strategies are rooted in knowledge, not convenience. Risk and resilience demand collective approaches. Working groups and cross-sector alliances elevate sustainability from individual commitments to systemic impact. True engagement means entering a space of shared design. It is in these interactions that sustainability moves from compliance to transformation, and from promises to outcomes. #sustainability #business #sustainable #esg

Ever have 3.5x pipeline coverage and still miss by 20%? Well, here's a potential solution for ya. To be clear, this stuff happens often, and it tends to be a surprise to some leaders. Mainly because lots of folks still think that pipeline VOLUME is the same as pipeline HEALTH. If you're looking at your pipeline and don't really have a clue about what's in it AND you're comfortable with a bit of math, here's a different way to gauge your pipeline health. You can call it something like the "30-Point Quality Score." I'm not a marketing whiz, so feel free to come up with something more creative if you want. Anyway, here's how it works...instead of tracking gross dollar coverage, score each opportunity across six dimensions (0-5 points each, 30 points max): 1. Stage velocity (0-5 pts): - 0 pts = Sitting 3x longer than average cycle. - 3 pts = At average cycle length. - 5 pts = Moving faster than average. 2. Multithreading (0-5 pts): - 0 pts = Single contact. - 3 pts = 2-3 contacts. - 5 pts = 4+ contacts across buying committee. 3. Source quality (0-5 pts): - 0 pts = Cold inbound form fill. - 3 pts = Marketing qualified lead. - 5 pts = Rep-generated with champion. 4. Budget confirmation (0-5 pts): - 0 pts = "We think we have budget." - 3 pts = "Budget approved, waiting on timing." - 5 pts = "Budget allocated with PO number." 5. Intent signals (0-5 pts): - 0 pts = Passive engagement. - 3 pts = Responding to outreach. - 5 pts = Multiple stakeholders actively engaged. 6. Next step commitment (0-5 pts): - 0 pts = Vague "let's reconnect." - 3 pts = Calendar invite scheduled. - 5 pts = MAP with named owners. So your total quality-weighted pipeline = Sum of (deal size x quality score/30). For example: - Deal A: $100K × (25/30) = $83K quality-weighted. - Deal B: $100K × (12/30) = $40K quality-weighted. Now you can start tracking quality-weighted coverage instead of just gross coverage. I mean, you can keep celebrating 500 opportunities at $50M total value if you want. But it might be more effective to start tracking 150 opportunities with validated champions, defined next steps, and budget confirmation. I'd personally recommend the latter, mainly because your board doesn't care how many deals you forecast. They care how many you close. Math doesn't lie. Even when your pipeline does.

𝐒𝐭𝐚𝐤𝐞𝐡𝐨𝐥𝐝𝐞𝐫 𝐄𝐧𝐠𝐚𝐠𝐞𝐦𝐞𝐧𝐭: 𝐌𝐞𝐞𝐭 𝐓𝐡𝐞𝐦 𝐖𝐡𝐞𝐫𝐞 𝐓𝐡𝐞𝐲 𝐀𝐫𝐞 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

🎄 Day 14 of the #AdventOfOR 2025! The single biggest mistake in optimization projects? Engaging stakeholders once. Most teams nail the "Early" part (kickoff, problem framing, initial requirements). But then they disappear into complex code. Weeks later, they return with the perfect solution... but trust has eroded. Engagement isn't a single event. It's a continuous cadence: Early AND Often. Why is this continuous interaction essential? 🤝 Maintains trust: Consistent updates prevent the project from becoming a black box. 🎯 Ensures relevance: Requirements shift; regular check-ins keep your model aligned with business reality (just like we got new requirements on Day 12!). 🪡 Drives adoption: Stakeholders own the solution when they help build it. The secret to making it work is lowering the cost of understanding the model's progress. But you don't need to do heavy presentations; do easy, frequent demos with tools that help: 🔹 GAMS MIRO for interactive apps stakeholders can explore 🔹 Streamlit or Taipy for quick Python dashboards 🔹 Nextmv for comparing runs and sharing scenarios When showing progress becomes easy, you'll do it more often. When you do it more often, trust compounds. 🫵 Your turn: What's the single biggest piece of friction that currently stops you from sharing model progress (work-in-progress, not final results) with your stakeholders more often? (e.g., "It takes too long to clean the output," "We lack visualization tools," "I only share final numbers.")

You can’t call it partnership if stakeholders only hear from you once before launch. True engagement isn’t a courtesy email. It’s about making stakeholders 𝘱𝘢𝘳𝘵𝘯𝘦𝘳𝘴 𝘪𝘯 𝘵𝘩𝘦 𝘱𝘳𝘰𝘤𝘦𝘴𝘴 from day one to follow-through. 4 shifts that make the difference: 1. Map before you move Not all stakeholders need the same level of attention. Use mapping tools to identify who has influence, what they care about, and how they prefer to engage. 2. Align objectives early Don’t wait until the end to prove impact. Bring stakeholders into planning to set KPIs, success metrics, and business outcomes together. 3. Keep communication alive Use clear, jargon-free updates. Share progress, invite feedback, and celebrate wins. Trust grows when stakeholders feel part of the journey. 4. Champion transfer, not just learning Make managers and sponsors active player, e.g. mentors, accountability partners, and reinforcement leaders. Because learning in the classroom means nothing if it doesn’t show up on the job. When engagement is tailored this way, L&D stops being a service provider… and starts being a strategic driver of business results. A question for you: What’s worked best in your experience: mapping, alignment, communication, or transfer support? _____________ High functioning ≠ high capacity. I consult with L&D teams to turn busyness into business impact.

Are you optimizing for traction… or just counting trophies? Trophies (or outcomes) are the obvious metrics: followers, subscribers, sales, launches, “big wins.” 🏆 Traction (or velocity) is the quieter stuff: the movement in behaviour that tells you your message is landing. 🏃 Most marketing metrics fall into those two buckets: Velocity and Outcomes. We tend to obsess over outcomes. But velocity metrics often tell you sooner if you’re on the right track. Outcomes = “Did it work?” These are the scoreboard metrics: ▪️ Revenue ▪️ Qualified leads ▪️ Booked calls ▪️ Conversions (trial → paid, cart → checkout, etc.) ▪️ Followers They matter because they’re the point of the work. If outcomes don’t move, the marketing isn’t doing its job (or the offer/sales process needs fixing). The catch: outcomes are lagging indicators. They show up after a bunch of things go right. Velocity = “Is it starting to work?” Velocity metrics measure movement in behaviour — signals that people are getting closer: ▪️ Click-through rate changes (especially to “money pages”) ▪️ Save rate (people want to keep it) ▪️ Share rate (people want to be associated with it) ▪️ DM/inbound mentions (“saw your post about X…”) ▪️ Return visitors/time on page shifts ▪️ Conversion rate improvements even if volume is flat (less leakiness) These matter because they let you diagnose and iterate before you wait 60–90 days for revenue to tell you what happened. Velocity metrics are directional, not definitive. They answer: Are we earning attention? Building intent? Reducing friction? Here’s why you need both: ▪️ If you track outcomes only, you’ll change strategy too late (or give up too early). ▪️ If you track velocity only, you can accidentally optimize for “interesting” instead of “effective.” And here’s a guideline on how you might implement this: ▪️ Determine one outcome metric (the business result) ▪️ Determine two to three velocity metrics (the leading indicators) ▪️ A timeframe (when you expect each to move) Example: ▪️ Outcome: booked calls ▪️ Velocity: CTR to services page, DM volume referencing the post, landing page conversion rate That’s it. Simple. Trackable. Actionable.

Your AI strategy will fail if clinicians are not involved from day one. There will be no use for AI if they are not involved. Most organizations tend to miss this key part,  involving key players early on, and it's hurting your adoption rates. From healthcare professionals to patients, administrative staff to tech providers, each stakeholder plays a crucial role in successful implementation. Here's how to engage them effectively: Healthcare Professionals (Doctors, Nurses, Specialists) 1. Engage early in the decision-making process 2. Gather input on practical requirements and potential challenges 3. Involve in pilot programs to assess usability and integration challenges 4. Provide comprehensive training on new technologies Patients 1. Educate about new technologies and their benefits 2. Screen for digital literacy to identify those who may need extra support 3. Choose user-friendly technologies that don't require logins or downloads 4. Explain how new tools will save time or improve health outcomes Administrative Staff 1. Include in needs assessment to identify inefficiencies in workflows 2. Provide training on new systems and processes 3. Gather feedback on technology effectiveness and areas for improvement Technology Providers 1. Involve in stakeholder discussions to understand healthcare-specific needs 2. Collaborate on pilot programs and validation of technologies 3. Ensure technology is effective for healthcare professionals and interoperable with existing healthcare infrastructure 4. Ensure intuitive navigation in healthcare technology systems to facilitate adoption Organizational Leadership 1. Conduct thorough needs assessments to align technology with organizational goals 2. Develop a strategic plan with SMART goals for digital transformation 3. Establish key success metrics to evaluate technology effectiveness 4. Create a common forum for stakeholder discussions Including the different stakeholders can lead to: 1) Shared vision 2) Trust building 3) Addressing (and avoiding) conflicting interest 4) Improved compatibility 5) Ethical considerations What learnings do you have from implementing new technical tools in your organization?

How do we approach stakeholders - and how do we generate meaninful value for them? Over the last years, working across multiple Horizon Europe projects (e.g. Soil Health Benchmarks, LILAS4SOILS, Project CAFAMORE, TRAILS4SOIL), I’ve spent a lot of time reflecting on how we design and run stakeholder engagement. Across projects and organisations alike, I keep encountering a familiar pattern. We design engagement frameworks. We create checklists. We define participation moments. And still, something often doesn’t quite land. Not because stakeholders are unwilling to engage — but because we often misread or interpret from our perspective what we’re actually hearing. And foremost, projects engage motivated by checklists. Lately, I’ve been exploring this challenge through the lens of epistemic justice (very much as a learner) - not as a theory to apply, but as a practical question: How do we recognise, work with, and value or enable different ways of knowing in stakeholder (needs, expectations, wishes, etc.)? One of the risks, when we don’t, is what is often described as epistemic injustice. The image below captures this quite simply: someone shares experience A, but what gets heard - and acted upon - is B. Not out of bad intent, but because interpretation is guided by existing knowledge structures and decision-making power. For example: in a workshop on regenerative agriculture, a farmer is asked to reflect on “barriers to adoption” using predefined indicators. When he explains that the real challenge is yield volatility, financial risk, and the inability to absorb a bad season, this is translated into labels like “risk aversion” or “lack of incentives”. The farmer is heard - but his framing is reshaped to fit project categories, rather than allowing those categories to adapt. What I’m learning is that this isn’t about adding more empathy workshops or slowing projects down. It’s about epistemic fluency: integrating different kinds of knowledge, coordinating different ways of knowing, and designing engagement processes that adapt with stakeholders, not just to them. In my role advising the Mission Soil Cluster on Stakeholder Engagement and Communication, working with 55+ projects,  I want to explore this more deliberately over the coming year - and I’d genuinely welcome critique or pushback from those who’ve thought about this far longer than I have. Alexandra Robinson Dave Snowden Adrian Wagner Anne Caspari Joshua Stehr How do you see the balance between structured project delivery and epistemic justice e.g. in EU-funded projects that aim to engage stakeholders around diverse understandings of challenges and objectives (e.g. soil health across different regions)?

In many projects, stakeholders know they have a problem but aren’t clear about the solution. As Business Analysts, it’s our job to turn that uncertainty into clarity. Here’s how I approached it in a report automation project: 🎯 𝐂𝐨𝐧𝐭𝐞𝐱𝐭: The organization manually prepared monthly financial and operational reports using Excel. The process was tedious, error-prone, and delayed decision-making. Leadership knew they wanted “automation” but couldn't articulate what exactly they needed. 🛠️ 𝐇𝐨𝐰 𝐈 𝐇𝐞𝐥𝐩𝐞𝐝 𝐓𝐡𝐞𝐦 𝐃𝐢𝐬𝐜𝐨𝐯𝐞𝐫 𝐓𝐡𝐞𝐢𝐫 𝐍𝐞𝐞𝐝𝐬: Start with Business Outcomes, Not Solutions → I asked, "What decisions are delayed today due to slow reporting?" and "What’s the impact of late or incorrect reports?" → This shifted the discussion from "build a dashboard" to "we need accurate reports within 3 days after month-end to improve decision speed." 𝐂𝐨𝐧𝐝𝐮𝐜𝐭 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐖𝐚𝐥𝐤𝐭𝐡𝐫𝐨𝐮𝐠𝐡𝐬 → I organized sessions where stakeholders walked me through the current report generation steps. → Outcome: Identified bottlenecks like manual data consolidation from multiple systems, version control issues, and formula errors. 𝐔𝐬𝐞 𝐕𝐢𝐬𝐮𝐚𝐥 𝐀𝐢𝐝𝐬 → I mapped the As-Is report preparation process on a whiteboard: data sources → manual steps → approvals → final report. → Stakeholders immediately saw inefficiencies they hadn’t verbalized before. 𝐄𝐥𝐢𝐜𝐢𝐭 𝐏𝐚𝐢𝐧 𝐏𝐨𝐢𝐧𝐭𝐬 𝐭𝐡𝐫𝐨𝐮𝐠𝐡 𝐎𝐩𝐞𝐧-𝐄𝐧𝐝𝐞𝐝 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 → Instead of asking, "What features do you want?", I asked: "What’s the most frustrating part of preparing these reports?" "What do you wish was faster or easier?" → Answers revealed that data reconciliation and last-minute formatting were major pain points. 𝐏𝐫𝐨𝐩𝐨𝐬𝐞 𝐒𝐦𝐚𝐥𝐥 𝐏𝐫𝐨𝐭𝐨𝐭𝐲𝐩𝐞𝐬 → I created quick mockups (even in Excel or Power BI) of how an automated report could look. → This gave stakeholders something tangible to react to, sparking more specific feedback and helping refine the requirements iteratively. Facilitate Prioritization Workshops → Stakeholders often have a wishlist once they start seeing possibilities. I conducted MoSCoW prioritization sessions to separate “must-have” automation (data refresh, error checks) from “nice-to-haves” (fancy dashboards). 𝐓𝐫𝐚𝐧𝐬𝐥𝐚𝐭𝐞 𝐔𝐧𝐜𝐥𝐞𝐚𝐫 𝐖𝐚𝐧𝐭𝐬 𝐢𝐧𝐭𝐨 𝐂𝐥𝐞𝐚𝐫 𝐑𝐞𝐪𝐮𝐢𝐫𝐞𝐦𝐞𝐧𝐭𝐬 → Statements like, "We need to make reports faster" were converted into clear specs: Data from 3 systems consolidated automatically. Standardized templates in Power BI. Report availability by the 3rd business day. 💡 𝐊𝐞𝐲 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲 𝐟𝐨𝐫 𝐁𝐀𝐬: When stakeholders are unclear, they don't need immediate solutions — they need discovery. Our role is to: ✔️ Focus on outcomes. ✔️ Walk the current journey. ✔️ Ask powerful open-ended questions. ✔️ Show possibilities visually. ✔️ Translate pain points into structured requirements. BA Helpline

Shared understanding is fundamental to any change endeavour. But how do we orchestrate a journey towards a shared understanding? This framework - from the fantastic Challenge-led system mapping handbook by Climate-KIC - highlights a structured progression inspired by the DIKW pyramid. I really like the way iterative dialogue is embedded in a way that ensures resources become living documents that evolve with stakeholder insights, reflecting the dynamic nature of the system. "The evolving conversation contributes to the collective understanding of the challenges, the questions, and the mapped system itself." This journey begins with participatory processes and data generation, which lay the foundation for understanding the makeup of the system. These steps involve diverse stakeholders coming together to identify core components and relationships within the system. As the process evolves, we move into harvesting and documentation, where data transitions into manageable sources and is organised into coherent information. This phase involves physical structuring and cognitive processes, framing data into actionable insights and beginning to illuminate system patterns. The next phase—conceptualisation and analysis—builds on this structured base to foster a deeper understanding. Here, information transforms into knowledge through analytical structuring. This stage involves recognising connections, patterns, and dynamics, enabling stakeholders to identify key indicators of progress or change. Finally, the journey culminates in wisdom, where insights are communicated through visualisation and interpretation. This stage bridges the gap between abstract analysis and practical application, enabling informed decision-making and co-produced practices. Wisdom reflects a high level of both structure and understanding, empowering stakeholders to act collaboratively toward systemic change. This iterative and participatory process emphasises the importance of feedback loops and incremental understanding, ensuring that stakeholders grasp the complexities of the system and also feel invested in its transformation. "Knowledge management integrates links between interpretation, analysis, and action, allowing practitioners to move from traditional 'learning to manage' practices to 'management as learning'."