Process vs Objective
| Category | Decision-Making |
| Origin | Zettelkasten import |
| Surfaced in OS | Mar 8, 2026 (imported from Zettelkasten) |
Core Concept
Every team implicitly optimizes for one of two things, and each carries a distinct risk:
-
Focusing on the process carries the risk of building a culture that avoids errors instead of doing great work. Process becomes the point. People optimize for not getting in trouble rather than shipping something remarkable. Innovation dies because every deviation from process feels like a violation.
-
Focusing on the objective carries the risk of building a culture that looks for shortcuts to achieve the goal. The ends justify the means. Quality erodes, technical debt accumulates, and ethical lines blur because “we hit the number.”
Neither extreme works. The art is holding both in tension — disciplined process that serves ambitious objectives, with the wisdom to know when process should yield to the goal and when the goal should yield to the process.
Why It Matters to Me
This is a diagnostic for organizational health. When a team feels stuck, ask: are they process-prisoners (afraid to deviate) or objective-cowboys (cutting corners)? The answer determines the intervention.
At OrangeQC, the pre-turnaround culture was heavily objective-focused (ship features, hit deadlines) with process as an afterthought — which is how quality got so bad. The turnaround involved introducing process (QA, code review, vertical slices) without swinging to the other extreme.
Where I’ve Seen It
- OrangeQC (pre-turnaround) — objective-focused to a fault. Shipping speed over quality led to the codebase problems Dave inherited.
- OrangeQC (turnaround) — introducing process without killing velocity was the central challenge
- Enterprise environments generally — large orgs tend toward process-focus; startups toward objective-focus
Related Patterns
- Personal Minimums — minimums are a process discipline; the risk is they become rigid rules instead of protective boundaries
- Effectiveness Over Efficiency — choosing the right objective matters more than optimizing the process
- Maintainability Over Comprehension — good process (maintainable code) serves the long-term objective