Embed Size (px)
Citation preview
Zaloni BedrockUser research insights
Guerrilla Research
Objectives1. Identify the user pain points with entity
listing and entity creation segment of Metadata module.
2. Conceptualize an advanced UX addressing user’s pain points & best practises.
Methodology
Semi-structured interviews
Interviewee diversity: Limited
1 solution architect1 Developer & 1 Support leader
Research Limitations
Sample sizeLimited module discoveryWorkscope
Research statistics
10 Participants
500+ Minutes of discussions
3.5
AVERAGE 48.3%
2.5
2
2
2.5
2
INTERVIEWEE GROUP 1
Explorability of entities
Entity Creation
INTERVIEWEE GROUP 2
Explorability of entities
Entity Creation
INTERVIEWEE GROUP 3
Explorability of entities
Entity Creation
1 2 3 4 5
Persona 1 DAVID
Age: 29
Job title: Software engineer
Experience: 4+ years
Goals: Turning mountains of data to actionable insights.
Needs: Crisp and selective data
Opinionated and assertive.Aware about the interfaces and expects the UX to match the current trends.Affinity towards tabular structure of data representation.
Note: Personas are focused on users of web interface
Persona 2 CAREN
Age: 25
Job title: Data Steward
Experience: Entry Level/Mid-Senior
Goals: Administration of data
Needs: Easy on-boarding and viewing of data.
Understands databases and associated aspects like query languages, metadata.Possibly does not have experience with lot of contextual interfaces.
Note: Personas are focused on users of web interface
Areas of improvement
● Entity Exploration● Entity Creation
Entity Search
• The search system should be designed in a manner to provide clues to the user about1. Where to search ?2. What to search?3. How to search ?
• The current search design lacks in all 3. The search box should use dominant design elements like color, fonts etc with placeholder text guiding the user as what to search and how to search.
• The research shows the users sometimes could not even identify there was a search option.
Entity Exploration
Help• Intuitiveness of a digital system is directly proportional to best practices and help
incorporation in design• The current design missed to incorporate help to users in general and specifically in
1. Search2. Configuration of the table in terms of column adjustment.3. What can be done with entities ?4. Explorability of entities.5. What all bulk operations can be done and how?6. General information about table elements like source schema, source platform etc to
help onboard unfamiliar users on to the system.
This was the most spoken about pain point during user interviews
Entity Exploration
Action Buttons & Feature clues
• The action buttons should be available in the first sight of the user, helping him accomplish required actions without any visual or logical hindrance. In the current design the immediate actions are hidden behind a native hamburger menu.
• User research validates the need for upfront action buttons, with an intention to decrease the clicks required to do so.
• The current UI also has the ability to adjust the column size, edit the entity by one click, bulk deleting of entities etc but the user research reveals that the system fails to guide the users to use these features.
Entity Exploration
Entity Creation
STRUCTURE
1. The user research acknowledges the need of a wizard style interface for defining entities, the reason being
a. In user interviews, the users failed to acknowledge that entity creation is a 3 step process with basic, fields & advanced section to be filled simultaneously.
b. The interface lacks in providing the user a control over the process by not acquainting him of what he has done in the prior stage and what he has to do next, bucketing the information which is immediately required and the information which can be fed later.
c. Physical structure of the form needs to work out in a manner, which appeals to the eyes.
Entity Creation
HELP
Help in creating entities i.e., providing information to the user about the fields which he is not aware, keeping in mind the convergence of multiple profiles of professionals who are going to use the system.
Basic features like drag and shuffle in case of ordering fields, one of the most discussed pain point during research in entity creation.
“THE BEST INTERFACES ARE THOSE WHICH DON’T NEED ANY EXPLANATION”
Entity Creation
Solutions
Dual listing interface
• The user research provides the insight that the system potentially is going to be used by both technical and non technical users like developers, data stewards, and customer support teams. While the developers displayed affinity towards tabular structure of data representation for entity listing, a grid system (tiles) will cater to a wider audience. Hence, the Interface should have both tabular as well as grid system for listing entities.
• All Interviewees strongly agreed to this proposition in the research phase
Solutions
Personal configuration
• The research shows that it is quite possible that data needs of each user may vary drastically, keeping in mind that each user may derive insights in a different way, therefore giving each user the same set of data in listing module can impact the efficiency and certainly can limit the opportunity to get diverse insights and analytics. INKONIQ insists that the users should be given the freedom to populate what information should be populated to them about entities in entity listing based on their needs.
• This will not only boost the overall experience with the system but also allow the users to enhance the productivity from this system.
Solutions
Explorability
• The biggest challenge with a system which has huge amount of information is how the user reaches what exactly he wants in the shortest period of time, with minimum operations.
• It is common understanding that the size of entities can go into thousands, the challenge is to make the user reach his needed data keeping the option of exploration intact.
• Inkoniq suggests “string search with auto fill” as a solution to this problem. Keeping in mind that the system is a platform to both technical and non-technical users and the user might not always be aware of what exactly they want, autofill can prompt suggestions to the users and engage them in terms of Explorability.
• All interviewees who were asked for their feedback on this proposition confirmed that it will immensely help in achieving their goals and rated it >4, on a scale of 1-5.
Solutions
Intuitiveness
• Intuitiveness is prominent point of discussion when interfaces are conceptualized and designed the reason being, it lets an extremely easy on-boarding of the user on a new system, decreasing the learning curve to a possible minimum, making the user more efficient and system highly usable.
• saying a UI is intuitive is like saying it exhibits several positive attributes: it's memorable, discoverable, easy to learn, familiar, matches expectation, and so forth.
• During the interviews it was discovered that the users could not figure out where was the search box, were not aware that the size of columns can be adjusted, could not figure out how to view an entity, could not figure out what exactly were search parameters, that the entity creation was a 3 step process & many other things, this can be fixed by incorporating standard UX practices into the interface in question.
Solutions
Entity definition wizard
• 2 out of 3 interviewees could not figure out by themselves that the entity definition was a 3 step process and had difficulties understanding how the information feeding was grouped.
• On putting up the proposition of a definition creation system which is stepwise, segregating what information has to be immediately put up and what can also be filled later, which keeps the user informed of what he has done in the last step and what he has to do in the next step, all interviewees unanimously agreed to such a concept.
• Inkoniq strongly suggests that the entity definition should be a creation wizard style UI, having snippets of information filled in completed tasks and a completion percentage. Also further research should be conducted on how the whole experience of entity definition should be novel, what portion of it can be auto-populated, what can be auto completed and what should be the minimum time to define an entity and how it can be achieved.
Solutions
A better table
• The tabular structure is important keeping in mind the affinity of developers towards it. Removing it can hamper the productivity and familiarity for them.
• But a better tabular structure is needed.• The option to freeze a column or a row is must.• Auto adjust rows and columns to fit in large sets of information.• Segregation between each cell.• Icons to guide the user to sort information.
Solutions
Ease of use
• Features like bulk operation to edit source schema, source platform, subject area etc can enhance the productivity of the product.
• Bulk export of entities.• Further INKONIQ suggests a detailed research to understand the user’s needs as to
how the productivity of BEDROCK can be enhanced.• INKONIQ also suggests an extensive research on how this module impacts other
modules within BEDROCK, and explore the possibility of how the associated aspects of this module can be enhanced in terms of user experience.
Solutions
