Embedded Files
My Role:
Heuristic Evaluation
Stakeholder interview, requirement elicitation
User survey
Persona creation
Concept creation, wireframes and visual design
Design goals
Design goals
Something for every user who logs in through progressive discovery. Moving away from the existing paradigm of the portal being designed for people with domain knowledge
Provide a better experience for the users approaching the portal through different perspectives like education, analysis, legal or financial
Make the portal self sufficient in order to reduce the number of enquiries sent to the staff asking for data that exists on the portal, but is not discoverable
Preface
Preface
The global AIDS monitoring oragnisation had observed that the rich data portal they have built to display the data to the world is not being used to its full potential.
Users were unable to locate a particular data set, despite everything being published on the portals.
The staff received a lot of emails asking for the said data. The staff runs the query on the same portal and send back the results
Heuristics Evaluation
Heuristics Evaluation
To initiate the project that will completely change the way this portal was going to look, it was essential to get a buy-in from the stakeholders. A heuristic evaluation report, that elaborates the issues with usability, accessibility and aesthetics was a stepping stone towards emphasizing the need for such redesign exercise.
To identify the usability issues with the portal, a complete heuristic evaluation was conducted for the entire portal on both web and mobile screens. The report card of that exercise highlighted more issues than the staff was aware of. The 🔒 report card within the evaluation report underscored the necessity of the redesign exercise. Following are a few key slides from the said report
The final report card enlisting all the issues found.
Critical issues found in the very first page, above the fold
Few issues that made the navigation even more difficult after scrolling
Further, the google behaviour data was also analyzed to identify the frequent visitors and their demographics
The snapshot showing user distribution and sessions. The avg. session duration is shown to be less than 3 minutes, while the page load time was roughly 29 seconds
Google analytics shot showing device distribution. On mobile the users were getting frustrated within 1 minute.
With the help of the team in the organisation, the user personae were identified and mapped to the following
Tech-savviness
Domain expertise
Excel expertise (the portal allowed downloading the raw excel to perform your own analysis)
and exposure to the other website (Jakob's law)
The personae marked with a yellow arrow were the most frequent users.
Challenges
Challenges
Different stakeholders wanted to present different aspects of the data in a different format. This compromised the consistency of the entire portal
The data on the portal was available in two formats, which was useful for analysts and strategists, however, the complexity of the data made it difficult to understand for a non-academic
The portal was not built in a single session and hence the navigation was haphazard.
The real estate was not utilized properly, resulting in longer scrolls and unintuitive navigation
Stakeholder intervierws
Stakeholder intervierws
The qualitative interviews conducted for the stakeholders, internal users and external users, helped to identify a few common traits. following procedure was used for the same
- Preparing the questionnaire
Getting the questions right is essential for the interview to succeed. A question guide was created to ensure that all the information required to be gathered is covered. The questions were categorized into three parts of 20 minutes each
Introduction
A few ice-breaking questions about the interviewees, their domain of expertise, what section of the data portal they are responsible for, and how long they have been doing this.Purpose and audience
The questions were about the expected demographics of the ideal users and the stakeholders' contribution toward the section of the portal they were responsible for. This section also included ideas about what the new audience should be.Report content
The questions in this section revolved around the content displayed on the portal, how that data was collected, how that data was structured, how to read/use the same and what needs to be included in the section to make it more usable and more aligned to the intended userbase.Areas of improvements
Since the stakeholders receive a lot of emails regarding the content on the portal, they had ideas about what was working and what was not. So this section revolved around what they think needs to change/improve in their section. A few questions around success criteria were also included.
- Conducting actual interviews
The stakeholders were identified and their profiles were analysed beforehand to tweak the questionnaire. The interview audio was recorded with the interviewees' consent so that during analysis, the entire data is available. Notes were also taken to ensure the emotions were captured. all the stakeholders also provided some documents which were helpful in further analysis.
- Follow up emails
The recorded audio along with the follow-up questions were sent to the stakeholders to get further insights. These emails established a communication line in case I need further information.
- Analysis of the interviews
The interview recordings and notes were 🔒 documented and were analyzed thoroughly to align the design process with the vision, expectations and personae. The documents were structured according to the structure of the interview questions to find common patterns across the answers provided by the stakeholders.
The purpose of the same was to extract key information and common patterns from all the interviews
Solutions
Solutions
Cascading complexity model
The entire data was redesigned for drill-downs
On the very surface, the entire data gathered over 2 years was placed in the form of charts and graphs. These were intentionally made into interactive visualisations, which could be shared as an image at a particular instance
Users depending upon their interests and academic level could keep clicking on the "know more" button and find more complex datasets, visualisations and eventually they could access the raw data for their own analysis in legacy tools like excel
Care was taken to maintain the way data was visualised, consistent across the entire portal
Silos and Playground model
The data was arranged in silos, where the concerned personae can find all the data, without interference from other silos
A playground was to be built, where all the data could be accessed to generate combined reports as per the users' needs.
Google Sites
Report abuse