How to facilitate a remote persona prioritisation exercise

Remote persona prioritisation helps a team decide whose needs should shape the next stage of product or service work. It converts research-derived personas into an evidence-based order, with reasons that can guide design, strategy and testing. The aim is alignment, not a vote on which customer matters most.

Begin with credible personas rather than attractive illustrations. Each should connect to interviews, observation, survey data or existing behavioural evidence, and should describe goals, needs, barriers and context. Give participants enough pre-reading to understand the evidence before they rank anything.

Australian teams may be spread across Sydney, Melbourne, Brisbane, Adelaide and Perth, so logistics matter. Sydney and Brisbane usually share the same clock time, while Adelaide is typically 30 minutes behind and Perth can be two or three hours behind Sydney when daylight saving changes. Rotate inconvenient sessions, capture contributions asynchronously and keep the live workshop to ninety minutes.

The facilitation style should be plain, collegial and direct. Australian workplaces often use first names, informal language and good-humoured banter, but a prioritisation discussion still needs psychological safety and evidence-based challenge. Public agencies, small consultancies, start-ups and not-for-profits also have different constraints; let the group agree on criteria that reflect its market, funding and service obligations.

Prepare the evidence and decision

Start by framing a single decision: which personas should receive attention in the next design cycle and which needs can be deferred. Turn that goal into one prioritisation question and two or three weighted criteria, such as severity of unmet need, strategic fit, reach or delivery feasibility. Define what a useful outcome looks like so the session does not drift into general persona discussion.

Assemble a shared evidence board before the meeting. A free UCD workspace can organise personas, research notes, requirements and test results, while the facilitator prepares a concise brief for each persona. Show the source, confidence level and strongest behavioural insight rather than every transcript.

Check that the personas are distinct, evidence-based and based on current behaviour. Remove duplicates, merge traits that describe the same user pattern, and flag assumptions. For public-sector work, align the exercise with the Australian Government Digital Service Standard and WCAG accessibility needs so high-priority journeys can be translated into compliant service requirements.

Design the remote session

Invite a small cross-functional group: a facilitator, a note-taker, a researcher, a product or service owner, delivery staff, and one or two customer-facing colleagues. Give each participant a persona brief containing needs, evidence, current pain points and relevant use cases. Use a reliable online whiteboard, a poll for ranking and a document for notes.

Related UX use cases can confirm whether a persona's needs appear in real service journeys. During the session, test the implications of each priority rather than debating whether a fictional character is realistic. A fictional persona should never outrank direct evidence from users.

Offer both spoken and written routes into the discussion. People connecting from regional areas or with intermittent broadband may need a telephone dial-in and downloadable worksheets. Share agendas and instructions early, avoid video dependence, provide live captions where possible and build in short breaks. Use a poll to find a workable meeting time when the group spans Australian zones.

Run the prioritisation activity

Open by restating the decision and criteria, then walk through the 90-minute flow: context, silent scoring, evidence discussion, final ranking and actions. Allow five minutes for private review. Participants score each persona against every criterion before seeing group results. This first silent pass reduces anchoring, senior-title bias and the tendency for the loudest voice to determine the order.

Run three rounds: independent scoring, evidence-based discussion and a final vote or allocation of ten priority points. In the discussion, ask what would have to be true for a persona to move up or down. Separate observable evidence from assumptions, and record both as distinct notes. A low-confidence result can be valid when the evidence gap is explicit.

When communicating the outcome to executives or delivery teams, the guidance on presenting UX findings supports a clear narrative: decision, evidence, implication and action. Show why one persona ranks above another, name uncertainty, and connect the ranking to an observable change in the roadmap rather than a generic preference.

Capture decisions and keep momentum

Publish the final ranking, scoring method, rationale, dissenting views and unresolved evidence gaps. Store the decision alongside the source material so future teams can understand whether the order still reflects current behaviour. Name an owner for each follow-up action and set a review date, since market conditions and user needs can change quickly.

Use a collaboration shoutbox to collect short asynchronous updates from colleagues who could not attend. This keeps late input visible without rewriting the workshop record. Summarise each contribution, confirm whether it changes the decision, and close the loop with the person who submitted it.

Where a persona concerns Aboriginal or Torres Strait Islander communities, workshop consensus is not cultural authority. Involve the relevant community-controlled organisation in reviewing research, wording and consequences, and treat their advice as a distinct source rather than an optional endorsement. Confirm consent and data governance before sharing persona details outside the project.

Materials for a focused workshop

Prepare the input board with four elements:

• A one-page persona summary with needs, goals, context and confidence
• Three to five cited research observations for each persona
• The decision criteria, weighting and time available for the exercise
• A visible source for each claim, including contradictions and missing evidence

Use four prompts to move discussion from preference to evidence:

• Which observed need creates the greatest consequence if we ignore it?
• How confident are we that this pattern applies to the intended population?
• What could we learn cheaply before committing more design effort?
• Which journey, service or market constraint changes the priority?

The facilitator can turn the agreed order into a short decision artefact, an updated research backlog and links to the affected service requirements. This completed record keeps later usability tests, heuristic evaluations and accessibility reviews traceable to the same priorities and makes the rationale for the roadmap visible.