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

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


































PF2>Appendix>Section ◄◄◄           .           ►►►

Who Created The Pragmatic Family of Frameworks (PF2)?

A simple man.

My career began at the age of 16 in 1978 as an Electrical and Electronic Apprentice with Marconi Radar Systems (Blackbird Road, Leicester, UK) At that time I was really into electronics and had been playing with little circuits for a few years. It was really exciting. I spent my time between college and “The Factory” where I got the chance to work in many different departments. It was really exciting. Around 1980 I ended up in a Department (New Parks, Leicester UK) called TEPIGEN (TElevision PIcture GENerator) who had built the visual system for a ship simulator. Six million Pounds of custom built hardware (that had less processing power than the CPU in the phone that’s in your pocket) consisting mainly of four racks of “Picture Processors” (Motorola 68000s) driven by a PDP11. It was really exciting. The output was on three channels each delivering 40 degrees field of view which drove three large Barco projectors. Interestingly at one point there were black speckles that kept appearing on the displays, moving about in random patterns and appearing and disappearing in the same apparently random fashion. After months of software and hardware investigation the problem was identified. It was a test Radar across the apron from where our Portacabins where located that was spraying us periodically with microwaves! It was really exciting.

 ...to read more, please Login or Register

PF2>Appendix>Section ◄◄◄         Enroll to Self Study Now!         ►►►

Keypoint

Adopt this component by...

Use people for the type of person they are, not the type of person you want them to be. If we were all the same, nothing would ever get done.

Questions to ponder...

What are the MBTI, DISC and Belbin profiles of the people in your Enterprise?

Do they all suit their roles?

Have you ever found someone to be a “difficult person” or a “loose cannon”?

If so, did their MBTI/DISC/Belbin profile taken into account?

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