Healthcare
ROLE
Design Sprint faciliatator
UI/UX Design
Prototyping
TEAM
Stephanie Hu, Designer
Alex Charnas, Project Manager
Jorge Burgos, Engineer
GOAL
To create a medium fidelity prototype to validate the usefulness of a no-code editor for their PM user group to create workflows around Redox's API offerings.
TIMELINE
11/14/2022 ~ 11/18/2022
(1 Week)
Understanding Client Needs
The purpose of a design sprint is to use a short period of time to address as much of the client's design needs as possible. I had been working with Redox for 6 months at this point but not on this initiative so the first day was spent debriefing with the PM. In order to get to the point it was necessary to clarify the team's objectives as well as prioritize the features that needed validation.
Wireframes and Lightning Demos
After narrowing down the scope to a few screens and key features, we would usually start the design process by doing "Lightning demos", which is when the client and the facilitators would bring in screenshots of existing apps/websites that have good examples of features that the team is interested in.
However, the team was also interested in what I thought the user-flow would look like without their influence. They requested I wireframe without their examples and compare with them afterwards.
Luckily, the bit of experience I had with "workflows" through working on email automation paid off and the first pass of wire-framing was very close to what the team had in mind. Using it as a springboard, we cross-referenced the lightning demos they had compiled and started refining the features for the mid- fidelity prototype.
Final Prototype
The final prototype was narrowed down to 3 core screens, which could be each be used to validate the team's hypothesis on what steps users would take in using this editor.
The first two screens were created to see how users reacted to a friendly and graphic UI that is easy to understand as well as surfacing pre-made workflow templates that users may be interested in.
1. Homepage
2. Template Selection
3. Interactive Editor
The Interactive Editor was also prototyped to showcase features such as:
- Suggesting an action when adding a new block.
- Providing a list of the available collected data at any point in the workflow.
- Writing an email with collected data.
- Returning an error status for empty or invalid fields after testing.
Handing Off to the Client
A lot of the value of a design sprint is ideation, and with the limited time we had, not everything the team and I discussed made it into the finished prototype. On the last day after reviewing the final prototype together, I reviewed old notes and complied a board of "nice to have" features that could be tested in the future. I had also created a couple components for the engineers to get started on and cleaned up a vertical variation of the editor the team was interested in.
