Human-Centered Design

Page tree

Lean Coffee

July 26, 2018

Goals

  • Share best practices and educate people on the benefits of HCD
  • Collaboratively solve problems
  • Help each member be more successful in their role

Agenda

ItemNotes
HCD Community of Practice Discussion
  • Tools that can be used for collaboration include: Mural, HipChat, and Confluence.
  • Team would like to generate topics of discussion for upcoming information sharing meetings. Need to create a backlog of topics that are submitted by users.
    • Has anyone used participatory design with CMS? Sara Neel (iQIES) has. They had people come in, review a deck with instructions, then work out the problem. She is willing to do a short presentation at the next UX Info Sharing meeting.
    • How does UX fit in with the Agile process (sprints)? Would be great to be able to share tips and techniques.
    • How to identify and recruit user participants – reach them and keep track of them.
    • Sharing things that are demoed at PO sync meetings.
    • Sharing research that can be leveraged by another team.
    • Brainstorm ways to collect topics on Confluence and even have a way to take a dot vote to prioritize.
  • Product Owners have been invited to this CoP meeting with the intention that they would be able to help solve blockers to access to users. Their role is complementary to the HCD team roles. The HCD workshops sponsored by CCSQ and ISG will go a long way to having the Product Owners become advocates and champions for the HCD teams.
  • HCQIS Library
  • Metrics Tip Sheet – does the community want something more high-level or more in-depth? Seems to be the right balance.
  • Metrics – CCSQ is interested in leveraging HCD toward their goal of cost savings/avoidance.
  • HCD Process Graphic – reviewed graphic located on Confluence.
Lean Coffee
  • Purpose of the CoP should be solving problems and sharing ideas.
  • Proposed topics to discuss during the Lean Coffee portion of the meeting (can also serve a backlog of topics):
    • "Code Sharing" for common activities - something standard like "capture Requestor information" and making it like a "service" to be shared across HCQIS projects
    • There is no project-specific HCD strategy
    • Participatory design or co-designing
    • How do you sell this to non-designer participants? Important to identify stakeholders and set expectations.
    • An ice breaker activity is a great way to get participants in the creative mindset.
    • Sara shared that a successful exercise they did was to allow participants a few minutes to do Google searches and take screen shots of their results before getting in to the actual designing.
    • http://www.designkit.org/mindsets/2
    • Content Strategy
    • Accessibility
    • Design Systems
    • Socializing HCD as an internal team communication process
    • How to create a HCD strategy for a project
    • Design Studios
    • Issues converting design to development
    • Backlog - when things are put in as an "enhancement" and not a "bug"
    • Best practices to capture human interest in the GUI (e.g. avoid clutter, be concise, use visuals to the max extent, etc.)
    • Carol mentioned a short video that would be of interest to the group: “Embrace Ambiguity” with Patrice Martin, Creative Director and Co-Lead, IDEO.org speaking about not being afraid of designing and failing.


Resources

Connect with Us!


 




QualityNet Slack: #hcd-share and #help-hcd

Email Lists: Sign up at https://qualitynet.cms.gov/listserv-signup 

General CoE News: "CCSQ HCD CoE News" 

Community of Practice Emails: "CCSQ HCD-CoP Notify"



HCD Center of Excellence   |   Join the CCSQ HCD CoE News Mailing List