Scope & user journeys
The workbook defines the proposed navigation hierarchy. The PDF separately defines homepage blocks and four required end-to-end journeys. The homepage introduces the content and connects people to relevant pages. It does not need seven sections matching the navigation.
Scope status
| Brief requirement | Current status |
|---|---|
| Creative direction | Multiple homepage studies available. Client selection of one route remains. |
| Four journeys | Paths and CTA intentions documented below. Prototype entries exist. Full end-to-end journeys remain incomplete. |
| 20 templates | Not yet delivered as the approved responsive template set. |
| Web design system | Exploratory styles exist. Formal components, states, selection component and usage rules remain. |
| CTA system | Primary and tertiary treatments explored. All-template consistency and contextual forms remain. |
| Catalogue wrapper | Catalogue entry and return intention exist. Wrapper design and integration remain. |
| Developer handoff | Figma component library, tokens, responsive rules and annotations remain. |
| Development design support | QA hours and review plan require agreement. Not represented as completed work. |
| Site-wide search | Entry, results, initial/empty/unavailable states now available as a design prototype. Live full catalogue integration remains. |
| Brand, responsive, languages, accessibility, performance | Concept-level choices and selected checks exist. Full localization, accessibility and performance validation remain. |
Known product need
Entry: Home or BU page, search or external product landing
Decisions: Market, product type, size and finish
Proposed CTA sequence:
1. Home / BU: Find your glass
2. Catalogue: View product
3. Product: Request a sample / Request a quote
4. Request: Submit and receive confirmation
Conversion: A product-specific sample or quote request
Status: Entry, catalogue routing, sample search and enquiry choices exist. Product-to-request continuity, validation and confirmation need a complete prototype.
Bespoke project
Entry: BU page or capability landing
Decisions: Collection or bespoke, relevant techniques, credible project proof
Proposed CTA sequence:
1. BU: Make your product unique
2. Capability: Explore related case studies
3. Case study: Contact an expert
4. Enquiry: Send project requirements
Conversion: An expert enquiry with market, project context and requirements
Status: v12.d provides capability storytelling, case links and expert contact. Context transfer and full form/confirmation remain.
Agency / creative partner
Entry: Case study or inspiration entry
Decisions: Suitable decoration, customisation options, early technical input
Proposed CTA sequence:
1. Case study: Explore decoration
2. Decoration: Explore customisation
3. Customisation: Contact an expert
4. Contact: Share your project
Conversion: An early-stage project conversation
Status: Case studies and capability links exist. Complete related-content links, project context and selection states still need design.
Candidate
Entry: Careers hub or external vacancy landing
Decisions: Role, location, language, requirements and fit
Proposed CTA sequence:
1. Careers: View opportunities
2. Job list: View role
3. Job detail: Apply
4. Application: Submit and receive confirmation
Conversion: A completed application
Status: Careers entry and official service handoff exist. Job detail, application, errors, confirmation and multilingual flow remain.
Review package
The overview holds the concise status. The separate personas deck explains audience hypotheses, observed competitor patterns and how v12.d responds. This scope review holds the detailed path and CTA documentation.
Personas are working hypotheses from the brief and desk research. No user interviews or conversion tests have validated them.
Review the search design ↗