Drilling Down on UX Design Details

Screen Shot 2015-04-02 at 10.55.49 PMI met D., my UX mentor, last Saturday afternoon for two hours in a coffee shop near his home. The pre-agreed purpose of the meeting was to introduce him to my senior project and walk him through my preliminary work on it.

He quickly grasped the project’s concept and purpose to enable caregivers to share proven recommendations and resources with each other. I had various documents on aspects of the project but not surprisingly, he was drawn to the visual materials. D. wanted to start with my personas. He said they were well thought out and looked professional. For future scenarios, he recommended breaking each into smaller chunks, which are easier for a UX designer to reference when developing wireframes.

I showed him process flow diagrams for the Q&A module user path and housing review user path. I also showed him the first wireframe for the Q&A screens.

He reviewed the user flow diagrams in detail and made several suggestions, including:

  • Grouping ‘Yes’ options together and separate from ‘No’ options stemming from the same decision point
  • Limiting rating scale options to three to avoid user fatigue
  • Highlighting the most positive outcomes on the chart with a background tone or colour.
  • Exploring design additions to offset the user’s disappointment in negative areas of the path, such as when they don’t find an immediate answer to their question.

For my wireframes, D suggested limiting horizontal buttons on mobile screens to three and to strive for more white space. He recommended Designing Social Interfaces, by Christian Crumlish and Erin Malone, as a great reference for social solutions. This is particularly helpful as early on I searched for UX resources specific to social and came up dry.

My biggest challenge with senior project is time, as I thought we would have more time this semester to focus on development.  D. suggested shaving time by using Axure for the prototype instead of formatting it in a separate tool, as I’d initially planned.  He also recommended proposing varied stages for the solution to manage breadth of scope and avoid scope creep.

I’m now busy implementing D.’s recommendations, which means making some time-consuming structural adjustments to my user flows.

D. has agreed to meet me again but as his best time is weekends, we can’t meet again until April 11. This is two days before my senior project is due for my semester mark. However, as I’m looking at phases, I consider this the deadline for phase one. I can iterate further for phase two, which is when I will show it as part of a digital show’s student exhibit in early May.

I also heard back from M. with a date to meet with her and a content expert just after the semester deadline for senior project. However, I can apply any advice I glean from this meeting to phase two.

Advertisements