At INZMO, we are on a mission to make insurance more user friendly, hassle-free, and transparent.
I work closely with the founding team to innovate and design solutions that bring business success, unblock challenges, and facilitate a good, high-quality, understandable, delightful, and beautiful product experience.
What I'm working on lately: Aegis – INZMO's unified design system INZMO Rental Deposit Guarantee product ( 9+ months ) Design of the new web app – the most exciting work here is to humanize forms. 🤩 Workflow process refinements
I've also worked on: New branding direction (under works) Product revamp art direction (under works) Improved communication across the product Landing page improvements using the existing stack Claims flow improvements (Massive impact on business and support team) Sales demos (Presentations and videos) New product launches: Amazon, Re-selling, Sales Core Values, Mission, Vision All INZMO emails Partner portal, Claims portal Anti-fraud improvements Introducing the design function at INZMO
<aside> 💡 As the only designer in an early-stage startup, I'm always wearing multiple hats, sometimes zooming-in to craft details or push pixels and sometimes zooming-out to strategize and plan our alignment with the bigger picture to realize the company's mission.
Applying the best workflow and team management processes helps me to deliver with speed without compromising on the quality.
</aside>
These help me to remove friction and confusion at work, and to ensure what we ship is meaningful with the highest quality.
Roadmap planning with product leads and founding team
The usual roadmap and planning structure
planning when stakes are high and time is short
We follow a workflow plan and maintain the artifacts under Confluence, Jira, and Figma. Every new requirement, be it a design initiative or a problem coming from business, support, or from internal teams – we create "Problem analysis doc" rather than "Business requirement doc – Design x to solve y"
<aside> 📃 Problem analysis Context (Eco-system info) Problem Stakeholders Platform Supporting data Status quo (Flow charts/IA/Screenshots) Open questions Next steps Timeline Constraints Goals Opportunity areas Priority
</aside>
<aside> 📃 Product and tech analysis What problem are we solving and why (As agreed with stakeholders) Goal Who is it for Solution Hypothesis Jobs to be done with a release plan Design, Content, and Tech stack Priority Success Metrics
</aside>
<aside> 📃 Research and synthesis Top insights Ask why 3 times ****HMWs Opportunity
</aside>
<aside> 📃 Discovery Artifacts Status quo Qualitative / Quantitative data Competitive analysis Moodboard/Inspirations Ideas/Concepts
</aside>
<aside> 📃 Design Proposed solution Design rationale States User flow Prototype User stories / Jobs to be done Scaling up States Testing records What success looks like / Metrics to be tracked
</aside>
<aside> 📃 Hand-off Meeting notes Specifications Breakpoints/Viewports Interaction states Transition states Success and fail states Content limitations and handling Jobs to be done Prototype
</aside>
<aside> 📃 Retrospective We use an external tool, but plan to maintain retro under project directory
</aside>
<aside> 📃 Performance We share this in monthly all hands and slack
</aside>