The measure of good user interface design is not that visitors notice it. It is that they do not.
When a museum visitor finds the program they were looking for without thinking about how they found it, the interface worked. When a funder navigates from the About page to the outcomes section without friction, the interface worked. When a board candidate moves through a nonprofit’s leadership pages and arrives at the contact point feeling oriented and confident, the interface worked.
None of those visitors will mention the design. They will mention the organization, its clarity, its professionalism, its sense that everything is in order. The interface created that impression by staying out of the way.
Every institutional website presents visitors with a series of small decisions: where to look, what to read, what to do next. Interface design is the discipline of making those decisions easy, so that the visitor’s attention stays on the content rather than on figuring out how to find it.
This is harder than it looks. Most institutional websites have more content than any single visitor needs. Programs, staff, outcomes, history, events, news, resources, donation pathways, contact options, each of these competes for attention. The interface determines what a visitor encounters first, what they understand immediately, and what they can find when they need it.
When interface design works, that competition resolves invisibly. The visitor experiences coherence, not navigation. They feel that the website was built for them, even though it was built for many different types of visitors simultaneously.
Structured data tables are one of the most underused and most valuable interface elements available to mission-driven organizations. A museum managing collection data, a nonprofit tracking program outcomes across multiple sites, a healthcare organization presenting research results, all of these have information that is more useful organized as a structured table than presented as prose or bullet points.
A well-built data table does more than organize information. It respects the visitor’s intelligence by letting them sort, filter, and navigate to what is relevant to them rather than requiring them to read everything to find what they need. The interface becomes a tool rather than a container.
Contextual tooltips are the second. For organizations whose work involves terminology that varies by audience, clinical language that needs explanation for community members, technical program descriptions that need context for funders, governance language that needs clarification for prospective board members, a tooltip allows the full version of the content to remain accurate while making it accessible to readers who need more context.
Used well, tooltips do not interrupt reading. They extend it. The visitor who needs the explanation gets it. The one who does not is not slowed down.
Neither of these tools produces value by being present. They produce value when they are deployed in service of a specific visitor encountering a specific type of content.
A data table that organizes information the visitor did not need helps no one. A tooltip that explains a term the visitor already knows creates friction rather than reducing it. The interface decision is always downstream of the content decision, which visitors need what information, in what form, to move from uncertainty to confidence.
Organizations that make interface decisions before making those content decisions consistently produce websites that look considered but feel unclear. The execution is correct. The judgment behind it is missing.
That judgment, about who the visitor is, what they need, and how the interface can serve that need without announcing itself, is where the most valuable design work happens. It is also where most institutional website projects spend the least time.
The clearest signals are behavioral. If visitors frequently contact you to ask questions your website should already answer, if staff regularly send people directly to specific pages because the navigation is unclear, or if you find yourself apologizing for the site in professional contexts – the interface is creating friction the organization has learned to work around rather than address.
Only when the content requires them. A data table is appropriate when visitors need to compare, sort, or filter structured information – not simply read a list. A tooltip is appropriate when a term or element genuinely requires explanation for some visitors but not others. Using either without a specific visitor need in mind adds complexity rather than reducing it.
When visitors notice the interface rather than the content. Complexity that serves a clear visitor need – a sortable table for research data, a tooltip for technical terminology – is appropriate. Complexity introduced because a feature was available, or because it looked sophisticated in a demo, consistently undermines the clarity it was meant to support. The question before adding any interface element is whether it makes a specific visitor’s task easier – not whether it is technically possible.
Frances Naty Go is the founder of Goldlilys Media, where she helps mission-driven organizations turn their websites into clear, durable systems that support meaningful work over time. She works with museums, nonprofits, health and wellness brands, higher education, life sciences, travel organizations, and expert-led businesses.
With a background in Computer Science from UC San Diego, Frances brings a thoughtful, strategic approach to building digital experiences that educate, orient, and build trust, without unnecessary complexity.
Questions first? Start a conversation
