Schwerpunkt as Focus is Richards' translation of john-boyd's third pillar of organizational climate — Schwerpunkt, the German military concept of the main effort or focus of operations — into the sprint goals, product visions, and team alignment mechanisms that enable business and software teams to act autonomously while remaining strategically coherent.
Boyd's Schwerpunkt
Boyd drew Schwerpunkt from the German operational tradition, where it designated not a physical location but a conceptual center of gravity for operations: the point around which all actions by dispersed units — acting on their own initiative, under Auftragstaktik — remain mutually coherent. A well-understood Schwerpunkt meant that unit commanders, exercising local initiative in response to conditions the high command could not see, would nonetheless pull in compatible directions because they shared a deep understanding of what the operation was trying to achieve.
In Boyd's framework, Schwerpunkt resolves the apparent tension between decentralized initiative and strategic coherence. Without Schwerpunkt, Einheit and Fingerspitzengefuehl produce energetic but incoherent local action. With Schwerpunkt, autonomous units with mutual trust and expert judgment produce coordinated effects that no centralized command could have directed — because the coordination emerges from shared understanding rather than shared orders.
Richards' Business Translation
In certain-to-win, Richards translates Schwerpunkt as any shared understanding of main effort clear enough to guide local decisions without requiring central direction. The translation move emphasizes that Schwerpunkt is not a detailed plan but a focusing intent: the difference between "we need to capture market share in the enterprise segment" and a detailed quarterly plan is the difference between Schwerpunkt and centralized directive.
For business organizations, Richards identifies Schwerpunkt in:
The failure mode without Schwerpunkt is not chaos — it is fragmentation: each part of the organization pursues its own locally rational goals, and the aggregate is strategically incoherent. The symptoms look like misalignment, conflicting priorities, and "everyone doing their best but nothing coming together."
Schwerpunkt in Software Development
The software development application is the most direct. Richards argues that sprint goals — properly formulated as outcome-focused intentions rather than task lists — function as Schwerpunkt for the sprint cycle. A good sprint goal tells the team what result to achieve and gives them the basis to make autonomous decisions about how to achieve it. A sprint backlog without a clear goal is a task list that eliminates the judgment component of Fingerspitzengefuehl rather than enabling it.
Product vision serves as longer-horizon Schwerpunkt: the shared understanding that allows feature teams, platform teams, and design teams to make locally autonomous decisions that produce a coherent product rather than a collection of unrelated features.
The boyd-agile-bridge maps Schwerpunkt to the Agile Manifesto's third value — "customer collaboration over contract negotiation." Richards reads this as a Schwerpunkt statement: keeping alignment around customer outcomes (rather than contractual deliverables) provides the focusing intent that makes autonomous team decisions strategically coherent.
Relationship to the Other Pillars
Schwerpunkt is the direction-setting element of organizational-climate-for-business. Without einheit-as-trust, Schwerpunkt cannot enable decentralized action because teams will not act without approval regardless of how clear the intent is. Without fingerspitzengefuehl-as-expertise, Schwerpunkt provides direction to practitioners who cannot effectively exercise the judgment it is meant to enable. All three pillars are co-required: trust to act, expertise to judge, focus to align.