Understand the job and the constraint.
Users, evidence, business goal, technical limits and the current behavior that is creating friction.
Product design · Nepal + remote
Product design for software that has outgrown simple screens.
I help software teams turn incomplete requirements, dense workflows and inconsistent interfaces into product experiences people can understand and teams can build. The work can start with one difficult flow or extend across a larger product system.
When this is useful
Useful when the product has real states, permissions, roles, data or technical constraints and the design work needs to resolve more than visual polish.
Typical scope
- Product flows and information architecture
- High-fidelity responsive interface design
- Interactive and state-complete prototypes
- Reusable components and design-system decisions
- Developer handoff, implementation notes and UI QA
Make the product decision explicit before making the screen look finished.
Resolve flow, hierarchy and states.
Turn the problem into reviewable decisions before high-fidelity design makes ambiguity expensive.
Design for the implementation.
Responsive rules, components, interaction notes and QA make the work useful after handoff.
See the decisions in real project context.
piHub
Investment, credit, application and verification experiences organized around the information financial users need most: current status, missing requirements and the next useful action.
Read case study
Orkest HQ
A shared product grammar for CRM, Sales, Inventory and Finance, designed so the modules feel related without pretending their operational jobs are identical.
Read case study
Masteriyo
Product-design work inside an established LMS, covering course authoring, quizzes, learner states and reusable patterns that had to fit an existing system and a larger design team.
Read case study