Altisource is a leader in providing services and technology for the mortgage and real estate industries. There client list had gotten so big that it was necessary to break apart there monolithic software platform and create a more modular design system so they could quickly build a smaller, more customizable product for there new and diverse clientele.
UX Lead. I was responsible for leading research studies with existing clients and identifying there pain points. I created a modular library that the architecture team could use to quickly build products that suited each new client. I presented to the architecture teams and product owners on a daily basis. Worked in 2 week sprints getting the ideas into development quickly so we could fail fast and learn from our users.
Axure. Photoshop. Illustrator. PowerPoint.
What were our users searching for?
Here are a few initial sketches that I drew to show my VP of architecture so that I wouldn’t waste time going in the wrong direction. This project was to employ the kendo UI toolkit so I had to make sure the UX ideas were compatible. Sketching is a huge part of my design process.
I worked closely with my BA’s, Architecture team, and Product owner to come up with this IA. Here we hammered out every use case for the users and product features our clients requested.
Next, I wanted to learn were our current customers pain points were. Then discover our parameters and technical limitations. From there we designed screen flows and presentations to showcase the applications basic structure and customizable features to our stakeholders.
Modules – Wireframes
I created wireframes that we could make quick prototypes for the AOS users. I created everything in Axure so I could prototype and deliver polished visual comps all in one tool.
After all the prototypes went thru multiple rounds of testing we were ready to launch our 1st iteration of this immense project. Each client could customize their look and feel, add their logo and choose the modules that fit their needs.
One of my favorite parts to designing systems is pattern libraries and style guides. With an atomic design approach I like to capture every nuance to the look and feel module by module. It’s not only super fun to design but much easier than designing separate pages.
Levels of access
Increase in platform builds
'We’re not designing pages, we’re designing systems of components.'—Joe Fulginiti