Skip to main content

IVFCRYO

Client project · Fertility logistics

Five parties working from one shipment record

Shipping fertility specimens means coordinating a patient, two clinics, a courier, and IVFCRYO. I designed and built the shared interface where everyone confirms readiness before a shipment moves, along with its public site.

ONE SHIPMENT · FIVE PARTIES Patient Ready Sending clinic Ready Receiving clinic Ready Courier Ready Equipment Waiting Scheduled once all five clear
75%
fewer support calls
55%
fewer shipping errors
My role
Product design and front end
Owned
Research, workflows, components
Partnered on
Rails backend and tracking
Team
Three developers

Project summary

Interviews with the owner, COO, and office manager showed that the hardest part was getting the patient, two clinics, a courier, and IVFCRYO confirmed and ready before a shipment could start.

The decision
I chose one shared record over two separate apps, so patients and staff always see the same status.
The result
Support calls dropped 75% and shipping errors 55% once patients could see that both clinics had signed off.

Shipment parties

IVFCRYO ships frozen embryos between clinics, and a missed temperature drop can cost someone their only remaining embryo. As Don, the owner, put it, a shipment “looks like one transaction to the patient, but it is actually a chain of separate responsibilities,” so I mapped each party and handoff first. Priya, Lauren, Tessa, and Martin are the people on either side of those handoffs.

The five parties

  • Patient

    Authorizes the transfer and completes forms, records, and payment.

  • Sending clinic

    Prepares and releases the specimens through a named lab contact.

  • Receiving clinic

    Confirms intake requirements, then inspects and accepts the specimens.

  • Dedicated courier

    Hand-carries the sealed unit directly between facilities.

  • IVFCRYO

    Provides the monitored shipping unit and coordinates the case.

Chain of custody

  • Prepare & release

    The sending lab loads the tracked unit, and a named contact releases it.

  • Courier pickup

    The courier takes custody, and both sides confirm the handoff.

  • Delivery & inspection

    The receiving lab records a calibrated temperature before taking custody.

  • Accept & close

    The record closes when staff accept the specimens.

The shipment detail page: the title Hudson Valley Reproductive to IVFCRYO Lab, a four-step custody timeline with In transit current, a key-facts strip for pickup, delivery, service, and quoted price, then sensor data with a large −192.9 °C probe readout, a temperature chart below a dashed set-point line marked “All 12 below set-point”, ambient readings, and a live map. A side panel lists shipment details and staff comments.
Shipment detail

Custody status comes first, followed by key facts, the temperature trace, and the map.

Research

Requirements gathering

IVFCRYO’s requirements reached me as photographs: printed Word pages listing everything they had to collect for a single shipment, and sample labels from their two couriers. They talked me through the process, then had me interview an existing customer so I could learn it from the customer’s side.

I also sat down with the owner, COO, and office manager, and all three named the same first fix: a readiness check both clinics confirm before a courier is scheduled.

“One of the worst operational patterns is scheduling first and hoping the remaining requirements are completed before pickup.”
Daryl, COO, on scheduling

From there I moved from notebook sketches to Figma designs and reviewed them with customers. Once we agreed on how it should work, we built high-clarity mocks in code. Tasks lived in GitHub Projects, where IVFCRYO could check status between our scheduled touchpoints.

The app had grown to 226 views with no shared rules for buttons, inputs, or status, so I ran a front-end audit. I kept the brand, every route, and every form field name.

Audit findings

30

button class combinations

Including white on orange at 2.6:1, which fails WCAG AA.

4

ways to style an input

Plus 14 one-off input class strings.

115

inline style attributes

Plus 7 style blocks in views and 19 hand-drawn SVG icons.

Red

meant “pending”

A normal state looked like an error.

The audit also found security holes: 14 leftover pages let any signed-in clinic edit every company and user, shipments opened by guessing an ID, and the list filter built queries from raw URL text. I fixed those first, with request specs to keep them closed.

Heuristic audit

I scored every flow 0–10 against Nielsen’s ten usability heuristics, citing a file and line for each finding. The bar was 8 or above everywhere, and fixes went into shared components first.

