2018-07-12 Meeting notes - UX Maturity & Process

Owned by Josh Zamor
Last updated: Nov 13, 2018 by Nikodem Graczewski (Unlicensed)
2 min read

Date

Attendees

Goals

  • How to track which UX user's have been trained on - and which are dificult to move forward
  • Improve process / communication

Discussion items


Which UX

We think that a list, maintained in the Essential Toolbox for developers, is the right approach for now to keep track of which UX user's have been trained on and therefore is the UX which we can't change without a careful process.


The items that'd go in that list are:


High user sensitivity

  • Requisition
  • Table forms (tables that are wholly a part of a form) - needs a semantic term
  • Tag component
  • Datepicker component
  • View Orders screen


Medium user sensitivity

  • Administration


We also identified that some terms need a lot of explanation and aren't standardized across developers, much less product and developers.  We need semantic (i.e. terms with meaning to the user/business) terms for these UI/UX pieces.  For example on table forms we could define forms such as:


  • List form or Search Results form
  • Detail Form or Line Item Form

Process


When discussing our process and our communication, we agreed to iterate on the current process.


We felt that this is good:

  • Continue to discuss and brainstorm on the dev forum


We wanted to add:

  • We should distinguish in the conversation when we're brainstorming vs. when we're making decisions.
  • Further when we're making decisions, we should qualify any time pressure from that decision or if there's a blocker involved.



Action items

OpenLMIS: the global initiative for powerful LMIS software