Product Design Sprint: New Module or Design System + Prototype by Narenkumar MuthukumaranProduct Design Sprint: New Module or Design System + Prototype by Narenkumar Muthukumaran
A new feature or a messy UI, designed properly and proven in working code, in about 3 weeks. Most design work stops at Figma. I design the module, then build a coded prototype your users and engineers can actually try.
5+ years designing complex B2B SaaS: construction and BIM platforms (I designed a Takt planning module from scratch) and environmental-data dashboards with white-label design systems.
Pick one
New module: a planning view, dashboard, reporting tool or workflow, from research to final UI
Design system: tokens, components and documentation in Figma, so your team builds consistent screens without a designer in every ticket
What you get
User flows and wireframes, agreed with your team in week 1
Final UI in Figma with every state: empty, loading, error, edge cases
A coded, clickable prototype (web or SwiftUI) to test with real users
Components and handoff notes your engineers can build from
How it works
Week 1: research, flows and wireframes
Week 2: visual design and design system pieces
Week 3: coded prototype, testing and handover
Two check-ins a week. You see progress every few days, not at the end.
A new feature or a messy UI, designed properly and proven in working code, in about 3 weeks. Most design work stops at Figma. I design the module, then build a coded prototype your users and engineers can actually try.
5+ years designing complex B2B SaaS: construction and BIM platforms (I designed a Takt planning module from scratch) and environmental-data dashboards with white-label design systems.
Pick one
New module: a planning view, dashboard, reporting tool or workflow, from research to final UI
Design system: tokens, components and documentation in Figma, so your team builds consistent screens without a designer in every ticket
What you get
User flows and wireframes, agreed with your team in week 1
Final UI in Figma with every state: empty, loading, error, edge cases
A coded, clickable prototype (web or SwiftUI) to test with real users
Components and handoff notes your engineers can build from
How it works
Week 1: research, flows and wireframes
Week 2: visual design and design system pieces
Week 3: coded prototype, testing and handover
Two check-ins a week. You see progress every few days, not at the end.