Empathy analysis

Empathy analysis is completed for each User Type and is presented as an Empathy Map. In many cases, these are presented as graphics, but it is also effective to present them as a textual analysis.

For each User Type, you consider them in 4 aspects. You describe what they: • Think • Say • Do • Feel

In development structures where the use of Desgign Thinking is part of the organisation's development framework, the process of understanding the users and creating empathy with them would involve interviews, either face-tp-face or online. This is a crucial component of validation. This helps to make sure that you build what the users want, NOT what you think they might want.

Let's look at some examples for the budegeting application.

1. The Client (Business Owner / Product Owner)

The Client is the individual or entity funding the development, aiming for business success, user adoption, and a return on investment.

Think:

• "How can this application attract and retain users in a competitive market?"
• "What's the ROI of this development project? How quickly will it pay off?"
• "Is the data being collected valuable for future business insights or features?"
• "Are we meeting a genuine need for householders, or just creating another budgeting app?"
• "Will this solution be cost-effective to maintain and scale?"
• "How can we differentiate this app from others? What's our unique selling proposition?"
• "Are there legal or compliance risks we need to address (e.g., data privacy)?"
• "What key performance indicators (KPIs) should we track to measure success?"
• "Can this app generate additional revenue streams in the future?"

Say:

• "We need a clear strategy for user acquisition and retention."
• "What's the project timeline and budget? Are we on track?"
• "How can we get more users to sign up and actively use the features?"
• "Show me the dashboards. What are the key metrics telling us about user engagement?"
• "Is the user experience intuitive enough for everyone, not just tech-savvy individuals?"
• "We need to ensure data security is top-notch – user trust is paramount."
• "Can we add a premium feature or subscription model down the line?"
• "Competitor X just launched Feature Y – how do we respond?"

Do:

• Review financial projections, market research, and competitor analysis.
• Approve budgets, sign contracts, and allocate resources.
• Participate in high-level strategic planning and roadmap definition meetings.
• Review progress reports, mock-ups, and user feedback summaries.
• Make decisions about feature prioritization and market strategy.
• Communicate with marketing teams about launch strategies and campaigns.
• Seek opportunities for partnerships or integrations.

Feel:

• Excited about potential market share and innovation.
• Anxious about budget overruns, missed deadlines, or competitive threats.
• Confident when user engagement numbers are positive.
• Frustrated by unexpected delays or poor user feedback.
• Responsible for the project's success and the team's direction.
• Optimistic about solving a real problem for householders.

2. The Developer (Software Engineer / Architect)

The Developer is focused on the technical implementation, code quality, system performance, and maintainability of the application.

Think:

• "How can I build this efficiently and robustly, while minimizing technical debt?"
• "Is this code scalable? Will it perform well with thousands of users?"
• "What's the most secure way to store and transmit sensitive financial data?"
• "Are the requirements clear enough for me to start coding, or do I need more details?"
• "Which technologies or frameworks will be most appropriate and maintainable for this application?"
• "How can I ensure the application is reliable and has minimal bugs?"
• "Is there a good testing strategy in place for this feature?"
• "Will this new feature introduce any performance bottlenecks or security vulnerabilities?"
• "How do I balance rapid development with long-term maintainability?"

Say:

• "We need to discuss the API endpoints for the utility bill data."
• "That database schema might need refactoring for better performance."
• "Have we considered the implications of X for scalability?"
• "The estimated time for this feature is Y, but we need to account for Z."
• "Can we get clearer user stories for this particular workflow?"
• "We should implement automated tests for this critical path."
• This third-party library is great, but what are its security implications?"
• "I've found a potential edge case that the requirements don't cover."

Do:

• Write, test, and debug code.
• Participate in daily stand-ups, sprint planning, and code reviews.
• Collaborate with other developers, designers, and product managers.
• Research and evaluate new technologies or solutions.
• Configure development environments and deployment pipelines.
• Document code and technical decisions.
• Address bug reports and performance issues.

Feel:

• Challenged by complex technical problems.
• Accomplished when a difficult feature is successfully implemented.
• Frustrated by unclear requirements, technical roadblocks, or persistent bugs.
• Proud of well-written, efficient, and secure code.
• Pressured by tight deadlines or performance demands.
• Curious about new technologies and optimal solutions.
• Collaborative when working effectively with the team.

3. The End User (Householder)

The End User is the person who will actually use the application to manage their household finances, seeking ease, clarity, and control over their budget.

Think:

• "Where does all my money actually go each month?"
• "Am I spending too much on utilities, and how can I reduce it?"
• "When is my rent/mortgage due again? I always forget."
• "Is this app easy to understand, or will it just add to my stress?"
• "Can I trust this app with my financial information?"
• "Will this actually help me save money, or just track what I already spend?"
• "I wish there was a way to see a clear breakdown of my fixed vs. variable costs."
• "What if I make a mistake entering data?"
• "Will I get annoying notifications, or helpful reminders?"
• "Can I access this on my phone easily?"

Say:

• "I need a simple way to see all my bills in one place."
• "Can this tell me if I'm on track with my budget this month?"
• "It needs to be quick to input new expenses."
• "I always miss utility bill due dates – can this help me remember?"
• "Is it secure? My bank details are sensitive."
• "This graph is confusing; I just want to see if I'm over budget."
• "Why can't I edit a past payment?"
• "It would be great if it could predict my next bill."
• "I want to know if my energy usage is higher than my neighbors'."

Do:

• Download and install the application (if mobile).
• Create an account and input personal details.
• Enter recurring rental/mortgage costs and utility bill details.
• Regularly input new utility bill amounts and meter readings.
• Check upcoming payment due dates and current budget status.
• View historical spending reports and charts.
• Set up notifications and reminders.
• Attempt to track and categorize their spending.
• Seek help or customer support if they encounter issues or confusion.
• Delete the app if it's too complicated, unreliable, or doesn't meet their needs.

Feel:

• Overwhelmed by managing multiple bills and financial obligations.
• Relieved when they gain clarity and control over their finances.
• Empowered by understanding where their money goes and finding savings.
• Frustrated by confusing interfaces, bugs, or missing features.
• Anxious about impending bill due dates or potential overspending.
• Secure when they trust the app with their sensitive financial data.
• Optimistic about achieving financial goals and reducing stress.