UX meeting 20190801

Attending: @ninavizz, @creviera, @redshiftzero, @rmoll, @eloquence; @huertanix + @harris, both out

Discuss: Rethinking Feedback Cycles wrt UX

• Has what's been happening for the past year really been working? It could be better...
  • More focus
  • Clearer disclosure of intent up-front
  • Framework to distinguish between challenging a proposed solution vs targeted design principles; it's ok to do either, and most productive to channel "subjective" feedback to the latter
  • Critique & design reviews on fully distributed teams, still a relatively new thing, and totally new to Nina, so—let's do this!
• 3 Proposed frameworks...
  • Critique: Solicit feedback on what works and what doesn't work, in either a proposed design solution or the design principles a proposal was drafted to solve for—and within tech constraints, opportunities, or other requisites (different from implementation scope).
  • Design Review: How to get a solution the team agrees maps well to sought goals and targeted design principles, built
    • Identify solution inter-dependencies, and MoSCoW parts/attributes (if possible) against effort/value of each.
    • Strategize how to break across sprints, if necessary, with defined scope boundaries for each.
  • PR Review: What did the developer need to do to accomplish the scoped implementation? Does the implementation match agreed-to solution points? Are there issues folks on the dev team need to discuss to get the PR to pass? Do these design changes impact standards that may need updates in the styleguide or other change management stuff for customers or contributors?

Present: 1.0 UI updates, split into "Rev1" and "Rev2"

• Nina, review Rev1 Design principles & broader user needs framing (5min)
  • Note: Link is for a mobile Invision, for meeting participants to view on phones while screensharing. Invision has 3 pages, that may be navigated on ye phone by swiping, or in a desktop browser by hovering outside the mobile phone graphic and clicking on the barely-visible arrows that appear ~200px to the left and right of the phone.
• Erik, review Rev1 PR (20min)
  • In progress Styleguide(ish) documenting updated styles & with PNG assets
• Nina, review updates to Design Principles for Rev2 (3.14159min)
• Nina, review proposed Rev2 Updates
  • Footer w/o "Learn More" link
    • "Learn More" page needs more design love, not in scope for 1.0 release
  • Index page text & layout things
    • Revisit origins of today's index page, history on how updates in Erik's PR evolved, look at simplified .index solutions to better meet design principles—or, either update design principles or punt 'till later for further discussion.
  • All: Discuss!
  • Note: "Get Codename" page not discussed; no time!

Feedback

• Design/goals principles, user needs framing
  • Noooo feedback, rlly...
• Erik's PR
  • Noooo feedback, rlly... everyone pleased!
  • journo an admin SASS/HTML cleanup emerged as biggest need, as basic colors/styles were updated in source UI; subsequent minor usability nits addressed in CSS, in Newsroom UIs.
• Rev2.0 critique/design-review
  • Jen: Simplified text makes sense, likes simplified design
  • All: No clear consensus on footer, Nina/Erik to iterate on "Advisement" line-o-text
  • John: Is the Tor banner enough?
    • Erik: Let's keep out-of-scope for now (nina #doh!)
  • Erik: Priorities for Rev2 = footer, then .index if time
    • All agree

Been Reading:

• Collaborative Product Design, O'Reilly