Your schedule isn’t a document. It’s a feed.

The printed schedule was a fine tool for a world where the schedule never changed. That world doesn't exist. Somebody's kid gets sick, a private party books Tuesday, the new hire quits by text on Sunday night — and now the piece of paper taped inside the office door is wrong, and everyone who photographed it on Thursday is carrying the wrong week in their pocket.

That's the actual failure mode. Not "we don't have scheduling software." The schedule exists — it's just a snapshot, and snapshots rot.

A document you check vs. a feed that reaches you

Every tool we replaced treats the schedule as a document. Excel is a document. The printout is a document. Even most scheduling apps are documents with a login in front of them — the information sits there waiting for someone to come and get it.

Group texts got popular because they inverted that: the message comes to you. That's the one thing the group chat gets right, and it's why it survives every attempt to kill it. The problem is everything else — no structure, no record, the Saturday cover request buried under forty replies.

So the design brief for ShiftGlance was: keep the reach of the group text, keep the structure of the grid, and lose the rest.

Why the lock screen

The most valuable screen real estate in your staff's life is the lock screen. They see it dozens of times a day without deciding to. Put the next shift there — with a countdown, updating the moment the schedule changes — and "did you see the new schedule?" stops being a question anyone has to ask.

That's the whole product philosophy in one object. Not more notifications. Not another inbox. The one fact each person actually needs — when do I work next — sitting where they already look.

More notes as we build. If you run a floor and want to argue with any of this, we'd genuinely like to hear it.