STfA
Persona learning path

Start here:
Enterprise Architect

Focus on governance, portfolio steering, and structural coherence across multiple domains.

Level 1: Foundations

0/6 read

After this level you can describe governance, goal systems, and steering limits using core systems vocabulary.

Requisite Variety

Ashby's Law of Requisite Variety says that only variety can absorb variety. To control a complex system, the control system needs at least as many response options as the system it is trying to govern.

Why here: Explains why central control must fail against complex landscapes.

Policy Resistance

Complex systems often contain a built-in defensive force that counters and blocks even well-intended solution attempts.

Why here: Shows why governance mandates get neutralized by the system.

Goodhart's Law

When a metric becomes a target, it loses explanatory value because the system starts optimizing for the proxy instead of the underlying outcome.

Why here: Required knowledge for any KPI system at portfolio level.

Purpose and Function

Every system has an objective purpose or function that can be read from its actual behavior, not from its official slogan.

Why here: Separates declared goals from actual system behavior — the basis of any governance analysis.

Open and Closed Systems

Closed systems decouple from their environment, while open systems exist in constant exchange of energy and information.

Why here: Clarifies which external influences your organization can control and which it cannot.

Top-Down vs. Bottom-Up Architecture

Navigating between hard centralized top-down architecture guidelines and the local bottom-up evolution of teams.

Why here: The tension field in which all architecture governance operates.

Level 2: Practitioner

0/6 read

After this level you spot organization-wide patterns such as resource conflicts and goal erosion early.

Governance Thawing

Rigid top-down governance cannot keep up with the speed of decentralized development, leading to chaos or standstill.

Why here: The reference symptom of this path: governance that gradually loses its effect.

Tragedy of the Commons

Locally reasonable use of a shared resource can overload the whole system when access rules, cost transparency, and responsibility are missing.

Why here: The pattern behind overloaded platforms and shared resources.

Success to the Successful

Competition for limited resources can further favor teams with a slight head start while others receive fewer development opportunities despite their potential.

Why here: Explains how budget allocation cements winning teams and skews portfolios.

Drifting Goals

Teams gradually adapt their standards to insufficient system behavior instead of improving the causes of that behavior.

Why here: The pattern behind gradually eroding standards at the organizational level.

Viable System Model

A masterpiece of organizational cybernetics that describes the mathematical and fractal structure every software company needs in order to stay alive under intense market pressure.

Why here: The reference model for systematically finding steering gaps in the organization.

Boundary Critique

A method for exposing deliberate blind spots by questioning what, and who, was actively excluded from an architecture decision.

Why here: Questions who is considered in architecture decisions — and who is missing.

Level 3: Strategic depth

0/5 read

After this level you design incentives, cadences, and couplings so strategy and architecture stay aligned.

Governance Feedback Cadence

The orchestration of the company's heartbeat by adjusting how often and how quickly IT leadership reviews architectural signals and reacts.

Why here: Replaces static control with learning steering cycles.

Incentive Redesign

The destruction of the cobra effect in IT by stopping the reward of failure-producing behavior and aligning incentives with system health instead.

Why here: Acts on the root of most organizational patterns: the incentives.

Structural Coupling Adjustment

The surgical separation or reconnection of teams and systems to dissolve tight coupling and radically increase the innovation speed of individual squads.

Why here: Adjusts the coupling between units — the core tool for portfolio coherence.

Knowledge Graph Tooling

Graph-based knowledge bases that connect code, architecture decisions, and ownership in one searchable network.

Why here: Makes relationships between systems, decisions, and teams queryable across the organization.

Dependency Graph Analysis

Tools that extract dependency graphs from real systems and show which couplings make changes risky.

Why here: Provides the data basis for decoupling decisions at landscape level.