8.8

average score after

up from 5.3 across 8 flows and 10 heuristics

2 → 9

lowest error-recovery score

the weakest heuristic on three flows

Score by heuristic

Lowest score on any flow, before → after, and the change that moved it most.

  1. Visibility of system status

    4 9 /10

    Overdue pickups are flagged, and labels and quotes show working, done, or failed.

  2. Match with the real world

    5 9 /10

    One set of stage names everywhere, replacing raw values like “Pending” and “Delete”.

  3. User control and freedom

    3 9 /10

    Archived contacts can be restored, unsaved edits are guarded, and filters clear in one click.

  4. Consistency and standards

    4 9 /10

    Filters are a real form, so Enter works. Every page uses the same confirm dialog and flash message.

  5. Error prevention

    2 9 /10

    “Delete” needs confirmation, package types in use can’t be deleted, and forms block double-submits.

  6. Recognition over recall

    6 8 /10

    Hidden filters show a count. Contacts added in a dialog can be picked right away.

  7. Flexibility and efficiency

    4 8 /10

    Press / to search any list. The in-transit list makes one query instead of one per row.

  8. Aesthetic and minimalist

    3 8 /10

    Public tracking shows no names, addresses, or printable labels.

  9. Recovering from errors

    2 9 /10

    Failed bookings keep what was typed, errors appear inline, and bad tracking links get a recovery page.

  10. Help and documentation

    5 8 /10

    Empty states explain how shipments reach each stage, with hints under fields that need them.

Average score by flow

  • Auth, shell, error pages 5.4 → 8.8
  • Home, detail, public pages 4.8 → 8.9
  • New shipment 4.9 → 8.9
  • Admin shipment edit 4.4 → 8.7
  • Address book, users, templates 4.8 → 8.9
  • Inventory 6.2 → 8.8
  • Settings, feedback 6.2 → 8.8
  • Shipments list 6.0 → 8.8

Every interview identified the same main problem: getting all five parties ready before pickup.

Personas

  • Priya Nair

    The patient

    “When patients call, they may not only be asking where the courier is. They may be asking whether their chance to have a child is safe.”
    Sasha, office manager

    Moving embryos between clinics, often already carrying anxiety from the IVF process.

    Needs
    • Know both clinics are ready without calling
    • Status in plain language
    • A real person to reach when something looks wrong
    Frustrations
    • Hearing different answers from the clinic and IVFCRYO
    • Vague updates like “being processed”

    Based on interviews with IVFCRYO’s owner and office manager, who speak with patients every day.

  • Lauren Cho

    The clinic contact

    “‘Sent’ is not the same thing as ‘received and approved.’”
    Don, owner

    Creates and manages shipments, and needs to release or receive specimens correctly.

    Needs
    • A fast, repeatable way to create shipments
    • Specimen details that stay accurate
    • Saved instructions for each facility
    Frustrations
    • Upfront default settings that had to be undone
    • Technical questions landing at the front desk

    Based on the interviews and on prototype sessions with customers.

  • Tessa Morgan

    The IVFCRYO coordinator

    “My job is often to make sure the right person has the right information at the right time.”
    Sasha, office manager

    Keeps patients, clinics, cryobanks, couriers, and the internal team moving on every shipment.

    Needs
    • Email, fax, and phone notes in one case
    • A clear owner at every handoff
    • Every shipment visible by readiness
    Frustrations
    • Couriers scheduled before everyone is ready
    • Being told something was handled, with no record of it

    Based on the interviews with the office manager and COO.

  • Martin Reyes

    The customer using a screen reader

    “If the page changes and nobody tells me, I don’t know it changed.”

    A legally blind customer who had trouble with the older shipping form on IVFCRYO’s website.

    Needs
    • Complete a shipment without help
    • Hear errors next to the fields they belong to
    • Hear status changes as they happen
    Frustrations
    • Form errors not tied to their fields
    • Parts of the form that didn’t work by keyboard
    • Updates that were never announced

    Based on testing sessions with this customer.

