Jeeone*
All work
(02) Case Study

Vertex

An AI copilot for field researchers in the Arctic circle.

Year
2024
Duration
9 weeks
Role
Lead Product Designer
Client
Vertex Labs — seed, 6 people
Vertex
(01) Problem

Researchers on 30-day expeditions had spotty satellite internet, frozen fingers, and no patience for chat UIs. The existing AI assistant required typed prompts and always-on connectivity — two things the field could not offer.

(02) Constraints
  • Must work offline for 72 hours and reconcile when a link is found.
  • Touch targets big enough for insulated gloves.
  • No LLM call costs more than $0.04 — budgets are tight on expedition.
(03) Approach

Turn the copilot into a notebook. Researchers dictate or scribble; the AI fills in fields, suggests tags, and flags contradictions — but never takes the wheel. Streaming UI hides latency; optimistic UI hides offline gaps.

(04) Process
  1. 01

    Field study

    Ran a two-week pilot with the Svalbard team over Starlink. Logged every interruption. There were 312.

  2. 02

    UX for unreliability

    Designed state machines for every sync scenario. 'Draft' / 'Queued' / 'Reconciled' / 'Conflict'. Every change has a reversible history.

  3. 03

    Prompt design

    Wrote 40+ system prompts, evaluated against 200 historic logs. Built an eval harness in TypeScript that grades output against rubrics.

  4. 04

    Motion as affordance

    Subtle Framer Motion cues for sync status — a 400ms opacity dip, a gentle underline. Zero pop-ups.

Vertex artifact 1
Vertex artifact 2
(05) Outcomes
42 min/day
Saved per researcher
99.4%
Sync success rate
4.8/5
NASA-TLX workload score
9 → 3 min
First log written after boot
(06) Learnings
AI in hostile environments is not about model quality. It's about gracefully failing in 14 different weather conditions. Design for the worst day.
Next case study
Finch

Finch

A neobank for freelancers across Southeast Asia.

Read next