workflow

The percentage of newly registered users who actually reach the key action that signals they've experienced a product's core value — not just logged in or browsed. It's the core metric for judging whether onboarding is actually working.

The process of a designer handing off everything an engineer needs to actually build a finished screen — not just the visuals, but specs, states, and edge cases — done well, it's what keeps the shipped product looking like the design file instead of drifting from it.

Checking a live, shipped build against the original design spec item by item — verifying whether spacing, color, copy, and interaction behavior genuinely match what the design file specified — rather than checking whether a screen changed at all, which is what visual regression testing does. The two are easy to conflate.

A shared library of components, rules, and documentation that designers and engineers both reference, so questions like "which color, which spacing, what does this button look like" have one answer everyone can look up instead of re-deciding each time.

Design decisions like color, spacing, and type stored as named, structured values so the same source of truth can drive both design tools and production code, instead of scattered hex codes and magic numbers.