Multi-Project Dashboard

Overview

A Multi-Project Dashboard brings two or more of your existing projects into a single Insights workspace. Each product from the projects you include becomes its own column, so you can read the same question across studies that were fielded separately. A dashboard always says Products, even when it was built from concept tests.

Reformulated a bar and retested it six months later? Put both projects in a dashboard and you'll see whether Overall Liking actually moved. A dashboard collects no responses of its own — it's built from projects that already exist, and deleting it leaves them untouched.

Most of this article is about the part that's easy to get wrong: knowing when a cross-project comparison tells you something real.

Where to Find Your Dashboards

Two places. The Home page, under Multi-Project Insights, and the Projects page, on the Multi-Project Dashboards tab. Both have a Create Dashboard button.

Creating a Dashboard

1. Click Create Dashboard.
2. Give the dashboard a name — it's required.
3. Tick the projects you want. The Search... box matches on project name and project ID.
4. Click Create Dashboard — it stays disabled until two projects are ticked.

Highlight AI then matches the questions across your projects, which can take up to a minute, and lands you on the Explore tab. Not every question finds a partner, so check the Comparable Questions card in the header — it shows how many of your question rows hold more than one question. A healthy count isn't a guarantee, so confirm the KPIs you actually plan to compare found their match.

A project that's still in field can be included, and contributes whatever it has so far.

Tip: The first project you tick sets the template — the dashboard takes its team and solution from that project, and that project becomes [1] in your product names, so Vanilla Bar [2] came from the second project you picked. The Projects section of the legend in the Settings sidebar decodes the indices. Choose your order deliberately.

When a Comparison Is Sound

Dashboards earn their keep when the projects were designed to be read against one another:

• Iterative testing — prototype, refine, retest, and see whether the changes helped
• Variant testing — flavours, scents or packaging tested separately as samples became ready
• Benchmark tracking — the same test repeated quarterly or annually against a changing competitive set
• Audience comparison — the same product among different consumer targets
• Concept-to-product validation — does the finished product deliver on the concept's promise?

When to Be Careful

A comparison is only as sound as the research design behind it. Before you read the numbers, work through these:

• Audience. Were participants screened on the same qualifications and quotas? If the audience composition differed, a shift may reflect who took part rather than how the product performed.
• Questionnaire. Question wording, order and response scales need to be consistent. Even a small change in phrasing or scale anchors changes how people answer, creating differences that aren't real — a question rescaled from 5 points to 7 isn't comparable to its earlier version at all.
• Sample size. Aim for similar bases. You can compare unequal ones, but proceed with caution — under about 50 responses behind a column, read differences as directional rather than treating every numeric gap as meaningful.
• Testing conditions. Usage instructions, test duration, environment, seasonality, holidays and campaigns, even product freshness.
• Formulation change. If a product's core formulation, sensory profile or positioning has fundamentally changed, it may no longer be the experience you measured last time. Treat that test as the baseline for a new generation rather than a continuation of the old benchmark — directional learnings hold, metric-to-metric comparisons don't.

Focus on the differences Highlight marks as statistically significant at your chosen confidence level, and look for the same pattern across more than one metric before you call it a finding.

Document the differences between your projects. When you pass the findings on, say which projects are included, disclose them, and keep the caveats attached.

Changing Which Projects Are Included

Use the Manage button in the dashboard header. A Confirm Dashboard Update step warns you first — because changing the project list resets the dashboard's Scorecard and Segments. Your product groups go with them, and the [n] indices are reassigned from the new order. Nothing is merged, and nothing comes back.

Tip: If you only want a different combination of projects, create a second dashboard rather than editing this one. There's no limit on how many you can have, and the first one keeps its scorecard and segments.

To rename or delete a dashboard, use the row menu on the Multi-Project Dashboards tab. Deleting one never affects the projects it was built from.

Related

• Explore — where a dashboard opens, every product a column
• Scorecard — reset by a project-list change
• Segments — also reset by a project-list change
• Product Groups — where the [n]-suffixed Core Products appear

← Back to Insights Overview