Docusign Integration
UX Design
Web
Background
Aya Healthcare is a healthcare staffing company that bridges the gap between hospitals and nurses/physicians. Aya's software offerings enable it to place A TON of staff at hospitals across the country and one of the key technologies that is vital to this process is DocuSign. Historically, whole departments of Aya staff would use the exact same Docusign login information to send Docusign envelopes to thousands of different people (nurses, physicians, hospitals, etc) every year. This was not scalable and left a lot to be desired in terms of automation and visibility of who is taking what actions in the system.I recently worked on a project at Aya to integrate with the Docusign API and bring envelope creation/sending inside our internal platform (called Nova).
Project Goals
1. replace the need to go to docusign website to send envelopes - be able to do more within our platform (Nova)2. have users do everything within our system so we can track it better (better reporting)
3.in addition to allowing the user to send Docusign envelopes, we want to create a mapping between our internal requirements and templates in Docusign so that our users dont need to manually reselect templates every time (reduces manual labor and removes human error)
Research
After meeting with the stakeholders of the project, it was clear that they really just wanted Docusign within Nova (our internal platform). The first step was to investigate what the current feature set of Docusign looked like and how closely we'd be able to emulate its functionality.
Preliminary Wireframes
There turned out to be so many features that the users wanted, but didn't really need (especially for an MVP version of the feature). I took the research I had done on Docusign along with the pared down requirements list and started creating some quick wireframes.
Iteration: Round 1
Because Nova is such a mature product, we already had a pretty defined set of styles to work with. I was able to get feedback on my quickie wireframes from the stakeholders and then immediately jump in to hi-fidelity mockups using pre-existing UI components. There were a few new components that didn't exist in the styleguide, such as how to render each of the "Documents" within the Documents section, that I spent most of my time on.
Final Mockups
Mappings
Since we were building the ability for the system to map our internal requirements to the templates stored in DocuSign for future automation, we also needed an interface to review/edit these mappings.
