How We Think About How We Work

Copyright (c) 2016 Michael Herman (Alberta, Canada) – Creative Commons Attribution-ShareAlike 4.0 International Public License
https://creativecommons.org/licenses/by-sa/4.0/legalcode

How do we think about how we work? We rely on a few simple processes. Here is a list:

  • Progressive Improvement & Learning Process (PILP)
  • Continuous Transformation Process (CTP)
  • Deliverable Review: Initiate, Create, Review, Validate & Approve Process (ICRVA Process – “I crave a” Process)
  • Purpose: Awareness, Knowledge, Understanding, and Wisdom

Many thanks go to Alison Williams for helping me to clarify the Continuous Transformation Process (CTP).

Michael Herman (Toronto)

Progressive Improvement through Continuous Transformation

Progressive Improvement thru Continuous Transformation 1-0-1

Progressive Improvement & Learning Process (PILP)

Progressive Improvement A 1-0-1

Progressive Improvement B 1-0-1

Continuous Transformation Process (CTP)

Parallelspace Continuous Transformation 2-0-1

Deliverable Review

Initiate, Create, Review, Validate & Approve (ICRVA) Process (“I crave a” Process)

Parallelspace ICRVA v12-0-2

Parallelspace ICRVA v12-0-2 Complete

The roles in the ICRVA process are based on the RACI matrix of responsibilities.

Content Purpose

– when writing a whitepaper or creating a new presentation

  1. Awareness (An Overview of what is being described (Information))
  2. Knowledge (The “What” of what is being described)
  3. Understanding (The “How” of what is being described)
  4. Wisdom (Deep Knowledge and Understanding acquired through Experience)

By wisdom a house is built, and by understanding it is established; by knowledge the rooms are filled with all precious and pleasant riches. A wise man is full of strength, and a man of knowledge enhances his might, for by wise guidance you can wage your war, and in abundance of counselors there is victory. Wisdom is too high for a fool; in the gate he does not open his mouth. (Proverbs 24:3-7)

Intended Audience Statement (Example)

The intended audience for this tutorial about Structured Credentials is a broad range of professionals interested in furthering the application of Verifiable Credentials technology for use in software apps, agents, and services. The primary audience includes software architects, application developers, and user experience (UX) specialists; as well as people involved in a broad range of standards efforts related to decentralized identity, verifiable credentials, and secure storage.

Michael Herman’s Hierarchies

  • Awareness – Knowledge – Understanding – Wisdom
  • Dream – Desire – Want – Need
  • Sensing – Learning – Training – Experiencing
  • Keywords – (Controlled) Vocabulary – Glossary – Dictionary – Taxonomy – Ontology

Michaels Hierarchies

Product Management: 3 Prioritization Levels

  1. Need to have
  2. Nice to have
  3. *Neat* to have

Scalability Levels

hyper-scalability-1-0-1

Best regards,
Michael Herman (Toronto)
Parallelspace Corporation
mwherman@parallelspace.net

4 Comments

Filed under Architecture Reference Models, continuous transformation, Crossing the EA Charm, Definitions, How do we think, Parallelspace TDM, Process, Progressive Enterprise Architecture Map (PEAM)