What goes in a concept canvas?

The concept canvas includes a concept name, a neutral definition of what it is, the target audience, a quick sketch, benefits and features, and the actors involved. The actors cover the teams, systems, and channels that need to participate.

When should you use a concept test after the concept template?

Use a concept test to validate the concept before building it. A clear, traceable concept is what makes that next testing step meaningful.

Concept Template (Define a Solution, With an Example)

A concept template captures a solution idea clearly enough that anyone can understand it — before you invest in designing or building it. It forces you to state what the thing is, who it’s for, the value it creates, and who needs to be involved to make it real.

Why it works: a fuzzy concept wastes weeks. Writing it down in one structured page exposes the gaps early — and gives the team a shared, neutral description to rally around or challenge.

What goes in the concept canvas

Concept name — a memorable handle for the idea.
Definition — a neutral, self-explanatory description of what it is.
Target audience — who it’s for.
Sketch — a quick visual of the solution.
Benefits and features — what value it gives the user, and what it offers.
Actors involved — who needs to participate (teams, systems, channels) and how they relate.

How to use it

Start from a real opportunity — ideally a How Might We you’ve already framed.
Write the definition so an outsider gets it in one read. No jargon.
Be specific about the audience — not “everyone.”
Map the actors — concepts fail on the parts no one owns, so name them now.
Then test it with a concept test before building.

A worked example: SesTech

Connecting to the same user and problem as our other templates — Maya, the freelancer who keeps calling the bank:

Concept name: SesTech — your voice-activated personal assistant.
Definition: A voice assistant that works across mobile OSes. When you have a question or problem, you ask SesTech directly; it can access your account and an FAQ database to answer you.
Target audience: The bank’s customers with modest digital skills — comfortable with mobile apps, not experts, who currently default to the call center.
Benefits & features: Independence and convenience; solve a problem anytime, anywhere without the main app, website, or call center; personal attention.
Actors involved: Customer ↔ SesTech; the call center receives callback notifications; bank marketing supplies FAQs; the bank tech team provides the platform.

Notice how the concept traces straight back to a real pain (the call-center burden) and names every actor needed to ship it. That traceability is what makes the next step — testing — meaningful.

What to use before and after

Before: a How Might We gives you the opportunity to turn into a concept.
After: validate it with a concept test, then narrate it with a storyboard.

For how a concept becomes part of a portfolio story, see the UX case study guide.

A clear concept shows you can move from problem to a defensible solution — the heart of a strong case study. Folioverse helps you turn that thinking into a case study recruiters trust. Try it free.