STfA
Persona learning path

Start here:
Tech Lead

Focus on team dynamics, decision-making, and the connection between delivery, learning, and responsibility.

Level 1: Foundations

0/6 read

After this level you understand how communication structures, mental models, and boundaries shape your team's behavior.

Conway's Law

Organizations that design systems are forced to create designs that mirror the communication structures of those organizations.

Why here: The single most important relationship for tech leads: team structure becomes system structure.

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: Explains why velocity targets and bug quotas deform your team's behavior.

Mental Models

Mental models are deeply rooted assumptions that determine which system signals we notice at all and how we make decisions.

Why here: Team conflicts are often model conflicts — seeing that changes how you facilitate.

Interdependence

Elements in a system depend on one another; you cannot change one part in isolation without influencing the whole.

Why here: Shows why local team optimization can degrade the overall system.

System Boundaries

System boundaries are purely mental lines that we draw to separate what belongs to our architecture from what supposedly lies outside our control.

Why here: Unclear boundaries are the most common root of friction between teams.

Resilience

Resilience is the ability of a system not only to survive destructive shocks from outside, but to recover while preserving its structure.

Why here: Shifts the focus from 'no failures' to 'fast recovery' — for teams as well.

Level 2: Practitioner

0/6 read

After this level you recognize destructive team dynamics as system patterns instead of character flaws.

Communication Breakdowns

Information silos and misaligned mental models lead to architectural drift and friction across the team.

Why here: The reference symptom of this path: communication breakdown as a system phenomenon.

Accidental Adversaries

Teams that actually want to collaborate drive each other into ruin through selfish local optimizations.

Why here: Explains how teams that want to cooperate end up blocking each other unintentionally.

Shifting the Burden

Teams repeatedly relieve symptoms in the short term and gradually lose the motivation and capability to address the structural architecture problem.

Why here: Shows why hero fixes permanently crowd out the structural solution.

Escalation

Two parties respond to each other with increasingly strong measures because each side wants to outdo or protect itself from the other.

Why here: The pattern behind escalating team conflicts and tooling wars.

Stakeholder Mapping

A tool for locating organizational power and potential veto power around architecture decisions.

Why here: Reveals whose interests actually steer the team system.

Social Network Analysis

SNA exposes the real invisible architecture of organizational cliques by measuring who actually talks to whom and who remains isolated.

Why here: Shows the real communication paths — often different from what the org chart claims.

Level 3: Strategic depth

0/5 read

After this level you deliberately change decision paths and accountability structures instead of moderating symptoms.

Decision Rights Clarification

The drastic removal of ambiguity about who in architecture may recommend, veto, or ultimately press the buy button.

Why here: The structural answer to backchannel decisions and role ambiguity.

Servant Leadership in System Context

The reinvention of leadership from controller to system architect, with leaders focused on removing the physical blockers around teams instead of managing budgets alone.

Why here: Anchors leadership as system design instead of case-by-case heroics.

Moving from Blame to Accountability

A cultural intervention that abolishes "human error" as an excuse for production outages and holds flawed system design accountable instead.

Why here: Changes the failure culture structurally — a prerequisite for honest diagnoses.

Collaboration Whiteboard Tooling

Digital whiteboards for distributed teams: they enable collaborative architecture design and event storming across remote boundaries.

Why here: The carrier medium for modeling together with your team.

Decision Log Tooling

Machine-readable architecture decision records: they document why a trade-off was chosen and keep decisions traceable years later.

Why here: Captures decisions and their reasons — against forgetting and relitigating.