-
Notifications
You must be signed in to change notification settings - Fork 54
Ongoing: Feature Discovery
[Beta User Follow-up] (#beta-user-follow-up)
[Budget Experience] (#budget-experience)
[Emergency Request] (#emergency-request)
[Request Urgency] (#request-urgency)
[Usability Testing] (#usability-testing)
The 18F team conducted follow-up conversations with current C2 beta users to better understand their needs and gather feedback on system updates.
We initiated a series of conversations to better understand the reconciler experience and how C2 can better support them. We interviewed people with the roles of service center supervisors, reconcilers, and budget analysts.
We spoke with a requester to understand their needs around emergency requests. We learned that some people aren’t using C2 for emergency issues and there is an emergency request hotline for emergency approvals.
This document provides a summary of the goals, definitions and factors/levels of urgency when making a request in C2.
We started usability testing with current users of C2— both internally to the 18F team and externally within NCR. Usability tests were focused on identifying the needs of requesters, budget analysts/reconcilers and approvers.
Key documents
User Research
Research sprints
- Pre-launch
- Ongoing: Feature Discovery
- Sprint 1: Discovery October 2015
- Sprint 2: Search and interaction model December 2015
- Sprint 3: Interaction model February 2016
- Sprint 4: Email research March 2016
- Sprint 5: Interaction model June 2016
Style guide
Team tools
- [Trello] (https://trello.com/b/kAW72R3m/c2-birthday-cake)
- [Mural.y] (https://mural.co/)