Tallyfy is a SAAS workflow management platform.
Role: I was the sole product designer working cross functionally with the product owner and engineers.
Timeline: 3 Weeks
Tools: Figma, Figjam, Whiteboard and pen & paper.
.gif)
🎯 User understands task priorities.
📨 Quick access to important information.
🕹️ Easy navigation between tasks.
🖨️ Easy to find print option on the page.
🪢 User understands task dependencies.
👍 Quick access to dependent tasks.
🚦 Prioritize important actions first.
🖇️ Easy to understand automation conditions.
The current layout of the read-view is difficult to understand and lengthy.
The current layout is not optimized for print or read view, to make it more understandable and actionable.
.gif)
Customers have difficulty locating the print option within the page.
The old design had various usability issues like improper navigation, information layout, hard to find print option and failed on various heuristics like visibility of system status, mismatch between the system and real world, and efficiency of use.
The automations section in the view helps users understand task dependencies and priorities. The current layout of automations had various issues making it unfit for printing and sharing in a document format.
1. Understand Task Dependencies Easily:
Enable users to quickly comprehend which tasks are dependent on the current step.
2. Print and Share eSOP Documents : Users needed to be able to print and share the eSOP documents easily.
.gif)
3. Prioritize Important Tasks: Users needed to understand which tasks are more important and what their priorities are.
4. Navigate Long Processes Efficiently: With some processes having 20+ steps, users needed an easy way to navigate through the entire process.
.gif)
5. Comprehend Task Details and Responsibilities: Users needed to clearly understand what each task entails and who is responsible for it.
6. Access Information in a Compact, Digestible Format: eSOP view to be shorter and more concise, avoiding long, cluttered documents.
of users found the identifiers confusing.
Found it tough to understand the symbols used.
of the users felt the design was bloated.
.gif)
Designed components to represent identifiers that are easy to understand ensuring match between the system and the real world.
Reversed the if-then statement and only show the if conditions since that is what highlights task dependencies to make it actionable.
This change made it easier for users to understand task dependencies, especially in processes with multiple automations, without compromising print-friendliness.
This experience taught me the importance of questioning existing design patterns. Just because some UX patterns are common in web interfaces doesn't mean they're suitable for all contexts, especially when considering cross-media compatibility like printing.
This saved development time and resources while ensuring our final design was intuitive for our target users.
Even simple, low-cost user testing can provide invaluable insights. It's a reminder that as designers, we should always validate our assumptions with real users, no matter how clever or innovative our ideas seem.
By removing clutter and focusing on essential information, we've made the eSOP view more efficient for users, especially those dealing with processes that have 20+ steps.
Sometimes, the best design solution is not adding more, but taking away. Simplifying the layout not only improved usability but also helped us stay aligned with tech constraints.
Mobile UX
Data analytics
Data driven process leveraging analytics to improve the error resolution within the payments flow in the money transfer app.
