Approach

A method built for longevity: reduce surface area, name constraints early, and ship what can be maintained. Scale where realistic, not for scale’s sake. I will not burden you with systems you don’t need.

Principles

Design for the next person who inherits the system.
Prefer fewer pages and clearer paths over feature volume.
Shape attention so the correct action is the easiest action.
Build for the real environment: devices, bandwidth, staffing, and time.

Constraints first

Before design begins, the boundaries are defined: who maintains this, how often it changes, what must never break, and what the system should explicitly refuse to become.

Maintenance is the product

Launch is not the finish line. The goal is a system that remains understandable, editable, and stable months or years later, when the original context has faded and someone else has to make sense of it.