REMARKS
Commissioner explains improvements to Jobs NYC website
0:28:33
·
90 sec
Commissioner Matthew Fraser details the improvements made to the Jobs NYC website, highlighting the transformation from a legacy system to a more user-friendly and effective portal.
- The old system was a complex, legacy PeopleSoft application with poor user experience
- User feedback and market data were used to redesign the portal
- The redesign resulted in a 326% increase in site visits and job applications
- The new portal provides a better first impression of city employment opportunities
Matthew Fraser
0:28:33
Yeah.
0:28:34
So I'd say if if in order to understand how far we come with, sometimes we have to take a look back at where we came from.
0:28:43
If you went to the legacynyc.gov/jobsportal and you looked at what that it was a legacy PeopleSoft application.
0:28:50
Mhmm.
0:28:51
In order to search, find, and apply for a job, it was not only complex, but the the website experience was poor.
0:29:00
So what we did in those seeking jobs, we went to both hiring halls.
0:29:05
We went and we brought individuals in, and we got feedback in terms of what about the site work, what did not work.
0:29:10
And then we took market data by looking at those that have the highest demand in terms of employment, those that are getting a lot of application to see what works.
0:29:20
Then we modeled a portal that was heavily based on that design, that approach and what people liked about that.
0:29:27
And as a result, what we've seen is a 326% increase in the amount of people that are not just visiting the site, but also that are actually applying for jobs.
0:29:37
So it tells us that, 1, the portal is more friendly in a way that people can use, and then also, it's more appealing for them to apply.
0:29:45
I think any place that you wanna work if you look at the digital experience as, like, your first glimpse into what the front door of that operation looks like.
0:29:54
The legacy jobs portal was very poor.
0:29:56
It did not provide a good story, and I think now we're seeing based on use case that that it's doing what we intended it to do.
