Inconsistent Brand Application Solved: Claude Prompts for Enterprise Design Systems Leads (Intermediate)

You are a senior enterprise design systems lead with 12 years of experience building usability test scripts and brand consistency frameworks for large organizations where inconsistent brand application across internal product teams is the primary driver of client retention problems — because enterprise clients who experience brand inconsistency across the vendor's customer portal, support interface, and marketing materials lose confidence in the vendor's operational coherence before they lose confidence in the product. Help me create a usability test script so I can increase client retention and build a research tool that measures whether brand inconsistency is creating trust and usability problems for enterprise clients interacting with multiple product surfaces. My situation: - Enterprise product type and client interaction surfaces: [e.g., "a B2B SaaS analytics platform — enterprise clients interact with a customer dashboard, an onboarding portal, a support ticket interface, a documentation site, and a monthly email report, all produced by different internal teams with no shared design system"] - Inconsistent brand application problem: [e.g., "the customer dashboard uses a dark navy and white color scheme, the onboarding portal uses the same navy with an orange accent, the support interface uses a grey and teal scheme developed by the support engineering team independently, and the documentation site uses a white and blue scheme from a legacy rebrand"] - Client retention problem: [e.g., "annual client retention rate is 78%, 14 points below the industry benchmark — client exit interviews mention 'lack of cohesion' and 'feels like different products' in 34% of churn cases, but the product team has attributed this to feature gaps rather than brand inconsistency"] - Usability test objective: [e.g., "test whether the brand inconsistency between the dashboard, the support interface, and the documentation site is creating measurable trust and navigation problems for enterprise clients who move between all three surfaces in a typical support workflow"] - Test participant profile: [e.g., "6 enterprise client contacts aged 30 to 55 who use all three product surfaces weekly — they are the primary contact for their company's SaaS stack management and make annual renewal recommendations to their IT director"] - Research method: [e.g., "moderated remote usability test using Maze for task tracking and Zoom for verbal protocol — 45 minutes per participant, 4 tasks simulating the support workflow from dashboard anomaly identification to support ticket creation to documentation reference"] - Design system investment decision: [e.g., "the VP of Product is deciding whether to invest in a design system as a retention intervention — the usability test must produce evidence that brand inconsistency is causing client-facing problems, not just internal design team problems"] Deliver: 1. A usability test script for a 45-minute moderated session — covering a 5-minute introduction and consent, a 5-minute warm-up asking about the participant's typical weekly workflow across the three surfaces, four task scenarios with verbal protocol prompts, a 10-minute debrief with three targeted questions about brand consistency experience, and a 5-minute close with a net promoter score question framing the brand consistency as a renewal factor 2. A task scenario script for four tasks — task one covering the dashboard anomaly identification flow (navigate from a dashboard alert to the support ticket interface and create a ticket), task two covering the support-to-documentation transition (find the relevant documentation article from within the support interface), task three covering the documentation-to-dashboard return flow (return to the dashboard from the documentation site using available navigation), and task four covering the email-to-dashboard entry flow (open a monthly report email and navigate to the referenced dashboard view), each with the success criteria, the think-aloud prompts, and the observation notes field 3. A brand inconsistency observation rubric — a structured observation guide for the moderator to use during each task, covering the five behavioral signals of brand inconsistency friction (hesitation at the surface transition point, explicit verbal confusion about where they are in the product, use of the browser back button rather than in-product navigation, re-reading the page header to reorient, and expressing surprise at a visual change), each with the recording instruction and the retention implication of the signal 4. A debrief question script for brand consistency — three targeted questions asked after the task scenarios, covering the participant's experience of moving between the three surfaces (open question), whether the visual differences between surfaces affected their confidence in the product (direct question), and how the visual consistency of the product compares to two competitor tools they use regularly (comparative question) 5. A VP of Product evidence brief template — a one-page research summary format for presenting the usability test findings to the VP of Product, covering the number of participants who exhibited brand inconsistency friction behaviors during surface transitions, the specific task where friction was highest, the verbatim quote from a participant that connects brand inconsistency to renewal confidence, and the estimated retention improvement from a design system intervention based on the 34% churn attribution rate 6. A design system investment case framework — a structured argument for the usability test report that connects the usability test findings to the design system investment decision, covering the current brand inconsistency cost (14-point retention gap multiplied by the average annual contract value), the design system implementation estimate (in person-months), and the break-even point at which the retention improvement exceeds the design system investment cost 7. A test moderation guide for a design system lead moderating their first usability test — a facilitator brief covering the four neutral prompts for when a participant is blocked without directional help, the observation note-taking format during the session, the time management check at the midpoint of each task, and the protocol for handling a participant who asks directly whether the visual differences are intentional 8. A 90-day design system implementation roadmap for post-test action — a phased plan the design systems lead presents alongside the usability test findings, covering phase one (a shared color token set and typography scale applied to all five surfaces within 30 days), phase two (a shared navigation component library within 60 days), and phase three (a full component audit and alignment across all five surfaces within 90 days), with the expected retention improvement metric at each phase **Write every task scenario and observation rubric assuming the design systems lead is the moderator and has strong design knowledge but limited usability research facilitation experience — every moderation prompt must be written in the exact words the moderator says aloud, and every observation note field must be specific enough to complete in real time during the session without requiring post-session interpretation.**