Elisabeth SaehrProduct designer, Lausanne
Pro Juventute × Women++ · Hackathon · 2023

One panel to enter a KPI. One screen to see progress.

Pro Juventute, the Swiss foundation for children and young people, tracked goals that can’t be measured automatically in a spreadsheet. In a six-sprint hackathon, our team built an app to replace it. As one of the two UX/UI designers, I worked on the user flows and the charts, and shared the screens and the design system with the design lead.

Role
UX/UI designer, working with the team’s design lead. Mine: user flows, chart design. Shared: screens, prototypes, the design system.
Timeline
September → 4 November 2023 · six one-week sprints, then a demo to a jury
Team
Product manager, Scrum master, two UX/UI designers, a data scientist, two full-stack developers
Research
Two personas from the client’s brief · journey maps · user flows · information architecture · no user tests
The thread through this page. An economist in the Fundraising team enters October’s private donations. The same value then shows up in the activity log and in the organisation-wide overview, further down. Redrawn from the team’s screens. All figures are demo data, not Pro Juventute’s.

In 30 seconds

2ndof 10teams in the final ranking of the programme.
6one-week sprints, from the brief to a demo in front of the jury.
11features working in production at the end, from single sign-on to the activity log.
2personas given by the client: the person who enters the numbers, and the one who defines them.
Problem

Many of Pro Juventute’s goals can’t be measured automatically. Each team entered its numbers by hand in a shared spreadsheet: errors at entry, and a file that was hard to maintain.

What I did

Mapped one flow per persona, designed the charts, and shared the screens, prototypes and design system with the design lead. Two design decisions on this page are mine.

Where it stands

Demoed on 4 November 2023, with eleven features in production and three more as Figma prototypes. Ranked 2nd of 10 teams.

The problem

Goals you can’t measure automatically end up in a spreadsheet

Pro Juventute sets goals for each of its internal teams, which it calls circles: Fundraising, HR, Digital, Programmes. Some numbers come out of a system. Many don’t: someone has to type them in, every month. The brief asked for an open-source app that would make that entry easy, keep the data clean, and show the progress.

KPIs_2023_final_v3.xlsx
CircleKPIUnitJulAugSepOct
FundraisingPrivate donationsCHF69’00092’000105’000
FundraisingAdditional monetisationCHF24’50025’10025.000
HRInvoluntary headcount change%1.41.31.2
HRShort-term leave%2.90.0313.0
DigitalNet promoter scorescore313334
ProgrammesReachcount—12k12’400
ECTeam economist
Does
Enters the KPI values for their circle, at most once a month.
Pain
Confusion and errors when entering data.
Needs
A straightforward way to input values.
GKGatekeeper
Does
Defines and maintains the KPIs, and looks after the tool.
Pain
The effort of maintaining the current spreadsheet.
Needs
Data they can trust.
Both personas came with the client’s brief
Where the numbers lived. An illustration of the problem, not the client’s file: units mixed in one sheet, one person’s comma is another’s point, and October still empty. The yellow cells are the kind of entry errors the brief describes. Demo values.

Two people, two jobs. One types a number once a month. The other has to make every number mean something.

Research

No interviews, so we built on the brief

The client arrived with a well-defined problem and two personas. In six weeks there was no time to meet real economists or gatekeepers, so we treated the personas as a starting hypothesis and worked from there: journeys, flows, then structure.

2personas, given by the client: the team economist and the gatekeeper.Client brief
2journey maps, one per persona, to see where each one gets stuck today.Design lead
2user flows, one per persona, to decide which screens to design first.Mine
1information architecture for the whole app, with the out-of-scope features marked for later.Design lead
9months of real data in 2023. The data scientist generated a synthetic history so the charts could be tested.Data science
0user tests. The two prototypes, one per persona, were not tested with users.To do next
KPI app · single sign-on
OverviewBoth
Own circle’s KPIs, progress, yearly target
All circles, for the gatekeeper
Insert KPI valueEconomist · from every page
KPI, period, value
Edit a past value
ActivityBoth
Who changed what, and when
Report for a period
Gatekeeper toolsGatekeeper
Create a KPI: unit, periodicity, baseline, target
Circles and users
LaterOut of scope
Import from the data warehouse
KPIs shared between circles
Links to project tools
EconomistPrototype 1
Sign in→Overview→Insert KPI value→KPI · period · value→Save→See it in Activity
GatekeeperPrototype 2
Sign in→All circles→Create a KPI→Set baseline and target→Review KPIs, users, circles

