Using Personas to Evaluate Feature Requests from Customers

Customer feature requests often arrive as short, confident instructions: “Add dark mode”, “Let us export this report”, or “Make the dashboard work offline.” Each request may reflect a genuine problem, yet the proposed solution is shaped by one person’s context. Personas help teams examine the need behind the request and decide whether it matters to a wider group of users.

For teams using UCDmanager, this process can connect customer feedback with user research, requirements, use cases and usability evaluation. A persona is not a fictional customer invented for decoration; it is a practical model of goals, constraints, behaviours and accessibility needs that supports consistent product decisions.

Separate the request from the underlying need

Begin by rewriting each feature request as a problem statement. “Add a bulk upload button” might indicate that a customer handles hundreds of records each week, while “support another file type” could reveal a requirement imposed by an existing Australian government or accounting system. The requested feature is only one possible response.

Map the statement against relevant personas. Consider their responsibilities, digital confidence, device, environment, frequency of use and consequences of failure. A small business owner in regional Queensland may have a different priority from an operations manager in Sydney, even when both ask for faster reporting.

Use persona evidence rather than assumptions

A persona should be grounded in interviews, support conversations, analytics, usability tests and accessibility findings. Record the evidence behind each attribute, including how recent it is and how many users it represents. This prevents a memorable customer anecdote from outweighing a broader pattern.

When a feature request affects a key workflow, define the expected outcome before discussing interface changes. Guidance on aligning testing goals can help connect the request to measurable business and user objectives, such as reduced handling time, fewer support contacts or improved task completion.

Compare reach, impact and urgency

Create a simple comparison for each request: which personas experience the problem, how often it occurs, how serious the consequence is and whether a workaround exists. A feature used daily by a high-value customer may deserve attention, but a severe accessibility barrier affecting a smaller group can carry greater ethical and legal importance.

Australian context can change the ranking. Users on a slow or unreliable NBN connection, people working from mobile devices in regional areas, and customers operating across Australian Eastern and Western time zones may experience the same feature very differently. Add compliance, support cost and strategic value to the assessment without allowing commercial value to erase user needs.

Run collaborative persona prioritisation

Invite product, design, development, customer support and sales representatives to review the evidence together. Ask each participant to assess how strongly a request supports a persona’s goals and how much risk it creates for other users. Differences in opinion often reveal missing research rather than a need for louder debate.

A structured persona prioritisation exercise is useful when contributors work across Melbourne, Brisbane and remote locations. Give everyone the same persona summaries, request descriptions and scoring criteria, then document the reasons behind the result rather than recording only a final number.

Test whether the feature solves the problem

High-priority requests still require validation. Turn the proposed change into a use case, prototype or acceptance criterion and test it with participants who match the relevant personas. Observe whether the change improves the target task, introduces confusion or helps one group while disadvantaging another.

For example, a streaming service might receive a request for more regional sports coverage. A persona-based review could reveal separate needs around live broadcasts, replay access, captioning, data usage and family accounts. Reviewing patterns from services such as live TV platforms can provide market context, but direct research with Australian users remains the stronger basis for a product decision.

Include trust, privacy and accessibility

Some requests involve more than convenience. A customer asking for automated email notifications may also be asking for reliable identity checks, clear consent controls and protection against impersonation. Before expanding such a feature, teams should examine authentication, data retention, permissions and the likelihood of misuse.

Technical due diligence can support this analysis. For email-related workflows, a reverse MX lookup guide may help teams investigate domain configuration and spoofing risks. Personas should also represent users with vision, hearing, motor or cognitive impairments, including people who depend on keyboard navigation, captions or screen readers.

Turn decisions into traceable requirements

Once a request has been accepted, deferred or rejected, record the reasoning. Link the decision to the affected personas, evidence, priority score, use cases and validation results. This makes the product backlog easier to explain when a customer, executive or developer asks why a popular suggestion was not implemented.

UCDmanager can keep these artefacts connected across a project. Teams can export use cases when requirements need to move into development tools, while preserving the user-centred rationale behind them. A deferred request should remain visible with its assumptions and review conditions, rather than disappearing into an unsearchable backlog.

Review persona fit as the product changes

Personas become more valuable when they are revisited after releases, support trends and market changes. Track whether the delivered feature changes behaviour, resolves the original problem and creates new requests. If usage differs sharply from the forecast, update the evidence before updating the persona blindly.

The Australian market is diverse enough to expose weak assumptions quickly: a mobile-first customer in inner Sydney, a field worker near Darwin and a family sharing devices in Adelaide may all use the same service under different conditions. By treating customer requests as evidence to investigate, teams can prioritise work that improves real experiences rather than simply collecting the loudest ideas.