Persona names and photos are illustrative, as are quotes without a named source.

Journey map: one shipment

  1. Request

    Activity

    A patient places an order and names who they’ve been talking to at each clinic.

    Problem

    That person may not be responsible for specimen transfers, and details arrive incomplete.

    Design response
    Structured specimen fields, checked addresses, and reusable contacts.
  2. Confirm readiness

    Activity

    Both clinics confirm records, approval, and laboratory contacts.

    Problem

    Couriers get scheduled first, with everyone hoping the rest is finished before pickup.

    Design response
    Each party clears a checkpoint before a courier can be scheduled.
  3. Release and pickup

    Activity

    The sending lab loads the tracked unit and hands it to the courier.

    Problem

    Responsibility changes hands without the next person knowing it’s now theirs.

    Design response
    A named contact acknowledges every handoff.
  4. In transit

    Activity

    Staff watch the readings while the patient waits for news.

    Problem

    A reading that reassures an operator can alarm someone waiting on a specimen.

    Design response
    Public tracking with no personal details, a plain-language summary, and alerts with an assigned responder.
  5. Delivery and acceptance

    Activity

    The receiving lab takes the specimen into storage.

    Problem

    A delivery scan at the front desk doesn’t prove the lab accepted it.

    Design response
    Receiving captures a temperature reading and photos, and the finished shipment locks as the record of custody.

A readiness check before a courier is scheduled

I made readiness a status the system checks, with requested, provisional, and confirmed kept as separate states. Each responsible party clears a checkpoint before a courier can be scheduled.

Readiness checks before scheduling

  • Patient Authorizations, identity, and payment complete
  • Sending clinic Release approved, specimens prepared, contact named
  • Receiving clinic Acceptance approved, intake requirements confirmed, staff scheduled
  • Courier Route and timing confirmed as feasible
  • Equipment Shipping unit available and suitable for the duration

A shipment moves from awaiting_readiness to ready only after every check is confirmed. Only a ready shipment can be scheduled.

One shipment record for customers and staff

Customers need a short path from request to tracking. Staff need to see every shipment at once. Two apps would have kept two records that could disagree, so customers and staff read the same shipment record. Customers also get a readiness view.

Customer and staff screens

Customer

  • Shipping list

    Active and past shipments, with readiness and overdue alerts.

  • New shipment

    Route, specimen, live pricing, and CRYO Shield shipping guarantee tier.

  • Readiness view

    What each party still owes before it can be scheduled.

  • Active shipment

    Read-only tracking and sensor telemetry.

  • Receiving customers

    Saved delivery contacts.

  • Profile

    Billing, address, cancel account.

Admin · IVFCRYO staff

  • Shipping list

    Every client’s shipments, by readiness state.

  • Active shipment

    Edit, cancel, change status, notify, or open an incident.

  • Customer list

    Filter, sort, open a client.

  • Customer detail

    All orders for one client.

  • Equipment inventory

    Units, monitoring, maintenance and replacement flags.

  • Add customer

    Creates the account, emails credentials.

Shipment detail, rough hand-drawn concept sketch.

Sketch

Exploring the layout.

Shipment detail, clean wireframe without annotations.

Wireframe

Defining the behavior.

Annotated wireframe of the shipment detail page: a live position map above sensor readings for temperature, humidity, and battery, then two parallel tracking timelines, with callouts explaining why telemetry outranks logistics and why the two legs stay unmerged.

Annotated

Documenting the decisions.

Sketch, wireframe, and annotated sheet for the shipment page.
Annotated wireframe of the shipments index: a filter bar, status tabs, and a list of shipment cards, with six numbered callouts explaining why status lives in the URL and why cards replaced table rows.
Shipments index

Staff’s main workspace, filtered by status.

Recipients never sign in. They get a link by email or text and only need to know the shipment is on its way. The public tracking page had been showing names, addresses, and shipping labels to anyone with the link. With the owner’s approval, it now shows no personal details. The temperature chart opens with a plain summary such as “All 12 below set-point”.

