Designing for focus means removing interface rather than arranging it: view modes that strip the editor back, menus that appear on approach, and colour that lives in variables.
Interface chrome is everything on screen that is not your work: toolbars, rails, panels, status strips. It is all defensible individually and it is why a document can end up occupying a third of the window. Designing for focus is mostly the discipline of removing it — and the hard part is not the removing, it is deciding what has to stay reachable while it is gone.
Hiding interface is easy and usually wrong on its own. If the toolbar is gone and the action is now three steps away, you have not created focus, you have moved cost from the eye to the hand. The test we apply is whether the removed thing is still reachable in one gesture — hover, a key, or the command palette. Where it is not, the honest answer is that the element earns its place on screen, and the correct fix is to make it smaller or quieter rather than to make it disappear.
Watch what people do when a surface is unfamiliar. The first instinct is to look for a toolbar; if there is nothing to find, confidence drops immediately. Calm interfaces still have to announce that they are interfaces.
The suite is wide — documents, sheets, slides, boards, records and more — and a wide product is exactly where restraint matters. The alternative is every capability competing for permanent screen space, which produces the dense grey toolbars people grew up with and quietly stopped reading. Capability belongs in the command palette and in the modes; the surface belongs to the work.
It hides their permanent representation on screen, not the features. If something becomes unreachable rather than merely invisible, the mode is wrong.
Because a click to open and a click to choose is two gestures for one decision. Hover removes one of them while leaving the target in the same place.
It can be, which is why the exit from any mode has to be obvious and the command palette has to cover everything that was removed from view.
Presentation design is mostly subtraction. The decisions that matter — one idea per slide, type large enough to read, contrast that survives a bad projector — take an hour to learn and most decks ignore all three.
An on-call rota decides who answers at 3am. How to size it, what to pay, what counts as working time, and the handover that stops the same fault being rediscovered.
A canned response answers a repeated question consistently. Which ones to write, how to keep them from sounding automated, and the rule about never sending one unedited.