Case study · Product design
CheQRboard
Venues put QR codes on signs, exhibits and tickets. CheQRboard lets their own staff decide what happens after the scan: a poll, a quiz, a video, an event, a link hub. I redesigned the UI and design system for the admin platform that builds those experiences and the mobile screens visitors land on.
The problem
A scan that went nowhere interesting
The original visitor experience was a generic welcome graphic, a language menu and a name field. It looked the same at every venue, and staff couldn't change it without help.
The goal was to hand that control to the venue. A zoo educator or museum coordinator should be able to build an on-brand experience, attach it to a QR code and schedule it, without a developer.
The core pattern
Build on the left, see it on the right
Every editor in the product shares one layout: collapsible sections on the left (Main Image, Logo, Content, Design, Results), and a phone preview on the right that updates as you type.
Staff learn the pattern once and reuse it everywhere. The preview also answers the question they care about most: what will a visitor see?
Content system
Eight content types, one library
The product organizes content into eight types, each with its own icon, and groups the templates by what the venue is trying to do. Content lives in a library, so one poll or video can be attached to many QR codes and updated in one place.

Interactive
Call to action, multiple choice, open response and polls. Built for trivia, feedback and scavenger hunts.
Navigation & info
Direct links, link trees and upcoming events. The scan goes straight to a URL or a hub of links and socials.
Multimedia
Video and audio for behind-the-scenes tours, self-guided walks and instructional content.
QR design
Custom codes that still scan
Venues wanted codes that matched their signage. The editor exposes body shape, eye frame, eye ball, colors, a frame with top and bottom text, and three saved presets.
More freedom means more ways to break a code. When the color choices hurt contrast, the product says so in place and asks for confirmation before saving.
Details
The states nobody asks for
A lot of the work was the unglamorous part of a component library: making every piece hold up in its empty, filled, error and edge-case states.
- An image uploader with zoom, rotate, crop and portrait or landscape for logos and main images
- A collapsible sidebar and fluid columns so the editor fits a laptop screen
- A warning before a user switches organizations with unsaved edits
- Multi-language setup with a default language and per-visitor language switching
AI assistant
Rusty drafts, staff decide
Writing a good question and four good answers is hard work for a busy coordinator. The redesign adds an assistant, Rusty, that lives in the header and suggests copy in context, plus a one-click Shorten action on long descriptions.
The entry point also has a "Coming soon" state, so it can appear in the product before the feature is live.
Handoff
Design QA against the real build
I compared development builds against the Figma frames with Pixelay overlays, so spacing and alignment issues were caught before release.
Want to talk through this project?