One Form, One Job: Cut It Down Until It Fits in Rain
The 'All-in-One' form is a disaster. Why scrolling kills data quality, and how to design interfaces for people wearing gloves.
Big Buttons, Small Screens
I watched a crane operator try to use the new safety app. He was 30 meters up. It was windy. He had to fill out a “Pre-Lift Risk Assessment.”
He opened the app. It was a single, long scrolling page.
- Date (The phone knows this).
- Location (The GPS knows this).
- Crane ID (He is sitting in it).
- Wind Speed.
- Load Weight.
- Crew Names.
- …and 40 other fields for “General Notes.”
He spent five minutes scrolling. He took off his glove to hit the tiny “Submit” button. He was looking at the screen, not the load.
This is not just bad design. This is a safety hazard.
The Waste: Cognitive Load is Physical Weight
Office workers have big monitors. We use a mouse. We can scroll easily. We forget that a phone screen is small.
When you put 50 fields on a screen, you create noise. The user has to scan, filter, and decide what matters. This takes brain power. A worker in the field needs that brain power for situational awareness. They are watching for moving trucks, open pits, and swinging loads.
If you force them to fight the software, they stop watching the site.
Every “Optional” field is a stumbling block. Every dropdown menu with 100 items is a wall. Every time they have to type text instead of tapping a button, you add friction.
The result? They mash “N/A” into every box just to make the form go away. You get data, but it is garbage data.
The Flow: Context is King
We took the Mega Form and we shredded it. We replaced it with “Micro-Workflows.”
1. Don’t Ask, Detect. The app knows who is logged in. It knows the GPS coordinates. It knows the time. Do not ask the user to type what the machine already knows. We auto-fill the meta-data.
2. The Right Tool for the Job. If the user selects “Crane Lift,” they see five fields. Only the fields relevant to lifting. They do not see the fields for “Chemical Spills” or “Excavation.”
3. Big Targets. We made the buttons huge. The answers are “Pass” or “Fail.” Green or Red. You can hit them with a thumb while wearing a leather glove.
The Result
The inspection time dropped from 6 minutes to 45 seconds. The data quality went up. The operators stopped complaining.
We treated the software like a physical tool. You wouldn’t give a carpenter a hammer that randomly turns into a screwdriver. You give them a hammer. It does one thing. It does it well. It has a good grip.
Software must be the same. Sharp. Focused. Sturdy.
FAQs
But we need all that data for the dashboard.
Do you? Or do you just want it 'just in case'? 'Just in case' creates noise. Collect only what drives a decision.
Isn't it better to have one app for everything?
One app, yes. One screen, no. Break the app into small, sharp tools. A Swiss Army knife is bad at cutting down trees.
How do we decide what fields to cut?
Ask: 'If this field is blank, does the process stop?' If the answer is no, delete the field.