Svitlo

UX case study · Concept project · 2026

Svitlo

Designing a calm, confident companion for millions of people who plan their day around when the lights go out: outage schedules, battery runtime and smart tips in one glance.

Role
Lead Product Designer
Timeline
8 weeks
Team
1 designer, 1 PM, 2 engineers, 1 researcher (part-time)
Tools
Figma, FigJam, Maze, Claude

02 — Problem

Light is scheduled.
Life isn't.

Since attacks on Ukraine's energy grid began in 2022, rolling blackouts have become part of daily life. Grid operators publish schedules by "queue" or group, but they change often, arrive through a mix of channels, and leave the hard maths to households.

People don't just want to know if the power is on. They want to know what to do about it: when to cook, when to charge, whether the power station will last the night. Our job was to turn a stressful puzzle into a two-second glance.

  • 4.2

    Sources checked per day

    Operator websites, Telegram channels, screenshots from neighbours. Schedules conflict and go stale within hours.

    Survey, n = 340

  • 71%

    Can't estimate runtime

    Owners of power stations couldn't say how long their battery would last with their actual devices plugged in.

    Survey, n = 340

  • 58%

    Missed a charging window

    In the previous week, more than half had a device die during an outage they "knew was coming".

    Survey, n = 340

03 — Research

Listening before drawing.

Three weeks of mixed-method research across Kyiv, Kharkiv, Lviv and Odesa, run remotely and, more than once, by candlelight.

  • 12

    In-depth interviews

    45-minute calls with renters, homeowners, parents and pensioners. Diary follow-ups with 5 of them over one week.

  • 340

    Survey responses

    Distributed via community Telegram chats. Questions on habits, tools, battery ownership and trust.

  • 9

    Products audited

    Operator apps, schedule bots, power station companion apps and weather-style widgets.

Key insights

"I don't need the whole table. I need one sentence: when does it go off, and how long."

Insight 1 — Answer first. The schedule is a means; the next change is the answer.

"My EcoFlow says 3 hours. Then I plug in the heater and it's 40 minutes. I never know."

Insight 2 — Runtime is personal. Battery estimates must reflect real devices, not lab numbers.

"Every alert at 3 a.m. feels like an air raid siren. I muted everything."

Insight 3 — Calm is a feature. In a country of sirens, notifications must earn their place.

"My mum just calls me to ask. I am her outage app."

Insight 4 — Families share. People check on parents' addresses as often as their own.

Uncertainty

"Is it the 2nd or 3rd queue today?"

Schedules change after 22:00

Screenshots get outdated

Battery anxiety

Doesn't trust the % shown

Unplugs fridge "just in case"

Wants hours, not watts

Planning rituals

Cooks dinner at 16:00

Laundry only in green blocks

Charges everything at night

Care & sharing

Checks parents' address daily

Forwards schedule to building chat

Wants alerts for grandma

Affinity map: 214 notes from interviews and open survey answers, clustered in FigJam. Four themes, shown here with representative notes.

04 — Personas

Two people, one question.

Built from interview patterns, not demographics. Both ask "when?" but need very different answers.

Olena, 34

Remote UX writer · Kyiv, 9th-floor flat · Power station 1 kWh

"I schedule my calls around the outages. If my laptop dies mid-meeting, I lose the client."

Goals

  • Work 8 hours without interruption
  • Know exactly when to charge
  • Keep the router alive

Frustrations

  • Three Telegram channels, three answers
  • Battery % feels like a guess
  • Lift stops with the power

Tech-savvyPlannerDaily user

Mykola, 61

Retired engineer · Kharkiv, private house · Generator + small battery

"I understand the grid better than the app does. I just want big numbers and no nonsense."

Goals

  • Keep the boiler pump running
  • Plan generator fuel
  • Reassure his daughter in Lviv

Frustrations

  • Small text, cluttered screens
  • Too many notifications
  • Apps that need accounts

Low patience for UIAccessibilityShared with family

05 — Journey map

A day around the outage.

Olena's current-state journey on a day with two scheduled outages. The emotional low isn't the blackout itself; it's the uncertainty before it.

1Morning check

2Plan the day

3Before outage

4During outage

5Power returns

Doing

Opens 3 Telegram channels, compares group 3.2 schedule

Moves client call, plans cooking around the green block

Rushes to charge laptop, phone, power bank

Runs router + laptop on the power station, watches %

Re-checks if the evening schedule changed

Thinking

"Which one is right?"

"Do I have time for laundry?"

"Did I forget something?"

"Will it last until 22:00?"

"Okay. Again at 18:00?"

Feeling

Emotion curve Emotion is neutral in the morning check, improves slightly when planning, drops sharply before the outage, stays low during it, and recovers with relief when power returns. Confused In control Anxious Tense Relieved

Pain points

Conflicting sources

Mental maths on timings

No reminder at the right time

Runtime unknown

Silent schedule updates

Opportunity

One trusted source, answer on launch

"Good time for…" suggestions

Smart tip 40 min before

Live runtime by device

Quiet "schedule changed" diff

06 — Information architecture

Zero taps to the answer.

The home screen is the answer to "when is the next outage?". Everything else is one level deep. Onboarding asks for an address only; the battery is optional and can be added later.

