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




















POET>Artefacts>Ontology>Basics>Mapping-to-Phases ◄◄◄           .           ►►► POET>Artefacts>Ontology>Detail>Models

Here we see how the three fundamental ontologies from POET are woven together.

On the right we show the Structural ontology - MAGIC. On the left the Transformational ontology - MAGMA. Down the middle the Ontology for the fundamental parts of all Enterprises - DOTS.

Looking at the centre, it is the Transformation Capability we are interested in but we set that Capability in the context of the Direction Capability above which drives it and the Operations Capability below which it “delivers” into. (It should be noted however, that the Transformation Capability could also “deliver” into the Direction, Support or Transformation Capabilities, but only the Operation Capability is shown for clarity)

 ...to read more, please Login or Register

POET>Artefacts>Ontology>Basics>Mapping-to-Phases ◄◄◄         Enroll to Self Study Now!         ►►► POET>Artefacts>Ontology>Detail>Models

Keypoint

Adopt this component by...

This is the complete map of information required for Transformation to be executed in an Effective, Efficient, Agile and Durable way.

Management: Map the Artefacts of Transformation to MAGIC and MAGMA over the seven layers of Transformation, to determine where the gaps and overlaps are.

Questions to ponder...

In what way does your Enterprise consider Transformational as well as Structural models at all levels?

What ontologies and meta-models are you using?

How do they map to, and fit into, the POET Ontology?

Are they any gaps or overlaps?

If there are gaps and or overlaps, is it useful to know that?

What will you do to fill the gaps and remove the overlaps?

Do you agree this ontology is like Zachman on steroids?















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