One action for the economist, one overview for the gatekeeper. Inserting a value is not a section of the app: it is reachable from every page.

The structure and the two flows, redrawn. The information architecture is the design lead’s; the two user flows are mine. The dashed items were out of scope for the hackathon.
Key decisions

Two choices I made

Both come from the brief: the economist’s errors at entry, and the gatekeeper’s need for numbers they can trust. The team’s other choices are listed after them.

Decision 1 My decision

Enter a value without leaving the numbers.

Chose
A yellow “Insert KPI value” button in the header of every page. It opens a side panel with three fields (KPI, period, value) over the dashboard the economist is already looking at.
Rejected
A separate data-entry page, reached through the menu, away from the charts the value feeds.
Because
The economist comes in once a month for one job. Their pain is confusion and errors at entry. Keeping last month’s figures visible behind the panel gives them something to check the new value against, and the button never has to be looked for.
Rejected · separate page
OverviewActivityData entry
Data entry › New value
New KPI valueCircleKPIPeriodValue
Last month’s figures are on another page.
Chose · side panel over the dashboard
OverviewActivity+ Insert KPI value
Insert KPI valuePrivate donations ▾October 2023128’400Save

The circle is known from the login, so it isn’t asked. Three fields instead of four, and the context stays on screen. Both redrawn for this page; the rejected option is a reconstruction.

Decision 2 My decision

Show how far each KPI is from its target, not just its total.

Chose
Progress from the KPI’s baseline to its target, from 0 to 100%, the same way for every KPI. One colour per circle, so the gatekeeper can compare circles on one screen.
Rejected
The first dashboard screens: a card with the raw value for each KPI, a monthly trend, and a yearly target only for donations.
Because
The data scientist’s analysis showed the KPIs share no unit: francs, percentages, counts, a score from −100 to 100. Some succeed when they go down, like involuntary headcount change. Raw totals can’t be compared or added up; progress can.
First screens · raw values
Private donationsCHF128’400
Net promoter score34
Involuntary headcount change1.2%
On track? Ahead of last year??
Final · progress to target
Private donations61%
CHF 0CHF 1.6 m
Net promoter score58%
2044
Involuntary headcount changelower is better80%
3.5%0%

Same three KPIs. On the left you need to know each one’s target by heart. On the right, every bar reads the same way, whatever the unit or the direction. Demo values; baselines and targets as the team defined them for the prototype.

Team decisions I worked within

Not mine alone, but they shaped every screen

The client’s own brandYellow, Montserrat and a 12-column grid, taken from Pro Juventute’s corporate design so the tool would feel familiar inside the organisation. Purple for contrast, red for errors.Design system · built with the design lead
An activity log for every changeWho entered or edited which value, and when. The brief asked for traceability; for the gatekeeper it is what makes the numbers trustworthy.Brief requirement · whole team
Tooltips on every KPI fieldWhen a gatekeeper creates a KPI, each required field (name, unit, periodicity, baseline, target) explains itself on hover. The fields and their definitions came from the data scientist’s analysis.Brief requirement · design and data
What didn’t work

Two designers, and no line between our jobs

On paper there was a design lead and a second designer. In practice the roles were never set out: we both did a bit of everything.

It also made it harder, afterwards, to say exactly who did what. The table below is my best honest split.

Design workMeDesign lead
Information architectureLead’s
User flows, one per personaMine
Chart designMine
Design systemSharedShared
Journey mapsLead’s
Screens and prototypesSharedShared
Who did what in design. Yellow: mine. Striped: shared. Grey: the design lead’s.
What I’d do differently

Agree in the first sprint who owns which deliverable, write it on the team board, and revisit it at each retrospective. Even in a team of two designers, a clear split saves time and makes each person’s work visible.

My part, and everyone else’s

A full product team in six weeks

