Setting up a demo project to showcase UCDmanager features
A well-prepared demonstration project gives people a practical view of how UCDmanager supports user-centred design from early research through to usability evaluation. Rather than displaying empty screens, create a small, believable project with connected roles, personas, use cases, requirements and test findings.
For an Australian audience, a useful example might be a council service, a university enrolment portal or an online booking system for a Melbourne health clinic. This guide explains how to structure the project so stakeholders can follow the reasoning behind design decisions while seeing the collaborative features in action.
Choose a realistic showcase brief
Start with a service that has recognisable users, clear tasks and a mixture of accessibility needs. An online council permit application works well because it can include residents in Sydney, regional applicants with slower connections and staff who review submissions. A realistic setting makes each UCD activity easier to understand.
Define a short project statement, such as: “Improve the experience of applying for a residential parking permit.” Add the assumed business goal, target platform, delivery constraints and success measures. Australian references such as local council terminology, Australian date formats and the use of suburb and postcode fields will make the demonstration feel grounded in the local market.
Create the project and define its scope
Create a new project with a concise name and description, then record the boundaries of the work. State whether the demo covers the public application journey, the internal review process or both. A focused scope prevents the project from becoming a collection of unrelated sample records.
UCDmanager users can also browse a demonstration project before creating their own workspace. When building a fresh example, use the available project templates as a starting point, then adapt the terminology to suit an Australian government, education or retail scenario. Include project status, contributors and key milestones so the workspace resembles an active team environment.
Build user roles, personas and use cases
Create roles for the people involved in the service, such as a resident, council officer, accessibility adviser and product owner. Give each role a clear responsibility and indicate how their priorities may conflict. For example, a council officer may need complete information, while a resident may want the shortest possible form.
Turn those roles into personas with goals, behaviours, technical confidence and relevant context. A persona could represent a Brisbane renter using a mobile phone, a regional user relying on a patchy internet connection or an older applicant who prefers plain language. Connect each persona to use cases, including starting an application, saving progress, uploading evidence and checking a decision.
Document requirements and design rationale
Use requirements to capture what the service must do and why. Functional requirements might cover account creation, document upload and status notifications. Quality requirements can address response time, privacy, readability, keyboard operation and compatibility with common mobile browsers.
Keep the design rationale close to each requirement. Explain, for example, why a single-page form was divided into stages or why a clear progress indicator was selected. This demonstrates how research evidence informs design rather than presenting interface decisions as personal preference. Add priorities and links between requirements, use cases and evaluation findings to show traceability.
Demonstrate evaluation workflows
A strong demo should show how UCDmanager records analysis, not simply display final designs. Add a heuristic evaluation for the application form, noting issues such as unclear error messages, missing confirmation after upload or inconsistent button labels. Assign severity and record the recommendation for each finding.
Follow this with a small usability test plan. Define tasks, participant characteristics, measures and observation notes. A test might ask participants to find the permit requirements, upload a file and return to a saved application. Include representative findings, such as confusion about accepted file types or uncertainty about whether an application was successfully submitted.
For a broader view of stakeholder commentary, a separate 99Shoutbox feedback space can illustrate how informal observations or public-facing comments might be gathered before formal findings are entered into the project record. Keep the authoritative decisions and evidence inside UCDmanager.
Include accessibility and inclusive research
Accessibility should be visible throughout the project rather than added as a final checklist. Record checks for keyboard navigation, colour contrast, focus order, form labels, error recovery, captions and screen-reader announcements. Relate each check to the relevant use case and design component.
A test participant with low vision, limited dexterity or a cognitive disability may experience the service differently from a confident desktop user. Use the practical accessibility guide to shape inclusive test tasks and moderation practices. Refer to the Web Content Accessibility Guidelines and the obligations commonly considered under Australia’s Disability Discrimination Act when explaining the evaluation context.
Prepare a clear walkthrough for stakeholders
Arrange the project so a stakeholder can understand it in a short guided session. Begin with the project brief, move through roles and personas, open a use case, inspect linked requirements, then review an evaluation finding and its proposed resolution. This sequence tells a coherent story from user need to evidence-based change.
Use consistent names, realistic sample data and concise descriptions. Avoid filling every field with placeholder text, because sparse or generic records make the application appear less useful than it is. If the demonstration includes exported reports or downloaded evidence, explain normal security precautions; people handling unfamiliar file utilities can consult this discussion of PDF security context.
Recommendations for a convincing walkthrough
A polished demo project should be easy to browse, credible in its details and clear about how activities connect. Before presenting it to a client, colleague or university group, check that the records support a single service journey and that findings lead to actionable decisions.
- Use one realistic Australian service instead of several unrelated examples.
- Connect personas, use cases, requirements, evaluations and recommendations.
- Include both successful interactions and a few carefully documented usability problems.
- Add mobile, low-bandwidth and assistive-technology considerations where relevant.
- Use Australian spelling, local terminology and familiar date, address and postcode formats.
- Keep sample records concise enough for a live walkthrough.
- Show how a finding is assigned, prioritised and carried into the next design decision.