X:0 Y:0 DESIGNS & SHIPS
UI/UX + Product Designer — co-running The Design Walas.
I design and build digital products that actually work for the business behind them.
SEC/02 CASE STUDIES
NeerTrack is a civic digital product designed to bridge the communication gap between Jorhat residents and their water utility — turning anxiety into awareness.
"We only knew when it was too late — the water was already gone."
— Survey respondent · Jorhat, Assam · 2025
In Jorhat — a Tier 4 city in Assam — the local water utility communicates through phone calls and outdated website notices. Residents wake up not knowing if water will come, how long it will last, or what quality it will be.
A small online survey (fewer than 20 responses) of Jorhat residents aged 30–70: working professionals, homemakers and wage workers. Findings are directional, not statistically representative.
Raw survey responses were grouped into behavioural clusters. Each cluster directly maps to a design intervention.
Synthesised from open-ended survey responses and lived experience patterns across participant types.
Personas built directly from survey demographic data and behavioral patterns.
Due to a busy schedule, he cannot manage water storage. Poor water quality means buying bottled water frequently.
Manages the entire household water routine. Irregular supply leads to frustrated mornings.
Depends on morning water supply to get ready for work. Pipe leakage makes storage difficult.
Irregular supply disrupts basic routines. Most tech-savvy persona — fastest to adopt a mobile solution.
Each persona translated into a POV, then into a design-actionable HMW question — the north stars guiding every feature decision.
Rupam struggles to get to work on time because unpredictable water supply forces him to wait without knowing how long.
Sweta is unable to complete household chores because she cannot predict when water will arrive.
Rituraj cannot trust the water quality, leading to significant extra household expense on bottled water.
Bitupan gets late to college because he has no way to check water status before his morning routine.
The goal: design a digital solution that gives residents proactive supply information, a trusted reporting channel, and enough transparency to feel in control — even when the water doesn't come.
Five existing water management platforms compared across six capability dimensions. Assessed from public product descriptions, not hands-on use, so treat it as a desk review.
| Platform | Monitoring | Leak Detect | Offline | Multi-role | Reporting | AI/Analytics | Target |
|---|---|---|---|---|---|---|---|
| WaterApp | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | Residential |
| InSemiTech | ✓ | ✓ | – | ✓ | ✓ | Limited | Municipal |
| Wamasys | ✓ | ✓ | ✓ | ✓ | ✓ | Limited | Rural |
| Shayp | ✓ | ✓ | – | ✓ | ✓ | ✓ | Buildings |
| KarIoT | ✓ | ✓ | – | ✓ | ✓ | ✓ | Govt. |
| NeerTrack (Ours) | ✓ | ✓ | ✓ | ✓ | ✓ | V2 Plan | Tier 4 Cities |
Crazy 8s ideation generated 8 distinct screen concepts. Best directions carried into feature prioritisation.
| Feature | Priority | Why / Linked Pain Point |
|---|---|---|
| Real-time outage alert | MVP | Solves the core frustration — residents miss water windows with zero notice |
| Water quality indicator | MVP | Reduces uncertainty — directly linked to Rituraj's bottled-water expense |
| Report issue + track | MVP | Creates a trusted channel — replaces unanswered phone calls |
| Weekly schedule view | MVP | Solves unpredictable timing for Rupam and Bitupan |
| Multi-language support | MVP | Jorhat is primarily Assamese-speaking |
| Plumber booking | NTH | Useful but not critical for Day 1 |
| GPS zone mapping | NTH | Requires infrastructure data first |
Four core scenarios mapped across the app — each revealing an emotional state and a design opportunity.
| Stage | Goal | Pain Point | Emotion | Design Opportunity |
|---|---|---|---|---|
| Awareness | Know water status | No information at all | Stressed 😟 | Real-time alert on home screen |
| Engagement | Check phone for update | Confusing UI elsewhere | Frustrated 😤 | Clean, focused status home screen |
| Exploration | Discover outage details | Unclear schedule display | Uncertain 😕 | Simple in-time supply schedule |
| Action | Report a leakage issue | Takes too long, no reply | Annoyed 😠 | 3-step report with photo + location |
| Resolution | Plan morning accordingly | No confirmation received | At ease 😌 | Ticket ID + status tracking |
The sitemap defines navigation hierarchy. The flow below maps the most complex interaction — reporting an issue.
Every screen moved through three stages — low-fidelity sketch, mid-fidelity structure, then high-fidelity UI — refining copy, hierarchy, and interaction at each pass.
Each decision driven by research and tested against one constraint: usable equally by a 50-year-old homemaker and a 24-year-old student.
A comparison of design intent, not of measured results. NeerTrack has not been deployed or tested with residents yet.
14 production-ready screens across the full resident journey, built in Figma with Auto Layout components and a consistent design system.
None of these are measured results. Targets come from benchmarks of comparable civic apps (NextDrop India, BWSSB Bangalore, NYC 311) and stay unvalidated until the planned usability test and a one-ward pilot.
| ID | Hypothesis | Metric | Baseline today | Target | Benchmark basis | How I'll validate | Status |
|---|---|---|---|---|---|---|---|
| H1 | If residents get a push alert 2 hours before a scheduled outage, fewer will be caught by surprise. | Residents reporting an unannounced outage in the last 30 days | Residents say they learn of outages only after supply stops (survey quotes, n<20) | 73% reduction | NextDrop India | 4-week one-ward pilot + weekly diary check-in | Unvalidated |
| H2 | If reporting takes 3 steps with an optional photo, more residents will report issues than by phone. | Reports filed per 1,000 households per month | Unmeasured (phone-only, often unanswered) | 4.2× phone volume | NYC 311 | Pilot ticket log vs. utility call log | Unvalidated |
| H3 | If every report gets a Ticket ID and visible status, issues will be resolved faster. | Median hours from report to resolution | Unmeasured (no ticketing today) | 40% faster | BWSSB Bangalore | Ticket timestamps during pilot | Unvalidated |
| H4 | If the home screen answers "is there water?" first, residents will keep coming back. | Day-30 retention | 34% (comparable-app benchmark) | 58% | Comparable civic apps | Post-pilot analytics, 30-day cohort | Unvalidated |
| H5 | A resident can find today's supply status and explain what it means. | Task completion rate | Not tested | 80%+ | Usability test protocol | 5 moderated sessions, one per persona + one cross-type | Planned |
| H6 | A resident can file a leak complaint quickly. | Time to file a report | Not tested | < 90 sec | Usability test protocol | Same 5 sessions, timed task | Planned |
| H7 | Overall, the app feels usable to both a 50-year-old homemaker and a 24-year-old student. | System Usability Scale (SUS) | Not tested | 75+ | SUS industry norm | SUS questionnaire after the 5 sessions | Planned |
Read it left to right: assumption → how it is measured → where it starts → where I think it can go → how it gets proven. If a test disproves a hypothesis, the feature is redesigned, not defended.
Formal usability testing was not conducted within this 14-day sprint — this is a documented plan for the next step.
A moderated usability test with 5 Jorhat residents — one from each persona type plus one cross-type. Sessions run 20 minutes via Google Meet or in-person.
Three core tasks:
Success metrics: Task completion 80%+, complaint filing under 90 seconds, SUS score 75+.
Anchoring every feature to a specific persona's pain point kept scope from exploding. Every feature held back from the MVP had a documented reason.
I'd run informal walkthrough tests at wireframe stage, not just at high-fidelity — flow ambiguities would surface far earlier.
The motor inequity finding turned a technical supply problem into a social justice issue — it reshaped how I framed the reporting feature entirely.
SEC/03 WEBSITES
SEC/04 EXPERIENCE
SEC/05 ABOUT
UI/UX and Product Designer holding a B.Com in Human Resource Management, which lends a commercial lens to everything I craft on screen. Co-Founder of The Design Walas, a studio delivering end-to-end branding, logos, print, websites and interface solutions for entrepreneurs and small ventures. Skilled at turning user research and company goals into functional, thoughtfully made experiences.
I use AI tools throughout my process — from generating quick visual concepts to accelerating research synthesis — while keeping creative judgment and decision-making entirely human-led.
SEC/06 SKILLS & TOOLS
Skills
Tools