Annoyances vs Constraints
Automating personal annoyances makes you helpful; attacking the constraint the whole business is stuck behind is what makes real money — and they are not the same target. Theory-of-constraints applied to AI adoption. Annoyances are the recurring low-value chores that eat an individual's hours (a weekly status report, meeting notes, inbox triage). Automating them is genuinely worth doing — it is the right place to start because it is low-risk, and it builds proof and skill (see Low-Blast-Radius First) — but it does not grow the business; it just gives a few hours back. The constraint is the bottleneck the entire business is stuck behind: remove it and the company makes real money, and that is a completely different conversation with leadership. The source's diagnostic for finding the constraint reframes the audit question entirely: not "what's annoying / what eats a few hours of my day?" but "if we doubled our customers tomorrow, what process or thing would break first?" That first breakage is the constraint, and it is the project worth doing. The arc is deliberate: start on annoyances to learn safely, then graduate to constraints once you have wins stacked up.
Claims
- Automating annoyances makes you helpful; removing the constraint the whole business is stuck behind is how you make the company real money. principle — durable: this is the theory-of-constraints result (throughput is set by the binding constraint, so non-constraint improvements don't move the system), applied to where AI effort should point once you're past learning.
- Start on annoyances anyway — they are the low-risk sandbox where you prove value and build skill before touching anything load-bearing — then graduate to constraints. best practice — context: an operator early in an adoption arc; the ordering is start-safe-then-escalate, not annoyances-forever.
- Find the constraint by changing the audit question from "what's annoying?" to "if we doubled our volume tomorrow, what would break first?" best practice — context: an org-scale audit; the doubling frame surfaces the binding bottleneck instead of the most irritating chore. A scouting-style probe — see Frontier Scouting.
Related
- Low-Blast-Radius First — the start filter (where to safely begin, on annoyances); this concept is the where-the-money-is filter (where to go once you've proven value).
- Capability Overhang — attacking a constraint is "redesigning the building," where the non-commoditized value lives; automating annoyances is bolting the motor onto the old layout.
- Imagination Constraint — which problem to point AI at is the binding human input; this concept names the specific high-value class of problem (the business constraint).
- Frontier Scouting — the "what breaks if we double?" question is a diagnostic scouting probe at org scale.
- In-House AI Diagnostician — the role whose day-job is exactly this graduation from annoyances to constraints.
- Distillate: The $200K AI Job That Didn't Exist Last Year