• The Who
  • The What
  • The When
  • The Where
  • The Why
The team behind UX design

UX design work in progress at a desk

UX design project timeline and scheduling
The screens where UX design is experienced
The business case for UX design

Why User Research Beats Assumption-Based Design

Research Methods and Bias Removal:

Interviews, session recordings, and behavior analytics show how visitors actually move through a site instead of how the internal team assumes they move. The team may believe the pricing page is easy to find while recordings show 60% of visitors who look for pricing leave without it. Both cannot be true. The recording is right, and the assumption gets replaced with what really happens.

Personas as Design Constraints:

A persona is a written profile of the main visitor type built from real data such as age range, device, intent, and the exact question they arrive with. Designing for a named persona with fixed constraints produces different choices than designing for a vague average. A 52-year-old facilities manager on an iPad at a job site brings different patience than a 28-year-old on a phone at home. One design cannot serve both equally, so the persona settles which one it favors.

Why Site Structure Should Follow the Visitor’s Mental Model

Card Sorting and Navigation Labels:

Card sorting asks real users to group site topics into categories that make sense to them. The groupings often differ sharply from internal assumptions. When users file pricing information under a section labeled About, the fix is to match the navigation to how visitors think rather than to the company org chart.

Sitemap Structure and Depth:

Each extra layer of navigation is one more gate a visitor clears before reaching the target page. Flat structure with plain top-level links cuts decision fatigue. Deep nesting under vague parent labels breeds frustration that analytics often blames on low interest instead of the navigation failure that caused it.

Why Structural Problems Belong in the Wireframe Stage

Low and High Fidelity Wireframes:

Rough sketches set layout, content order, and navigation flow before any color or polish enters the picture. Looks do not matter at this stage. Solving the structure quickly is the whole point. High-fidelity wireframes come next, adding precise spacing, actual content, and interaction states. The two kinds answer different questions at different stages of the work. Skip ahead to high fidelity before the structure is settled and the result is a detailed wireframe with a structural problem buried inside it, harder to see because the visual detail covers it, and far more expensive to dig out later.

Clickable Prototypes and Usability Testing:

A clickable prototype copies the finished flow without a line of code. Handing that prototype to users for real tasks shows where the flow breaks before development starts, which saves both time and budget later.

Why Mobile UX Is a Physical Problem First

Touch Target Sizing and Spacing:

Apple and Google both set a minimum touch target of 44×44 CSS pixels for anything tappable. Below that size, an average thumb misses at a measurable rate. Packing elements too close together causes the same missed taps, and a menu with list items set only 8 pixels apart vertically leads to steady misfires.

Fitts’s Law and Interaction Efficiency:

Fitts’s Law holds that the time to reach a target depends on its distance and its size. On mobile that means the main action belongs near where the thumb already rests and needs to be large, not small and far away. A call-to-action button parked at the top of a long service page forces a scroll or a grip change before the tap. A sticky footer button asks for neither.

Why Inclusive Design Serves More Than It Excludes

Contrast, Focus States, and Error Messages:

Normal text that fails a 4.5:1 contrast ratio against its background is text a share of visitors simply cannot read. A focus state marks on screen whichever element the keyboard is currently sitting on, and a site that hides it strands every keyboard user with no sense of where they are. Error copy fails the same way. “Invalid input” sends a visitor back to guess at a form they have already half given up on, while “Phone number must be 10 digits, numbers only” hands them the fix. Every one of those gaps costs completed forms, and the site keeps paying for it until the gap is closed.

ADA Legal Exposure and WCAG Compliance:

Title III ADA lawsuits over websites have climbed every year since 2017, and businesses across Tucson are not exempt. The standard most courts cite is WCAG 2.1 AA. A site that leaves accessibility out of the design brief ends up adding it later, at higher cost, after an audit or a complaint. Building it in from the start costs less and works better for the whole audience.

UX designers reviewing app wireframes and interface design

Why Simplicity Lowers the Cost of Staying


UX team brainstorming UI and user experience for a mobile app

What is the difference between UX and UI design?

Structure comes from the logic of how a visitor moves, meaning navigation labels, the order of form fields, and the shape of the conversion path. Visual work follows, set by color, type, and imagery. A UX problem hides inside a polished site that converts poorly. A UI problem shows up as a dated site that still works. Both matter.

What is the difference between UX and CX?

UX covers how someone uses a digital product such as a website, an app, or a booking flow. Customer experience covers the whole relationship, including sales calls, service delivery, and follow-up. UX is one part of CX and an important part. Better UX improves that one part without settling the rest.

How long does a UX audit take?

A full UX audit usually runs two to three weeks. The work includes reviewing session recordings, interviewing stakeholders, and running a heuristic evaluation against known UX principles. For a Tucson business the result is a ranked list of specific problems along the conversion path, each with a recommended fix. A rushed audit tends to produce a checklist rather than real analysis.

Does fixing UX require rebuilding the entire site?

Most fixes stop well short of a full rebuild. Renaming a navigation label or moving a call-to-action button happens on the existing site with no teardown. A rebuild earns its cost only when the trouble runs deep, such as a broken page hierarchy or a code base that cannot carry the change. Plenty of Tucson sites need the first kind of fix, not the second.

Does UX design affect SEO?

Search ranking reacts to how visitors behave, including time on the page, bounce rate, and pages per visit. A page that holds attention feeds those signals and tends to rank better even when the meta tags are plain. A page that loses visitors fast sends the opposite signal, and strong keywords cannot cover for it.

What is a dark pattern in UX?

A dark pattern is a design trick that pushes visitors into choices they never meant to make. Pre-checked boxes, an unsubscribe flow buried under extra steps, and links hidden on purpose all count. The tactic can lift a number for a short while, then it drains trust and invites legal trouble.

Why does whitespace matter in UX design?

Open space gives each element room, so the ones that matter stand out without shouting. Spacing alone sets an order of importance, no extra size or bold weight needed. The result asks less of a visitor at each glance and makes the page easier to move through.

What is above the fold and does it still matter?

Above the fold covers what shows before a visitor scrolls, and it still carries weight because it sets the first read. A clear promise and the main call-to-action both belong up there so a visitor has a reason to keep going. Leave that space weak and many people drop off before a single scroll.

How are mobile menus handled in UX design?

The hamburger icon reads as the default for mobile navigation, and most visitors know to tap it. Whether it fits depends on how many destinations sit behind it and how often people reach for them. For a Tucson service business with a phone number and a booking link that need to stay in view, a bottom bar or a visible button often beats tucking everything away.

Who owns the wireframes and design files after the project?

Every UX deliverable belongs to the client once the work is done and paid for, including the wireframes, prototypes, persona documents, and design files. Those outputs form the base for whatever gets built next. A firm that keeps them locked up after payment is building dependence, not handing over value.