Alex Wolf 🌈
You're here because the world stopped making sense.
The org you work in is doing things it never intended to do —
just to keep functioning.
"But our values", we say.
Yet reality applies pressure anyway.
systemic.engineering treats collaboration as an optimization problem.
And language-as-infrastructure.
Not coaching.
Not motivation.
Embodied site reliability engineering for human systems.
New to this framing?
systemic.engineering in a nutshell.
Hi, I'm Alex.
(they/them)
I optimize for clarity.
I provide Regulation-as-a-Service.
I'm a SRE for human systems under load.
(Site Regulation Engineering.)
I co-construct, model, and stabilize in
complex human systems.
(25+ years under load.)
Most failures are not technical.
They are caused by:
- misunderstood requirements,
- deferred and unowned decisions,
- communication that collapses under load.
I surface ambiguity and mediate conflict
before
it hardens into structure.
After this work, teams usually notice:
- decisions converge instead of looping,
- incidents produce fewer narratives and more agreement,
- responsibility becomes explicit (without blame),
- leaders stop carrying unbounded ambiguity alone,
- incidents stop turning into political events.
Offering
Not coaching.
Not motivation.
Embodied engineering for human systems under load.
I work directly with leadership and teams,
observing real interactions and
intervening at decision points.
I never decide for you.
I help you hold shared context
and then you decide.
Typical engagements run 4–12 weeks.
(Focus: One live system under real load.)
1. (Re-)Direction
- We stabilize acute problems,
- Map out a snapshot of known constraints, interests and structure,
- Document next steps,
- And a clear direction and statement.
2. Culture-as-Structure
- Culture-as-structure bootcamps
- Individualized workshop chains
- Language-as-infrastructure
3. System Coherence
- Make unknown constraints known
- Integrate divergent mental models
- Surface ambiguity before it hardens into structure
4. Socio-Technical Architecture
- Domain-Driven Design (DDD)
- Conway-aware system design
- Architecture as organizational memory
5. Coherence Under Load
- Incident and outage dynamics
- Regulated decision-making under load
- Load distribution instead of load dumping
This is upstream work.
Before tech debt.
Before burnout.
Before failure modes repeat:
- three senior engineers disagree and no one can tell who’s right,
- incidents recur but every postmortem tells a different story,
- delivery slows, but metrics say everything is ‘green’,
- leaders feel like they’re carrying reality alone.
Which situation keeps repeating despite effort and intent?
Email me 5–10 lines describing it.
(Terms.)
Experience
Systemic Engineer — Freelance
Crafting systems where humans and tech can function under real conditions.
Systemic practitioner in high-cost family systems (supervised).
Team Lead / Principal Engineer — 7Mind
- Led backend and architecture for systems used by millions
- Introduced DDD-inspired architecture
- Reduced lead times from months to weeks
- Significantly reduced defect rates, code volume, and recurring conflicts
- Built a psychologically safe, load-bearing engineering culture
Senior / Technical Roles — BetterDoc, grandcentrix
- Health tech, platform engineering, distributed systems
- Tech Leadership, mediation, architecture, backend engineering
- Recurring pattern: technology wasn’t the bottleneck — alignment was
Lived Experience
- Deescalation, mediation, and maintenance in complex family systems
- Community building, moderation, and leadership (100+ members)
- Autonomous self-regulation and mindfulness practice
(I get calmer when people freak out] - Neuroqueer and trauma-aware leadership in human systems
Values
Bodies > Algorithms
If a model lies, I won’t protect it.
Coherence > Speed
Fast decisions that fragment systems are expensive.
Integration > Compensation
Unintegrated reality always gets encoded somewhere.
Regulation > Authority
Calm, not control, keeps systems stable.
Engineering > Narrative
Stories matter. And systems decide what survives.
If this resonates, you’re likely already carrying load.
This work can be done deliberately.
systemic.engineering is how I help teams and leaders
co-hold coherence under load.
Email me a situation that keeps repeating.
(5-10 lines is enough.)
Find my terms here.