yalla-coop/cost-of-living

A tool to help people with the Cost of Living crisis

cost-of-living's Issues

Review User Testing synthesis ahead of meeting

Usability Testing + Synthesis

Short overview

• Conduct interviews with users to test key functionality of the CoL tool and UC helper
• Yalla to synthesis research to be reviewed with Hyde

Needed from client

• Recruit potential users for UC helper
• Recruit potential users for CoL tool

Stakeholder Interviews

Short overview

Yalla to conduct interviews 1-to-1 or in small groups with various experts within Hyde (and partners?) who can help us better understand the problem areas we have identified in Problem Mapping

Client tasks

• Send emails OR intro us to the people we need to speak with

Add people's time on Float

Update scope of issues

Desktop research into Cost of Living content

Summary
A big part of the app will be the content we share - what are the key areas, how should we lay out information etc etc.
We need to then research how content is currently being communicated

• Search online for reputable places offering advice on CoL (e..g Martin Lewis)
• Add notes here: https://www.notion.so/yallacooperative/Content-Research-bc14fa27fd14473f8c89b4a1cd71e486
  • Try to group by categories
  • Add links to the websites you have researched (so others don't copy)
• At this stage it's just about getting as much content as possible

Watch recording of user stories feedback

User Personas

Short overview

• Build personas for CoL tool
• Prioritise

Links
https://www.figma.com/file/hMtA8dePTaga6KVkrTrMFQ/User-Personas

Send loom with changes to Maggie

User Journeys

Short overview

• We will map out the key user journeys for the CoL tool
• We will map out the key user journeys for the UC tool

Content / Problem Mapping

Short overview

• Use our research to map out the major problem areas for people facing the Cost of Living crisis
• Breakdown these problem areas into smaller problems
• Prioritise

Links
https://www.figma.com/file/l4BylUrfx3atBhGoXcdqpv/Content-%2F-Problem-Mapping?node-id=0%3A1

UC Helper - Add/Delete/Drag&Drop steps

Summary
We want to give super admins the option to:

• Add a new step
• Delete an existing step
• Change steps order

@jema28 I don't think I have wireframes for this... I found the link below in Notion, but I don't see mockups of the new functionality requested to add/delete/reorder steps.

Wireframes
Desktop: https://www.figma.com/file/2b1vIUlRczjuwhWr9cE9OY/Wireframes?node-id=1932%3A9679

Acceptance Criteria
Front End

• ...
• ...

Back End

• ...
• ...

User Stories

Short overview

• Yalla will map out the journeys into individual stories

Warranty

Raising an issue

There are three different types of issues:

1. Bug -> Something isn't working as we think it should
2. Task -> Something you would like to store to remember to do in the future (e.g. deleting a user)
3. Discuss -> Potentially a bug or task or something else, and you aren't sure

There are 4 priority levels to help us know how quickly to jump onto the task:

• Urgent -> ASAP - aiming for 24 hour resolution
• High -> To resolve this week
• Medium -> To resolve this month
• Low -> Not urgent or important, something to keep in mind as a potential use of proactive time or if it is super simple to

How issues should be raised:

Client responsibilities

• Create an issue in Github using the template depending on the type of issue (i.e. Bug or Feature request)
• Please provide us much detail as you can using the template on the issue provided
• If urgent (i.e. website has gone down) then also please email [email protected]

Yalla Responsibilities
Once an issue is raised in repository we will:

• Respond to you, letting you know that we have seen the issue and are looking into it
• (For Bugs) We will immediately assign someone from the team to investigate the issue
  • They will provide a written update on Github issue including:
  • Whether it is a bug
  • Next actions
  • Estimated time to resolve (if possible)
  • When an update will next be provided
• (For feature requests) These are purely there for your backlog

On the resolution of issues:

Yalla responsibilities

• We will give the issue a 'fixed' tag and provide you a final update (if required) in the issue

Client responsibilities

• Please test the issue
  • If you are happy it is resolved, then please close the issue
  • If not working or some other related issue, then please add a comment @'ing us

Landscaping

Summary / Context

We will carry out research into the tools out there to see what they are doing well and what can be improved on. Areas for us to look at:

• What other people are doing in this space:

  • What already exists and why it's not fitting the problems we're looking to solve - what are our users needing
  • The language other platforms use - what works and what doesn't

• UX / User Experience:

  • User experiences our user personas know and like
  • inspiration from platforms that we can use for how users might interact with our own digital platform
  • what apps / websites do these personas tend to use?

• Content:

  • What is the tone of other similar platforms looking to support people? Is there anything to learn from these? Anything we would want to then change in terms of our Content Guide?

• Visual:

  • Any further inspiration to consider that might lead to changes to the existing sort of style we have for the UC helper?

---

What to do

Using the template below, add comments on this issue below for each digital tool you feel worth discussing

Template:

• App/website name:
• App/website link:
• What is it relevant for: Other Person in Space / UX / Visual / Content
• If possible, the specific part(s) and/or flow(s) you like (with link or a few screenshots if possible!) and a description of why you and our users would like it. Why do you feel it's useful to look at with our project in mind?

Create User Testing scripts

Hey @bethanyios not seen this anyway so just creating an issue to be sure this is picked up this morning please. Thanks

Actions

• Create usability testing scripts for upcoming round of user testing
• Internal review Joe
• Send to Hyde for sign off (needs to be afternoon of 10th so they've got time to feedback)