[A Checklists Project]

[A Checklists Project]

Field Relevance

Field Relevance

Field Relevance

Improving data accuracy and completeness in Checklists.

Platform

Mobile / Desktop

Role

Product Designer /Researcher

Delivery Time

6 Weeks

A desktop screen in the background with an iPhone 14 Pro in the foreground. Showing the feature on both platforms.

The Problem

Irrelevant tasks in Checklists led to missing or unreliable data, frustrating users and creating messy reports. Many requested ‘Conditional Logic’ to show only relevant fields, improving accuracy.

The Problem

Irrelevant tasks in Checklists led to missing or unreliable data, frustrating users and creating messy reports. Many requested ‘Conditional Logic’ to show only relevant fields, improving accuracy.

The Solution

To fix this, we introduced a “Not Applicable” option, letting teams skip irrelevant sections without breaking checklist completeness. This prevents incorrect data entry, reduces confusion, and ensures clean, reliable reports—especially when shared with third parties.

The Solution

To fix this, we introduced a “Not Applicable” option, letting teams skip irrelevant sections without breaking checklist completeness. This prevents incorrect data entry, reduces confusion, and ensures clean, reliable reports—especially when shared with third parties.

~15%

decrease in user reported error

~15%

decrease in user reported error

~15%

decrease in user reported error

~18%

increase in checklists completed

~18%

increase in checklists completed

~18%

increase in checklists completed

Template Onboarding

The onboarding experience is tailored for our two main user personas: office staff and field workers. It introduces key features relevant to each role, ensuring users quickly see the unique benefits that matter most to them.

Template Onboarding

The onboarding experience is tailored for our two main user personas: office staff and field workers. It introduces key features relevant to each role, ensuring users quickly see the unique benefits that matter most to them.

Template Controls

Admins and managers can set sections as required or optional within a Checklist Template on the web. This controls when the “Mark N/A” button appears for field users on mobile. For example, if siding/soffit isn’t part of a job, that section can be hidden, keeping checklists relevant and ensuring accurate completion.

Template Controls

Admins and managers can set sections as required or optional within a Checklist Template on the web. This controls when the “Mark N/A” button appears for field users on mobile. For example, if siding/soffit isn’t part of a job, that section can be hidden, keeping checklists relevant and ensuring accurate completion.

Marking Sections N/A

Field users can mark entire sections as Not Applicable (N/A) to remove irrelevant tasks while automatically adjusting the total task count. Once marked N/A, the section collapses out of view, reducing clutter and making checklists easier to navigate.

Marking Sections N/A

Field users can mark entire sections as Not Applicable (N/A) to remove irrelevant tasks while automatically adjusting the total task count. Once marked N/A, the section collapses out of view, reducing clutter and making checklists easier to navigate.

Field User Error Prevention

User interviews revealed that field workers often complete checklists one-handed—sometimes while on ladders—leading to accidental mistakes. To solve this, I introduced a Restore feature, effectively adding an Undo button for quick corrections.

Field User Error Prevention

User interviews revealed that field workers often complete checklists one-handed—sometimes while on ladders—leading to accidental mistakes. To solve this, I introduced a Restore feature, effectively adding an Undo button for quick corrections.

The Context

Field users frequently encountered checklist items that didn’t apply to their work—like roofing tasks when working on gutters. To bypass these, users often took random photos or left fields blank, causing confusion and unreliable reports. Office staff repeatedly requested Conditional Logic, allowing checklists to dynamically show only relevant fields, improving both accuracy and usability.

The Context

Field users frequently encountered checklist items that didn’t apply to their work—like roofing tasks when working on gutters. To bypass these, users often took random photos or left fields blank, causing confusion and unreliable reports. Office staff repeatedly requested Conditional Logic, allowing checklists to dynamically show only relevant fields, improving both accuracy and usability.

…They’ll [field workers] just put in a picture of a vent from one of the trucks, you know, because they have to put something in. My crews won’t get credit for the job unless it’s 100% complete.