Svitlo information architecture and primary user flow Onboarding goes Welcome, Enter address, Detect group, then optional Add battery, leading into the Today home screen. A push notification also deep links to Today. Today branches to four sections: Schedule (week view, change alerts), Battery (devices, runtime calculator), Tips (charge now, plan the outage) and Settings (addresses and family, notifications). ONBOARDING · 60 s Welcome Enter address Detect group Add battery (optional) Today (home)status · next change · tip Push: outage in 40 min Schedule Battery Tips Settings Week view Change alerts Devices Runtime calculator Charge now Plan the outage Addresses & family Notifications Entry / answer screen Navigation Deep link from notification Optional step
Validated with a 24-participant tree test in Maze: 92% found "runtime with my devices" on the first try (up from 58% with the earlier 5-tab structure).

07 — Ideation

Three directions, one survivor.

I sketched 20+ home-screen concepts, then narrowed to three and tested them as paper-fidelity prototypes with 6 participants.

Chosen

A · Status-first timeline

One big sentence ("Outage in 40 min"), a 24-hour bar, and a single contextual tip. 6/6 participants answered "when is the next outage?" in under 5 seconds.

Rejected

B · Calendar grid

Felt familiar, but turned the answer back into a puzzle: users had to locate "now" and count blocks. Unreadable at Mykola's preferred text size.

Rejected

C · Chat assistant

Natural for complex questions, slow for the frequent one. Needs connectivity at the exact moment it's least reliable. Kept as a future "Ask" feature.

08 — Design system

Warm amber light in the dark.

Dark by default: it saves battery on OLED screens and is easy on eyes in an unlit flat. Status colors carry meaning, always paired with text or shape, never color alone.

Color tokens

  • --amber-400#FFB81F · Primary light
  • --amber-600#C97A04 · Pressed
  • --ink-950#0B0C0F · Background
  • --ink-800#1F232C · Surface
  • --ink-400#8A91A1 · Muted text
  • --green-500#22C55E · Power on
  • --red-500#EF4444 · Outage
  • --blue-500#3B82F6 · Possible outage
  • --violet-500#8B5CF6 · Battery

Type scale · Inter Tight

  1. DisplaySvitlo
  2. 3XLOutage in 40 min
  3. 2XLPower on until 18:00
  4. XLCharge your laptop now
  5. MDRuntime estimate is based on your devices.
  6. Mono00 · 06 · 12 · 18 · 24

Components · live

Open prototype
Power on Outage Possible
Power station 78% · ≈ 5h 20m at 140 W

09 — Final UI

The answer, before the question.

Every screen leads with a sentence, not a table. Detail is always one tap away for people like Mykola who want to check the maths.

17:20Obolon · 3.2

Right now

Power on until 18:00

Outage in
40 min

0006121824

Charge laptop now

Outage in 40 min · 62% left

Power station

78% · ≈ 5h 20m

  1. Status as a sentence

    "Outage in 40 min" is read in under 3 seconds. Countdown switches to a clock time when more than 3 hours away, to reduce anxiety.

  2. 24-hour bar with a "now" marker

    Green, red and blue blocks plus a striped pattern for "possible", so the bar still works for colour-blind users.

  3. One smart tip, not ten

    Tips are ranked by urgency and only one is shown. It appears 40 minutes before an outage, when charging still makes a difference.

  4. Runtime in hours

    Calculated from the devices you've added, updated live while on battery. Watts live one tap deeper.

18:05Battery

Running on battery

4h 55m
left

74%
  • Router12 W
  • Fridge90 W
  • Laptop38 W
  • Kettleoff
Battery: live runtime with the devices you're actually running.
09:00Schedule

This week

Updated 08:42 · 1 change

Mon
Tue
Wed
Thu
Fri
Sat
Sun

Thursday changed

Outage moved 16:00 → 18:00

Schedule: the week at a glance, with quiet change summaries.
Web dashboard for desk workers: the week and the battery side by side. Same components, wider canvas.

Before / after

The first clickable prototype (left) mirrored the operator's table. The final design (right) answers first. Drag the handle, or focus it and use the arrow keys.

10 — Usability testing & results

From puzzle to glance.

Two rounds: moderated sessions with 8 participants on the v0.3 prototype, then unmoderated Maze tests with 46 participants on v1.0. Same five tasks, same script.

  • Task success rate

    94%

    from 62% in round 1

    From usability testing

  • Time to answer "when is the next outage?"

    3s

    from 18 s median

    From usability testing

  • System Usability Scale

    86/100

    from 64 ("OK") to "excellent"

    From usability testing

  • Fewer missed charging windows

    −41%

    2-week diary study, n = 14

    Projected from diary study

What changed between rounds

  • Countdown vs. clock. Participants preferred "in 40 min" for near events, but found long countdowns ("in 7h 12m") stressful, so we switch to clock time beyond 3 hours.
  • Striped "possible" blocks. 3 of 8 participants misread blue as "power on" in round 1. Adding a diagonal pattern fixed it in round 2.
  • Notification budget. Max 3 tips a day, none between 23:00 and 07:00 unless the user opts in. Opt-out rate dropped from 38% to 9%.

11 — Learnings & next steps

Design for the worst hour.

  1. 01

    Calm is a measurable feature

    Fewer, better-timed notifications did more for trust than any visual polish. "Calm" became a review criterion for every screen.

  2. 02

    Offline is the main state

    Mobile networks degrade during outages. Caching the week's schedule and computing runtime on-device moved from "nice to have" to architecture.

  3. 03

    Accessibility is for everyone at night

    Large type and high contrast, designed for Mykola, turned out to be what everyone wanted when reading a phone in a dark stairwell.