How can project managers systematically assess the full impact of proposed changes across all project areas?

Host: Welcome to A.I.S. Insights — powered by Living Knowledge. I'm Anna Ivy Summers. Today, we're diving into an exciting study titled "Project Change Canvas," authored by Raquel Ferreira, João Varajão, Luís Silva Rodrigues, and Rui Dinis Sousa. At its core, this study introduces a practical, one-page visual tool designed to help project leaders systematically evaluate change requests in information systems and technology projects. Joining me to unpack the details is our resident analyst, Alex Ian Sutherland. Welcome, Alex.

Expert: Thanks, Anna. It's great to be here. This study tackles a challenge that virtually every manager faces: dealing with project changes without derailing the entire initiative.

Host: Exactly. We often hear that change is the only constant in business, especially in tech and IT projects. But why does handling changes so frequently lead to headaches, delays, and budget blowouts? What is the core problem identified in the study?

Expert: Well, Anna, projects are dynamic and unpredictable. In fact, the study highlights that more than half of all project changes are emergent—meaning they happen spontaneously due to unforeseen weaknesses, operational demands, or shifting business realities. The real issue lies in how we evaluate those changes. Historically, change management tools have been overly narrow. They focus almost exclusively on the classic iron triangle: cost, schedule, and scope.

Host: Right, the usual questions: "How much will this cost?" and "How late will this make us?"

Expert: Exactly. But a project is an interconnected ecosystem. If you only look at time and budget, you completely miss critical dimensions like team resource strain, external procurement bottlenecks, stakeholder communication shifts, new risk exposure, and overall project success. The authors point out that without a holistic assessment, decision-makers are operating with blind spots. They either rush into approving changes that cause catastrophic ripple effects or spend months in analysis paralysis trying to decide.

Host: That brings us to how the researchers tackled this. What methodology did the team use to build a better way forward?

Expert: The researchers used Design Science Research, which is specifically aimed at creating practical artifacts that solve real-world problems. They followed a six-stage process, starting with an extensive review of existing project management standards like PMBOK and ISO 21502. After identifying best practices and structural gaps, they designed the Project Change Canvas. Crucially, they didn't just leave it as a theoretical model. They tested and refined it in two real-world projects: one involving a workflow and multilingual website transformation, and another involving a core platform migration for software modules.

Host: Let's talk about the canvas itself. How does it work in practice?

Expert: It's designed as an intuitive, one-page tool structured around four clear stages of change control. Step zero and one cover characterization. You record the project header, specify whether the change is mandatory or optional, set the priority level, and detail the origin, justification, and applicant. Then comes step two, which is the heart of the canvas: the integrated impact evaluation.

Host: And that's where all those overlooked areas get scrutinized, right?

Expert: Precisely. The canvas forces the team to assess impacts across stakeholders, high-level goals, and three granular tiers of scope: requirements, deliverables, and activities. Then it moves into quality control measures, milestone schedule impacts, human and material resources, procurement needs, financial costs, communication adjustments, and risk factors. Interestingly, during real-world testing, team feedback revealed that the initial canvas lacked a explicit link to project success criteria. In response, the authors replaced a redundant "Responsibilities" box with a dedicated "Success" block, ensuring teams weigh benefits and drawbacks directly against the project's strategic outcomes.

Host: I love that iterative improvement based on real feedback. What happens after the evaluation?

Expert: Step three is formal decision-making. The canvas requires a clear status: approved, rejected, or deferred. If a change is deferred or rejected, the justification must be recorded right there. Finally, step four covers implementation recommendations and observations, outlining how to execute the approved change within existing constraints.

Host: That brings a level of discipline that often gets lost in informal conversations or buried in lengthy change management documentation. Why does this matter so much for business leaders and project sponsors?

Expert: There are three huge business takeaways here. First, transparency and speed. Instead of lengthy email chains or vague discussions, all stakeholders have a single source of truth summarizing the rationale, trade-offs, and downstream impacts. Second, it balances agility with control. It doesn't prevent change; it ensures that when you say "yes," you know exactly what compromises you are making across resources, quality, and risk. And third, it serves as an auditable change log that captures institutional knowledge and lessons learned for future initiatives.

Host: It turns change from a chaotic surprise into a structured, strategic decision. A single page that aligns the team, protects the baseline, and safeguards ultimate project success. Alex, thank you so much for breaking down this study for us today.

Expert: My pleasure, Anna.

Host: And to our listeners, thank you for tuning in to A.I.S. Insights — powered by Living Knowledge. Join us next time as we continue exploring actionable insights at the intersection of business and technology. Until then, take care.