Articles

Set up a demo project for client onboarding

A useful client-onboarding demo should feel like a small, coherent UX project rather than a catalogue of features. In UCDmanager’s free collaborative workspace, that means showing how roles, personas, use cases, design analysis and evaluation evidence can live together while remaining easy for a new stakeholder to follow. The project can create confidence in the workflow and give the client concrete language for the next stage.

Australian teams often begin a relationship with a discovery call in Sydney, Melbourne, Brisbane or Canberra, then continue through hybrid meetings from offices, homes and shared workspaces. Build the demo around that distributed reality: readable screens, short instructions and a realistic amount of content make it easier to follow when cameras, microphones or train connections are less reliable.

The example should also suit the Australian market, whether the client is a startup, retailer, financial service, consultancy or government agency. Avoid importing assumptions from another country. Use Australian spelling, dates, currency where relevant and plain English. If personal information is discussed, align the example with the Privacy Act 1988 and the Australian Privacy Principles rather than filling gaps with real customer records.

Choose one valuable journey, identify the decisions the client wants to discuss and limit the demonstration to activities that support those decisions. A narrow project is easier to assess and leaves room to expand later. You can browse the public demonstration for inspiration or start a fresh workspace, then organise the content so each screen answers a question the client is likely to ask.

Define the purpose and boundary

Start with a short project brief that names the primary audience, sector, product stage, constraints and success measures. State which client questions the demonstration should answer and which UX activities belong inside its scope. This keeps the session focused and prevents every template or technique from competing for attention.

Use synthetic names, addresses, quotations and research notes throughout. Real material can make a demo persuasive, but it also raises re-identification and handling risks. Keep consent status, source and retention details visible where relevant, and avoid loading identifiable participant recordings into the project.

Build a realistic sample project

A new workspace can be populated from the available project templates, then adapted to the client’s sector. Choose the closest starting point rather than changing every field; consistent terminology makes the walkthrough easier to follow and helps stakeholders recognise how reusable structures support different projects.

Begin with a clear user role and two or three complementary personas. For each use case, capture context, goal, steps, pain points and assumptions without inventing demographic stereotypes. Apply Australian spelling, dates and time-zone conventions, and use Australian dollars only when the scenario genuinely involves a transaction.

Connect research to design decisions

Make traceability visible by linking each role to its needs, each persona to a use case and each evaluation finding to a design decision. A short requirement can name its source, status, priority and owner, while an analysis note explains why the evidence matters. This creates a credible narrative from research evidence to product action.

Avoid displaying disconnected artefacts merely to prove the application is flexible. Explain which entries changed the brief, which need validation and which remain open. For a bank, retailer or public-service team, the same chain can be shown through a different risk, channel or customer-service constraint, demonstrating relevance across the Australian market.

Add evaluation and accessibility evidence

Prepare a short usability-testing plan with representative tasks, recruitment criteria and consent steps. Reflect the client’s audience rather than defaulting to a homogeneous group; this may include participants in regional and metropolitan areas, people using assistive technology and customers managing busy or low-bandwidth environments. Label planned activities separately from completed evidence.

Document heuristic observations and accessibility checks against the same use cases so severity has context. For Australian Government deliverables, check the Digital Service Standard, the Disability Discrimination Act 1992 and current WCAG conformance requirements rather than treating a demo as certification. When wording affects comprehension, use clear content guidance to review labels, instructions and error messages before assigning priority.

Run the client onboarding session

Plan a 45-to-60-minute session with a short context briefing, a guided project walkthrough and time for client questions. Give one person the facilitator role and another responsibility for notes and follow-up. Australian groups may span Sydney, Melbourne, Brisbane and Canberra, so state the time zone, avoid a rushed agenda and circulate materials before the meeting.

Walk through a decision sequence rather than opening every object. Begin with the role and use case, move into analysis, then show how testing or evaluation changed the plan. Pause at labelled decision points and capture unanswered questions as follow-up items. Keep the synthetic-data warning visible so nobody mistakes the walkthrough for a completed audit or a production client workspace.

Use a dependable launch checklist

Before sharing, check every name, date, link and status; confirm that the account and project access suit the intended attendees; and remove unfinished notes. Open the project in a clean browser session to catch missing content, confusing labels or inaccessible interactions. Record who owns each area so updates after onboarding have a clear destination.

If the available structure does not fit the client’s vocabulary or a setup step is unclear, contact the UCDmanager team for advice. Resolve those questions before adding more material, because a smaller coherent example is easier to trust than a crowded project.

A well-maintained demonstration becomes both an onboarding aid and a reference for the client’s first working session, while clear ownership keeps synthetic examples from being mistaken for live research or production records.