A small UX change that immediately reduced user confusion

I recently launched a small side project and felt pretty confident about the UX.

Turns out I was wrong, but in a specific way.

The search feature itself worked perfectly. It had live filtering, fast results, no delays or errors.

Technically, everything was fine.

But users were confused.

After watching how people interacted with the page, I realized the issue wasn’t functionality, it was visibility. Search results were updating as users typed, but they appeared in a section lower on the page, just outside where users’ eyes naturally stayed focused.when users hit enter it would take them directly to the results…I just didn’t anticipate users WOULDN’T hit enter.

Because the results weren’t immediately visible, people assumed search wasn’t working.

My first instinct was to fix it by adding more UI like a sidebar, extra menus, explicit search states, and navigation tweaks.

Instead, I paused for a day and asked a simpler question.

What would users expect to happen without thinking?

The answer was obvious in hindsight.

I swapped the order of two sections on the page, placing the results where users were already looking.

That was it.

No new features. No added complexity.

Confusion disappeared almost immediately.

It was a good reminder that users don’t experience “correct” design, they experience what’s obvious in the moment. Technical correctness means very little if the interface doesn’t align with instinctive behavior.

This change was part of a small project I’m building called ForgeIndex, a curated directory of open-source AI tools. It’s still early and intentionally simple, but this moment reinforced something I keep having to relearn lol..

The best UX improvements often come from removing friction, not adding features.

If you’re building something small, this is one of those lessons that’s easy to forget, and surprisingly powerful when you remember it.

If you’re curious, the project is called ForgeIndex: https://forgeindex.ai