The public tracking page: Hudson Valley Reproductive to IVFCRYO Lab with an In transit chip, a four-step custody timeline, From and To cities with the requested delivery time, latest sensor readings for probe and ambient temperature, humidity, and pressure, a probe temperature chart marked “All 12 below set-point”, and a line with the support email and phone number.
Public tracking

Shows status, latest readings, and a staffed phone number. It requires no account and shows no personal details.

The public tracking page for an unknown shipment: “We couldn’t find this shipment. The link may be old or mistyped. Check the link in your email or text, or contact IVFCRYO and we’ll look it up for you,” with Email IVFCRYO and Call 800.430.9830 buttons.
A tracking link that doesn’t work

Bad links used to crash the page. It now explains the problem and gives an email address and phone number.

A few choices on each shipment

There was a strong push for one-click shipping. Customers would set defaults for container size, departure and receiving facilities, and courier instructions, and each shipment after that would take one click. That required foresight and setup time customers didn’t have. A default that didn’t fit would also have to be undone.

I prototyped the workflow with several customers and timed it. Customers supported the idea at first. When they used the prototype, one-click shipping took more effort than it saved.

Prototype timings

  • Setting up all the defaults About 10 minutes
  • A shipment with no defaults set About 30 seconds
  • A shipment where the defaults matched About 10 seconds
  • A shipment where a default had to change Over 2 minutes

A matching shipment saved about 20 seconds. Customers needed about 30 matching shipments to recover the setup time, and most shipped far fewer in a year. Each changed default added more time.

After a lot of persuading, stakeholders agreed to drop the upfront defaults. Customers chose the departure and receiving facilities, container type, and personnel for each shipment, and reused instructions saved for each facility. Each shipment took four or five clicks. Because customers made each choice themselves, shipments were less prone to error.

After launch, we reviewed the workflow in Hotjar every week and talked through any sticking points. There was a push to get every shipment done in 30 seconds. People often start a shipment, get pulled away, and finish it later, so we decided further speed work wasn’t worth the cost.

Forms that prevent mistakes and let people fix them

Every form lets people fix mistakes without calling support. Addresses are checked against map data, and specimen details use structured fields.

CRYO Shield, IVFCRYO’s shipping guarantee, pays only on fully documented claims, so orders capture declared value and receiving captures a temperature reading and photos.

A legally blind customer, the basis for Martin’s persona, had trouble with the older shipping form on IVFCRYO’s website. They tested the new forms with a screen reader before and after launch. Those sessions turned up form errors that weren’t tied to their fields, keyboard problems, and missed aria-live announcements, as well as the labeling issue in Limitations.

Built into every form

  • Structured specimen records
  • Geocoded address validation
  • Inline validation, recoverable errors
  • Status shown by text, icon, and shape
  • Focus managed on visibility change
  • Live-region status announcements
  • Explicit acknowledgment at every handoff
  • Immediate, structured incident capture
Annotated wireframe of the new-shipment form, broken into seven numbered sections from service selection to insurance, with a live price quote pinned beside it and six callouts covering quote recalculation, contact reuse, and notification defaults.
New shipment

About forty fields in numbered sections, with a live price and a way forward from every error.

Flow diagram of the shipment creation path. Service selection resolves a live price quote or a contact-for-quote branch, then runs through date, package, pickup and delivery contacts, notification preferences, insurance, and agreement. Failed validation returns to the offending field with form state preserved, and a successful submit forks into a confirmation email and the admin fulfillment queue. Six numbered design notes sit alongside.
Creating a shipment

The highest-risk path: one submit, with validation that blocks bookings that can’t be fulfilled.

Flow diagram of authentication and account recovery. A visitor branches on whether they have an account, through sign-in, admin activation, a user-chosen email or SMS verification channel, and six-digit code entry. A failed code offers resend, backup code, or password reset, and a final admin check routes to either the admin or client view. Five numbered design notes sit alongside, and password recovery runs as a separate track underneath.
Authentication and account recovery

Every failed step offers a way to recover without calling support.

Shared components for 226 views

