ESEN
← Back to work

Case — Digital government · Chaco Province, Argentina

Tu Gobierno Digital 

The challenge of evolving a platform already used by thousands across Chaco — and making it simpler for every one of them.

Period2022 · 8 months
SectorGovernment / Digital public services
ClientECOM Chaco · Government of Chaco
ScopeUX Research · UI · Design System
Tu Gobierno Digital — main panel (v2)

The challenge 

TGD is the online services platform of the Province of Chaco — the provincial counterpart of Argentina's national citizen portal: appointments, procedures, credentials and access to state services in one place. The first version was live and in mass use, and the plan for the second stage was ambitious: new features, new services, and an experience taken to the next level. ECOM Chaco, the company that develops the platform for the provincial government, brought us in to add the specialized UX/UI perspective the team needed.

Starting point

  • A live platform with thousands of users and an ambitious roadmap of new services
  • An invaluable record — help desk, call center, operators — that hadn't yet been read through a design lens
  • An audience as heterogeneous as an entire province: from digital natives to seniors, from fiber optics to weak connections in rural areas

What the project really called for

Before drawing a single screen: understanding why some users couldn't complete their procedures. Turning existing data into design decisions, adding first-hand research with real users, and projecting a v2 worthy of everyone who uses it.

The approach

First

Research before design

The project started far from Figma: interviews with citizens, operators and developers, and a systematic reading of help desk inquiries. A detailed map of opportunities was sitting there, waiting to be read.

Then

Validate every decision with real users

Nothing was left to opinion: card sorting, guided tasks and heatmaps with actual platform users. Every iteration was adjusted with data.

What made it possible

  • Capitalizing on existing sources: the call center's topic ranking and the operators' first-hand experience
  • Designing for the least-favored user, not the average one
  • Remote testing with real TGD users (over 70% already used the platform)
  • Standing by the development team until the design reached production intact

The process

01Months 1–2

In-depth research

Interviews with citizens, platform operators and developers; a flow-by-flow review identifying where the experience needed more attention and where there was room to simplify. The key decision: capitalizing on sources that already existed but hadn't been read through a design lens — the call center's topic ranking and the reports of operators who assisted users daily.

A report for ECOM and the authorities with prioritized improvements, flows to optimize, and feature opportunities born from real needs.
Analytics and help desk inquiry ranking
Heuristic analysis of the system
02Months 3–4

Prototyping and iterative testing

New information architecture, low- and high-fidelity wireframes, responsive layouts. We designed for the least-favored user — seniors, low vision, weak connections — rather than the average one: tooltips, visual aids, tutorials and generous typographic hierarchies. Remote testing with card sorting, guided tasks and heatmaps; in every round, over 70% of testers were real TGD users.

Several iteration rounds adjusted with data, not opinions. Heatmaps confirmed the new entry points as natural paths.
New information architecture
High-fidelity wireframes
Testing: metrics, paths and heatmaps
Card sorting, conclusions and user comments
03Months 5–6

Final design and handoff

Final screens presented to the provincial government and ECOM; adjustments from the feedback round and production of the full implementation package: UI Kit, iconography, illustrations and documented Figma files.

A complete design system so the development team can implement autonomously and the platform can keep growing coherently.
Interaction specs for development
Component library
UI Kit: palette, typography and components
04Months 7–8

Implementation support

On-call support alongside the development team during implementation, resolving questions and specific needs so the design reached production without degrading.

V2 in production, faithful to the user-validated design.
Mobile views — v2

The shift

Before

Identity validation — the step that unlocks every procedure — was reached through My Profile → My Validations, a path few users discovered on their own.

After

“Validate your account”: a banner on the main panel with a guided process. Heatmaps confirmed it as the new natural entry point.

The same criterion ran through the whole platform: a reordered menu, clearer names, and key actions in plain sight — where users are already used to finding them.

The impact

The number

  • –56% in call center inquiries about procedures users couldn't find, in the months after launch. Support shifted its focus to account creation and specific cases.

An experience for everyone

  • Flows redesigned and validated with real platform users
  • A lightweight interface mode for weak connections: no one left out by their bandwidth
  • Tooltips, tutorials and visual aids built for the heterogeneity of an entire province

A system that keeps growing

  • Complete design system (UI Kit, icons, illustrations, documented Figma) for autonomous implementation
  • A document of future improvements and modules that mapped the path for the next version

Services provided

UX Research (interviews, card sorting, user testing)Information architecturePrototyping (low- and high-fidelity wireframes)UI Design (desktop + mobile)Design System (UI Kit, iconography, illustrations)AccessibilityHandoff and development support

Timeline

Apr–MayResearch: interviews, flow audit and call center analysis
JunImprovement report for ECOM and the authorities — first delivery
Jul–AugNew architecture, wireframes and first testing rounds
Sep–OctFinal design: presentation to the provincial government and adjustments
NovValidation testing on v2 and final delivery: UI Kit, Figma, assets
Dec–JanSupporting the development team through implementation

Key learnings

The call center is research

The ranking of support topics was an exact map of where to focus the design effort.

Design for the least-favored user

Solving for the weakest connection and the least digital user improves the experience for everyone.

Test with real users, not generic ones

Having over 70% of testers already using TGD changed the quality of the findings.

Handoff doesn't end at delivery

Standing by the devs is what guarantees the design reaches production alive.

Has your product outgrown its user experience?