11:05

There’s a bit of a problem of how to communicate these problems. Even if there are multiple good answers it should be easier to identify what answers are good or bad

Processes that deal with side effects or non value delivering sub processes

dealing with things that could go wrong

or get in the way of delivering value

A concept is pre architecture

Both convert function to form

Needs > Solution neutral function > Concept > Architecture

1

Concept bridges solution neutral to solution specific

Something fundamental about the subject object verb triple in language

Concepts can be different degrees of specialization / generalization

I wonder how this maps to Concept-space

Why make an OPM model?

Visualization

Low cost simulation

Discovering unknowns

Drawing the system boundary can be illustrative

It would be funny if someone in Zoom wrote a cape because it would sometimes come in and out of view since we all have the SDM backgrounds

Concept operations converts concept to form

Go from level 0 to level 1 to level 2

Use level 2 to refine level 1