Don’t Make Me Think: Usability Tips for R&D

Usability is often seen as something for UX and Product teams, but it directly impacts R&D, testing, and support. When users struggle with an interface, it leads to unnecessary validation logic, state handling, and rework — problems that end up on the engineering side.

I’ve spent years developing complex software applications, and while I’m not a UX expert, I’ve seen usability mistakes turn into engineering problems, extra meetings, and feature redesigns. The core principle of good usability is simple: Don’t make the user think.

Here are the key usability principles R&D teams should focus on in discussions with UX and Product.

1. Fact: People Scan, They Don’t Read

Users do not carefully process everything on the screen; they scan for what stands out. They look for recognizable patterns, clickable elements, and key actions. If critical actions or information aren’t obvious, users hesitate, misclick, or assume something is broken.

How This Affects Development:

• UI should be divided into meaningful blocks so users can process information quickly.
• Instead of adding tool tips or help text, it’s better to improve layout and contrast.
• If validation errors go unnoticed, message placement is likely the issue, not user behaviour.

2. Structure Matters More Than Individual Elements

A well-structured UI guides users naturally. Poor structure forces developers to handle unnecessary errors and workarounds.

How This Affects Development:

• If Product asks for complex backend checks to prevent mistakes, a better UI flow might prevent those mistakes from happening at all.
• A poorly structured form might result in incorrect data submissions that require backend fixes.
• Bad structure creates false bug reports because users interact in ways that weren’t anticipated.

3. Navigation Should Prevent Users From Getting Lost

Users should always know where they are, what they can do next, and how to go back.

Best Practices for Navigation:

• Breadcrumbs help users understand their position.
• Persisting state in URLs allows users to refresh or share links without losing progress.
• Consistent navigation placement prevents confusion and unnecessary relearning.

How This Affects Development:

• Instead of building extra error handling for lost users, proper navigation prevents confusion upfront.
• Instead of adding confirmation dialogs, better navigation removes the need for extra warnings.
• Poor navigation increases support tickets and backend tracking complexity.

4. Users Shouldn’t Have to Guess (Obvious Always Wins)

If users hesitate, they’re unsure what will happen next — a clear sign of bad usability.

How This Affects Development:

• Buttons and icons should be self-explanatory — users shouldn’t rely on hovering for more info.
• Instead of building extra user guides, improve button labels and layout.
• When users constantly click the wrong option, the UI is misleading, not the user.

5. Users Won’t Read Instructions (So the System Should Guide Them)

Most users ignore manuals and tooltips. If they need instructions, the UI isn’t intuitive enough.

How This Affects Development:

• Instead of forcing users to read FAQs, design workflows that guide users through steps naturally.
• Long error messages should be replaced with real-time input validation.
• Instead of adding more text, use clearer labels, placeholders, and progressive disclosure.

6. Every Click Should Have a Clear Result (Instant Feedback Matters)

When users click something, they expect an immediate response. If nothing happens, they assume it’s broken.

How This Affects Development:

• Buttons should provide instant visual feedback when clicked.
• If an action takes time, a loading indicator should appear immediately.
• Instead of handling duplicate submissions on the backend, better UI feedback prevents extra clicks.

7. The Home Page Isn’t the Starting Point for Everyone

Users often land on deep links — a search result, shared URL, or bookmarked page.

How This Affects Development:

• URLs should always reflect state, so users don’t have to restart workflows.
• Every page should provide enough context — users shouldn’t have to navigate back to the homepage.
• Features should be accessible from multiple entry points, not just through a fixed flow.

8. Conventions Exist for a Reason — Follow Them

Users don’t want to relearn basic UI interactions. They expect buttons, menus, and forms to work like they do everywhere else.

How This Affects Development:

• Custom UI elements should only be used if they provide real value — otherwise, they confuse users.
• Common UI patterns (like placing “Submit” buttons at the bottom of forms) should be respected, not reinvented.
• If a feature behaves differently from what users expect, they will assume it’s broken.

Final Thought: Understanding the main principles of Usability Saves R&D from a lot of unnecessary work

Every usability issue that isn’t addressed early eventually turns into extra development, rework, or support tickets. Understanding these core principles helps R&D collaborate more effectively with UX and Product, making the development process smoother, more efficient, and less frustrating for everyone.

These aren’t just abstract ideas — I’ve practiced these principles for over a decade while developing and architecting complex applications. Time and time again, I’ve seen how applying them reduces unnecessary work, improves user satisfaction, and prevents last-minute design fixes.

Many of these challenges are explored in Don’t Make Me Think by Steve Krug, a book that captures the essence of usability debates that happen in every development team. Hope this helps.