Index

PF2

Introduction

Introduction

Companies

Overview

Training

Certification Courses
Focused Workshops
Options

Pragmatic Publishing Platform

Overview
Design

Frameworks

Frameworks

Overview

X Frameworks
Applicability

Available Now

PEFF Enterprise Fundamentals
Why Use It
POET Enterprise Transformation
Why Use It
Operating Model
PEAF Enterprise Architecture
Why Use It
Logical Model
PTMC Transformation Maturity
Why Use It
Logical Model

PEFF

Head

Language

Language

Basics

I Didnt Mean What You Heard
What is a System
What is an Enterprise
What is Transformation

Ontologies

Ontologies

Structural

MAGIC

Transformational

MAGMA

Enterprise

DOTS

Adoption

Adoption
Overview

Measures

PTMC

Levels
Tools
Step 0

Measures PTMC

Level 0

Motivation

Paradigm Shift
WE Deming
70 of All Change Initiatives Fail
Enterprise Viability
Sage Words
Basic Premise
The Transformation of Transformation
What Your Transformation Capability Looks Like
Building the Machine that Makes the Machine
Culture

Demotivation

Psychology
Dont Throw The Baby Out With The Bathwater
Domain Blindness
The Red Pill
Timing Paradox
Management Workers Paradox
Process Paradox
Unconscious Degradation
False Accomplishment
Oversimplification
Reality Avoidance
Its Just Not Sexy
The Drowning Children
Step 1

Measures PTMC

Level 1
Step 2
Level 2
Step 3
Level 3

POET

Head

Adoption

Adoption
Step 4
Step 5
Step 6

Methods

Methods

Phases

Resource Utilisation

Solutioning

A Pragmatic Approach
Pattern

Disciplines

Overview
Capability Model

Governance and Lobbying

Technical Debt vs Transformation Debt

Transformation Debt

Investment Profiles

Artefacts

Artefacts

Ontology

Basics

Mapping to Phases

Detail

Structural and Transformational Zachman
Models

Meta models

Hybrid

Items

Architecture and Engineering

Architect Horizontally Engineer Vertically

Culture

Culture

Organisation Structure

Management
Workers

Architects and Engineers

Comparison

PEAF

Head

Adoption

Adoption
Step 4
Risks
Step 5
Step 6

Methods

Methods

Phases

Strategising

Capability Modelling

With DOTS

Roadmapping

Create update Portfolio Model

Artefacts

Artefacts

Ontology

Meta models

Models

Relationships

Guidance

Guidance

Principles

Types

WHAT We Produce
HOW We Do Transformation

PF2

Appendix

Appendix

Background

The Author
       
Click a Thumbnail to read the component. Hold down Ctrl while clicking to expand the image

 

Intro - An Introduction to Pragmatics Frameworks












PEFF>Adoption>Step-0>Motivation>Culture ◄◄◄           .           ►►► PEFF>Adoption>Step-0>Demotivation>Dont-Throw-The-Baby-Out-With-The-Bathwater

This model explains why people frequently resist change even when the proposed change appears rational, beneficial or necessary. Its central proposition is that people do not generally resist change simply because they are stubborn, irrational or unwilling to improve. Instead, they resist the perceived threats that change creates. These threats may relate to safety, predictability, mental energy, loss, identity, competence, belonging, influence or social status.

 ...to read more, please Login or Register

PEFF>Adoption>Step-0>Motivation>Culture ◄◄◄         Enroll to Self Study Now!         ►►► PEFF>Adoption>Step-0>Demotivation>Dont-Throw-The-Baby-Out-With-The-Bathwater

Keypoint

Adopt this component by...

People do not resist change. They resist the threat that change represents to their safety, energy, value, identity and belonging

C-Suite: Create the organisational conditions in which change is psychologically credible, safe and worthwhile.

Management: Translate those conditions into the day-to-day human experience of change.

EA Project Team: Design and enable the transition through which people can understand, influence, learn, adopt and sustain the change.

Questions to ponder...

What aspects of the proposed change could reduce people's sense of predictability or control, and what could we do to make the purpose, journey, consequences and opportunities for influence clearer?

What additional mental effort, learning or workload will the change require, and what existing work, complexity or competing demands could we remove to create sufficient capacity for adoption?

What might different people or groups believe they will lose—including familiar ways of working, autonomy, expertise, influence, status, relationships or security—and which of these losses are real rather than merely perceived?

Whose identity, competence, confidence or professional value might be threatened by the change, and how could we recognise existing expertise while enabling people to become confident and competent in the target state?

How might the change affect people's relationships, belonging, influence, status or place within the enterprise, and what should we do to preserve valuable connections and create new ones?























© 2008-2021 Pragmatic 365 Ltd         A Non-Profit dedicated to improving Transformation, and the lives of people that work in Transformation.