I now encourage leaders to make four questions routine when new work is introduced. What are we asking people to start? What are we asking them to stop or reduce? What existing work does this connect to? What time, clarity, or support will make the new practice realistically usable? These questions turn wellness from a celebration-week topic into a design discipline.

Another useful practice is to examine strain as data. Repeated requests for clarification, incomplete implementation, workarounds, cynicism, meetings that continually revisit the same issue, and dependence on a few overfunctioning people can all be signals that the system is asking for more than the current design can reliably hold. Instead of labeling those signals as attitude, leaders can ask what condition is missing.

The goal is not to make work effortless. It is to create a system in which important work has a reasonable chance to be done well, sustained, and learned from.

Leaders can also protect wellness through predictable communication. If adults do not know which priority is most important, who owns a decision, or whether a new expectation replaces an old one, they spend energy interpreting the system. A short weekly priority message, a visible decision log, or a consistent meeting close that names what is changing and what is not can reduce that ambiguity. These are modest practices, but they communicate that leaders are paying attention to the cognitive and relational load of work rather than asking staff to absorb uncertainty on top of everything else.

Finally, I think leaders should ask directly what support would make a priority more usable. Not “Do you need support?” but “What would make this easier to do consistently?” The answers are often practical: a model, protected time, clearer ownership, fewer competing tasks, or permission to stop something else. Those answers are implementation data, and they belong in wellness conversations.