Leading design for an application consolidation project
(Make new header image)
PLANNING
I was asked to join the consolidation team to lead design for this project. I Researched what each app does, listed all funstionality of all apps,
The problem
On the DID(it) contract, there are ## applications that we maintain, and many of the apps do the same thing. The government is looking to cut excess spending where it can, so the idea to consolidate all redundant DID(it) apps into one emerged. This will reduce the number of people on the development teams needed to
This project will combine the functionality from 5 apps into one. Those apps and their functionality are listed below:
- ROSS: Time keeping and reservation booking
- ePulse: Organization management
- app3: User management
- app4
- app5
What I’ve done about it
I was asked to join the consolidation team to lead design for this project. I Researched what each app does, listed all funstionality of all apps,
I was asked to join the consolidation team to lead design for this project. I Researched what each app does, listed all funstionality of all apps,
ROSS
The ROSS application does most things the other apps do. It was chosen to be the “base” for this project, meaning all other app functionality was brought into ROSS, and I redesigned parts of ROSS to accomidate
(ROSS images and story)
ePulse
The ROSS application does most things the other apps do. It was chosen to be the “base” for this project, meaning all other app functionality was brought into ROSS, and I redesigned parts of ROSS to accomidate
(ePulse images and story)
Disclaimer: All screenshots in this case study are representations of the ROSS application. They include no PII or sensitive USCIS data.
Check out the next case study
Updating tedious workflows for a federal enterprise app
A series of UX improvements for a federal time tracking & scheduling app.
Learn more
Leading design for an application consolidation project
(Make new header image)
PLANNING
Document what each app does, how it works, who uses it, compromises made along the way, decisions that come from higher ups, how I adapt my deigns to meet the updated business needs
The problem
On the DID(it) contract, there are ## applications that we maintain, and many of the apps do the same thing. The government is looking to cut excess spending where it can, so the idea to consolidate all redundant DID(it) apps into one emerged.
This project will combine the functionality from 5 apps into one. Those apps and their functionality are listed below:
- ROSS: Time keeping and reservation booking
- ePulse: Organization management
- app3: User management
- app4
- app5
What I’ve done about it
I was asked to join the consolidation team to lead design for this project. I researched what each app does, listed all the functionality of the apps, and designed new flows that are familiar but improved flow-wise. This will reduce the number of people on the development teams needed to maintain the apps, and it will lower the cost of the contract for the USCIS.
This case study will go through each app, it’s functionality, and where it fits into the overall new design.
ROSS
The ROSS application does most things the other apps do. It was chosen to be the “base” for this project, meaning all other app functionality was brought into ROSS, and I redesigned parts of ROSS to accommodate this new functionality.
(ROSS images and story)
ePulse
ePulse stuff
(ePulse images and story)
Disclaimer: All screenshots in this case study are representations of the ROSS application. They include no PII or sensitive USCIS data.
Check out the next case study
Updating tedious workflows for a federal enterprise app
A series of UX improvements for a federal time tracking & scheduling app.
Learn more
