For the Australian Government's Centrelink mobile app, should we prioritize adding new features or improving the speed and reliability of existing core functions?

Introduction

The trade-off we're examining today is whether to prioritize adding new features or improving the speed and reliability of existing core functions for the Australian Government's Centrelink mobile app. This scenario involves balancing user experience enhancements with system stability for a critical public service application. I'll approach this analysis by first clarifying key aspects of the situation, then diving into a structured evaluation of the trade-offs involved.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming this app serves as a primary interface for citizens to access government benefits. Could you confirm the app's current user base and its growth trajectory over the past year?

Why it matters: Helps gauge the scale of impact and potential strain on existing systems. Expected answer: Significant user base with steady growth. Impact on approach: High user numbers would emphasize the importance of reliability.

• Business Context: Based on public sector priorities, I imagine cost-efficiency and accessibility are key drivers. How does the app's performance align with the department's current KPIs?

Why it matters: Ensures our strategy aligns with overarching governmental objectives. Expected answer: Some KPIs are being met, others need improvement. Impact on approach: Would help prioritize which areas to focus on first.

• User Impact: Considering the diverse user base, are there specific segments (e.g., elderly, rural users) experiencing more issues with the current app?

Why it matters: Identifies if certain groups are disproportionately affected by existing problems. Expected answer: Certain demographics struggle more with app usability or access. Impact on approach: Might suggest targeted improvements for specific user groups.

• Technical: Given the sensitivity of data handled, I'm curious about the current architecture. How scalable is the backend to support potential new features?

Why it matters: Determines the feasibility of adding features without compromising performance. Expected answer: Some limitations in current infrastructure. Impact on approach: Might necessitate backend upgrades before adding new features.

• Resource: Understanding government budgets, what's the current allocation for app development and maintenance?

Why it matters: Helps frame realistic expectations for improvements or new features. Expected answer: Limited budget with potential for increase if justified. Impact on approach: Would influence the scope and timeline of potential changes.