I started with design tokens, then built shared Rails components for buttons, fields, cards, headers, badges, alerts, tables, and empty states. Most views improved before I edited them directly. I then rebuilt screens in order of importance without rewriting the app.

The visual direction, called clinical instrument, displays data in the style of lab-device readouts.

Design decisions

  • Navy means you can click it

    Navy is only for actions, links, and the current nav item, at 11:1 contrast. Orange no longer appears as button text.

  • Numbers line up

    Readouts use Geist Mono with tabular figures, so temperatures, times, and prices compare at a glance.

  • Every status has a shape

    Each status chip has a glyph as well as a color. Pending moved from red to amber.

  • One primary action per page

    One navy button per page. Breadcrumbs on 27 nested pages replaced scattered “Back” buttons.

  • Planned times are labeled

    The custody timeline labels planned times “Scheduled” or “Requested” so they aren’t read as actual times.

  • Keep the warmest reading

    The temperature chart keeps the warmest reading in each interval, so a short spike can’t be averaged away.

The app’s development-only style guide: color tokens with their roles, the type scale, a page header with breadcrumbs, buttons in four variants and four sizes, form fields including an inline error, status badges, alerts for info, success, warning, and error, an empty state, and a data table.
Style guide /styleguide

Shows every shared component in every state. When a token changes, this page shows every component it affects.

The shipments list, signed in as staff: a sidebar, four stage tiles (Awaiting pickup 6, In transit 4 selected, Delivered 8, All shipments 18), a filter row, and shipments grouped under Today and Yesterday. Each row shows pickup time and zone, a route such as NY to CA with both clinic names, a probe readout of −192.9 °C with a sparkline, hours since pickup, and the quoted price.
Shipments, in transit

The stage tiles also work as navigation. Each row shows both clinics, the probe temperature, and the time since pickup.

As someone books a shipment, the sidebar shows a live summary of the route, package, service, and quote. One sentence says what’s still missing.

The new-shipment page: Ships from and Ships to company pickers with search, the selected companies marked with an orange bar, prefilled pickup and delivery instructions, three package cards with line drawings and dimensions, and a sticky Summary panel showing the route, pickup date, unselected package and service, an empty quote, a terms checkbox, and a disabled Book shipment button with the hint “To submit, choose a package and a service, then agree to the terms.”
New shipment

Company pickers side by side, package cards with drawings, and the live summary.

Once a shipment is delivered it locks, and the page says why.

The edit page for a completed shipment, titled Shipment complete: a lock panel reading “Delivered and locked. This shipment is complete and can no longer be edited. Its details stay exactly as they were at delivery, as the record of custody,” with the delivery time, door-to-door duration, a View shipment button, and the full custody timeline below.
Delivered and locked

A completed shipment can’t be edited because it is the record of custody. The page says so.

Mobile

Patients, embryologists, and couriers check shipments away from a desk, so every main screen was checked at 390 pixels wide with no sideways scrolling. Grids reflow into fewer columns on narrow screens.

  • The public tracking page on a phone: shipment title, an In transit chip and reference number, then a vertical custody timeline from Created to Delivered, followed by From and To clinic names and cities.
    Public tracking

    A vertical timeline, then the two clinics.

  • The shipments list on a phone: Export and New Shipment buttons, four stage tiles in a two-by-two grid with In transit selected, and stacked search and company filters.
    Shipments

    Stage tiles two by two, filters full width.

  • Shipment detail on a phone: breadcrumb, title, invoice and Edit buttons, a vertical custody timeline, then pickup, delivery, service, and quoted price in a two-column grid.
    Shipment detail

    Vertical timeline, then key facts in pairs.

  • The My shipments page for a clinic user on a phone: stage tiles with the clinic’s own counts and the same search and filter controls as staff.
    Clinic view

    A clinic sees only its own shipments.

Public site

The public site now shares the app’s domain, and its product previews are the app’s own components rendering a labeled sample shipment. Changes to the app appear on the site automatically.

Press mentions link to their sources. Reviews are ones IVFCRYO had already published, and the legal pages moved over word for word.

