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
  • Risk Assessment Matrix
  • Assessing Implementation Experience
  • Evaluating Impact
  • Escalation Process
  • Example Risk Levels and Actions

Was this helpful?

  1. Change Management (3C Change Model)
  2. Consider

Risk

Determining a change's risk level is essential for effective change management. It involves evaluating both the change's impact and the implementation team's experience. This dual assessment allows organisations to categorise changes according to their potential consequences and the likelihood of successful execution.

Risk Assessment Matrix

A risk assessment matrix can be utilised to facilitate this process. This matrix considers two main dimensions: Implementation Experience and Impact. Each change can be positioned within this framework to ascertain its risk level, as demonstrated below:

Implementation Experience

Impact:

Extensive / Widespread

Significant / Large

Moderate / Limited

Minor / Localized

No Experience

Critical

Critical

High

High

Previously Done With Issues

Critical

Critical

High

Medium

Limited Experience

High

High

Medium

Medium

Experienced With Multiple Successes

Medium

Medium

Low

Low

Routine

Medium

Low

Low

Low

Assessing Implementation Experience

  1. No Experience: Changes initiated by individuals or teams with no prior exposure to similar implementations pose the highest risk. This lack of familiarity can lead to critical failures, especially for changes that have widespread impacts.

  2. Previously Done With Issues: Previous attempts at implementing similar changes with issues also indicate a critical risk level. Although there is some experience, the past problems highlight potential pitfalls.

  3. Limited Experience: Teams with limited experience show a moderate to high-risk level. While they may be somewhat familiar with the process, uncertainties remain that could lead to challenges during implementation.

  4. Experienced With Multiple Successes: A track record of successful implementations significantly lowers the risk. Such teams are better equipped to handle challenges and anticipate potential issues, resulting in a medium to low risk.

  5. Routine: Changes that are routinely implemented carry the least risk. Established processes and familiarity within the team ensure smooth execution with low risk across various impact levels.

Evaluating Impact

The impact of the proposed change must also be assessed:

  • Extensive / Widespread: These changes affect the entire organisation and pose a critical risk due to the potential for large-scale disruption.

  • Significant / Large: Changes with significant internal implications are high-risk and require thorough evaluation and planning.

  • Moderate / Limited: Changes affecting specific departments or groups are of moderate risk, necessitating careful consideration.

  • Minor / Localized: These changes carry the lowest risk, impacting only a small department or role, allowing for more straightforward implementation processes.

Organisations can effectively identify the associated risk levels by systematically analysing the implementation experience and impact of a proposed change. This structured approach enables proactive risk management, ensuring appropriate resources and strategies are in place to facilitate successful change implementation while minimising potential disruptions.

Escalation Process

The escalation process is vital to effective risk management and change implementation within an organization. It involves a structured approach to addressing risks based on their severity and the necessary level of response. The escalation process ensures that appropriate action is taken promptly to mitigate potential organisational impacts.

Example Risk Levels and Actions

  1. Critical Risks:

    • Approval Level: Managed by the Managing Director.

    • Actions: This requires urgent and immediate attention, and an action plan must be developed immediately. The action plan must identify controls to reduce the likelihood and impact of the risk. The Managing Director (MD) should escalate the matter to the Board as appropriate, while the General Manager actively manages, monitors, and updates the MD.

  2. High Risks:

    • Approval Level: Handled by the General Manager.

    • Actions: Emphasis is placed on identifying and implementing controls promptly. The action plan should be developed promptly, with the Functional GM escalating to the MD as needed and monitoring the situation closely.

  3. Medium Risks:

    • Approval Level: Supervised by the Direct Manager.

    • Actions: The focus is on reviewing existing controls for effectiveness. Team members are expected to escalate issues to the General Manager and actively manage, monitor, and update them as necessary.

  4. Low Risks:

    • Approval Level: Automatically managed.

    • Actions: The focus remains on maintaining existing controls, with team members responsible for monitoring any changes in the risk environment.

Last updated 7 months ago

Was this helpful?