UX: Usage Quotas page standardization across consumables
Summary
This is the UX design issue for &7123
The usage quotas page needs to be cleaned up visually to create more consistency between the three tabs (vertical vs horizontal layouts, font sizes, how numbers are displayed, graph styling, etc.)
Storage is confusing. It looks like there's three types (namespace, excess, purchased) and it can be confusing. We don't have the "excess" distinction with CI minutes, there's simply "Current period usage" and "Additional minutes". This makes more sense and could work for storage also ("Namespace storage" and "Additional storage" with a CTA that says "Purchase additional storage"). This is less of a research insight and more of a common sense observation that we don't need three labels for one thing - storage.
Design Details
- Who will use this solution? Group owners
- What problem do they have? Difficulty predicting and managing costs associated with consumables
- When do they have the problem? Bigger companies: always. Small companies: ?
- Where in the app do they have the problem and at what frequency (if known)? Less of an app problem and more of a business problem.
- Why will a design help them? Help them understand usage, overages, and predict costs.
- JTBD and/or Tasks
- Is this problem supported by user research (please link relevant research issue/s)?
- Known technical constraints
- How does this help the business?
Edited by Matthew Nearents