Idea Flow
Models
Idea Flow
  • Welcome!
    • Why Models?
    • Why Principles?
  • Agility & Transformations
    • Intro to Agile
      • What Does Agile Mean?
      • What Is An Agile Mindset?
    • Intro to Transformation
      • Why Transform?
      • How Is The Transformation Done?
      • Who Transforms?
      • Which Areas or Functions Transform?
      • How Long Does A Transformation Take?
  • Agile Transformation (Idea Model)
    • Intro to IDEA
      • Leadership-Strip (Tanzaku)
      • Managing The Change
      • Metrics
      • Coaching Plan
        • Coaching Assessment
    • Initial Exposure
      • Training & Coaching
      • Assessment
    • Develop Basics
      • Training & Coaching
      • Assessment
    • Evolve & Reflect
      • Training & Coaching
      • Assessment
    • Accelerate & Kaizen
      • Training & Coaching
      • Assessment
  • Delivery Approach (Flow Model)
    • Intro to Flow
      • Flow of Work
      • Dev Sec Ops
    • Conceptualise
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Commence
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Construct
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Confirm
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Complete
      • Process
      • Outputs
    • Check
      • Process
  • Scrum, Kanban & Other Agile Frameworks
    • Double-Loop Scrum
    • Kanban
  • 3D Work-Breakdown
    • Intro to Work Breakdown
    • Direction
    • Discovery
    • Delivery
    • Flow & 3D Work-Breakdown
  • Roles & Responsibilities
    • Overview
      • Trust Circles
      • Enterprise View
    • Core Team Roles
      • Scrum Master / Iteration Manager
      • Product Owner
      • Developer
      • Tester
      • Business Analyst
      • Infrastructure
    • Extended Team Roles
      • Product Manager
      • Test Lead
      • Tech Lead
      • Subject Matter Expert (SME)
      • UX/UI Designer
      • Infrastructure Lead
      • Project Manager
      • Solution Architect
      • Delivery Manager
      • Change Analyst
    • Trusted Advisor Roles
      • Project Sponsor
      • Stakeholders
  • Topics
    • Prioritisation
    • Estimation
      • Estimation Overview
      • Epic Estimation
      • Initiative Estimation
    • Planning
      • Sprint / Iteration Planning
      • Release Planning
      • Quarterly Planning
      • Problem Statement
    • Ceremonies
      • Showcase
      • Scrum of Scrums
      • Stand-up
      • Retrospective
      • Elicitation
      • Elaboration
      • Acceptance Criteria (AC)
    • Artefacts
      • Tech Spike
      • Definition of Done
      • Social Contract
      • Personas
      • Lean Canvas
      • User Stories
    • Toolkit
      • Success Sliders
      • ICaRuS Scoring
      • Accountability Cards
    • Quality
      • Test Strategy
      • Test Plan
      • Quality Attribute Definitions
      • Test Type Definitions
      • Regression Test Suite Definitions
      • Defect Definitions
      • Defect Severity
      • Defect Priority
      • Agile Testing Quadrants
      • Risk-Based Testing
    • Templates
      • 3rd Party Handover Template
      • Audit Logs
    • Data
      • Information Management
    • Kanban
  • Agile Testing (4Aces Model)
    • Intro to Agile Testing
      • Test Principles
        • Test Automation Principles
      • Test Artefacts
      • Test Triangle
      • Agile Testing Quadrant
    • Arrange
    • Act
    • Assert
    • Annihilate
  • INCIDENT MANAGEMENT (TRACeR MODEL)
    • Intro to TRACeR
      • What is Incident Management
      • Incident Management Workflow
    • Triage
    • Review
    • Action
    • Check
    • Resolve
  • Change Management (3C Change Model)
    • Intro to 3C Change
      • What is Change?
      • What is Change Management?
      • 7Rs of Change Management
      • Model States
      • Implementation
    • Capture
      • Priority
      • Experience
      • Impact
      • Change Types
    • Consider
      • Risk
    • Conduct
      • Plan
        • Change Activities Matrix
      • Perform
        • Rollback or Roll-forward
      • Prove
        • Change Result/Status
  • Faciliation
    • Intro to Faciliation
      • Agile Facilitation
      • Planning and Running a Workshop
    • Meetings
      • Meeting Prep
    • Workshops
      • Quarterly Planning Workshop
      • Integrated Culture Workshop
    • Games
      • Dice Game
      • Battleships
      • Kanban Pizza Game
    • Icebreakers
      • Check Your Personal Thinking Style
  • Agile Coaching (A6 Model)
    • Intro to Coaching
    • Agree
    • Address
    • Assess
    • Align
    • Assign
    • Account
  • Agile Leadership
    • Intro to Agile Leadership
  • Strategy
    • What is Strategy?
    • What is Vision?
    • What is a Mission?
    • What are Values and Drivers?
    • Intent-based Outcomes
    • MunroMaps
  • OKRA
    • OKRS + ACTIONS = OKRA
      • Implementation
      • Cycle Cadence
    • Objectives
      • OKRs
    • Key Results
    • Actions
  • Agile Software Architecture (C4 Model)
    • Intro to Architecture
      • Role of the Architect
      • SOLID Principles
      • DRY Principle
      • Single Source of Truth (SSOT)
    • Context
      • Examples
    • Container
      • Examples
    • Component
      • Examples
    • Code
      • Examples
    • Patterns
      • Back-end for Front-end (BFF)
      • Event-Driven Microservices
  • Portfolio Management (PMO Practice Model)
    • Intro to Portfolio Management
      • Practices & Flow
      • Objectives
      • Types
      • Maturity Assessment
      • Setting Up
        • Charter
    • Demand Practice
    • Risk Practice
    • Performance Practice
      • Cost of Delay (CoD)
      • Metrics
    • Report Practice
    • Delivery Practice
    • Asset Practice
    • Change Practice
  • RAFT
    • RAFT Framework
  • Tools
    • Jira
      • Best Practice
      • Printing Physical Cards
    • Confluence
      • Best Practice
      • Example Confluence Layout
    • Power BI
      • Power Query M
    • Miro
      • Best Practice
  • FAQs
    • Frequently Asked Questions
    • Glossary of Terms
  • Thanks & Contributors
    • Thanks
    • License
