1. Execute
1.1. Product Feature Usability Health Status
1.1.1. create a dashboard for all the key pieces of Product UX, with corresponding health assessments for each, with links to work planned or proposed
1.2. First UX
1.2.1. in-app help
1.2.1.1. recommend Pendo
1.2.2. templates
1.2.2.1. should be tied to personas to be effective
1.2.3. user learning
1.2.3.1. bluescape u.
1.2.3.2. overlays
1.2.3.3. new feature pop up
1.2.3.4. tutorial as functional exercise
1.2.3.5. onboarding
1.2.3.5.1. freemium model
1.2.3.5.2. social sign on
1.2.3.5.3. quickflows
1.2.4. user preferences
1.2.4.1. gesture mapping
1.2.4.1.1. web app competitiors offer users choice on gestures for pan, zoom, etc.
1.2.4.2. portal>webc
1.2.4.2.1. favorites
1.2.4.2.2. recent
1.2.4.2.3. share
1.2.4.3. customization
1.2.4.3.1. subscription
1.2.4.3.2. background color
1.2.4.3.3. grid
1.2.4.3.4. orientation
1.2.4.3.5. avatars
1.3. Personas
1.3.1. BNow
1.3.1.1. Unite
1.3.1.2. Consumer
1.3.2. BEnt
1.3.2.1. M&E
1.3.2.1.1. enough data and experience in the space to start building personas in this space
1.3.2.2. Gov't
1.3.2.2.1. should confer with BCore to help construct personas in this space
1.3.2.3. Bundled Solution (Horizontal)
1.3.2.3.1. need input from Dell and Ricoh on their envisioned personas to inform ours
1.4. CXL and Client Form Factor
1.4.1. explicit strategy for curating CX according to device
1.4.1.1. notifications via 'subscription'
1.4.1.2. mapping out the distribution of the cognitive load
1.4.1.2.1. e.g., pan/zoom interaction model on wall not portable to smartphone
1.4.1.3. define basic CXL roundtrip use cases
1.4.1.4. mobile content consumption UX
1.4.2. how does BEnt Windows redefine client portfolio UX thinking?
1.4.2.1. Lap/Desktop UX definition
1.4.2.1.1. upload
1.4.2.1.2. responsive design
1.4.3. BNow 'skinning'
1.4.3.1. Freemium path
1.4.3.1.1. prosumer target
1.4.3.2. Unite path
1.4.3.2.1. synch with Unite on their priorities, feedback thus far
1.4.3.3. BEnt companion
1.4.3.3.1. look at ways to 'embed' different versions of BNow to test out product ideas
1.4.4. Usability Health
1.4.4.1. Client Rationalization
1.4.4.1.1. feature parity
1.4.4.1.2. UI parity
1.4.4.1.3. workflow parity
1.4.4.2. Fit and Finish
1.4.4.2.1. 'vestigial tails'
2. Measure
2.1. User Research/Ethnography
2.1.1. on-site studies
2.1.1.1. promising initial candidates
2.1.1.1.1. J&J
2.1.1.1.2. WB
2.1.1.1.3. Haworth
2.1.1.1.4. Altius
2.1.2. ux group embedded earlier in sales engagements
2.1.2.1. high profile, long pilot cycles always provide diluted, secondhand info to UX
2.1.3. startup-style User Testing
2.1.3.1. Craigslist recruiting
2.1.3.2. Prototype Surveys
2.1.4. data
2.1.4.1. contingent on prioritization and implementation of Platform Strategy
2.1.4.1.1. would add crucial new stream to inform UX choices
2.1.4.2. google analytics
2.1.5. surveys
2.2. Multivariate Testing
2.2.1. process and infrastructure needs to be established
2.2.1.1. bring on 3rd party service
2.2.2. will help greatly in determining success/effectiveness of designs
2.2.3. reduces subjectivity of design decisions
3. Iterate
3.1. Design System
3.1.1. maintain asset libraries
3.1.2. establish UX grammar
3.1.2.1. interaction model
3.1.3. establish reusable UX components
3.2. User Research/Ethnography
3.2.1. on-site studies
3.2.1.1. promising initial candidates
3.2.1.1.1. J&J
3.2.1.1.2. WB
3.2.1.1.3. Haworth
3.2.1.1.4. Altius
3.2.2. ux group embedded earlier in sales engagements
3.2.2.1. high profile, long pilot cycles always provide diluted, secondhand info to UX
3.2.3. startup-style User Testing
3.2.3.1. Craigslist recruiting
3.2.3.2. Prototype Surveys
3.2.4. data
3.2.4.1. contingent on prioritization and implementation of Platform Strategy
3.2.4.1.1. would add crucial new stream to inform UX choices
3.2.4.2. google analytics
3.2.5. surveys
3.3. Multivariate Testing
3.3.1. process and infrastructure needs to be established
3.3.1.1. bring on 3rd party service
3.3.2. will help greatly in determining success/effectiveness of designs
3.3.3. reduces subjectivity of design decisions
4. Innovate
4.1. 2019 Competitive Efforts
4.1.1. Voice UX
4.1.1.1. mobile first?
4.1.2. CXL on Client
4.1.3. Recognition
4.1.3.1. authentication
4.1.3.1.1. face
4.1.3.1.2. qr code
4.1.3.1.3. badging
4.1.3.1.4. ultrasonic
4.1.3.2. content
4.1.3.2.1. speech to text
4.1.3.2.2. strokes to shapes
4.1.4. Comm Surface
4.1.4.1. displacing QuickLaunch
4.1.4.2. from Bluescape to BlueRoom
4.1.5. AR
4.1.6. Exploiting API for new feature and flow
5. Define
5.1. Experience Design
5.1.1. Bluescape UX
5.1.1.1. First UX
5.1.1.1.1. in-app help
5.1.1.1.2. templates
5.1.1.1.3. tutorials
5.1.1.1.4. user preferences
5.1.1.1.5. Bluescape for Newbies
5.1.1.2. Personas
5.1.1.2.1. BNow
5.1.1.2.2. BEnt
5.1.1.3. Cross-Device CXL
5.1.1.3.1. explicit strategy for curating CX according to device
5.1.1.3.2. how does BEnt Windows redefine client portfolio UX thinking?
5.1.1.3.3. BNow 'skinning'
5.1.1.4. Design System
5.1.1.4.1. maintain asset libraries
5.1.1.4.2. establish UX grammar
5.1.1.4.3. establish reusable UX components
5.1.1.5. Innovation
5.1.1.5.1. Voice UX
5.1.1.5.2. CXL on Client
5.1.1.5.3. Recognition
5.1.1.5.4. Comm Surface
5.1.1.5.5. AR
5.1.1.5.6. Exploiting API for new feature and flow
5.1.1.6. Usability Health Report
5.1.1.6.1. Client Rationalization
5.1.1.6.2. Fit and Finish
5.1.1.6.3. Iteration
5.1.1.7. User Research/
5.1.1.7.1. data
5.1.1.7.2. on-site studies
5.1.1.7.3. ux group embedded earlier in sales engagements
5.1.1.7.4. startup-style User Testing
5.1.1.7.5. surveys
5.1.1.7.6. Multivariate Testing
5.1.2. Bluescape CX
5.1.2.1. API Dev CX
5.1.2.1.1. Dev Portal
5.1.2.2. Existing CX
5.1.2.2.1. App Store
5.1.2.2.2. Community
5.1.2.3. Prospective CX
5.1.2.3.1. Ricoh
5.1.2.3.2. Intel
5.1.2.3.3. Dell
5.1.2.3.4. Website
5.1.2.3.5. Dev Portal
5.1.2.4. Internal CX
5.1.2.4.1. Field Assets