Design Labs troubleshooting
Common Design Labs sticking points — palette switching, component approval, and playbook scope.
Overview
Design Labs leans on governance more than self-serve toggles in a few specific places today. This page covers where teams usually get stuck and why.
Common issues
"I want to switch a tenant's palette myself, right now."
The self-serve, in-studio brand switcher is still building. Today, changing a tenant's palette is a token-source change that goes through Design Labs governance rather than a live toggle. See Tokens & brand switcher.
"I can't find a component I know exists somewhere in the fleet."
The component gallery's index is still filling in — components already used in production are shipped and working, but the browsable, searchable index of all of them isn't complete yet. Ask the team directly in the meantime.
"A playbook ran but my ranking didn't move."
No playbook — here or anywhere — can guarantee a ranking or AI-answer placement. Growth & AEO playbooks are structured guidance and automation where it exists, not a result guarantee.
"My component request seems to have gone nowhere."
Requesting a missing component or variant routes through Design Labs review, not an instant self-serve add — expect a governance pass, not immediate availability.
Limits & honest scope
Design Labs governs the shared system; it doesn't do hands-on page design for you — that's still your team's call, guided by what's approved here.