Pavel Bukengolts • UX Magazine 2026 Quarterly Operating System 2 / 2 Rules Active

15 Rules of Design Leadership: Quarterly System Builder

Enterprise failure modes repeat in familiar patterns. Speed comes from leverage, not stamina. Pick exactly two rules that will change your next quarter, inspect how conserved complexity shifts into your system, and build the smallest viable mechanism to make them permanent team habits.

Load Preset Profile:

1. Diagnose & Select 2 Rules

2 of 2 Selected
Strict 2-Rule Constraint: "Pick two rules that would change your next quarter. Ignore the rest for now."

2. Conserved Complexity Transfer

Larry Tesler's Law

Complexity never vanishes; it changes hands. Observe where your two chosen rules shift cognitive friction:

Operational Complexity Distribution 72% Absorbed by System
Downstream User
25%
Engineering Toil
20%
Designer Friction
15%
System Defaults
72%

3. The Smallest System Mechanism

Team Habit Architecture
Quarterly Directive

Leadership Operating Agreement: Q2 Focus

Enterprise B2B Product Design Team (18 designers, 6 squads) • Cadence: Bi-weekly sprint planning & design review gate

Pillar 1: The Rule of Leverage

“Give me six hours to chop down a tree, and I will spend the first four sharpening the axe.” — Abraham Lincoln

Mechanism: Establish a searchable decision/research log in planning tickets; refuse re-arguing settled component patterns without new evidence.

Quarterly Sanity Check:

What decision do we keep re-arguing because the system won't hold it?

Prevents: Burnout, inconsistency, and the rework loop that eats roadmaps.

Pillar 2: The Rule of Conserved Complexity

“A system's complexity is a constant; the only question is who has to deal with it — the user or the designer.” — Larry Tesler

Mechanism: Absorb workflow complexity into smart defaults and progressive disclosure rather than pushing manual reconciliation to the customer or support team.

Quarterly Sanity Check:

Where can the system absorb it once, instead of people absorbing it forever?

Prevents: Reconciliation work that the system should have handled.
The Year-Start Invariant: "If we want 2026 to feel lighter, we can’t use stamina as a strategy. We need systems: Shared language, clear models, evidence we can find, and rhythms that reduce rework. That’s not bureaucracy. That’s compassion."
✓ Active Operating Contract Verified