There are very different types of homes and situations that we run into. And if we run into situation A, we need photos one, two, and three. If we run into situation B, we need one through four. And if we run situation C, we need three, six, and eight. And that's where the conditional logic would really, really help.

We want to be able to click something here to say close task complete even though with nothing available to it, like so that we can get to 40% no matter what without having to take pictures of our shoes and write a bunch of stuff here.

Not every project needs all the fields, so the crew either skips them or fills them with junk...

The Users

This project had two main user groups: office staff and field workers. Office staff needed accurate checklists for financial reporting but struggled with data accuracy. Field workers needed to get tasks done efficiently but dealt with irrelevant tasks and physical constraints, leading to bad data.

The Users

This project had two main user groups: office staff and field workers. Office staff needed accurate checklists for financial reporting but struggled with data accuracy. Field workers needed to get tasks done efficiently but dealt with irrelevant tasks and physical constraints, leading to bad data.

Office Manager

Responsibilities

• Keeping track of crew

• Communicating with clients

• Ensuring accurate information

Frustrations

• Struggles with clear communication between the office and field teams

• Finds it time-consuming to verify authenticity of inrofmartion provided by field workers

• Frequently has to manually correct or fill in missing data

Technical Proficiency

• Medium

Field Worker

(non-supervisor)

Responsibilities

• Completing tasks created in advance

• Communicating updates and changes to the main office/supervisor

• Regular documentation of ongoing progress

Frustrations

• Often faces irrelevant tasks within Checlists, leading to incomplete or inaccurate data

• Feels rushed to complete tasks quickly

• Struggles using many digital tools, and is forced to use work-related applications

Technical Proficiency

• Low

Sketch Exploration

While developing a solution, I initially explored broadly, considering larger fixes like incorporating accumulated debt and implementing conditional logic to show and hide relevant tasks. This approach aimed to address the core issue of ensuring only pertinent tasks are displayed to improve data accuracy and streamline checklist completion.

Sketch Exploration

While developing a solution, I initially explored broadly, considering larger fixes like incorporating accumulated debt and implementing conditional logic to show and hide relevant tasks. This approach aimed to address the core issue of ensuring only pertinent tasks are displayed to improve data accuracy and streamline checklist completion.

Early sketches exploring the flow of various layouts and interactions for task management and conditional logic.
Early sketches exploring the flow of various layouts and interactions for task management.
Early sketches exploring the flow of various layouts and interactions for task management and conditional logic.

Prototyping

This was my first attempt at prototyping conditional logic, focusing on drag-and-drop interactions. The goal was to validate some of the larger architectural changes.

Prototyping

This was my first attempt at prototyping conditional logic, focusing on drag-and-drop interactions. The goal was to validate some of the larger architectural changes.

A Refocus on MVP

fter extensive discussions with the team, engineering, and stakeholders, we decided to pause the larger vision and refocus on the core MVP: preventing bad and missing data. While the initial exploration showed promising potential, the risk was too high to move forward. The biggest concern? We didn’t have enough clarity on how widely this feature would be adopted across the broader checklist audience.

A Refocus on MVP

fter extensive discussions with the team, engineering, and stakeholders, we decided to pause the larger vision and refocus on the core MVP: preventing bad and missing data. While the initial exploration showed promising potential, the risk was too high to move forward. The biggest concern? We didn’t have enough clarity on how widely this feature would be adopted across the broader checklist audience.

A Defining Direction

Below is the keystone sketch for the project’s future direction. Instead of remaking Checklists for conditional logic, can we ‘simply’ make entire tasks or sections optional?

A Defining Direction

Below is the keystone sketch for the project’s future direction. Instead of remaking Checklists for conditional logic, can we ‘simply’ make entire tasks or sections optional?

An early sketch exploring various options to 'skip' or mark entire sections as optional within a checklist.

Work

About

Work

About

Work

About

LinkedIn

© 2025 Lance Rice | Built in Framer

Work

About

LinkedIn

© 2025 Lance Rice | Built in Framer