Powered by GitBook
On this page
  • 1. Plan
  • 2. Perform
  • 3. Prove
  • Remember
  • Impacted Areas
  • ADKAR Framework

Was this helpful?

  1. Change Management (3C Change Model)

Conduct

The Conduct phase of the change management process is critical for effectively executing planned changes. It comprises three key sub-stages: Plan, Perform, and Prove. Each sub-stage ensures the change is implemented smoothly and yields the desired outcomes.

1. Plan

This initial sub-stage focuses on generating the Minimum Viable Change (MVC), which represents the smallest applicable adjustment necessary for the desired outcome. This involves:

  • Align the resources, time, and calendar for the change while being mindful of any interdependencies that may affect the implementation.

  • Developing a comprehensive plan that outlines the steps needed for a controlled and successful execution.

2. Perform

The Perform sub-stage involves enabling the change according to the established plan. This requires:

  • Ensuring that all actions are carried out in a controlled manner to minimise disruptions and ensure a smooth transition.

  • Monitoring the implementation process closely to identify any issues or challenges during execution.

3. Prove

Once the change has been implemented, the final sub-stage, Prove, focuses on evaluating the success of the change. This entails:

  • Determining whether the change met its objectives and identifying any further plans or adjustments needed to enhance outcomes.

  • Documenting lessons learned throughout the process to inform future change initiatives and improve practices.

Remember

  • Generate from options the smallest applicable change, MVC.

  • Align the resources, time and calendar for changes (and be aware of interdependencies).

  • Enable the change according to plan and in a controlled, successful manner.

  • Determine if the change was successful, if further plans are needed, and identify lessons learned.

Impacted Areas

  • People - who are affected?

  • Process - which processes are impacted?

  • Technology - What are the technology impacts?

  • Culture - How will this affect culture?

ADKAR Framework

Utilizing ADKAR in the Conduct Process

The ADKAR model, which stands for Awareness, Desire, Knowledge, Ability, and Reinforcement, is a practical framework for guiding the Conduct phase of change management. By applying ADKAR, organisations can ensure that changes are implemented effectively and embraced by the people involved. Here’s how each element of ADKAR contributes to a successful Conduct process:

  1. Awareness: Before implementing a change, all stakeholders must understand the reasons behind the change. During the Conduct phase, ensuring everyone is aware of the change and its benefits helps mitigate resistance. Communicating the purpose and anticipated outcomes fosters a shared understanding among team members (Hiatt, 2006).

  2. Desire: This component focuses on fostering a desire among stakeholders to participate in the change. By engaging employees and addressing their concerns or motivations, leaders can enhance commitment to the change initiative. This can be achieved through open forums, feedback sessions, and recognition of contributions, which help to cultivate a positive attitude toward the change (Kotter, 1996).

  3. Knowledge: Providing comprehensive training and resources is essential during the Conduct phase. Stakeholders should have the necessary skills and expertise to implement the change effectively. This can involve formal training sessions, workshops, or instructional materials that outline new processes and systems (Prosci, 2021).

  4. Ability: Beyond knowledge, individuals need to be empowered to act on that knowledge. This involves creating an environment where employees feel confident and supported in executing the change. Regular check-ins and support systems, such as mentorship or peer support groups, can help ensure team members can apply their training in real-world scenarios (ADKAR Model, n.d.).

  5. Reinforcement: Finally, reinforcing the change through recognition and rewards is critical for sustaining momentum. Acknowledging the efforts and successes of individuals and teams during the Conduct phase solidifies the change and encourages ongoing commitment. This can include celebrating milestones or offering incentives for achieving specific goals related to the change (Hiatt, 2006).

By integrating the ADKAR model into the Conduct phase, organisations can better navigate the complexities of change, ultimately leading to more successful outcomes and a more engaged workforce.

References

  • Hiatt, J. M. (2006). ADKAR: A Model for Change in Business, Government, and Our Community. Prosci.

  • Kotter, J. P. (1996). Leading Change. Harvard Business Review Press.

Last updated 7 months ago

Was this helpful?

Prosci. (2021). The ADKAR Model: A Goal-Oriented Change Management Model. Retrieved from .

ADKAR Model. (n.d.). Retrieved from .

Prosci
ADKAR Model Overview