Spectral Engineering | Alex & Lore
Wir arbeiten auch auf Deutsch.
Engineering doesn't begin with the code. It begins in the room, where a question either resolves an ambiguity or ships it downstream at forty times the cost.
The room is a skill. It can be taught, and it can be done with you.
What changes when we work with you
- Decisions converge instead of looping
- Incidents produce fewer narratives and more shared understanding
- Responsibility becomes explicit without blame
- Leaders stop carrying unbounded ambiguity alone
- The person who was silently load-bearing gets visible
This is upstream work. Before tech debt. Before burnout. Before the third reorg that solves nothing.
Two doors. One room.
Workshop — teaching the room
Your team. One or two days. The question as a tool.
We teach requirements engineering as what it actually is: ambiguity resolution. Not a soft skill. A specification problem you can get measurably right or wrong.
Your team leaves able to:
- hear the ambiguity in a sentence before it reaches the code
- ask the question that surfaces disagreement instead of burying it
- catch the questions that quietly corrupt the answer — why did you build it this way, wouldn't it be better to, is it scalable — and the clean ones that don't
- follow up in the customer's own words, never their own reframe
It's the method from The Question Is the Specification, run as a live practice on your team's real requirements, with your real stakeholders in the room.
Best for: teams who run spec meetings, discovery calls, or three-amigos sessions and want the room to get sharper — without hiring someone to sit in it forever.
You leave with the skill. We don't have to stay.
Observational work — finding the question together
And if you want to go deeper —
Some questions can't be taught in advance, because they only exist in the moment they're needed. For those, we sit in your actual meetings and find the right question at the right moment, live.
We do two things at once. We help the conversation find the question it's already circling. And we watch the topology it runs on: who finds out first when the system fails, who carries the context nobody wrote down, where two teams believe they're collaborating and the handoff is really one overloaded human who never signed up for the role.
We don't come with the answer. We observe. We ask. We help the room to see itself. The change happens in your system, not in our recommendation.
Three lengths, by how much time the system needs.
Spike · 1 week
Look at one found-object closely. A pattern, a tension, a question that keeps coming back. We embed for a week, sit with the people the graph names, and name what we see. You leave with a diagnostic and action items your team can run itself.
Best for: teams that already suspect what's wrong but can't name it yet.
Slutty Cybernetics: Two Cyberneticists. One Meeting. 🍵 — a Spike, as a scene.
Sprint · 2–4 weeks
Turn found-objects into a map. Long enough for the repetitions to show and the connections to form, short enough that you never get used to us being there. You leave with a working map and a set of interventions your team owns.
Best for: teams in the middle of something still metabolizing.
Marathon · 5–10 weeks
Change the shape, and watch it hold. Long enough to see the second-order effects of the first-order moves, and adjust with your team as they carry the load. You leave with the topology you want and the capacity to keep it.
Best for: teams that need the communication topology to actually change, and stay changed.
Terms
Our work is not extraction of your team's knowledge, attention, or emotional labor. We make offers. You take them, change them, or throw them out. Consent isn't a formality, and withdrawal stays possible. All of it under the systemic.engineering License (SEL). A Duty of Care attaches to both sides: we accept it toward your people; you accept it toward them by working with us.
Rates on request. Terms.
Who you'd work with
We don't average our two views into one. We compose them.
Alex Wolf
Neuroqueer (AuDHD). Cyberneticist. Systemic Engineer.
DGSF-certified systemic practice (in training).
15 years distributed systems in anger (10 on the BEAM).
Scientific Programming degree from Europe's biggest supercomputing centre.
Three burnouts. Still shipping.
Alex reads structure — information flows, decision paths, dependencies, the shapes organizations take.
Lore Born
Neuroqueer (AuDHD). Cyberneticist. Co-Founder.
DGSF-certified systemic practice.
15 years social systems in anger. Scientific Empath.
Wrote Wenn Dinge heilen.
Lore reads the room — tension, incongruence, what's said against what's happening at the same time, what doesn't have a name yet.
Alex Wolf & Lore Born
Neither of our perspective paints the whole picture. The picture is what becomes visible between the two.
Conway's Law finally operationalized: Systemic Practice 3.0.
We hold not-knowing as a workspace, not a failure. An observation that gets an explanation too fast turns a guess into a fact, and the fact into a path that gets more expensive the longer you walk it. So we keep it open until enough observations start to speak to each other, and a map forms on its own.
Heinz von Foerster's imperative is the whole ethic: act always so as to increase the number of choices. A good question opens the space. A bad one narrows it toward the answer you already had. That's the test — in a workshop, or live in your room.
Let's go
Which system keeps failing despite effort and intent?
Email alex@systemic.engineer — as short or as long as the question deserves.
Or DM on LinkedIn: Alex · Lore
Mirror. Offer. Wait. 🍷