If Everything Is Priority, Nothing Is Designed

A stakeholder calls every objective critical. Every policy deserves emphasis. Every exception needs a slide. Every button should stand out. The result is an experience where nothing stands out. When everything receives the same visual and instructional weight, learners must create the hierarchy the team avoided.

01Name the problem

A stakeholder calls every objective critical. Every policy deserves emphasis. Every exception needs a slide. Every button should stand out. The result is an experience where nothing stands out. When everything receives the same visual and instructional weight, learners must create the hierarchy the team avoided.

02Look at the real work

Importance depends on what a person must do, how often they do it, the cost of error, and the support available. A rare catastrophic exception may need a clear signal. A common low-risk detail may belong in reference material. A daily decision may deserve repeated practice.

Design is deciding what receives attention and what does not.

03Choose the right response

Limit primary outcomes. Cap what can appear in the main path. Require every requested addition to explain what it displaces. Constraints can feel uncomfortable, but they expose weak reasoning before it becomes learner overload. A design with no tradeoffs is usually a storage container.

04Protect the learner

Removing content does not mean the information lacks value. It means the main experience is not the right place, time, or format. Reference resources, optional depth, and performance support can preserve access without demanding equal attention.

05Make the decision visible

Tell stakeholders what is primary, supporting, available later, and out of scope. Connect those choices to performance and evidence. Carry that hierarchy through writing, practice, feedback, visuals, and reinforcement. If everything is priority, nothing has been designed.