Use cognitive load as a design constraint when evaluating platform capabilities.
The principle: every field, flag, and exception path consumes attention before it creates value. Hide accidental complexity If a product team should not need to know how certificates rotate, how namespaces are labeled, or how a scanner is wired, the platform should encode that decision. Hiding is appropriate when the choice is standard, low variance, and expensive to explain repeatedly. Expose service-owned choices Some choices belong with the service owner: availability target, data sensitivity, rollback tolerance, traffic profile, and dependency criticality. Expose these as product-language questions, not tool-language switches. Teach capability gaps deliberately When teams need to build lasting skill,…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in