The four perspectives

The level you work at is a perspective. It decides what is in focus, what falls into the background, and what the system is actually for. Like choosing a perspective in a photograph.

Workflow

Lens. One-point perspective. In focus. A single painful workflow. You build. An MVP system for that one thing.

Everything in the frame leads to a single vanishing point. The painful workflow is that point. Nothing else is in focus yet, and that is the whole reason the work moves quickly.

Personal OS

Lens. Overlapping perspective. In focus. An individual's full stack of work. You build. A working operating system for their role.

Subjects layer to create depth. An individual's work is never one workflow, it is a stack of habits, responsibilities, tools, and routines that overlap. What's in front affects what is behind it.

Team integration

Lens. Multi-point perspective. In focus. The individual plus the team they live in. You build. Personal OS plus the connective tissue to the team.

Two vanishing points instead of one. The individual has their own way of working. The team has its conventions. The system lives at the corner where both directions meet.

Team or org

Lens. Atmospheric perspective. In focus. The shape of how a function operates. You build. An operating model for the function.

You design for the contour of the work, not individual keystrokes. The detail blurs by design, and that is correct. From this far away, you see the shape.

A warning: forced perspective

The trick where someone "holds up" the leaning tower with a fingertip. It only works from one angle. A workshop sold as "transformation" when only one workflow is in scope. A small fix dressed up as enterprise change. Always work in the perspective that matches the actual scope. Force the angle and the illusion breaks.