2026-07-21 · 7 min read · Raw Drafts / UX / Product Design
The First Win Is Not a UI Problem
Attio's home screen is clean, legible, and easy to scan. Yet onboarding can still fail when the product shows its system before it produces one useful result.
I sign up for new apps because I can already imagine the improved version of my life inside them.
A CRM will help me remember people. A planning tool will make work feel controlled. A knowledge app will prevent ideas from disappearing. The promise is strong enough to make me create an account, choose a workspace name, and accept another product into my digital life.
Then I reach the home page.
In Attio, the visible page is clean and calm. The left navigation separates companies, people, tasks, notes, emails, calls, and reports. The main area contains an AI prompt, meetings, tasks, and a getting-started card. The typography is readable. The hierarchy is understandable. Nothing looks broken.
And yet this is exactly the kind of page I may close and never return to.
That does not make it bad UI. It reveals a different problem.
The interface has shown me the system before the product has shown me a result.
This is not a complete review of Attio, and the page may represent a workspace that is only partly configured. The point is narrower: a visually successful interface can still produce an unsuccessful first experience.
Attio home page check
The interface is polished. The first outcome is missing.
| UI design | UX design | Product design |
|---|---|---|
Clear navigation and readable hierarchy | No single obvious first action | No immediate business outcome |
Meetings, tasks, and records are easy to find | Empty sections create uncertainty | Value still depends on more setup |
Getting started is visible | Some guidance, but several competing choices | No useful follow-up is surfaced automatically |
UI has already done its job
UI design asks whether the visible interface is understandable.
Can I read the labels? Can I distinguish one section from another? Do the buttons look interactive? Can I find meetings, tasks, people, and companies? Does the page feel coherent?
On the visible Attio home page, the answer is mostly yes.
The problem is not that the user cannot operate the interface. The problem is that operating it has not yet become worthwhile.
This distinction matters because redesign conversations often jump directly to presentation. Make the getting-started card larger. Increase the contrast of the primary action. Simplify the sidebar. Add an animated empty state.
Those changes might improve clarity, but they would not decide what the user should achieve first.
A more prominent checklist is still a checklist. A prettier empty dashboard is still empty.
UX is the sequence, not the screen
UX design asks what happens across time.
The user signs up with curiosity. They arrive with limited attention and almost no commitment. They scan the page, search for a clear next step, estimate how much setup will be required, and decide whether continuing feels worth it.
Every empty section creates a small question.
Should I connect my calendar? Import contacts? Create a list? Ask the AI something? Add a task? Finish the onboarding checklist? Explore the sidebar first?
None of these choices is individually difficult. Together, they create uncertainty.
The user does not know which action will produce value fastest, so the responsible-looking choice is to postpone the decision. They tell themselves they will set everything up properly later.
That sentence is often the beginning of abandonment.
The UX problem is therefore not simply friction. It is the absence of a confident sequence from signup to usefulness.
Product design must choose the first outcome
Product design asks the question that UI cannot answer:
What should Attio make true for this user within the first few minutes?
For a CRM, the answer should probably not be "the user has explored the navigation" or "the user has completed four setup steps."
Those are signs of activity, not signs of value.
A meaningful first outcome might be:
- Three relationships that need a follow-up
- One important conversation that has gone quiet
- A contact timeline assembled from existing email and calendar data
- An upcoming meeting with the relevant history already prepared
The exact outcome depends on the intended user and Attio's product strategy. That decision is the product-design work.
Once the first outcome has been chosen, UX can create the shortest credible path toward it. UI can then make that path clear, legible, and reassuring.
The order matters.
Product design chooses the win. UX designs the journey into the win. UI makes the journey operable.
A checklist is not a win
The getting-started card shows that Attio knows onboarding is unfinished. It offers structure and visible progress, which is better than leaving the user completely alone.
But setup completion and user success are not the same thing.
A checklist usually describes what the product needs from the user: connect something, create something, import something, configure something.
A first win describes what the user receives in return.
This is the difference between:
Connect your email.
and:
Connect your email to find three conversations that may need a reply.
The first is a task. The second is an exchange.
The user gives access and effort. The product promises a concrete result.
Without that exchange, onboarding creates setup debt. The app becomes another unfinished project waiting for the user's future energy.
The emotional journey declines quietly
The user does not necessarily become angry. That would at least create a memorable event.
More often, interest fades through small reductions in confidence.
Illustrative emotional journey
Curiosity falls before value appears
A conceptual journey based on the visible Attio home page, not measured user research.
The user begins with a belief that the product could help. The empty home page converts that belief into a list of possible chores. The lack of an immediate result makes the value feel theoretical. Leaving feels harmless because nothing important has happened yet.
The product has not been rejected. It has simply failed to become memorable.
This is why onboarding should not only explain the product. It should create evidence.
Show value before exposing the whole system
Attio is a flexible product. Flexibility requires lists, records, attributes, views, integrations, tasks, and workflows. The product cannot remove all complexity without removing its power.
But it can decide when complexity appears.
A better first-use sequence could be opinionated:
- Ask what the user wants to manage, such as sales, clients, partnerships, or a professional network.
- Request one relevant connection, with a clear explanation of the result it will produce.
- Generate one useful output from existing data.
- Let the user act on it.
- Only then introduce the broader system that makes the result repeatable.
The product would still become flexible. It would simply earn the right to ask for configuration.
This is progressive complexity applied to product value, not just interface controls.
Activation is proof, not persuasion
The language of activation can sound manipulative. It can suggest tricks designed to hook users, inflate engagement, or manufacture habits that do not serve them.
A real first win is different.
It does not persuade the user that the product is useful. It demonstrates usefulness.
The user returns because something became easier, clearer, or more actionable. The product earned attention by producing evidence.
That is the central failure mode visible in the Attio page. The UI communicates the available machinery, but the onboarding experience has not yet converted that machinery into one undeniable result.
The page says: here is your CRM.
It should first say: here is something your CRM already helped you notice.
The first screen should reduce uncertainty
A successful first screen does not need to show the whole product. It needs to answer three questions:
- What can this do for me right now?
- What is the smallest action required?
- What useful result will appear next?
When those answers are missing, visual polish cannot rescue the experience.
The interface may be beautiful. The components may be consistent. The navigation may be excellent.
But the product has not yet created a reason to care.
That is why the first win is not a UI problem.
It is a product decision expressed through a UX sequence and supported by an interface.
Do not onboard users into the system.
Onboard them into a win.
AI authorship note
This essay grew from Kris Haamer's first-use experience with Attio and his analysis of the visible home page. AI supported the article structure, distinction between UI, UX, and product design, editing, table design, emotional-journey visualization, and implementation. Kris supplied the central observation, directed the Attio-specific critique, and made the decision to publish it.