Latest / 5 Minute UX / Justifying Data Entry Requests
Transcript
- 0:08This lesson is Justifying Data Entry Requests. Let's get
- 0:12started.
- 0:18When a web design team rushes to gather rich data, they often
- 0:21create sites demanding an intimidating number of personal
- 0:24information fields. User research identified this
- 0:26specific failure mode: the absence of an obvious statement
- 0:28explaining why that data is needed. Users are typically
- 0:31solving urgent issues, a situation that does not lend
- 0:33itself to patience with data entry requests. Without clear
- 0:36justification, they feel the company is taking their time and
- 0:39data without clear returns. This creates a direct conflict
- 0:41between business needs for rich data and user needs for low
- 0:44patience and clear returns. The principle "give and take and
- 0:47give" resolves this tension. It is a short, memorable phrase
- 0:50designed to help project teams understand when and how to
- 0:52gather user information beneficially. The phrase plays
- 0:55on the common idiom to make the guidance stick in busy project
- 0:58environments. The principle is rooted in that specific research
- 1:01finding about intimidating fields. It forces the team to
- 1:03look at the user’s context before asking for input. The
- 1:06goal is to ensure every request serves a clear purpose. This
- 1:08shifts the design focus from data collection to user benefit.
- 1:11The next step is to justify the initial "give" by providing
- 1:14users a good reason for needing that specific data at that
- 1:17particular time.
- 1:23Consider a user trying to resolve an urgent billing error.
- 1:25They are not browsing; they are solving a problem. In that
- 1:28specific moment, their patience is low, and every extra field
- 1:30feels like an obstacle. The first test question addresses
- 1:33this directly: Can we give users a good reason for needing this
- 1:35particular data at this particular time? This phrasing
- 1:37is critical because it ties the request to the immediate
- 1:40context, not just the general business goal. The third edition
- 1:42of the guide emphasizes this point by asking for a good
- 1:44reason for needing the specific data at the specific moment of
- 1:47request. Without that clear justification, the user
- 1:49perceives the company as taking their time and their data
- 1:51without clear returns. That perception leads directly to
- 1:53frustration. So when you design a form, you must articulate why
- 1:56that specific piece of information is needed right
- 1:58then, not just why the business values it later. This
- 2:00justification is the "give" that earns the user's willingness to
- 2:03provide the "take."
- 2:09The second test question asks, "Do we only take data that we
- 2:11can’t get some other way?" This forces designers to consider
- 2:14alternative methods of data acquisition before requesting
- 2:17direct user entry. The third edition phrasing sharpens this
- 2:19by emphasizing that you take only the data you need and can’t
- 2:22get some other way. It’s a strict filter for any field on a
- 2:25form. Consider a user solving an urgent issue with low
- 2:27patience. They are not willing to re-enter their email address
- 2:30if your system already has it. If you can pull that information
- 2:33from an existing user profile or an A.P.I. check, you must. The
- 2:36"take" is only justified when no other route exists. This
- 2:38criterion protects the user’s time by eliminating redundant
- 2:41fields. It ensures every data request is truly necessary for
- 2:44the immediate task. So when you audit a form, you check each
- 2:46field against this standard. You verify that no alternative
- 2:49source exists for that specific piece of information.
- 2:57So you have the principle, you have the two test questions, and
- 3:00now you have a form in front of you that needs to pass. The
- 3:02audit starts by looking at every single field and asking the
- 3:05first question directly: can we give users a good reason for
- 3:07needing this particular data at this particular time? You aren't
- 3:10just checking if the data is useful to the business, you are
- 3:12checking if the justification lands in the moment the user is
- 3:15filling it out. If a field asks for a billing address but the
- 3:17user is just checking their order status, that field fails
- 3:20the first test because the reason doesn't match the
- 3:22specific time of the request. Once you have cleared that
- 3:24hurdle, you move to the second test, which is where the real
- 3:27pruning happens. You ask: do we only take data that we can’t get
- 3:29some other way? This forces you to look at the field and see if
- 3:32the information already exists somewhere else. If the user is
- 3:34already logged in, does the system have their email address?
- 3:37If so, asking for it again is a violation of the principle. You
- 3:39might be able to pull it from an existing user profile or check
- 3:42it via an A.P.I. call. If the data can be obtained through
- 3:44those other means, the field should be removed from the form
- 3:47entirely, because taking it directly from the user adds
- 3:49friction without adding value. The final step is stepping back
- 3:51to assess the overall user experience. You need to
- 3:53determine if the form respects the user's low patience level
- 3:56while they are solving an urgent issue. When a user is trying to
- 3:59fix a broken process or resolve a critical problem, their
- 4:01tolerance for data entry is at its lowest. If your form still
- 4:03feels like a wall of personal information fields after you
- 4:06have applied both test questions, it is not meeting the
- 4:08standard. The goal is to leave the user feeling like the
- 4:10interaction was a fair exchange, not a tax. You have now applied
- 4:13the think-aloud protocol to critique a sample data entry
- 4:15form for intrusive or unnecessary fields. The moment
- 4:17you next open a form to design or review, you will hold each
- 4:20field up to those two specific questions before it ever reaches
- 4:22a user's screen.
- 4:26Welcome to The Take. I'm joined by a fellow practitioner and
- 4:29together we're going to dig into Justifying Data Entry Requests —
- 4:32what it means in practice and what's worth remembering.
- 4:36[HOST] That phrasing about the "specific time of request" is
- 4:39where most teams fail. [LEARNER] It’s the context gap. We justify
- 4:43the data for the business, not for the user’s panic. [HOST]
- 4:46Exactly. The user isn't browsing, they’re fixing a
- 4:49broken invoice. [LEARNER] So the justification has to be
- 4:52immediate, not strategic. [HOST] It has to land in that very
- 4:55second they’re staring at the form. [LEARNER] I struggle with
- 4:58that in legacy systems. The data is stored, but the UI can’t show
- 5:02why it’s needed right now. [HOST] That’s a technical debt
- 5:05problem disguised as a UX issue. [LEARNER] Right. We ask for the
- 5:09email again because the API call is slow or flaky. [HOST] But if
- 5:12you can get it another way, you must. [LEARNER] Even if it’s
- 5:16inconvenient for the backend team? [HOST] Especially then.
- 5:19The friction is on the user, not the dev. [LEARNER] That’s a hard
- 5:22sell to engineering. [HOST] You frame it as removing a tax on
- 5:26the user. [LEARNER] I like that framing. It shifts the cost to
- 5:29the company. [HOST] Which is where it belongs. [LEARNER] What
- 5:33about AI? Can it help write those justifications
- 5:35dynamically? [HOST] It can, but it’s dangerous. [LEARNER] Why?
- 5:39[HOST] Because it might generate a polite excuse instead of a
- 5:42true reason. [LEARNER] A hallucinated benefit. [HOST]
- 5:45Yes. It sounds nice, but it’s not the specific justification
- 5:49the user needs. [LEARNER] So AI is a risk if we let it fill the
- 5:52gap in our thinking. [HOST] It amplifies whatever intent we
- 5:55have. [LEARNER] If the intent is lazy, the output is worse.
- 5:59[HOST] If the intent is clear, the output is sharper. [LEARNER]
- 6:02That’s a good way to look at it. [HOST] The tool is neutral. The
- 6:06principle isn't. [LEARNER] We still have to do the hard part.
- 6:09[HOST] We do. The AI just types faster. [LEARNER] But it doesn’t
- 6:13think for us. [HOST] No. It just makes our bad decisions scale.
- 6:16[LEARNER] So the audit has to happen before the prompt. [HOST]
- 6:20Exactly. You verify the need, then you generate the copy.
- 6:23[LEARNER] If we skip the verification, we just have a
- 6:26smarter form. [HOST] A more efficient tax. [LEARNER] That’s
- 6:29a scary thought. [HOST] But it’s avoidable. [LEARNER] By sticking
- 6:33to the give and take. [HOST] Yes. And the give has to be
- 6:36real. [LEARNER] Not just a placeholder. [HOST] Not a
- 6:39placeholder. A reason. [LEARNER] A specific, immediate reason.
- 6:42[HOST] That’s the standard.