Practices to promote PMBOK 7th Edition's 12th principle says: "Enable change to achieve the envisioned future state."

You've highlighted some excellent practices:

In my experience, neglecting change management is a recipe for project failure. Thanks for emphasizing its importance!
Francisco

In my experience, enabling change to achieve the envisioned future state requires creating an environment where adaptability is embraced as a core value rather than seen as a disruption. I have found that three practices work particularly well:

Early and Continuous Stakeholder Engagement – From the very beginning of the project, I ensure stakeholders are involved not only in defining the vision but also in validating incremental progress. Regular feedback loops help identify misalignments early and give stakeholders a sense of ownership in the change process.

Clear Communication of the “Why” – People are more likely to embrace change when they understand its purpose. I make sure to connect each change to the broader organizational objectives and explain how it benefits both the business and the individuals involved. This alignment between the vision and day-to-day actions helps reduce resistance.

Agile Mindset and Iterative Delivery – Even if the project is not fully agile, I integrate iterative delivery cycles. Delivering in smaller increments allows for quick wins, builds confidence, and provides opportunities to adjust based on feedback before committing to larger changes.

What has worked for me is maintaining transparency and building trust through open communication channels. When team members feel safe to express concerns or propose alternatives, they become active contributors to the envisioned future state rather than passive recipients of change.

What hasn’t worked as well is implementing too many changes at once without considering the team’s change saturation level. I’ve learned that even beneficial changes can fail if people feel overwhelmed, so pacing the transformation and prioritizing initiatives is essential.

By combining stakeholder engagement, a strong narrative for change, and adaptable delivery methods, I’ve seen teams move from initial resistance to full commitment to the project’s goals.

Looking forward to hearing about the approaches that have worked for you all.

Desde mi experiencia en el sector público, este principio es el pan de cada día cuando trabajas con programas que buscan transformar realidades, como lo hemos hecho con iniciativas dirigidas a emprendedores, comerciantes o sectores estratégicos del estado.

¿Qué prácticas aplicamos para promover este principio entre los equipos y los stakeholders?

Empatía con el entorno: Muchos de nuestros beneficiarios no están familiarizados con conceptos de formalización, financiamiento o digitalización. Adaptar el lenguaje, acercarse con sensibilidad y entender su contexto ha sido clave para facilitar el cambio.

Involucramiento desde el diseño: Cuando los actores locales (como presidentes de cámaras, asociaciones, gobiernos municipales) participan desde la planeación, el cambio no se siente impuesto: se vuelve colaborativo.

Pilotos y validación previa: Antes de escalar un programa, lo probamos en un entorno controlado. Eso nos ha permitido hacer ajustes rápidos y reducir fricciones al implementar.

Narrativa de beneficios concretos: Más allá del discurso institucional, mostramos cómo el cambio impacta positivamente en su operación diaria, por ejemplo: mayor acceso a clientes, ahorro en costos o incentivos económicos.

Estrategia de comunicación continua: No basta con lanzar un programa y esperar resultados. Lo reforzamos con mensajes claros, ejemplos locales de éxito y seguimiento constante.

Lo que sí ha funcionado:

Mostrar resultados tangibles en poco tiempo.

Crear redes de aliados que repliquen el mensaje desde lo local.

Entender que los tiempos políticos y operativos son distintos, y saber moverse entre ambos con flexibilidad.

Lo que no ha funcionado:

Lanzar proyectos sin acompañamiento territorial.

Subestimar la resistencia al cambio en estructuras tradicionales, incluso internas.

Confiar solo en la plataforma digital sin considerar brechas tecnológicas (como vimos con el programa Atienda).

El principio del PMBOK 7, "Permitir el cambio para lograr el estado futuro previsto", en un auditor de Coppel, significa usar la auditoría como una herramienta de mejora continua, no solo de control.

Para lograrlo, se usan prácticas como:

Un enfoque consultivo, colaborando con los equipos para encontrar soluciones.

Adaptar el plan de auditoría a los nuevos riesgos del negocio.

Hacer reportes enfocados en soluciones prácticas y no solo en problemas.

Lo que funciona:

Generar confianza y relaciones sólidas.

Priorizar los cambios de mayor impacto.

Usar herramientas visuales para explicar los hallazgos.

Lo que no funciona:

Un plan rígido.

Una comunicación unidireccional.

Enfocarse en buscar culpables en lugar de riesgos.

Hi Francisco,

Thanks for raising such an important point. Principle 12 has become a central focus in my projects, especially when dealing with complex environments.

In my experience, one of the most effective practices to promote this principle has been engaging stakeholders early and consistently. I try to involve them not only in planning but also throughout the execution phase via regular feedback sessions, and informal check-ins. This has helped reduce resistance and build a sense of shared ownership.

Iterative approaches, like Agile, have been very helpful as well. Delivering change incrementally makes it easier for teams to adjust and for me to identify and address issues before they escalate.

On the flip side, what hasn’t worked so well is pushing change too quickly without giving teams time to process or adapt. Also, when communication has been too formal or top-down, I’ve noticed lower engagement and more passive resistance.

Overall, what’s worked best is creating a space where feedback is welcome, where people understand the “why” behind the change, and where small wins are recognized and celebrated.

Best,
Alison Rosales

Excellent points! I completely agree that strong, confident leadership, empathy, and transparency are crucial for fostering resilience during times of change.

I particularly appreciate your emphasis on:

Creating a supportive and transparent environment is key to helping everyone navigate change successfully. Thanks for sharing these valuable insights! Francisco.

Hello Francisco,

In our work at the Ford Cuautitlán plant, my team and I are responsible for tracking and securing all the parts needed to build the Mach-E. Because any delay can cause a costly line stoppage, “enabling change to achieve the envisioned future state” for us means building flexibility and responsiveness into every step of our supply chain and coordination processes.

What works for us:

Real-time tracking and escalation protocols We use live dashboards and direct communication channels with suppliers to detect and address potential delays before they impact production.

What hasn’t worked as well:
Late communication of changes: When change requests or supplier issues are reported too late, even the best contingency plans can fall short. We’ve learned to push for earlier visibility and proactive reporting.

Ultimately, fostering a culture where change is seen as a normal part of the job—not an exception—has been key for us in meeting our deadlines and avoiding line stoppages.

Benjamin I agree that clear and consistent communication is the most critical factor in managing change effectively.

As you pointed out, no one appreciates being surprised by changes. Proactive communication, understanding colleagues' concerns, and providing support are essential for a smooth transition. Building a confident relationship and motivating the team, even when faced with resistance, is key to success.

Thanks for emphasizing the importance of communication - it's truly the cornerstone of successful project management!
Francisco