We attacked our own catalogue
Using an anonymous key from outside, we tried to read the tables behind every live design: 653 tables. Nothing came back that should have been private.
Operations
Move it off the spreadsheet everyone edits
The sheet works until three people open it. Then you are reconciling versions instead of running the work. Describe the screen your team needs and get one with roles, a shared table, and a history.
Out of the box6 roles
- roles you can assign
- tables probed from outside
- that leaked
- designs to start from
- checks before publishing
- credits to start from one
Access is decided on the server, not in the browser. A hidden button is not a permission.
The situation
Four sheets, three versions, nobody sure which is current.
Operations runs on spreadsheets because a spreadsheet starts in a minute. It stops working at the point where several people edit it, nobody can tell who changed a number, and the person who built the formulas has left. Asking for a proper internal tool puts you behind customer-facing work, so the sheet stays. This is the shortcut out of that: describe the screen, get one your team can log into.
How it goes
Describe the work, give people logins, watch it.
The parts that usually make an internal tool expensive are the ones already handled.
- Describe what the team does
"Shift requests get approved by a manager, and the schedule shows the week." The tables come out of that description.
- Give people the right access
Up to six roles. Who can approve, who can only file, who can only read. The server checks it, so hiding a button is not the whole story.
- Put a dashboard on top
Counts, queues, and what is stuck. Built from the same data, so it does not drift from the sheet it replaced.
Start from one of these
Three operations teams reach for.
Each one has a live demo. Starting from one costs no credits.
- Operations Dashboard
Today's numbers in one place: throughput, backlog, and what is stuck.
- Shift Scheduling
Requests, swaps, approvals. The thing that lives in a group chat until it does not.
- Maintenance Jobs
Work orders with a status and an owner, so nothing sits unassigned for a week.
All 336 have a running demo. Open one before you copy it.
Straight answers
What we measured, and what we did not.
Internal tools hold data you would not want on the open internet. Here is where we stand.
One dashboard was built for real
An attendance dashboard was built end to end on a real account in 311 seconds. It is the closest thing on our list to an operations screen.
Company sign-in is not connected
The code for provisioning users from a company directory is written, but it has never been connected to a real identity provider. Logins today are email and password.
No load numbers
We have not measured how these screens behave with a large team hitting them at once. If that matters to you, treat it as untested.
Start
Replace one sheet.
Pick the one that hurts most and rebuild that. The rest can wait.