Case study · Workforce housing · 4 min read

Manzl: running workforce housingat scale, validated before built.

A role-based admin platform and an Android resident app for India's migrant workforce.

Altstar Research → Design 4 weeks → UAT Web + Android
The problemA client wanted a feature-rich app for migrant workers. Nobody had spoken to a worker yet.
What I didPaused the build, ran 4 weeks of field research and a 2-day co-creation workshop with the client.
The resultMost of the brief got cut. A smaller, sharper MVP moved into UAT with a co-owned 3-6-9 month roadmap.
01 · The brief

They'd built the ecosystem. They needed to run it.

Altstar already had housing, food, transport and services for migrant workers in place. They asked for a role-based admin web app and a worker mobile app to coordinate a workforce that was "highly fragmented and difficult to coordinate."

Worker housing building
02 · The turning point

Were we solving real problems, or designing against assumptions?

No ground validationNobody had spoken to a worker or operator.
An unknown userDid workers even use smartphones?
An over-built feature setElegant in a deck, wrong for low-literacy users.
The call: stop, and validate before we scale. Altstar's leadership agreed.
03 · Into the field · Weeks 1–3

The field contradicted the brief.

Site visits and phone interviews across 7 cohorts, plus a competitor scan (Civeo, Tikaana, ARHCS) that showed transport and meals were the real differentiators in industrial housing.

Blue-collar workers Supervisors & foremen Facility managers Business owners HR managers Vendor managers Altstar stakeholders
"What we require is a place that they can lie down, with common bathroom/washroom facilities. All other requirements are additions…"
- a business owner, on what workers actually require
Workers needA clean place to sleep, working washrooms, drinking water, decent food, fair wages.
Managers struggle withManual attendance, leave and reporting. "Next-day prep depends on memory."
Digital habitsWhatsApp, yes. Service apps, no. Calls over forms, cash over UPI.
Field research photos
04 · Co-creation

A 2-day workshop that made the client co-author the direction.

Day 1 · Mapping the presentAs-Is journeys for workers and managers. Altstar added their own pain points and we defined the worker MVP.
Day 2 · Designing the futureTo-Be journeys, then a group exercise to prioritise features into a 3-6-9 month roadmap.
3 MonthsWhatsApp integration, language selection, complaints, live occupancy, onboarding
6 MonthsQR feedback, meal & transport planning, utility billing, vendors
9 MonthsDocuments, finance & accounting, procurement HRMS
Workshop photos
05 · Four decisions

One discipline: need over nice-to-have.

WhatsApp first, not an appWorkers trusted WhatsApp and little else. A chatbot meant zero install and zero learning curve.
Then one native app that scalesGrey-collar workers needed more. After a second interview round: one app for blue- and grey-collar, with WhatsApp logic as its simplest tier.
Cut most of the briefThe decision I'm proudest of. Every cut feature would have been built, maintained and ignored.
A role-based platform, not a dashboardTenants and facility managers each see their slice: who's in, what's broken, what needs a decision now. Responsive, because managers were rarely at a desk.
Brief proposedPersonal finance hubHealth records & appointmentsGamified trainingAmenity bookingLive GPS bus tracking
MVP shippedMeal schedule + opt-outTransport timingsSupport ticketsNotificationsVisitor & parcel pre-approval
06 · The product

What we designed

Dashboard
Food management
Campus map
Dashboard · Food management · Campus map
07 · Where it landed

Altstar walked away building the right thing.

Android resident appBridges blue- and grey-collar users.
Role-based web appManual firefighting to real-time monitoring.
3-6-9 month roadmapOwned by the client, not imposed.
Where AI helped
Refining interview questionnaires Synthesising recorded sessions Rapid UI during the workshop Edge cases & UX writing
What I took away 01Observation beats assumption, especially for users unlike you. 02Co-creation isn't a nicety, it's how you kill rework. 03An MVP earns adoption when it maps to real needs, not feature ambition.
Next project
02 · Healthcare · Mobile appMedEasy