Harvard Medical had three areas that need to be addressed for three very distinct users. An admin login, a professor login and a student login.
I needed to create a way to consolidate existing information into a concise, and easy to use experience. I also had to allow users access to course data, enroll in courses as well as keep track of certifications in a clean, cohesive manner.
Initial Information Gathering
What Do the Stakeholders Want/Need?
The wants of the Stakeholders and users can sometimes be very different. I like to gather information on what the stakeholders want from the app or website and how they see it fitting in to the organization. What problems would they like it to solve?
•How do they see it functioning, what role will it play in their organization?
•What is their budget? for both time and finances. A more complicated design will take more time and money.
•What are some of their needs when it comes down to standards? Do I need to maintain a level of compliance such as ADA? Are there legal standards I need to met or maintain.
•Is there a design system in place that I can use or recycle? Will I need to implement a whole new design system?
What Do the Users Want/Need?
What do the users need the app or website to do? How will this affect their overall experience with the organization and what problems would they like the experience to solve for them? Are their current needs being met if not how can we meet them?
•What is the current amount of users? and what are the demographics that make up the user base.
•What is the core user? while there might be many users ,what is the main user that will be using this day in and day out?
•What are some known pain points that users are currently or might potentially experience? How can I help alleviate the stress or confusion associated with functionality.
•What are some things the user would like to see? what charms and delights them; are their current programs they use that they like? Can I gain some inspiration from those to create a great user experience.
What is My Game Plan?
Once I get my key information on the Users and Stakeholders I like to setup a plan of action so I can hold myself accountable for what needs to get done.
•What is my timeline? When does this project need to launch?
•What are some issues I can see arising in the future what designing? will it affect timeline or budget?
•What are my resources like? Will I have enough time, data and budget to accomplish the things I need to accomplish in order to make this a successful design?
•Do I have all the information I need? If not how can I obtain it if I need to circle back around? Will I be able to conduct user studies?
•What is my team like; is my team experienced or are they just starting out? Will I need to help some of the junior members with their tasks?
•What is the PM’s idea for the project, how does it match up with my plans.
User Stories and Flows
The Key Users.
After initial information gathering is done I like to create my user stories and personas. This will allow me to get a sense for who is actually using the product and what they are using it for.
Here are three key user personas I had built out to better understand who would be utilizing the app and how I could best meet their needs.
Go With the Flow
Once I have some user stories and personas built out I like to start building user flows. Or how the user will navigate through the app or website.
•Where does the user start out? Do they start at a dashboard or login in screen?
•What’s the navigation like?Where with the user be able to go and what will these areas allow them to do?
•When the user puts in the required data or begins to move through the navigation where does it take them? does it lead them to new screens?
•What is the end result? Where does the user end up after they complete the flow loop?
The First Design Round
Building Out the Wireframes
When I have my user studies, flows and general information gathering in a good spot I start to build out my wireframes.
Here is where I will start figuring out page layout and what type of real-estate I’ll be working with.
This is an example of some of the wireframes used to show the rough design layout and map of functionality for course proposals and active courses.
Presenting to the Stakeholders
When I have the flow and wireframes ready to present to the stakeholders I like to create an interactive presentation to show the current layout and functionality ideas.
•Does the current functionality make sense and does what the user needs? Does it met the requirements the organization is looking for?
•Does the rough layout meet requirements? does it make sense are there elements that I are missing or areas that seem lacking?
•Are there any overarching concerns that I need to address? Are there items that I need to revisit with more scrutiny?
•What do I need to do next to get ready for next steps? Do I need to rethink any key areas in the design before I can move forward?
The Second Design Round
Refining Into High Fidelity
After meeting with the stakeholders and having them sign-off on the wireframes and I will often move into high fidelity models.
This were the more polished design begins to take shape and I start working towards the finished product. Here branding standards like color, fonts and assets will begin to play an important role.
This is an example of some of the high fidelity mockups for the course management portal and reports screens used to show the nearing completion designs.
User Testing
I like to build out an environment for core users to actually go through and test. This will allow me to track the functionality and engagement to ensure that the app is meeting user needs. And if not what can I do to make it meet those needs?
•I start by organizing a testing day or days; working alongside project managers and stakeholders to gather a user group.
•I take notes during testing if users are actually going through the app as expected. Are there areas of confusion?
•Are there still areas of confusion or strain that need to be addressed? While a rating system is sometimes used I like to take user comments and overall feedback.
•Before the launch moves forward what do we need to change or update to make the best possible user experience the for launch day?
Ready for Launch
Making Sure the Launch Goes Smoothly
Once the designs are finalized and core user studies conducted. I work alongside the devs and project managers to ensure a smooth launch.
•I make sure the devs have access to any material or assets they need.
•I will often go into the backlog or current sprint to double check to make sure that all requirements are met.
•Attend the Scrums to make sure if any questions or concerns come up I can help address them or figure out a best approach.
•Listen to user feedback after the launch to provide continued support.
