Closed colbycheeze closed 7 years ago
@colbycheeze @rvennam
Latest Dashboard Wireframes: https://ibm.ent.box.com/folder/11986570664
Latest HiFis: https://ibm.ent.box.com/folder/12032239829 (I'm not sure if @kingtraceyj has completed these yet so treat them as subject to change)
@kingtraceyj commented on Tue Aug 02 2016
Complete UX & Visual for layout
Story needed
@Austinauth commented on Wed Aug 17 2016
@jakepeyser @rvennam
As @kingtraceyj and I start to take a deeper look at putting together a dashboard design a few questions came up.
@jakepeyser commented on Wed Aug 17 2016
@Austinauth
Yes, those still apply, but they are not all valid for v1. Let me know if you need clarity around v1 expectations again but check the email I sent first.
Yes, the company is LargeCorp and they are a big box retailer (e.g. Walmart) that sells just about anything. This makes the various scenarios (snow, heat wave, social media, etc) relevant for the company. However, the UI/UX should be pretty agnostic of the company/products. It should be easy for someone to white label the demo.
The views should be relatively the same for both personas. The scope of the data (global vs localized) will be the main difference, but this is mostly an implementation detail. I think we should discuss questions you have about specifics modules/details if they exist. You may have to make some assumptions for the personas and that is ok for the purpose of this demo, but refer back to the wiki descriptions when in doubt.
@Austinauth commented on Fri Aug 19 2016
A brainstorming session we held yesterday ended with @jakepeyser reiterating the main requirements for the MVP:
View Distribution Centers
View Retailers
View Shipments
@darinduvall Long-term I think we need to have a discussion around how far we want to take this demo and how we set the context for the design playbacks we have to the greater Bluemix team.
Based off what has been scoped to the MVP it seems like most of the demo is set to revolve around a map view featuring items like: Distribution Centers, Retail Stores, Shipments, and Stock Levels. While a map view is valuable it can be difficult to use as a primary means of keeping track of things like inventory, store locations across a large region, scenarios featuring many retail/distribution centers, and comparing data sets.
In the future I'd like to explore how we can incorporate other modules and patterns like table and list view to detail incoming/outgoing orders.
Initial Low-Fidelity Dashboard Concept (Supply Manager)
These concepts are meant not only to illustrate a potential Supply Dashboard but to raise questions regarding the appropriate amount of data/content to surface to the end-user of our demo app. The map is comprised of:
Visually we can explore the best way to convey these items through iconography and color.
Checking Status
Selecting a map item would reveal relevant content to the selected item.
@colbycheeze commented on Mon Aug 22 2016
Are there plans for something to be inside that bar on the left?