Readiness tools are built for dashboards, not decisions
Monitoring platforms are good at collecting and terrible at deciding. A trainer opens one and gets forty charts; what they need at 6am is a short list: who's ready, who's managed, who needs eyes on them before practice. Every design decision in this product optimizes for that morning call, not for the completeness of the archive.
The systems below are decided and built. The product screens are forming on top of them, and this page will grow as they do.
Kinetic: one family, two speeds
Archivo, variable width as the system's one expressive axis. Expanded and loud for states and headers, the things you read across a gym, normal width for everything you read up close. Tabular numerals everywhere a number can change, so readiness scores never jitter.
Forged Bronze: a fixed shell that takes any team
The shell is permanently dark, training rooms at 6am, gym light, sideline glare, and it never changes per customer. Bronze carries the product's own voice: warnings, structure, identity. Everything a team touches emotionally comes from one variable instead: their color.
One token, whole product. Try it.
Every org gets its identity through a single accent token that threads the entire interface: rings, meters, pills, avatars. The shell never moves, so the product stays legible and the brand work is one decision, not a theme audit. Pick a team color and watch it propagate.
Design rule the engine enforces: the team color never carries meaning. Ready, flagged, and warning states stay in the product's own palette, so a crimson team and a green team read risk identically. Identity is decoration; safety semantics are fixed.
Unresolved, on purpose
Is a single readiness number honest? One score is decisive but hides its inputs. The current bet: lead with the number, keep the four drivers one glance away, never let the score appear without them.
Where does alert fatigue start? Trainers ignore systems that cry wolf. Exploring thresholds the staff tunes per athlete, versus fixed sport level defaults.
Sideline versus office density. The same data needs a glanceable phone view at practice and a dense review view at a desk. One responsive system or two deliberate products?
Athlete facing honesty. If athletes see their own readiness, does self reporting get gamed? The training room says yes unless reporting stays consequence neutral.
Other things I'm making
This site
Designed and built as a working demo of the same systems: Kinetic type, the Forged Bronze palette, and a light and dark theme that switches like a sunrise.
Woodworking
Furniture and decor out of the home wood shop. Different material, same obsession: joints that hold under load.