...
...
View file |
---|
name | HCDCoP_092718_Meeting (4).pdf |
---|
height | 250 |
---|
|
Attendees
HCD CoP Sponsor: Valles-McCullough, Ginny
- Bellamy, Kyle
- Robert Fay
- Humphreys, Lesley
- Chirombo, Lovemore
- Mertan, Craig
- Neel, Sara
- Tisinger, Karen
- Yu, Lilian
| CMS Design SystemSeptember 27, 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
|
|
...
AgendaTime | Item | Who | Notes |
---|
5min | Welcome |
|
|
...
...
- Intent is to save you time by removing roadblocks
- Intent is to provide "overhead" resource support
- Intent is to teach all stakeholders the value of HCD/UX
...
...
...
...
Recap of last month:
- HCQIS HCD HipChat channel for communication
- HCD Toolkit Updates
- HCQIS Library Updates
...
- HCD Training for CCSQ Staff on HCD process
- Small groups: 16-20 people
- Workshops and group activities
- Persona Evaluation
- Finding similarities between across LOBs
- HCQIS Design/Code Samples
- HCD Center of Excellence
...
QPP
| Adam, Program Manager (Huge) - Responsible for 3 UX and design teams for QPP
- Web Interface (submission mechanism), Performance Feedback and Scoring Team, Analytics & Reporting Team (Internal dashboard and data modules)
- Almost been 2 years and no real issues
Glennette Clark (QPP) - Primary work on Claims data and getting feedback on their data needs
- Working with Huge
- Does DC UX Camps – next one in January
|
| | QualityNet, HARP & iQues | Sara Neel - UI/UX designer and developer on redesigning QualityNet.org, HARP and iQIES application redesign
|
|
| EQRS | Chirombo Lovemore - UX designer on EQRS and currently working on HARP, facility module and EQRS dashboard
- Using CMS design system for internal EQRS system
|
|
| HCD @ CMS
| Leslie Flaherty, Patients over Paperwork - Meeting with customers to create journey maps and what needs to be implemented
- Pilot in OIT – Completed development life cycle journey maps
- HCD approach for CMS employee on-boarding to improve experience
- Problem: getting clearance for external publication
|
|
| PM3 HCD Team | Primarily focused on: - HCD Pilot Training sessions for everyone in CCSQ and how they can use it in their work,
- CoP will move into HCD Center of Excellence and part of the HCD Charter,
- Working and analyzing design systems across all LOBS and Design.CMS.gov and see if there is value in creating a HCQIS design system
- Looking at a service to improve for CCSQ - looking at personas and see if there is an enterprise persona that overlaps. Will be doing journey map workshops and create a service blueprint.
|
| Upcoming Events |
|
|
...
|
| - Design Thinking DC Meetup Group - Fall Summit 2018
|
|
|
...
...
- 30PM - 6PM
- REcon18: Desinging
|
|
|
...
...
...
...
...
...
...
...
...
...
- Have a Design Studio when you're starting from "ground zero" (early in the design process)
- Usually 1.5-2 hrs
- Participants: researchers, designers, BAs, developers, POs, etc.
- The more diverse, the better to get everyone's perspectives
- Materials: pens, papers, web conferencing software, smartphone
- Document end results (photos)
- Design Studio
- Design Prompts
- Design tasks all written in user story formats (follows Agile process)
- Sketching
- Take photos after sketching session and email to facilitator
- Share sketches of each participants
- Explains their sketches, why they made design decisions, etc. and get feedback
- Have an ice breaker if there is a resistance amongst participants*
- Design discussion
- Drive initial wireframes and design decisions
- Additional Resources
...
- Discuss potentially looking at other topics suggested from July CoP "lean coffee"
- Robert Fay suggested it may be helpful for teams to share how their teams are organized, what works and what has been a challenge
- Post CoP discussion regarding getting access to end users - is it easy or a challenge?
- Post CoP discussion regarding design.cms.gov - can we get reps to speak at our event?
|
| Design.CMS.gov Presentation | Sophia Dengo, Ad Hoc | - Responsible for making Design.CMS.gov more robust for CMS
- Contact information: sophia@adhocteam.us
- History
- Elements were out of date and didn't take accessibility into account
- style guides not easily extensible
- Created for consistency, promote 508 compliance, responsive web design and to make development faster
- Serve as a living source of truth for UI standards
- Design system: one stop shop for code for design patterns and documentation for things we use on a regular basis
- Haven't been tested as a web design system
- Individual components have been tested in different applications
- Governance
- Constantly being updated and modified and primarily been driven by AdHoc
- Anyone can contribute by Github PRs and has a "Code of Conduct" guideline
- There is a AdHoc team that manages pull requests and contributions from Github
- Has not been a lot of outside contributions
- How to use the system
- Meant to be consumed by any technical stack
- Have to manually update design system when there are updates
- You don't have to use the whole system if you don't want to
- Can just use packages by need - core, layout, etc.
- Where do you go from here?
- Should be a living standard
- Everyone should be helping Design.CMS.gov to improve and evolve
- Questions
- Goals
- Wants it to be what drives most CMS designs
- Serve as a best practice documentation
- Help unify the experience on CMS
|
| Next Community of Practice Meeting |
| - October Topic: PRA
- Next Meeting: October 25, 2018
|
|
Column |
---|
| Panel |
---|
borderColor | #343434 |
---|
borderWidth | 1 |
---|
borderStyle | solid |
---|
| Resources View file |
---|
name | HCDCoP_092718_Meeting (4).pdf |
---|
height | 250 |
---|
|
|
|
|
...
We Need Your Help
...