The full IVFCRYO home page: a 24/7 desk phone bar, the hero sentence “Your embryos are holding at −192.9 °C, 3h 05m into a trip we watch every minute” beside a US map with the sample route, key figures, press and partner logos, sections for patients and for clinics, a live tracking card from the app, a five-step booking-to-delivery timeline, coverage and support cards, a founder quote from Don Fish, customer reviews, a services list, and a closing call to action.
Full page ivfcryo.com

The tracking card, temperature trace, and timeline are live app components.

Results

75%

fewer support calls

Client data, 90 days after launch

55%

fewer shipping errors

Client data, 90 days after launch

For patients like Priya and clinics like Lauren’s

  • See when both clinics have signed off
  • A readiness view of what each party still owes
  • Tracking by email or text, with no account
  • Forms that let them fix mistakes without calling support

For IVFCRYO staff like Tessa

  • Email, fax, and phone notes gathered into one case
  • Every client’s shipments, by readiness state
  • Alert levels, each with an assigned responder
  • A named contact acknowledges every handoff

For the business

  • No courier scheduled until every party confirms readiness
  • Orders capture declared value for CRYO Shield claims
  • Custody closes when staff accept the specimens
  • Patients and staff always see the same status

Success measures

Safety

  • Temperature excursions
  • Monitoring gaps
  • Chain-of-custody exceptions
  • Incomplete receiving records

Reliability

  • On-time pickups and deliveries
  • Rescheduled shipments
  • Shipments started without full readiness

Efficiency

  • Order-to-readiness time
  • Manual follow-ups per case
  • Exception resolution time

Experience

  • Status inquiries
  • Complaints
  • Stage-appropriate updates delivered

Testimonial

Don Fish

Don Fish

Owner · IVFCRYO

Josh didn't just design screens. He sat with me, our COO, and our office manager, and came back with the insight the whole rebuild turned on — the hard part is getting everyone ready, not tracking the truck. He designed the product and owned the front end, and worked shoulder-to-shoulder with our engineers on the data model and the integrations underneath. Our team runs on it, and our patients feel the difference: they finally know someone has the whole case.

Build and integrations

I turned the interview findings into the shipment stages and readiness check the backend enforces, mapped where each outside service plugs in, and set the alert requirements. Engineering built the backend to that spec, and I built the front end.

Integrations

  • IVFCRYO-Sense

    GPS, internal and ambient temperature, humidity, and pressure

  • ShipEngine

    Multi-carrier rates and labels

  • Dedicated courier

    Direct medical hand-carry, no sorting hubs

  • SendGrid

    Tiered email notifications

  • Twilio

    SMS alerts

  • Devise + 2FA

    Sign-in with two-factor authentication

Alert levels

  • Normal

    The reading is within the expected range. It is logged and shown quietly, and no one is paged.

  • Early warning

    A reading is trending toward a threshold. Staff monitor it more closely and call the courier.

  • Required action

    A reading crosses a defined threshold. The owner is notified and must respond.

  • Emergency

    A reading shows a critical excursion. The pre-assigned escalation path starts.

Daryl warned that staff stop trusting a device that sends “false or unhelpful notifications,” so each level has an assigned responder.

Limitations

Both come from live data arriving from several sources, with no early rule for timing or wording.

  • Screen reader updates are too frequent

    The tracker updates every 60 seconds, so a screen reader starts each update before the last one finishes. A setting slows it down, but I’d change the default instead.

  • Carriers announced with the same label

    With two carriers, both were announced the same way, so a screen reader user couldn’t tell which had the shipment. I’d name each carrier explicitly.

Still open

  • No bulk actions or saved views

    Staff still handle shipments one at a time. Bulk actions need a product decision about which admin queues get them.

  • Device IDs are still typed in

    Staff enter trackers and dry shippers by ID. A picker built on availability data would be faster and harder to get wrong.

  • No real-device accessibility pass

    Phone layouts were checked only in automated captures. The public site still needs a keyboard and screen reader pass on real devices.

More screens

Annotated wireframes for the screens the case study doesn’t cover, plus more screens from the shipped app.

See all 19 in the gallery