Optimiser vs Learner Organisations
Two organisation-design archetypes for the agentic era — the Optimiser (engineers pull automatically-queued work from feedback/monitoring while agents change any part of the enterprise) and the Learner (product/technical pairs situate with users and curate a highly filtered work stream) — distinguished only by whether data/measurement or humanist curation owns the inbound work stream.
Also known as: Optimiser, An Optimiser, Learner, A Learner, optimiser or a learner, is your org an optimiser or a learner
Part of: Sociotechnical Architecture
Documents (1)
- Notes from FOSE Europe Giles Edwards-Alexander · 2026-07-07 source ↗ Reader 🖥️
Five months into the agentic era the value of agentic engineering is now settled ('the evidence is in'), so the live frontier of the debate has moved from the tools themselves to the socio-organisational questions they raise — how to design your organisation (Optimiser vs Learner), where engineering rigour and human judgement now live, and how to coordinate agentic work across teams and enterprises — none of which is yet resolved.
Propositions touching this concept (2)
By publication month, oldest first (extraction month when no publication date is known).
2026-07
- explicitOrganisations face a real design choice between two archetypes — an Optimiser and a Learner — that differ only in who owns the stream of inbound work: data and measurement, or conspicuously humanist curation.
- explicitThe Optimiser model risks a software equivalent of 'grey goo' — unbounded agentic change — which can be mitigated by a continuously evolving central, shared harness of architecture guidance and engineering rigour.
Tensions
Should the harness/platform-building function be centralised, or emerge per-team?
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
- Notes from FOSE Europe (Giles Edwards-Alexander): Dedicated harness-engineering teams are a mistake; the friction of each team building its own harness is generative and creative.
- Looking back at the Future of Software Engineering unconference (Bartosz Ocytko): A centralised platform / 'software factory' with tight, low-friction constraints should absorb operational concerns and guide both citizen developers and their agents from the first prompt.
Assessment: A precise split about the organisational form of the scaffolding, not its existence: both want shared architecture guidance, but Edwards-Alexander wants the building capability distributed (friction as feature) while Ocytko wants it concentrated in a platform (constraint as feature). Each concedes the other's pole — Edwards-Alexander keeps a central harness; Ocytko warns against over-constraining — which is why this is a live, unresolved tension rather than a clean contradiction.
Is the value question genuinely settled by evidence, or does uncertainty and sampling bias still dominate?
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
- Notes from FOSE Europe (Giles Edwards-Alexander): The evidence is in; the value is clearly here and here to stay.
- Finding Comfort in the Uncertainty (Annie Vella): Nobody has it figured out; there is more uncertainty than certainty, and the shared set of questions is the real outcome.
- What Survived Contact (Sam Ruby): 'Rigor migrates' is about as settled as this young field gets, but the room is a non-random, incumbent-tilted sample, and the doubt is currently better evidenced than the hope.
Assessment: The single sharpest divergence, and it sits directly under the headline whether-to-how convergence: they narrate the same shift but disagree on what it establishes. Edwards-Alexander and Herlein read the room's confidence as evidence; Vella and Ruby read the same room as a self-selected in-group. Ruby has the better of it methodologically — he is the only one to interrogate the sample and to notice the evidence is asymmetric (upside anecdotal, downside studied), which is uncomfortable precisely because the cohort's confidence is built on the weaker side.
If code is no longer the bottleneck, what is the new binding constraint?
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
- Finding Comfort in the Uncertainty (Annie Vella): Decision capacity and downstream absorption — 'humanity is not ready for this much software'; decision fatigue is becoming the real bottleneck.
- Notes from FOSE Europe (Giles Edwards-Alexander): Learning is the constraint now, not engineering delivery.
- We've Stopped Arguing About Whether AI Changes Software (Greg Herlein): Knowledge — the tacit, unwritten 'why' behind past decisions — is the scarce resource, not code.
Assessment: They agree code/delivery has ceased to be the constraint but name three different successors, with different investment implications — expand decision-making capacity (Vella), optimise for learning (Edwards-Alexander), or capture tacit knowledge (Herlein). These are complementary in principle but rivalrous for attention and budget; the disagreement matters because each implies a different 'first thing to fix.'
Will the classic fundamentals (especially DDD / domain modelling) actually deliver this time — is the revival evidenced or merely asserted?
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
- Notes from FOSE Europe (Giles Edwards-Alexander): Skeptical: domain modelling kept being proposed, but it is not a new idea and never became the standard before — why would it suddenly work now?
- Software Design in the Agentic Age: Place Your Bets (Mathias Verraes): Evidenced: feeding an agent an explicit domain model first yields better code structure and database performance, and bounded contexts also reduce token cost.
- Jimmy Nilsson's Post — reflections after the Thoughtworks 'Future of Software Development' retreat (Jimmy Nilsson): Asserted: DDD, XP, TOC, TDD, BDD, CD are 'more important than ever' in the agentic age.
Assessment: The single slogan 'fundamentals matter more' spans concrete evidence (Verraes), unargued assertion with admitted bias (Nilsson), and active skepticism (Edwards-Alexander) — from attendees of one retreat. This directly exposes the 'the fundamentals are agreed' assumption below: the cohort's flagship convergence is doing a lot of work with very uneven support underneath it.
Where does the non-delegable human asset now live — the harness/platform, the oracle, the fundamentals, or the developer's understanding?
from: What is the future of software development in the agentic/AI age?
- Notes from FOSE Europe (Giles Edwards-Alexander): In the harness — the continuously-evolving scaffolding of architecture guidance and rigour around the agents — though it must stay team-distributed, not centralized.
- What Survived Contact (Sam Ruby): In the oracle — the objective's evaluation is the single thing the person directing the model cannot delegate back to it.
- Jimmy Nilsson's Post — reflections after the Thoughtworks 'Future of Software Development' retreat (Jimmy Nilsson): In the fundamentals plus a renewed 'Extreme Humanism' — the durable disciplines and the conspicuously human element.
- AI Is Changing Software Engineering. The Fundamentals Still Matter. (Abby Bangser): In right-sized boundaries and the operational loop — humans must stay in operations because their learning is the irreplaceable asset.
- Fragments: February 9 (Martin Fowler (Feb 9)): In the developer's model-building and shared understanding — the craft of devising abstractions to reason about the domain.
Assessment: This is the deepest structural disagreement — every author agrees a human residue remains but nominates a different residue, and the choice determines what to invest in and what to teach. The harness-centric (Edwards-Alexander), oracle-centric (Ruby), fundamentals-centric (Nilsson/Bangser), and understanding-centric (Fowler) camps are not merely emphases: they imply different career ladders, different hiring, and different failure modes. Ruby's oracle and Bangser's operational-learning are the most operationally concrete; Nilsson's is the least argued. The absence in the corpus of anyone who holds 'nothing is non-delegable' is itself telling (see unexamined assumptions).
Should the harness/platform and its safety be centralized or left distributed across teams?
from: What is the future of software development in the agentic/AI age?
- Notes from FOSE Europe (Giles Edwards-Alexander): Distributed — dedicated harness-engineering teams are a mistake; per-team friction in building harnesses is creative and generative.
- Looking back at the Future of Software Engineering unconference (Bartosz Ocytko): Centralized — safety for non-engineers should come from a tightly-constrained, self-healing platform that ships access and data guardrails.
- AI Is Changing Software Engineering. The Fundamentals Still Matter. (Abby Bangser): Centralized enabling layer — platform, SRE, and ops teams should provide API-first, MCP-accessible tooling that others safely consume.
- Fragments: February 18 (Martin Fowler (Feb 18)): Centralized golden path — platform teams should provide fast-but-safe 'bullet trains' with security built in by default.
Assessment: A real operating-model split. Edwards-Alexander's distributed stance rests almost entirely on the DevOps-team analogy (his own extraction flags it as asserted-on-intuition, not argued), whereas the platform camp has the stronger concrete case for the citizen-developer safety problem — you cannot distribute production-data guardrails to non-engineers. The tension is partly reconcilable: Ocytko himself concedes a platform tight enough for non-engineers may be too constraining for expert engineers' identity and innovation, which is exactly the freedom Edwards-Alexander is protecting. The unresolved question is whether one platform can be both.
If code was never the bottleneck, what is the binding constraint now?
from: What is the future of software development in the agentic/AI age?
- Finding Comfort in the Uncertainty (Annie Vella): Human decision capacity and downstream absorption — 'decision fatigue is becoming the real bottleneck.'
- Notes from FOSE Europe (Giles Edwards-Alexander): Learning — 'learning is the constraint now, not engineering delivery.'
- We've Stopped Arguing About Whether AI Changes Software (Greg Herlein): Knowledge — the tacit, unwritten 'why' is the scarce resource agents starve for.
Assessment: A productive three-way split downstream of the shared 'code was never the bottleneck' finding. They are not incompatible so much as differently located — decision capacity (Vella) is organisational, learning (Edwards-Alexander) is about the team's rate of understanding the problem, and knowledge (Herlein) is about capturing rationale. But they imply different investments: expand downstream absorption, restructure around learning, or build knowledge-capture pipelines. The corpus has not reconciled which is the true binding constraint, and each author generalizes from a different vantage (a retreat-floor convergence, an org-design frame, a knowledge-engineering frame).