S.H.I.T.: How to apply and examples
I created this tool during turbulent planning for a sprint, with many interface elements and complex requirements, I then realized that it was possible to evolve. From there on I started using it to make decisions where I needed to decide the ideal elements for a complex interface.
It’s about four layers (in circles) similar to a target, where the center is the Objective of Iteration + Personas (can also be User Story or Jobs to Be Done). If you are familiar with agile frameworks, you know that one item of backlog must be small and be about a single objective.
From the defined target, the distribution of requirements across the layers becomes easier. Write them, separately, in each postit (very likely that these items are functional requirements defined during planning).
Layer T: Treasure
The first layer is where we define gold. This is where many teams are wrong to think that everything is a priority. Ask the team and analyze postit to postit:
Is this item ESSENTIAL to meet the goal of the iteration and the persona?
Distribute in the Layer T only the essential items. These will be the elements that will be visible as soon as the page loads.
Examples: headlines, descriptions, call to action, buttons, etc.
The other items, throw to the next layer.
Layer I: Interactions
In this layer will only be the items that will be accessed after some user action. That is, information that may appear after a click, mouse hover, tap or other interaction with the interface. Are actions and information in second instance.
Examples: tooltips, menus, dropdowns…
Layer H: Hidden
If any item gets here it is because it will be the last element of contact with the user in the journey of his goal. This layer may contain form error messages, success messages or even turn into another objective, such as modals or other pages.
Examples: floating messages, modals, loading on another page …
Layer S: Shall We?
Finally. Most likely, (especially in re-design) some items are left out. Certainly, they ended up here because they make no sense for the ultimate goal. Take the time to ask yourself why this element came to stop here and if possible, discard it.
Properly distributed requirements, I suggest looking at the macro, compare them and adjust the distribution between layers.
Now you will have a material to assist in the design of the interface. Each layer will represent the level of interaction that the user will have with the interface.
The S.H.I.T. is not only for full screens and the tool may be used for isolated components, for example, if your team has already worked with atomic interfaces and design system. But remember to have a guiding purpose, even when they are isolated elements.
This is a self-authoring tool, therefore, all feedback is welcome. Feel free to adapt it according to your need (let me know later how it was!).
In case you want to talk more about it, feel free and connect with me on Linkedin.