04 / Design Jam
Given the project’s scope, I organized a Design Jam with my UXD team:
Initially, users entered “# of minutes,” but feedback suggested reversing this to “start time” + “end time” for automatic minute calculation to avoid mental math
Ideas included a “general timer,” but it requires manual “start/stop” clicks by the Scribe, so we’re seeking more automation
Linking to another part of the EMR was a promising idea but, for the MVP, we opted for simplicity. Not all users use that EMR feature correctly, so we aimed to avoid disrupting the workflow
Skills
✔️ Creative Thinking
✔️ Leading Discussions
Lofis from design jam
05 / Design System
While starting the lo-fi design, I realized our design system lacked a calculator pattern.
I submitted the rationale and benefits for its creation, and it was approved!
Skills
✔️ Visual Design
✔️ Systems Thinking
Having the questions stacked like that takes up a lot of room, but was necessary to follow the design pattern of questions
06 / Lofi Evolution
The lofis evolved with each iteration, trying to solve the riddle of providing the clearest experience while accounting for complexity.
Each iterative attempt was necessary in unlocking truths, or seeing how a certain layout impacts the effectiveness of the design.
Skills
✔️ Iterative Design Approach
✔️ Troubleshooting
The iterative approach of the lofi process
07 / Dev Approval
Early in lo-fi creation, I consulted with my dev team to confirm functionality and avoid limitations.
Their advice helps guide my design, ensuring efficiency and preventing wasted effort.
Aside from the detailed annotations and hifi’s, I always like to hand off a super specific user flow mapping to my devs. I find it acts as a concrete instructional manual for them to get behind the workflow.
Skills
✔️ Proactivity
✔️ Clear Communication
User flow for the most efficient use of time in getting devs behind the designs
