A Better Shortcut Is Usually a Better Feature
Good product work often looks like removing a step, a decision, or a moment of uncertainty.
When I think about features, I am trying to think less about new screens and more about shorter paths.
A good shortcut is not just a keyboard command or a menu item. It is any reduction in effort that preserves intent. Fewer decisions. Fewer taps. Less waiting. Less text to parse. Less doubt about what happens next.
This matters a lot in small apps. If the product is narrow, friction is loud. A focus timer should not require ceremony before starting. A fasting tracker should not turn a simple habit into a configuration project. A Mac utility should not make the user babysit a process that can explain itself.
Sometimes the best feature is a default. Sometimes it is remembering the last choice. Sometimes it is making the destructive action harder to hit. Sometimes it is deleting a setting that only existed because I had not committed to a product opinion.
I like this way of thinking because it connects design and engineering. The implementation might be a tiny state variable, a clearer validation rule, or a better empty state. The user experiences it as momentum.
That is usually the kind of polish I care about most: not decoration, but the feeling that the product is quietly helping you keep moving.