PROJECT 1 - UX Writing
Language Simplification &
Iconography Integration in Etality
Project Overview
This UX writing project was for Etality, a SaaS product focused on process automation and management.
The initial challenge included simplifying the language throughout the tool’s navigation system. When I joined, the terminology used was highly technical and code-based, creating a barrier for users.
Approach
The workflow was designed on the basis of a lot of assumptions.
Without a designer in the company, the tool had many problems:
• The language used was very technical
• The terms used lead to different actions
Using FigJam allowed me to carefully plan each step before diving into the project, keeping me organised and focused throughout the entire process
User Interviews and
Usability testing
Market research
Competitors' analysis
To gain insights into market standards, I collaborated with the business team to conduct market research. We analyzed tools like Zapier, Microsoft Power Automate, Automate.io, and Appian to understand why users preferred certain tools over others and to explore the common language used in these platforms.
Similar Navigation and Technical language :
While we found many similarities in their navigation systems, the language used was often highly technical, making it difficult for users to learn. For instance, Power Automate had a particularly steep learning curve.Limitations of Onboarding Systems : Some of these tools offered onboarding systems, but they were not very intuitive and only covered basic features.
Accessibility Barriers : Additionally, many tools weren’t easily accessible, requiring a demo call just to get familiar with them.
User Problems Findings
During my initial research into the software, I quickly noticed that the language used throughout the tool was highly technical, filled with code-specific terminology
To validate my concerns, I conducted usability testing, which confirmed that this technical language contributed to a poor user experience. These are the most common issues that surfaced during the testing sessions:
Confusing & Misleading Terminology Leading to Navigation Issues
Many users struggled to navigate the tool due to unclear and confusing feature titles. Several terms were unfamiliar, and in some cases, the wording led to actions that were different from what users expected, making the experience misleading.
For example:
• ‘Boolean’
• ‘Value Type’
• ‘Trigger’ was labeled as ‘Requirement’
• ‘Requirement’ was labeled as ‘Validation’
Disorganised Navigation & Lack of Clear Hierarchy
There was no clear hierarchy of information or actions, making navigation feel disorganised.
Elements were scattered across the interface, leaving users unsure of where to go next.
Navigation Complexity, Leaving Users Uncertain on Workflow Creation
Because of placement of many icons and buttons, users' had hard time creating a flow as they could not find the button to create workflow.
Design Sprint
To tackle the challenge, I organised Design Sprint with the team of Developers frontend and backend, Business and Product owner.
This was also a great chance to teach the team about the importance of design thinking and user research.
Things I concentrated on:
Understanding the problem : I had all problems from the user that were observed during the research on the white board on post its
Agenda defined: I clear agenda on what to expect and how much time to spend on each stage was defined to already establish a an awareness of a clear process and exclude any confusion.
HMW and Brainstorming: After going through all the problems and talking about each of the post-it and clearing the reasons and situations of these problems, we started with HMW statements. Each member of the sprint was given post-its to write down their How might we statements next to the problem. We had a cluster of HMW post-its at the end, which initiated brainstorming over all the possibilities.
Crazy 8: To visualise the possible solutions, each team of 2 were asked to create 8 ideas. The most voted ideas were chosen to be sketched as low-fi.
Solutions and Results
Functionality You Will Love
01
Language Simplification
Explain how you transformed the technical jargon into everyday language, followed by testing to ensure comprehension. Highlight the positive feedback from users on these changes.
In Etality, we transformed the technical jargon into everyday language. After conducting multiple usability sessions and analysing the data collected, the language was changed to ensure users understand the meaning of actions and buttons. The language change was followed by more testing sessions to ensure comprehension.
These sessions were a success.
02
Iconography Integration
Discuss the introduction of icons to complement certain terminologies, addressing the residual confusion found in usability testing.
Durning many Usability sessions, we found out that many users were confused about few terminologies. They knew the visual interpretation of those words instead of the technical term.
For instance a toggle, many users did not know what a toggle is. But when shown an icon, they recognised what the icon means and what it can do.
Hence, we decided to include icons with the text, so it becomes more clear for users what the word entails, with an added benefit of users learning the tool's language along with the icons.
03
Navigation System Overhaul -
Redesign the dashboard and
process creation system
Redesign of the tool's navigation architecture to enhance user experience.
Coming up —>