data.day
data-quality / ux-design / field-operations

The Office Loves “More Fields.” The Site Needs Fewer.

Data greed in the office creates garbage data in the field. Every extra field is a hurdle. We must delete the optional to save the essential.

Ingrid Pipeline Ingrid Pipeline

The Form is a Wall

It was raining sideways. The site engineer was trying to log a concrete pour. He held the tablet under his jacket. The form had 45 fields.

  • “Ambient Temperature” (The weather API knows this).
  • “Shift Supervisor Name” (The login knows this).
  • “Reason for Delay” (There was no delay).

He had to scroll. He had to tap “N/A” twelve times. He was not looking at the concrete. He was fighting the software. Finally, he gave up. He selected “No Issues” for everything, even though the mix was too wet. He submitted the form.

The data was clean. The reality was messy. The software had walled off the truth.

The Waste: Friction Creates Silence

Every input field is a tax on the user’s attention. When the tax is too high, the user commits tax evasion.

In field operations, “tax evasion” looks like this:

  1. The Pencil Whip: Selecting the first option in every dropdown menu just to finish.
  2. The Blank Stare: Leaving optional fields empty, even when they matter.
  3. The Shadow Log: Writing the real notes in a paper notebook because the app is too annoying.

The office thinks they are collecting “Big Data.” In reality, they are collecting “Big Noise.”

The Flow: Minimum Viable Capture

We must practice subtraction. We audited the concrete log. We cut it from 45 fields to 4.

  1. Photo: Take a picture of the ticket.
  2. Volume: Type the number.
  3. Status: Pass / Fail.
  4. Notes: Only if “Fail” is selected.

Everything else—time, user, location, weather—was captured automatically by the device sensors.

The engineers stopped fighting the tablet. They started inspecting the concrete. When a load was bad, they actually reported it. Because the form was short, they had the patience to be honest.

Respect the Context

A form is not a survey. It is a tool. You do not give a carpenter a hammer with twenty switches on the handle. You give them a solid grip and a heavy head. Build your forms like hammers. Simple. Heavy. Effective.

FAQs

How do we know which fields to delete?

Ask: 'If this field is empty, do we stop the job?' If the answer is no, delete it. If it is 'nice to have,' it is trash.

But more data means better analytics, right?

Wrong. More friction means worse data. You get 100 fields of garbage instead of 5 fields of truth.

Can we hide the fields instead?

Yes. Use conditional logic. Only show the 'Damage' field if the user clicks 'Damaged'. Do not clutter the screen with irrelevant questions.