Kognetra

The project started on the floor, not in a design tool. Following how a maintenance team actually works surfaced the same pattern everywhere: when a machine stops, the fastest fix is not in any system, it is in the head of whichever veteran technician happens to be on shift. Procedures sit in scattered PDFs, incident fixes are never written down, and the plant’s real memory retires one person at a time.

The second finding set the bar for the interface. A technician at a stopped machine has minutes, greasy hands and, in half the plant, no signal. Whatever I built would be judged in that moment: if the answer takes longer to find than the veteran takes to ask, the system loses and the old habit survives.

The platform is framed as four spaces under one shell, grouped the way a maintenance team thinks: Knowledge for procedures, articles and search; Maintenance for equipment, interventions and return-of-experience; Community for the feed, workspaces and recognition; Administration for accounts and quality. The dashboard adapts to who is looking, an administrator, an expert or a floor technician.

Search sits deliberately above navigation. A global command palette covers the whole base from anywhere, because a technician under pressure will not walk a menu tree: they type “roulement grippé” and the procedure, the past incident and the article come back in one list, in milliseconds, online or off.

The obvious references all existed, and all failed the floor test. I walked the stopped-machine scenario through three shapes: a wiki like the intranets plants already ignore, a records module like the CMMS screens technicians already avoid, and a search-first field companion built around the question rather than the archive.

The wiki organises knowledge for the people who file it, not the ones who need it; five clicks deep is five clicks too many with a line stopped. The records module treats knowledge as rows: accurate, complete and unread. The field companion inverts both: one search field, answers ranked for the machine at hand, and navigation demoted to a secondary path.

The maintenance core is domain-specific, not a generic wiki. Procedures carry their lockout-tagout safety steps in the open, where a rushed technician cannot miss them; an equipment register anchors every piece of knowledge to a real asset; and return-of-experience reports capture failures with structured methods, five whys and Ishikawa, so an incident becomes reusable knowledge rather than free text.

The REX pipeline is where designing the process mattered more than the screen. A failure only becomes knowledge if it is captured while fresh, analysed with a method and filed against the machine, so the report walks the technician through exactly that, and the result is found by the next person on the next shift.

The hardest problem in any knowledge system is not reading, it is writing. The living layer exists to solve that: an editorial article space that makes hard-won fixes feel worth publishing, a community feed, workspaces and an idea box that keep the base moving, and light gamification, points, badges and a leaderboard, that makes contribution visible.

Recognition is designed as the engine, with quality control around it: moderation and an admin console keep the standard high, so the leaderboard rewards useful writing rather than volume. And the whole product is designed in light and dark from one token system, so the plant office and the dim control room both feel native.

Kognetra shipped as a production-quality concept, designed and built end to end, front and back, fourteen modules in light and dark. Working alone across design and code kept the loop honest: every structure I drew I then had to build and search against, which killed several elegant taxonomies within days.

The lesson I keep is about where knowledge products fail. They do not fail at the database; they fail at the moment of writing and at the moment of need. Designing for those two moments, recognition on one side, a stopped machine on the other, is what the whole system hangs from.