Skip to main content

Logatot

Follow-up · Changes from user feedback

What users told us after launch, and what we changed

An open-ended questionnaire surfaced three problems. I audited every affected screen and turned each fix into a written rule backed by a shared component.

Method
Open-ended questionnaire, then a screen-by-screen audit
When
November 2026
My role
Design and front-end
⅓
less height for two weeks of menusAbout 820px to 540px at 1440 wide
⅔
less scrolling on the voiceboard for a full day3,849px to 1,318px at 1280 wide

What we asked

No question named a screen, so people could raise problems we didn’t know about.

  1. What do you use Logatot for most in a typical week?
  2. What’s the most frustrating part of using it?
  3. Has anything on screen ever done something you didn’t expect?
  4. Is there anything you still check on paper or somewhere else, even though Logatot has it?
  5. If you could change one thing, what would it be?

For each theme, I captured every affected screen and listed what had gone wrong in the markup and tokens.

Themes

One focus per page

Every panel had become a white card, so nothing stood out. The new rule: each page gets one white surface, for the thing the page is for.

Lifted
White with a soft shadow, for the page’s main content only.
Recessed
A tinted panel for filters, quick-add forms, and secondary details.
Canvas
The background, for headings and light controls.

Applied page by page

  • Children

    White card: The roster. Recessed: The quick-add form.

  • Expenses

    White card: The expense table. Recessed: One totals strip, replacing three cards.

  • Calendar

    White card: The selected day’s agenda. Recessed: The month picker and this week’s events.

  • Calendar event

    White card: Date, time, repeat, and child. Recessed: Nothing; the title and actions moved into the page header.

  • Child profile

    White card: The header card, with health tiles inside it. Recessed: Contacts, attendance, billing, and linked apps.

  • Account

    White card: The header with contact info. Recessed: Team, billing, reminders, and sharing.

The old child profile for Ava Johnson: a white header card, then separate white cards for Health, Attendance, Billing, Legal Guardians, and Authorized Pickups.
Child profile, before

Six white cards of equal weight.

The new child profile: one white header card holding the photo, name, and a row of four health tiles. Below it, Legal Guardians, Authorized Pickups, Attendance, and Billing sit on tinted recessed panels.
Child profile, after

Health in the header card, the rest recessed.

The old Expenses page: three white cards for This month, This year, and Receipts above a white expense table.
Expenses, before

Three summary cards compete with the table.

The new Expenses page: This month, This year, and Receipts in a single tinted strip above the white expense table.
Expenses, after

One totals strip; the table is the only white surface.

The old calendar event page: a back link, then a white card with the date and a row reading All Day, Sophia’s Birthday, Sophia Ramirez, and a “…” button.
Calendar event, before

Title buried in a card, actions behind “…”.

The new calendar event page: the title Sophia’s Birthday as the page heading with Edit and Delete buttons beside it, then one white panel showing Nov 23rd, 2026, All day, and Sophia Ramirez.
Calendar event, after

Title and actions in the page header.

Compact Voiceboard

With twelve children, a full day ran about four screens, but providers mostly ask where everyone is and whether each child has had the basics. I added a Compact and Detailed switch.

  • Compact tiles

    Avatar, name, status, and one chip per type of moment logged today.

  • Missing chips are the signal

    A child with no afternoon nap chip has a shorter row.

  • Three or four per row

    Instead of two tall cards. Absent children get one recessed tile.

  • Compact by default

    Remembered per device. Detailed is one tap away.

Same day, same twelve children, same scale

The detailed voiceboard for a full day: twelve tall child cards in two columns, each listing health check, diaper, nap, snack, and activity entries with times and notes, running about four screens long before Provider time and Employee shifts.
Detailed

3,849px tall at 1280 wide.

The compact voiceboard for the same day: twelve short tiles in three columns, each with an avatar, name, pickup time, and a row of small colored icon chips for the moments logged. Noah Patel appears as a single absent tile, and Provider time and Employee shifts panels sit just below.
Compact

1,318px tall.

Shared components

The components existed, but not every screen used them. Filters looked like navigation, and each report built its own table.

Control types

  • Button

    Does something

    A filled pill.

  • Navigation

    Goes somewhere

    A segmented control.

  • Filter

    Narrows what you see

    A checkbox chip.

Every filter moved to one chip, and the old variants were deleted.

  • One page structure

    Back link, title and primary action, section navigation, filters, then content, enforced by the shared layout.

  • One table system

    Typed columns format themselves, and rows stack into cards on phones.

  • One form field style

    A soft border, white fill, and blue focus ring.

Typed cells exposed a bug the hand-built table had hidden: the attendance report sometimes showed an entry under the next child.

Accessibility fixes

The audit found these, mostly where the recessed surface changed contrast.

  • Color-coded categories also get an icon and text
  • Recessed-panel text moved from gray-500 (4.08:1) to gray-600 (6.37:1)
  • Off-state filter chips moved from 4.37:1 to gray-600
  • Filter state comes from real checkboxes and aria-pressed
  • Dark-mode recessed panels got darker to stay distinct
  • Links underline on hover and focus

What I learned

  • Components aren’t a system until they’re the only option

    What lasted was deleting the alternatives.

  • Open questions find problems a task test misses

    We never asked about the calendar or the white cards. People raised them anyway.

  • Show exceptions, not every status

    Removing the approved badge made the failing meal stand out.

  • Hierarchy needs a rule people can follow

    “One white card per page” helps the next person; “make it stand out” doesn’t.

Limitations

  • Not measured with users yet

    Height savings are measured; speed isn’t. Next is resending the questionnaire and timing one task before and after.

  • Softer field borders on purpose

    Field borders are about 1.5:1, below WCAG’s 3:1. Checkboxes keep 3:1 because their edge shows their state.

  • Snacks saved with the wrong meal time

    The calendar sorts around it; the add-meal flow still needs the fix.

  • Not every page is on the new tiers

    The parent dashboard and the expense location and category pages still use the old all-white panels.