lucixMotion lab · feel alive, not a video game

Motion that narrates, never decorates.

Every moment here conveys a real state, relationship, or pace — and nothing pulses, chases, or pressures. Click things. Tactility is invisible in a screenshot. Flip the switch to preview exactly what a visitor with reduce-motion sees: the end-state always survives, only the movement drops.

01

The alive baseline — microinteractions

Physical, quiet feedback: press settles the button in, a row lifts toward you, focus arrives with a soft ring. No bounce, no glow — the feeling is paper and ink responding, not an arcade.

Press & hover

RD
R. Delgado
owns Pipeline readiness

Hover the row; press the buttons. Feedback is ≤120ms — instant, never latency.

Focus

Focus is a soft navy ring, not a jump. Keyboard-Tab through this section: every focus is visible and calm.

02

Progressive disclosure — density that breathes

The sanctioned answer to dense surfaces: collapsed by default, opening in place with a short staggered reveal so you read the group as a group. Nothing is hidden from anyone entitled to see it — it's one click away.

PT
Priya T.
owns Platform v2 dependency
committed
GT
G. Tan
owns Data migration
deferred · Thu

Click the header. Open it, then flip reduce-motion above and open it again — the rows still appear, just without the stagger.

03

Signature moments — where delight lives

In a serious tool, delight isn't confetti — it's the product's own verbs made tactile. Each of these fires once, on a real event, in ~460ms. Trigger them.

RD
Pipeline readiness
R. Delgado
open
commit — the dot settles in. The answer is signed into the record.
Committed Mar 31
seal — the brief presses down like a stamp. Once, and it's final.
Condition · Data migration
Platform v2 decision
The Apr 2 date
The Q1 check-in
bind — one condition reaches every place it touches.
04

Flow & pace — feel where it moved fast, slow, or blocked

open · awaiting sign-off

Press Replay the season. Watch the decision graph assemble at the pace it actually happened: Sales resolved fast, Engineering laboured, Finance never engaged. You feel the pace — because this is a replay of what already happened, not a live status. That distinction is the whole law: narrate history, never pressure the present.

3 days 3 weeks · bottleneck never opened APACFRAMED
framing → committed
Fast & committed — a confident ease-out draw; the node lands as a filled navy dot. You feel it resolve.
Slow / bottleneck — a laboured draw that visibly drags; the node holds open with a "3 weeks" residue and the plain word bottleneck. No red, no alarm — just the honest pace.
Never engaged — a faint dashed edge that stops short. Unowned, shown plainly, never as a nag.
Motion runs on demand (you pressed play) — never a perpetual ambient loop, which would read as live pressure and forbid itself.
Decision package — flow / pace

The idea you raised — letting a user feel where decisions moved fast, slow, or got blocked — is strong and product-true (the map is grown from real acts; velocity is the core signal). It also brushes the boundary law, so here's the recommendation, the line, and the alternatives.

Recommendation → retrospective-only flow (option A)

Flow/pace motion lives only on surfaces that narrate the past: the retrospective replay (T14) as its home (a scrubbable season you watch assemble), the map with on-demand flow (hover/select an edge to replay its pace — never ambient), and the exec readout (T15) where MT2R + durability already live. Pace is encoded by the timing and easing of the draw itself (confident vs. laboured) plus plain residue labels — no new reserved color, so PL-1/PL-2/PL-7 stay intact.

The line (why this is legal)

Legal: narrating elapsed pace on committed-time data, after the fact. Forbidden: animating a live, unanswered ask to feel "stuck / behind / urgent" — that is pressure on silence (boundary + notification laws). The tell: does the motion describe what already happened, or push someone to act now?

Alternatives (rejected / higher-risk)

  • B · Ambient live flow on the map (a perpetual current on all edges): richer, but risks reading as live status/pressure, distracts on a dense surface, and flirts with animating silence. Rejected.
  • C · No motion — pace as static labels only: safest, fully legal, but forgoes the "feel it" opportunity you explicitly want. Available as the fallback if A tests poorly.

Proceeding on option A as the working assumption; the map's visual language remains a separate consciously-open item, so A's map specifics fold into that decision when it's taken.

How this becomes the product: these tokens and moments are the motion layer every surface inherits during assembly — the disclosure pattern on every dense surface, the microinteraction feel everywhere, one signature moment per surface (commit on Waiting-on/Resolve, seal on the brief & the plan, bind on condition), and flow/pace reserved to the retrospective surfaces per the package above. Nothing loops forever; everything respects reduce-motion; nothing animates silence.