Brand Story & Positioning
Firm Identity
Present the firm as an integrated design partner across brand, product and experience. Repeat this position consistently; do not frame the business as a single-discipline studio.
“We design brands, products and experiences that work together.”
Show brand, product and experience in website navigation and introductions.
Describe teams as integrated, rather than separate service silos.
Integrated Value Proposition
Explain why connected disciplines create stronger outcomes for clients and end users. Tie integration to reduced friction, greater consistency and more effective implementation.
Show how an identity system informs a digital product experience.
Explain how a service journey connects physical and digital touchpoints.
Contrast one connected approach with fragmented multi-vendor delivery.
Global Positioning
Demonstrate international relevance without implying that every market is the same. Pair global strategic principles with clear acknowledgement of local research and cultural context.
Feature work from verified markets and regions.
Explain how local audience insight shaped a project decision.
Avoid universal claims that lack market-specific evidence.
Pillar Definitions
Use the firm’s approved definitions for brand, product and experience in every channel. Define specialised work in plain language before introducing technical detail.
Brand: identity, messaging and systems.
Product: digital or physical interfaces, tools and services.
Experience: journeys, environments and service moments.
Client Outcome Framing
Describe outcomes in both business and human terms. Do not reduce design work to aesthetics or claim impact without evidence.
Business outcome: stronger conversion, adoption, engagement or retention.
Human outcome: clearer choices, smoother flows or more useful touchpoints.
Support measurable outcomes with approved data, source and date.
Differentiation
Position the firm through integrated capability, strategic depth and implementation know-how. Avoid generic claims such as “creative excellence” unless you can demonstrate them with evidence.
Show how cross-disciplinary teams solve complex, multi-touchpoint challenges.
Explain the link between strategy, design and delivery.
Present long-term client partnerships only with approved context and permission.
Core Promise
Ensure every major asset reinforces one shared outcome: the firm aligns brand, product and experience so they work as one connected system.
A case study demonstrates consistent experience across customer touchpoints.
A service page connects an individual discipline to the wider system.
A social post links specialist craft to a client or user outcome.
Proof Requirements
Match each significant claim to an appropriate approved source. Use direct client evidence rather than assumptions, unsupported opinions or confidential detail.
Performance results require client-approved data and a reporting period.
Testimonials require written approval and agreed attribution.
Process claims require confirmation from the relevant discipline lead.
No-Silo Rule
Do not publish content that describes a capability in isolation when an integrated connection is relevant. Individual discipline content remains valid but should contribute to the overall firm narrative.
A product story notes relevant brand-system or service-experience considerations.
A brand case study shows identity in real digital or physical application.
An experience story identifies the product, people or environment involved.
Pillar Standards
Brand Pillar
Connect brand work to strategy, clarity and real-world application. Do not present logos as isolated artefacts.
Show identity systems across packaging, interfaces or environments.
Explain the strategic problem behind a naming, messaging or identity decision.
Link outcomes to recognition, cohesion or clearer customer understanding.
Product Pillar
Show product work through usability, usefulness and viability—not visual polish alone. Provide enough context for non-design clients to understand the problem solved.
Show key flows, decisions or product moments in context.
Explain how the product supports adoption, satisfaction or repeat use.
Include relevant digital, physical or service components.
Experience Pillar
Show experience design as the orchestration of journeys, environments and service moments. Explain how people, places and systems interact.
Map a relevant customer journey from start to finish.
Show the relationship between digital, physical and human touchpoints.
Link outcomes to ease, confidence, delight or reduced friction.
Cross-Pillar Storytelling
Show how brand, product and experience contribute to one client problem. Use a shared narrative rather than three disconnected discipline descriptions.
Follow a project from strategic positioning to product interaction to service delivery.
Use diagrams to show relationships between touchpoints.
Name cross-disciplinary contributors and their roles where approved.
Portfolio Balance
Plan visible, purposeful representation of all three pillars. Avoid extended periods when social channels, website updates or thought leadership feature only one discipline.
Include each pillar in the editorial calendar.
Rotate single-pillar and integrated project stories.
Use integrated case studies to represent multiple capabilities efficiently.
Discipline Recognition
Maintain the craft and specialist value of each discipline within the integrated offering. Avoid flattening all work into vague references to “design.”
Explain user-experience flows in product work.
Show identity grids and application systems in brand content.
Use journey maps or service blueprints in experience storytelling.
Case-Study Evidence
Every case study must include a verified problem, approach and outcome. Secure client approval for names, visuals, data and public claims before publication.
State the client challenge in approved, non-confidential language.
Explain the integrated approach and each relevant discipline contribution.
Report outcomes with source, scope and period where data is available.
Cross-Selling Pathways
Use content to make related services discoverable without forcing an irrelevant sales message. Offer a logical next step based on the project problem or client need.
A rebrand case study links to product and experience capabilities.
A product-launch story links to naming, messaging and service design.
An experience audit page explains pathways into integrated engagement.
Thought-Leadership Standard
Use public thinking to demonstrate connected, practical design reasoning. Avoid siloed expertise or abstract theory without client relevance.
Publish frameworks that link brand, product and experience.
Use cross-disciplinary examples to explain a market or user challenge.
End with practical implications for decision-makers.
Client & Market Standards
Use-Case Clarity
Describe the business problems the firm solves using concrete, recognisable situations. Avoid abstract capability lists without an applied context.
Repositioning a business entering new markets.
Improving a product experience that customers find difficult to use.
Aligning fragmented customer touchpoints after growth or merger.
Sector Breadth
Show adaptability across industries while maintaining a consistent, integrated design method. Do not imply specialist sector expertise unless the firm can substantiate it.
Feature approved work across technology, retail and hospitality where available.
Explain the common principle that transfers across sectors.
State sector focus only when supported by relevant project depth.
Engagement Models
Explain how clients can begin, expand or structure an engagement. Set realistic expectations about project scope, collaboration and decision-making.
End-to-end brand, product and experience engagement.
A focused audit or single-pillar starting point.
Sprints, embedded teams or retainers where operationally available.
International Collaboration
Set clear expectations for how the firm works across markets, time zones and local contexts. Emphasise research and collaboration rather than one-size-fits-all delivery.
Describe remote workshop and research processes using approved tools.
Explain how local stakeholders contribute to decision-making.
Clarify local validation requirements before entering a new market.
Market-Appropriate Content
Adapt examples, language, visuals and references for their intended market without changing the core positioning. Do not use region-specific assumptions as universal proof.
Use local customer context in case-study introductions.
Confirm translation and terminology with appropriate local expertise.
Review imagery for cultural relevance before regional publication.
Measurement Rigour
Use consistent, approved methods to describe project impact. State what changed, how it was measured and the limits of the data.
Include baseline, measurement, and reporting timeframe where available.
Distinguish client-reported results from independently measured outcomes.
Avoid causal claims where other factors may have affected performance.
Client Confidentiality
Protect sensitive client information in all public work. Obtain written approval before identifying clients, publishing work or sharing results.
Anonymise a project where public disclosure is not approved.
Remove confidential product screens, research findings and commercial data.
Seek permission for client names, logos and testimonials separately.
Accessibility and Findability
Build content that is understandable, searchable and usable across audiences and devices. Treat accessibility and clear information architecture as required design standards.
Use descriptive page titles, headings and internal links.
Add meaningful alt text, video captions and readable visual contrast.
Ensure case-study pages have clear service and contact actions.
Fixed and Flexible Rules
Treat integrated positioning, evidence, client confidentiality and brand voice as fixed. Test formats, editorial angles, channel choices and visual applications within those boundaries.
Do not alter the core brand-product-experience proposition without leadership approval.
Test alternative case-study formats while maintaining the required narrative structure.
Refresh visual or CTA treatments using performance evidence and documented review.
Voice & Tone
Unified and Confident Voice
Sound like one firm, not separate service teams. Use a collective voice that connects every discipline to a shared client challenge and outcome.
“We align brand, product and experience around the same customer need.”
“Our team brought strategy, interface design and service thinking together.”
“The result was a more consistent experience across key touchpoints.”
Strategic and Clear Voice
Explain design decisions through business priorities and user needs. Use accessible reasoning that a non-designer can follow.
“We simplified the product journey to reduce friction at sign-up.”
“The identity system gave regional teams clearer tools to work with.”
“The service design clarified what customers needed at each stage.”
Human and Collaborative Voice
Present the firm as an active client partner, not a distant authority. Give credit to clients, stakeholders and specialist contributors where appropriate.
“We worked with the client team to map the current journey.”
“Workshop feedback helped identify the priorities for the first release.”
“The final system was shaped with teams responsible for delivery.”
International and Precise Voice
Write in language that travels across markets. Use precise terminology, avoid cultural assumptions and explain market-specific context.
“The programme was adapted through local research and stakeholder input.”
“The team tested the approach in [approved market] before wider rollout.”
“Regional considerations informed the final service model.”
Non-Hype Voice
Be direct about real progress and outcomes without buzzwords, inflated promises or defensive qualifiers. Share learning as well as achievement.
Prefer “increased completed registrations” to “revolutionised onboarding.”
Prefer “a clearer service journey” to “a game-changing experience.”
State a verified constraint or lesson alongside an approved result.
Consistent Cross-Pillar Tone
Maintain the same confidence, clarity and sentence rhythm across brand, product and experience content. Technical depth can change, but the firm’s character should not.
Explain a visual identity decision with the same clarity as a product-flow decision.
Use shared outcome language across all service pages.
Review content periodically for siloed jargon or conflicting tone.
Tone by Context
Adapt the level of detail and directness to the setting while retaining the firm’s core voice.
Sales: focused on business problem, integrated approach and relevant next step.
Case study: specific, evidence-led and transparent about process.
Thought leadership: clear point of view with practical implications.
Leadership Voice
Use leadership content to clarify the firm’s perspective on connected design, rather than simply amplifying individual opinions.
A leader explains how brand and product alignment supports business growth.
A project lead shares a lesson about cross-disciplinary collaboration.
A studio update links internal practice to a useful client insight.
Tone to Avoid
Avoid language that signals disconnected teams, abstract conceptualism, jargon or exaggerated transformation claims.
Avoid “disruption”, “game-changing”, and unsupported “industry-leading” claims.
Avoid internal acronyms without definition.
Avoid “we know best” language that downplays client or user participation.
Visual Style
Integrated Visual System
Use one shared colour, type and layout system across all content. Different disciplines may have subtle sub-styles, but they should never look like unrelated brands.
Use the master type hierarchy in brand, product and experience materials.
Keep grid, spacing and annotation patterns consistent in case-study layouts.
Use controlled pillar distinctions without replacing the overall visual identity.
Case-Study Visual Structure
Present every case study in a recognisable visual sequence: challenge, approach and outcome. Show how disciplines are connected rather than relying only on hero imagery.
Use an opening visual that establishes the business or user context.
Add diagrams mapping brand, product and experience touchpoints.
Use annotated images to explain decisions and outcomes.
Brand-Pillar Visuals
Show brand work as an applied system across real touchpoints. Avoid presenting logos, colour swatches or isolated marks without context.
Show identity across packaging, digital interfaces or environments.
Include relevant messaging, guidance or component-system examples.
Pair a visual application with a concise explanation of its role.
Product-Pillar Visuals
Show interfaces, interactions and product flows in enough detail to make usefulness visible. Prioritise visuals around decisions and user tasks, not surface styling alone.
Use focused screens to explain a key action or workflow.
Show relevant iterations or variants where they clarify the outcome.
Place interface imagery in a credible device or usage context.
Experience-Pillar Visuals
Show journeys, spaces and service moments as connected systems. Make the relationship between people, digital tools and physical environments legible.
Use journey maps and service blueprints with readable annotations.
Show environment photography alongside relevant user interactions.
Avoid generic stock images of people without experience context.
Motion and Prototype Style
Use movement to demonstrate meaningful interactions, transitions and connected experiences. Keep motion brief, purposeful and consistent with the brand system.
Use a short prototype clip to show a critical product flow.
Use animation to reveal a journey across channels or touchpoints.
Apply consistent timing, easing and transition patterns.
Diagramming Standards
Use diagrams to clarify systems, relationships and decision points. Design them for client understanding, not internal design-language performance.
Use a common legend, colour treatment and label hierarchy.
Limit each diagram to one main message.
Define specialised terms near first use.
Image Quality and Usage
Use current, high-resolution, approved work and photography. Avoid visuals that obscure the project, misrepresent the client or expose confidential information.
Replace outdated screenshots after material product changes.
Remove confidential metrics, test data or unreleased interface elements.
Use approved photography licences and client permissions.
Accessible Visual Design
Ensure visual information remains understandable for people with different access needs and across devices.
Provide meaningful alt text for images, diagrams and prototypes.
Use sufficient contrast and avoid colour-only distinctions.
Add captions or transcripts for video and motion content.
Copy & Structural Style
British English
Use British English consistently across all markets unless a client-approved local version is required. Apply one language pass to major assets before approval.
Use “colour,” “behaviour” and “modelled.”
Maintain consistent punctuation in lists, headings and captions.
Follow approved terminology across brand, product and experience narratives.
Headline Conventions
Use clear, patterned headlines that frame a business problem, client outcome or integrated process. Avoid vague creative slogans.
Problem-led: “Aligning global brand and product.”
Outcome-led: “Increasing engagement through integrated experience design.”
Process-led: “From strategy to launch across three disciplines.”
Case-Study Narration
Follow one storyline: context and challenge, integrated approach, then outcome and learning. Give each relevant discipline a clear role.
State the client challenge in approved, non-confidential language.
Explain the contribution of brand, product and experience teams.
Close with verified results, lessons or next-stage implications.
Discipline Explainers
Describe each discipline in plain language before using specialist terminology. Connect standalone explainers to relevant integrated work.
Brand design: creating the identity, language and systems that make a business recognisable.
Product design: making digital or physical tools useful and usable.
Experience design: improving journeys across people, environments and service moments.
Service-Page Structure
Keep service pages aligned in voice, hierarchy and decision-making flow. Explain the client problem, relevant capability, process and next action.
Begin with the problem or opportunity the service addresses.
Define what the team does and what the client receives.
End with a relevant enquiry or conversation CTA.
Profile and Biography Style
Write profiles as evidence of how people contribute to the integrated offer, not as disconnected lists of software skills or job titles.
Connect a leader’s expertise to brand, product or experience outcomes.
Use approved qualifications and project experience only.
Keep biographies concise, specific and internationally understandable.
Thought-Leadership Structure
Build articles, talks and posts around one clear connected-design idea. Use practical examples and finish with a useful implication for decision-makers.
Introduce a cross-disciplinary problem or market shift.
Use examples from more than one discipline.
Close with an action or question relevant to clients.
Technical Detail Control
Include enough technical detail to establish substance, but keep primary copy understandable for non-specialist decision-makers. Place deeper technical explanation behind clear labels or expandable sections.
Define specialised design methods when first mentioned.
Use annotated visuals for process detail.
Move long methodology descriptions into a supporting resource where appropriate.
Cross-Linking and CTAs
Connect content to the relevant service, case study or contact route. Each asset should give a client a logical way to explore the integrated offer further.
A product case study links to brand and experience capabilities.
A thought-leadership article links to a relevant integrated case study.
A service page ends with “Discuss your challenge with our team.”
Planning & Calendar
Integrated Content Calendar
Plan brand, product and experience content together rather than as separate publishing streams. Maintain a deliberate balance between individual-pillar expertise and integrated narratives.
Schedule regular spotlight weeks for each pillar.
Alternate single-discipline posts with cross-pillar project stories.
Align major case-study releases with supporting thought leadership.
Campaign Themes
Build campaigns around the advantage of connected design. Each campaign should show the relationship between brand, product and experience.
“From brand to product.”
“Designing end-to-end journeys.”
“Making every customer touchpoint work together.”
Regional and Sector Planning
Balance content across priority markets and sectors while retaining the same integrated firm narrative. Avoid concentrating visibility around one geography, industry or service line without strategic reason.
Rotate approved work from different markets through the calendar.
Feature different sectors without changing the firm’s core approach.
Include local context while maintaining consistent positioning.
Event and Launch Alignment
Use launches, talks, conferences and awards as anchors for focused content activity. Connect each occasion to a relevant client challenge or integrated design perspective.
Publish a case study alongside an approved client announcement.
Turn a leadership talk into a short series of connected insights.
Use a project launch to show the journey from strategy through implementation.
Resource Allocation
Assign enough time and the right contributors to integrated content. Protect time for multidisciplinary input, editing and approval.
Include relevant discipline leads in case-study planning.
Assign a content owner to coordinate sources, narrative and final assets.
Reserve time for review before committing to public launch dates.
Review Cycles
Review the content mix and strategic relevance at planned intervals. Use reviews to correct imbalance and update priorities, rather than only reacting to urgent requests.
Review pillar and market representation every quarter.
Refresh positioning, featured examples and approved proof points annually.
Adjust editorial focus after a significant business or positioning change.
Priority Scoring
Use a simple score to decide which stories deserve production resources. Prioritise content that best demonstrates integration, relevant market value and approved evidence.
Score case studies for strategic fit, proof, visual readiness and permission status.
Prioritise projects that involve two or three pillars.
Hold projects that lack client permission, evidence or usable source material.
Content Mix Guardrail
Set a planned proportion of integrated stories to prevent discipline silos. The exact ratio requires leadership confirmation, but each month should include content that demonstrates connections across disciplines.
Include at least one integrated narrative in each monthly publishing cycle.
Avoid long sequences featuring only brand, only product or only experience.
Use content tags to flag an emerging imbalance early.
Calendar Visibility
Maintain one shared calendar for planned, in-progress, approved and published content. The calendar should show the pillar, market, sector, format, owner and approval status for every substantial item.
Tag a case study by all contributing disciplines.
Display dependencies, such as client approval or forthcoming launch date.
Mark content that needs a factual, visual or positioning refresh.
Production Workflow
Cross-Pillar Briefing
Start every significant asset with an integrated brief. Before drafting, identify the client challenge, intended audience, relevant pillars, proof, goal, and next action.
Define how brand, product and experience contributed to the work.
Identify relevant cross-selling opportunities—not forced ones.
Record approved evidence, confidential boundaries and client permissions.
Case-Study Development
Build case studies through a consistent sequence: source gathering, shared narrative, discipline detail, review and final approval. Keep the whole project visible before refining individual contributions.
Gather input from all relevant discipline leads.
Draft the project challenge, integrated response and verified outcome.
Review the final story as a group for coherence and balanced representation.
Content Tagging and Repositories
Organise assets so teams can find, reuse and connect work across disciplines. Apply standard tags and keep approved source materials alongside final content.
Tag by pillar, sector, market, engagement type and client-permission status.
Maintain separate libraries for brand, product, experience and integrated projects.
Use tags to identify material for regional or cross-selling campaigns.
Approval Process
Route each asset through the appropriate specialist, content and leadership approvals. Do not publish work with unresolved factual, confidentiality or brand-positioning concerns.
Discipline leads verify technical accuracy.
The content or brand lead verifies voice, narrative and format.
Leadership approves high-profile, strategic or sensitive client material.
Collaboration Rituals
Build regular cross-disciplinary checkpoints into the content process. Use short, structured sessions to surface source material, align narrative and prevent siloed storytelling.
Hold a monthly internal show-and-tell across discipline teams.
Use shared channels for in-progress feedback on significant stories.
Run a short debrief after campaign or case-study publication.
Template Use
Standardise core structures while preserving appropriate creative flexibility. Templates should speed up quality work, not erase disciplinary nuance.
Use shared templates for case studies, service pages and thought leadership.
Use common slide and deck templates for client-facing showcases.
Include flexible sections for technical or pillar-specific detail.
Source and Permission Management
Record the source, approval status and permitted public use for every client asset. Treat client confidentiality and consent as a production requirement, not a final check.
Store client logo, image and result approvals with the project record.
Label unreleased, restricted and public-approved assets clearly.
Reconfirm permission when you reuse a case study in a new channel or market.
Version Control
Use controlled filenames, dated versions and a single final source of truth. Prevent old copy, screenshots or metrics from returning to public use.
Use YYYYMMDD_Client_Project_Asset_V01 as the naming convention.
Clearly mark approved files and archive superseded versions.
Record the owner, reviewer and approval date on final case-study files.
Publish Quality Gate
Require a final checklist before release. Every substantial asset must be accurate, integrated, accessible, permission-cleared and connected to a relevant enquiry route.
Confirm brand, product and experience roles are clear where relevant.
Confirm claims, client names, metrics and visuals are approved.
Confirm accessible formatting, working links and an appropriate CTA.
Measurement & Optimisation
Pillar Visibility Tracking
Measure how often each discipline appears and whether it is represented alone or as part of an integrated story. Use the results to correct content imbalance.
Track volume and engagement by brand, product and experience.
Track integrated stories separately from single-pillar content.
Adjust the calendar if one capability consistently dominates or disappears.
Cross-Selling Indicators
Track signs that audiences recognise and explore related capabilities. Do not treat a single inquiry as proof; review patterns over time.
Track enquiries that mention two or more service lines.
Monitor movement from a single-pillar inquiry to an integrated engagement.
Associate campaign activity with trends in qualified cross-disciplinary interest.
Integrated-Offering Recognition
Assess whether prospective clients understand the firm as an integrated partner. Use direct feedback and inbound language to identify positioning gaps.
Ask relevant prospects what capabilities they associate with the firm.
Review the language used in referral and enquiry messages.
Refine service-page explanations when audiences recognise only one pillar.
Content Performance Analysis
Evaluate which messages, formats and stories contribute to reach, consideration and enquiries. Compare performance across individual and integrated content types.
Compare engagement for brand-only, product-only, experience-only and integrated posts.
Identify patterns in high-performing case studies, such as evidence, format or audience context.
Use findings to update example selection and editorial structures.
Market and Sector Feedback
Collect qualitative feedback from clients, partners and sales conversations. Adapt emphasis by audience or sector while preserving the integrated core proposition.
Ask clients which content made the firm’s offer easiest to understand.
Note when a sector needs more product, brand or experience detail.
Update market-specific examples after local review.
Qualified-Enquiry Tracking
Track whether content attracts the right type of prospect, not just total traffic. Define qualification criteria with commercial leadership before measuring performance.
Record sector, market and requested service line for inbound enquiries.
Identify the entry asset or referral route where tracking allows.
Compare the share of integrated enquiries against the agreed baseline.
Case-Study Contribution
Measure the role case studies play in prospect consideration and conversion. Combine web behaviour with sales-team feedback rather than assuming a direct causal result.
Track visits, downloads, CTA clicks and time on priority case studies.
Ask qualified leads which work influenced their decision to enquire.
Identify case-study gaps by market, sector or service combination.
Optimisation Experiments
Run one focused content test at a time, with a recorded hypothesis and review date. Preserve the core positioning while testing formats, proof and calls to action.
Test an integrated project diagram against a conventional hero-image opening.
Test outcome-led versus process-led case-study headlines.
Test a related-service CTA against a general contact CTA.
Guideline Evolution
Keep the guideline current as the firm’s positioning, portfolio and markets develop. Update examples and systems using evidence from performance reviews and stakeholder feedback.
Conduct an annual guideline review and document material changes.
Add newly approved projects that strengthen the integrated proposition.
Retire formats, claims or examples that no longer match the firm’s direction.
Last updated 1 September 2026 by Zazoozoo.
