What research and optimization delivers

Why COLAB for research and optimization

What research and optimization includes

Scope depends on the question you need answered and the data you already have. Engagements draw from the following methods, and most combine a few of them.

Three ways to get started

Most clients start with a diagnostic or a single question. Some move into a standing program once the first round of changes shows results.

Site Diagnostic

A fixed-scope review across analytics, UX, accessibility, performance, and search. You get a findings report, a ranked list of changes with estimates, and a working session to agree on what comes first. A good starting point for an inherited site, or before deciding on a redesign.

One question, answered with the method that fits it. Testing a new navigation before it is built, interviewing members before reworking a product section, or reviewing competitors ahead of a rebrand. Scope and timeline are set by the question.

Optimization Program

A recurring cycle of measurement, hypotheses, tests, and changes against an agreed set of goals. It pairs with ongoing support. The changes that win get shipped by the same team that measures them.

Our approach

Research only helps if it leads to a decision and a change you can measure. Each engagement follows the same arc as our project work, scaled to the size of the question.

Understand what is happening

We start with the question and the people who need the answer, then get access to analytics, Search Console, and the CMS. The first task is usually checking that tracking works, because a surprising number of “drops” turn out to be a broken tag. From there we run the audits and research the question calls for.

Align on what to change

Findings are presented in a working session with your team, along with a ranked list of changes and the evidence behind each one. Together we decide what to fix outright, what to test first, and what to leave alone. Each item leaves the session with an owner and an estimate.

Grow by testing and measuring

Changes ship as A/B tests where traffic supports it, and as before-and-after measurement where it does not. The results go back into the list and shape the next round. Build, Launch, and Learn repeat for as long as there is a question worth answering.

Who we work with

We work with organizations whose website is expected to produce results, and where someone has to explain it when the numbers fall.

  • Marketing and communications leaders asked why web leads, registrations, or donations are down
  • Credit unions comparing their digital experience with peer institutions and online banks
  • Healthcare organizations where patients struggle to find a provider, a location, or a way to book
  • Nonprofits deciding where a limited budget should go before a campaign or redesign
  • Digital teams preparing for a redesign who want evidence before they commit to a direction
  • Organizations that inherited an analytics setup nobody trusts

When research and optimization matters most

This work earns its keep when at least one of the following sounds familiar.

  • Traffic or conversions dropped and nobody can say why
  • Leadership wants a redesign, and you want to know what is broken before paying to rebuild it
  • Stakeholders disagree about the navigation, and each has a strong opinion
  • A peer or competitor launched a new site and you want to know how yours compares
  • Your analytics reports and what your team hears from the front desk tell different stories
  • AI search tools describe your organization inaccurately, or leave it out

Methods matched to your traffic

A/B testing needs enough visitors to reach a reliable answer, and on many healthcare, nonprofit, and association sites that would take months. Tree tests, usability sessions, and before-and-after measurement answer the same questions with far fewer people. We tell you at the start which methods your traffic supports, before any budget goes into a test that cannot finish.

Frequently Asked Questions

How is this different from Product Strategy?

Product Strategy decides what to build and why. Research and optimization looks at what is already live and finds out why it is underperforming. The two often feed each other. A diagnostic can show that a redesign is needed, and when it does, the findings become the starting evidence for the strategy work.

Do we need a redesign to fix what you find?

Often, no. Many of the problems a diagnostic turns up, such as a broken form, a confusing label, or a slow template, can be fixed on the current site. When the findings point to a structural problem, we say so and show the evidence. You decide what to do with it.

Will you research a site COLAB did not build?

Yes. It is one of the most common ways these engagements start. We need access to your analytics, Search Console, and the CMS, and the first step is confirming that the tracking is collecting what it should.

Can you work with the analytics and tools we already have?

Yes. We start with what is in place, usually Google Analytics 4, Google Tag Manager, and Search Console, and check that it is collecting what it should. If the tracking cannot be trusted, fixing it becomes the first piece of work, and we document the setup for your team.

Who takes part in user testing?

Ideally, the people who use your site: patients, members, donors, volunteers, or staff. We can recruit through your own lists or through a research panel, depending on the audience and the budget. [CONFIRM: recruiting approach, panel provider, and how participant incentives are handled]

What tools do you use?

Google Analytics 4, Google Search Console, Semrush, SE Ranking, and BrowserStack are part of most engagements, along with session recording and testing tools chosen for the site. [CONFIRM: tool list, especially session recording and A/B testing tools] Anything we set up lives in accounts your organization owns.

What does research and optimization cost?

Cost depends on the methods involved and the size of the site. A Site Diagnostic is a fixed-fee engagement, Focused Research is scoped to the question, and an Optimization Program is billed monthly. [CONFIRM: starting price or typical range for each engagement type] We share an estimate after a short conversation about what you need to learn.

How long does it take?

A Site Diagnostic typically takes a few weeks from kickoff to the findings session. [CONFIRM: typical diagnostic timeline] Focused Research runs on the timeline the question needs, and an Optimization Program continues for as long as it is producing results.

What do we get at the end?

A findings report, a ranked list of recommended changes with estimates, and a working session with your team. Usability engagements also include highlight clips from sessions, which tend to settle internal debates faster than any report.

Do you fix what you find?

We can. Changes can be handled by your own team, by us under an ongoing support agreement, or as a defined project. The recommendations are written to be usable by whoever does the work.