Neoshift: a POS built for the line cook, not the desk worker

I led Neoshift — a smart POS platform built for high-volume restaurant floors, not desk workers. This project taught me a lesson I repeated later in enterprise IoT: adoption on a busy line beats feature count every time. My mandate was national scale through local proof — each site had to actually use the product during rush hour before we expanded.

Restaurant POS systems were built for managers reviewing reports, not line cooks processing orders under pressure. Feature-rich systems sat unused because the floor staff couldn't trust them when the queue was out the door. Scaling meant national footprint — but only if each site actually used the product. The trap was selling features to owners while cooks kept the old system open in the background.

I bet on floor-first UX: fewer taps, faster order entry, reliability under rush-hour load. The metric wasn't feature parity with incumbents — it was daily active use by the people who actually ran the restaurant. Every design review asked: "Does this help at 12:30 PM on a Tuesday?" If not, it waited.

Every stakeholder wanted reporting, inventory, loyalty, and integrations. I held the line on core order flow until sites abandoned their paper backup. Pilot-to-national rollout meant each cohort had to prove adoption before the next expanded. I killed features that owners requested but cooks ignored.

Neoshift scaled from pilot sites to 1,000+ restaurants nationwide. First proof that a product built for the person doing the work — not the person reviewing the dashboard — could scale in a market where most POS systems failed on adoption. National scale followed local trust, not the other way around.

I'd shadow rush hour before every major release. No usability lab replaces a hot kitchen. I'd also make "paper backup usage" a tracked metric. When it hits zero, you have a product.