Design and engineering for sharper product systems | Book a intro to start building with our squad.

Back to Work

Halo eWarga · 2024 — 2025

Halo eWarga — Civic Digital Platform

A neighborhood platform that makes civic services feel approachable — clear requests, transparent status, and trust-first design.

  • ClientHalo eWarga
  • RoleProduct Strategy, Brand & Platform Engineering
  • Timeline2024 — 2025
  • IndustryCivic / Community
Modern city buildings with soft daylight

Background

Where the project began

Halo eWarga connects residents with neighborhood services — announcements, requests, and community programs. The opportunity was cultural as much as technical: civic tools often feel bureaucratic. Dawn was asked to reshape brand and product so residents feel guided, not processed.

The problem

What we set out to solve

Forms were long, status was opaque, and the visual language looked institutional. Adoption stalled with younger residents. Administrators needed reliable tooling, while citizens needed something they would open without feeling like they entered a government portal from 2012.

Approach

How we moved

We reframed the product around life events instead of department names. Brand voice became warmer without losing authority. The platform was rebuilt with clearer request states, bilingual content patterns, and admin workflows that reduce back-and-forth between staff and residents.

Stages of work

The work journey

01/08

Scroll to move through the journey

  1. preparation

    01Stakeholder Brief

    Aligned administrators, community leads, and residents on what trust looks like in a civic app.

  2. start

    02Service Mapping

    Catalogued request types and rewrote them as resident life events, not department jargon.

  3. explore

    03Brand Direction

    Explored warmer visual directions that still feel official enough for neighborhood governance.

  4. structure

    04Flow Prototypes

    Prototyped request, status, and announcement flows in both Indonesian and English.

  5. craft

    05Admin Tooling

    Designed staff dashboards for triage, assignment, and clear public-facing updates.

  6. build

    06Platform Build

    Implemented APIs, notification hooks, and role-based access for residents and staff.

  7. finish

    07Community Pilot

    Piloted with selected neighborhoods, gathered feedback, and refined copy and defaults.

  8. launch

    08Public Launch

    Launched broadly with onboarding guides and measurable request completion goals.

Tech stack

Tools that carried the build

Chosen for reliability, speed of iteration, and fit to the product surface.

  • Next.js
  • Go
  • React
  • Figma
  • PostgreSQL
  • Kubernetes

Outcome

What changed after launch

eWarga launched with a renewed brand, simplified request journeys, and dashboards that make community operations legible. Resident completion rates rose, and administrators gained fewer ambiguous tickets to chase.

  • Completed service requests

  • ID + EN

    Bilingual system

  • −45%

    Ambiguous tickets

Services

  • Brand
  • Product Design
  • Platform