Cohesion is one of the most important design considerations to me. I find the analogy of a well-trodden path to communicate what cohesion means to me in the context of user experience design. A well-trodden path in the context of UX design is a frequently user-executed workflow. By encouraging a user to regularly perform certain sequences of actions, a user's familiarity with a product can be improved. I used this principle to decrease the chances of a user feeling overwhelmed by the sheer number of features Sort Stack has. However, it's not enough to design workflows. The components of a workflow should be woven together in such a way that none of them exist in a vacuum. I hate features in an app that force me to go out of my way to use them. It's for this reason that I replaced the Goals table I had in an earlier version of Sort Stack with the Meaningful boost.

One example of this design principle in action concerns the relationship between the Check-In and Checkout Time fields. To start, the names of these two fields communicate that they are a pair. To reinforce this relationship, the Anchor Events feature syncs an event's Start and End times to the Check-In and Checkout times, respectively. I consider this a well-trodden path because the user's familiarity with the Check-In Time field makes the concept of the Checkout Time field easier to grasp, which in turn makes the Anchor Event feature easier to understand. Each of the features in this example leading up to the Anchor Events one serve as stepping stones to another feature.

I hope learning of this design principle's implementation in Sort Stack will facilitate your acclimation to its feature set.