Confirmed users
587
edits
Taskfox/Goals: Difference between revisions
Jump to navigation
Jump to search
→Work with existing workflows, not against them
| Line 6: | Line 6: | ||
Existing workflows should not be broken, interrupted, or compromised in any other way. | Existing workflows should not be broken, interrupted, or compromised in any other way. | ||
A large part of perceived software bloat comes from piling on new features without a unified vision — each disjoint, with their own way of doing things, and own way to invoke them. The more we can place time-saving designs in the path of current work flows, the smarter, quicker, and lighter the software feels. Done well, the feature doesn’t even really feel like a feature, just a lending hand: “of course it was supposed to work that way”, says the user. | |||
A corollary, however, is that we can’t block the old work flow by trying to “help”. That would be rude. | |||
=== Tasks, rather than individual steps === | === Tasks, rather than individual steps === | ||