Web design methodology has substantial research behind it. Decades of studies have examined what produces effective interfaces, what affects conversion, what supports accessibility, and what enables maintainability. Yet design methodology in practice often departs from the research, defaulting to designer intuition or reference to current trends.
This article presents a methodology framework grounded in published research on web design effectiveness.
The research base
Several research traditions inform contemporary web design methodology:
1. Usability research. Decades of work by Jakob Nielsen, Don Norman, and others has produced robust principles for interface usability. Most are well-documented; many are routinely violated in practice.
2. Conversion optimization research. Empirical studies of what affects user behavior on commercial sites. Substantial body of evidence on form design, call-to-action effectiveness, and content presentation.
3. Accessibility research. WCAG guidelines and supporting research on what produces accessible interfaces for users with various disabilities.
4. Performance research. Studies of how page load time and interaction responsiveness affect user behavior and business outcomes.
5. Cognitive load research. Research on how interface complexity affects user comprehension and decision-making.
A methodology grounded in this research differs systematically from intuition-based design.
The phases of research-grounded methodology
Discovery phase
Research-grounded discovery investigates user needs, business objectives, and contextual constraints before design begins. Specific activities include:
- Stakeholder interviews to clarify business objectives and success criteria
- User research (interviews, surveys, or analytics review) to understand user needs
- Competitive analysis to understand market context
- Technical assessment of constraints and opportunities
- Content audit when working with existing content
Discovery produces specific deliverables: documented user personas, business objective definitions, success metrics, and technical specifications. Without these, subsequent phases lack defensible grounding.
Information architecture phase
Information architecture defines the structural organization of content and functionality. Research consistently shows that information architecture choices substantially affect user task success — often more than visual design choices.
Methodology elements:
- Card sorting or similar techniques to validate organizational schemes
- Site map development with rationale for organizational decisions
- User flow mapping for primary tasks
- Navigation pattern selection based on content depth and task structure
Interface design phase
Interface design produces the visual and interaction patterns that users encounter. Research-grounded interface design follows established usability principles even when fashion suggests otherwise.
Methodology elements:
- Wireframing to establish layout and content priority before visual design
- Visual design that reflects business positioning while respecting usability principles
- Interaction pattern selection based on platform conventions and user expectations
- Accessibility review against WCAG criteria
- Performance budget definition
Validation phase
Research-grounded methodology includes validation of design decisions through user testing or analytical review before final implementation.
Methodology elements:
- Usability testing with representative users
- A/B testing where appropriate and feasible
- Heuristic evaluation against established usability principles
- Accessibility testing with assistive technologies
Common methodological gaps
Several patterns of methodological gap consistently appear in agency practice:
- Discovery compressed or skipped. Time pressure leads to compressed discovery, which produces designs ungrounded in actual user needs.
- Information architecture treated as visual design. Agencies focus on visual treatment without rigorous IA work, producing visually polished but structurally weak sites.
- Accessibility treated as compliance afterthought. Accessibility considered late produces compromised solutions; integrated from start produces better outcomes.
- Validation skipped. Most projects launch without user testing of the actual design, missing opportunities to identify problems pre-launch.
The methodology versus deliverable distinction
An important distinction in agency practice: methodology is the process; deliverables are the artifacts. Agencies sometimes confuse the two, focusing on producing standard deliverables (wireframes, mockups, style guides) without the underlying methodology that gives those deliverables value.
A wireframe produced through user research is fundamentally different from a wireframe produced through designer intuition, even if the visual artifact looks similar. The methodology determines whether the deliverable is grounded in evidence or in preference.
The takeaway
Web design methodology has substantial research behind it that practice can systematically apply. The framework above identifies the key methodological phases and the research base that informs each.
For agencies seeking to improve design outcomes, audit current practice against the methodology framework. Gaps typically appear in discovery depth, information architecture rigor, and validation. Each is addressable.
Source notes
Methodology synthesizes published usability research from Nielsen Norman Group, accessibility guidelines from W3C/WCAG, and design methodology research from major HCI publications 2010-2024.
