05 How to fit information to different readers’ needs?
Build the visualisation providing a flexible system of components. Instead of creating a rigid structure consider designing modules can be rearranged in different layouts.
Based on the design activity and the stakeholders involved set the right visual hierarchy and granularity of information.
indexing
Consider having a shrinked version of the visualisation to overview the system at the first sight. Reducing all the action module in nodes helps to highlight connections and dependencies.
Also this synthetic form works as an index of the full version and helps readers to navigate the extended versions.
notations
When sharing the blueprint to propose improvements, it’s convenient to switch from a clear level of as-is visualisation to a view with annotations and more personal considerations.
This help to integrate the activities of analyis without loosing information of the original blueprint.
main actor pov
In some cases the user is not necessarily the protagonist of the service. Especially in B2B or B2E projects the focus is on the supplier or on the employer who never gets in touch with the user.
The change of hierarchy conditions also the links and dependencies of actions, showing the flow from another point of view. In this way all the relationship are analysed in different functions.
time span
Analyse the process focusing different time spans. Keep an overview that shows the entire delivery of the service and expand specific moments to scan in detail specific activities.
