Case Study - Role Based Security Feature
The OrthoFi product is meant to empower practices to be able to offer more affordable payment plan options and as result make Orthodontic treatment more accessible to patients regardless of their financials.
The current OrthoFi flagship product did not have a role based security system in place. External stakeholders and clients requested this type of feature be implemented to better track patient contract adjustments and other tasks performed in the system.
Create the foundation and initial version of a role based security solution. The security feature needs to be learnable and scalable. One reason being as other user flows are redesigned and brought into the new version of the flagship product, the potential for adding these “tasks” as a security “right” in the new security feature increases.
Some goals included in the solution...
The security solution would need to provide as seamless of an experience as is possible for users as the organization is in the midst of redesigning the entire flagship product. Therefore, currently users are living in two systems so to speak. The older Legacy system and the new one page application must coexist until the full redesign takes place.
The security solution also needs to be scalable to fit the changing orthodontic industry space as business models and client types are shifting. For example, not every client will be a one physical location practice.
Main User Goals …
Ability to limit the types of contract adjustments a specific user can perform in the system
Ability to provide tiers of security access. Some users will have Rights Management and be setting the security access of others
Ability to provide a different set of rights at different physical locations for the same user. Some orthodontic staff work out of various locations and carry different roles at these locations. For example, they may be a Business Practice Manager at one location and a Front Desk Associate at another
Ability to copy rights of one user and apply them to another in order to configure security rights with speed
My Role on the Project
Discover, Design, and Delivery of Security solution for Dev Team handoff
Some deliverables included…
User Interviews with both internal stakeholders/users and external clients
Annotated Comps for Visual and Development teams
Research and Discovery
User research efforts including a variety of exercises in order to understand the needs, goals, and concerns from the client facing side of the problem at hand. These needed to combined with the organization’s internal needs and goals as in order to best serve both sides through a well designed security solution. Some deliverables generated during the user research included an affinity map and persona generation/refining. Examples can be seen below.
User research was also conducting in the form of multiple user interviews and stakeholder interviews. External interviews focused on those users most likely to handle to set up of security initially such as doctors. Secondly, staff members likely to manage the rights of others such as BPMs or Treatment Coordinators were also interviewed.
Some Affinity Mapping Takeaways ...
Design and Validation
User research drove the design studio sessions held within my Scrum team. We used the information to help form what would be multiple design iterations of a feasible design solution which would not only serve the main user tasks but could be supported from a development standpoint as well.
Low Fidelity Wireframe Sample
High Fidelity Wireframe Sample
Further Information on this Case Study
The project plans, design iterations, usability testing results, annotated wireframes and prototypes are obviously limited by a NDA.
I am happy to provide more detail on these if need be. Please feel free to contact me directly at email@example.com or through the form below.