Pro Juventute brought the problem as product owner. Women++ ran the programme and the sprints. Our team designed, built and documented the app in one-week sprints, with a demo to a jury at the end.

  1. Brief and kick-offTwo personas from the client
  2. First screensSign-in, activity, the input panel, the first dashboard
  3. Overview for all circlesProgress to target, chart explorations
  4. App handed inCode, documentation, licence
  5. Demo and ranking2nd of 10 teams

What I did

  • User flows for the economist and the gatekeeper, used to choose which screens to design first.
  • Chart design: how each metric looks, from the monthly trend to the progress per circle.
  • Screens and prototypes, shared with the design lead.
  • Design system, built with the design lead: colours, type, grid, components.
  • The input panel and progress to target, the two decisions above.

What the rest of the team did

  • Design lead: led the design work, with the journey maps and the information architecture; screens and prototypes shared with me.
  • Product manager and Scrum master: planning, the sprints, the link with the client.
  • Data scientist: data analysis, the progress and performance metrics, the synthetic data, chart specifications.
  • Two full-stack developers: single sign-on, back end, front end and deployment.
DigitalFundraisingHRProgramProgramsProgram
Average progressAll circles together, against their targets.
Overall target · per KPIOne wedge per KPI, in shades of its circle’s colour.
Overall target · per circleOne ring per circle. A full ring means the target is reached.
Progression by monthCumulative progress, stacked by circle.
Circle activity · linesEach circle’s progress month by month.
Circle activity · streamThe same activity, as one flow across the year.
The charts I designed for the gatekeeper’s overview, redrawn from the design file with its colours: one per circle, and the KPIs of a circle in shades of it. The values are demo data. The circle labels are as in the file.
Results

2nd of 10 teams, with a working app

The October value from the hero, as the rest of the organisation sees it: a new line in the activity log, and a step forward for Fundraising in the gatekeeper’s overview.

ActivityOctober 2023
KPICirclePeriodValue
Private donationsFundraisingOct 2023CHF 128’400
Additional monetisationFundraisingOct 2023CHF 26’000
Short-term leaveHRSep 20233.0%
Net promoter scoreDigitalSep 202334
KPI overview · all circles
Circle: All ▾This year ▦
64%
Fundraising+8 pts61%
HR72%
Digital58%
Program66%

Average progress of all circles in the ring. Demo data.

Working in production on demo day · 11

Single sign-onInsert a KPI valueEdit a valueCreate, edit, delete KPIsTargets per KPIProgress for each circleProgress and performance, all circlesRadial progress chartActivity logProfile with change historyTooltips

Designed in Figma, not built · 3

Notifications and monthly remindersResponsive screensExport to PDF, CSV, Excel

From the team’s documentation of the minimum viable product and what comes after it.

Open the team’s Figma prototype ↗
Programme participants gathered in an office space at night, many waving or raising their arms, in front of a yellow honeycomb wall.
The closing ceremony, 4 November 2023, with the programme’s participants. Photo published by Women++.
How the ranking worked
  • Women++Implementation and learnings, judged over the six sprints.
  • The juryPitch, product, design and innovation, judged on the demo on 4 November. Design covered look and feel, but also whether the experience is intuitive and the flow makes sense.
2nd of 10teams in the final rankingWomen++ and jury
11 + 3features in production, plus three designed in FigmaTeam documentation
0user tests: the design is a strong hypothesis, not a proven oneNext step
What I’d do next

Where I would take it

The hackathon ended with the demo. These follow from what we left untested or unbuilt.

  1. Watch five economists enter a month’s valuesThe input panel has never met a real user
  2. Check that gatekeepers read “progress to target” as intendedEspecially for KPIs where lower is better
  3. Build the monthly reminderDesigned in Figma, it is what brings economists back
  4. Validate values at entry against last monthA warning for a value ten times too big or too small
What I learned

Three lessons

Agree on roles in week one, even with two people.

A design lead and a second designer still need a written split. Without it, work overlaps and each person’s part becomes hard to show.

A number means little without its target.

Once the KPIs didn’t share a unit, the real design question was not which chart to draw but what to compare. Working closely with the data scientist answered it.

Personas from a brief are a hypothesis.

They were well defined, and they let us move fast. But nobody on the team ever watched an economist enter a value. That is the first thing I would change.

Pro Juventute × Women++ · September–November 2023 Next: Symio →