Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Date

Attendees

Goals

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

Discussion


TimeItemWhoNotes
5minWelcome

PM3 HCD Team



Upcoming Events



Lean Coffee (Discussion)


  1. Product/Program Roadmap
  2. Recruiting
  3. Quality Conference
  4. Design Ops
  5. Outside CoP collaboration
  6. Research Ops
  7. CoP Format
  8. Promotion of UX work/Marketing
  9. How do we show complicated road map- portfolio level work
  10. Visualization of program portfolio level work

DiscussionRob Fay (RF)
  •  Our focus on
    • ISG
    • Folks working on product/dev teams
  • Remove roadblocks and challenges all of the above have.
  • Shared the new email address for HCD ( hcd@hcqis.org ) and to share with each other: hcd-cop@hcqis.org
  • Switch the time from 1-2pm to 3-4pm to help facilitate a happy hour after

Program Roadmap

Leslie (LH)

Eric (ES)

Rob

Maky (MA)

Program Roadmap

  • EQRS--3 legacy systems road maps
    • Legacy system maintained in conjunction of moving to new system
    • mandates
      • Reports and analytics
      • UI
      • Measure calculator—quality score calculator

Communication UX and product planning outside of PI has been very important

Who is in empowered to influence the roadmap

Portfolio Management ( roadmap example) ask Jeromy


(LH)

  • Dealing with and showing these roadmaps
    • Visualizations

They reorged to reports and analytics, SUI, Calculator (quality scores)

  • Letting teams come up with their own road maps
  • Dealing with issues surrounding getting off of old tech
  • Bringing features up in the backlogs

Problems with dealing with balancing Agile with the longer-term needs

(ES)

  • Forcing our way into visibility, and framing challenges within business contexts
  • Measuring something at PI events?

(RF)

  • A lot of it boils down to communication
    • using SAFE
    • how to move the communication up and down teams after the event is over
      • SCRUM/SCRUM of SCRUMs?
    • helping VIPs come up with the roadmaps and vision
      • where the rubber meets the road i.e. product teams
      • instead of ux being relegated as a worker bee, they're working arm in arm with the POs PMs etc to help inform and move things forward

(MA)

  • from HQR
  • constant communication between UX and the product teams
    • data points
    • api-first

(ES)

  • meeting about changes coming through the API
    • mapping user interaction mental models and how they relate to the APIs
    • showing the way we're considering end-user needs

(RF)

  • There isn't visibility for everyone
    • if it's not everyone's north star, what to make and how to make it so everyone can access it

(LH)

  • does anyone have any good examples of high level, long term roadmaps

(MA)

  • PM3 people may have examples

Quality Conference

Eric

Maky

Rob

  • How to represent HCD in Safe! (Eric Smallwood)
  • KPI/ KEI Cost benefit analysis----Metrics
  • Patient over paperwork a year in review 

(ES)

How to really represent HCD in the SAFE framework

  • communication strategies
  • what dev teams need
  • KEI's in relation to KPI's
    • label for some of the work we're doing
      • cost/benefits
    • articulate the ROI for teams working at this level

(MA)

ISG leadership is looking for this information

  • metrics showing the work we've done and the ROI of implementing this work

(RF)

  • Leaders talking about HCD in context
  • Patients Over Progress
  • Some of the work we're trying to do, from a transformation perspective was seen/heard

(ES)

  • presentation - we're trying on EQR, the end

Marketing

Maky

Eric

Louis

Matt

(ES)

  • in the trenches, it's hard to get out of the fray, to share challenges
  • what are other opportunities to get out of the vacuum across all of the other teams?
    • to communicate more broadly with ISG
    • can the CoP help with that?

(RF)

  • one opportunity in creating a COE for CMS
    • are there certain things , regardless of who is involved, stand the test of time and participation
      • social media presence
      • UX at CMS
      • establishing a presence

(ES)

  • communicating to the other teams the value being provided to the other teams
    • for the tighter audience

(RF)

  • some of what we're trying to do is ease/lubricate all of the communication
  • could we get volunteer participation that represent their LOB?
    • share already made stuff
      • talking about the design system

(MC)

  • the thing that made me a believer in HCD
    • 100% of the people couldn't find the reset password button (on a previous project)

(RF)

  • sharing successes
    • anecdotes
    • customer quotes etc.
  • We do have a topic next week
    • spoke with Aaron Alen about 508
      • he's open to be a guinea pig for a visually impaired person
    • 508 competence
      • it's the dev team
      • it's us and we have to make sure, or there's some other entity that takes care of it
    • Anyone have the ability to give Aaron permissions to test your 508 stuff!?

(ES)

  • we're always trying to meet 508
  • we'd be interested in demoing some of the work we've been doing
  • if we can technically do that, we're down
  • I want to run it up the flagpole to make sure it's ok with everyone before I commit. I'll check with management!

(Louis Gorres - 508 SME)

  • I have access to a couple apps within CMS
  • I'll check to see if we can provide what's needed
  • Send me an email and I'll take a look at it

Next Community of Practice Meeting
  • February Topic: 508 Demo


Action items

  • Unknown User (ki8431)  sample roadmap, speak to Jeremy Smith and Josiane Alagbe
  • Robert Fay follow up on the 508 Compliance with Eric Smallwood, Louis Gorres, and Aaron Allen
  • No labels