Data Data Data but there are few thing need consider.
Consumer products
- Most consumer products address specific problems for a user group, focusing primarily on retention, engagement, loyalty, and conversion.
- A typical user journey for a mainstream consumer product follows a linear sequence of steps, featuring limited entry points and several optional side quests (such as setting up account details while proceeding to checkout).
- Last but not least, a consumer product is often used in a personal context — for example, using your smartphone to request an Uber on your way to meet friends, making your own decisions about how much you’re willing to pay for the ride (come on, take that Uber Black; you deserve it 😬). You want to use that app right then and there, but it’s also within your power to set it aside or replace it with something else at any time.
Enterprise products
- Enterprise products, on the other hand, are “one-size-fits-all” solutions for various user roles, featuring different permissions, responsibilities, and levels of expertise. They primarily focus on efficiency, fault tolerance, and repetitive use—in other words, their purpose is to help employees complete their (repetitive) tasks quickly, affordably, and error-free possible.
- A single user journey can easily encompass over 100 screens, spanning 2 to 3 tools or more, with non-linear tasks and various entry points.
- The environment where enterprise products are often used can be highly regulated, as seen in industries like banking and government institutions. These settings can be stressful and impersonal, varying from outdated hardware used by employees in crowded open spaces to uncalibrated projectors with poor contrast. Additionally, some decision-making rooms may feature a matrix of high-quality displays covering an entire wall.
“Divide and conquer” when possible
To enhance user experience, it’s advisable to avoid loading the entire screen at once, as this can result in longer waiting times. Instead, consider breaking the screen into multiple areas or sections, each with its own independent loading state. This way, if the loading process fails for a specific section, it won’t impact the other areas. Users can still interact with the rest of the interface while they investigate or report the issue in the affected section.
Instead of loading an entire dashboard at once with one overall loading state, you can break it down into individual loading states for each widget, as they likely use different APIs.
Format data
Users from different locations may interpret the same data differently. Always format the data based on the user’s preferences. Remember that just because a user is based in a particular country, it doesn’t mean they will automatically use the standard formatting associated with that country.
For instance, as a European employee temporarily working in the U.S., I may not want to automatically switch to miles instead of kilometers or change to the `mm/dd/yyyy` date format instead of `dd/mm/yyyy`.
