# data[].attributes.attachment_link.title
User Testing Review March 2021 - Google Jamboard

# data[].attributes.attachment_link.description
The version of the browser you are using is no longer supported. Please upgrade to a supported browser. Dismiss

# data[].attributes.headline
Work in Progress - Development Phase Sprint Notes

# data[].attributes.subject
Work in Progress - Development Phase Sprint Notes

# data[].attributes.body
Ongoing: February - April 2021

# data[].attributes.body
September - November 2020

# data[].attributes.body
June - August 2020

# data[].attributes.attachment_link.readable_text
When so much happens in any given week in this amazing development programme, it is great to take a moment to reflect through it all and put it in writing to maximise the open working impact.

This week we want to focus on our highlight and challenging moments, as we feel this will be something that will resonate with other organisations going through this process.

Over these past five days we saw our music therapy digital platform transform from a bare draft to a mind-blowing prototype ready for user testing next week.

Navigating the wireframing process has been exhausting and exciting at the same time, with hundreds of decisions to be made on a daily basis to achieve the required fast paced development plans. From fonts to colours, design to content, flow to illustrations, buttons, key-words, styling, and a million etcetera, we were so excited to see it all taking shape so nicely. It feels that so much has been achieved already, and that is definitely so rewarding! Huge hats off to our developers, Yalla Coop, who are so experienced and patient, and absolutely amazing.

We are using Figma to work live and collaboratively on this wireframing, and at times it has been challenging to keep up with the speed of development. A very flexible and generous time availability has been required to keep up with progress and avoid any delays, and managing this in the context of other work is not an easy task.

Figma is a great resource for this process, and although we had no previous experience we were able to use it with a simple 15 minutes run through to get started. Highly recommended!

Another challenge this week has been recruiting all the users that will take part in the user testing round next week. As it happens, there is a point in which panic strikes when you think you don't have enough people lined up, but efforts always pay off and by Friday we had more than we originally anticipated, setting us in the right direction for week 4 plans.

Last but not least, it has been great to attend Peer Review and Power OWL sessions this week, with lots of new resources to be incorporated into our work.

Looking forward to the next steps on this journey!

# data[].attributes.attachment_link.title
The balancing act of building a digital platform, fast

# data[].attributes.attachment_link.description
When so much happens in any given week in this amazing development programme, it is great to take a moment to reflect through it all and put it in writing to maximise the open working impact.

# data[].attributes.attachment_link.title
CMT - Definition Data: User stories, Risks, Musts, Persona, etc

# data[].attributes.attachment_link.readable_text
We started with a Consequence Scanning session on Monday that led to very interesting findings.

The exercise was based in three main questions

1- What's the intended/unintended outcome of our project

2- What's the positive consequences we want to focus on

3- What negative consequences we want to mitigate

And we develop these in three phases (I know, the number three seems to be a trend, but did you know numerologists consider number three the number of creativity, energy and possibility?)

Phase 1 - Introduction - Writing down all the intended consequences

Phase 2 - Ideation - Write down any other consequences imaginable

Phase 3 - Action - Colour coding

It was great to be able to organise our thoughts around intended and unintended consequences of our project, and categorise them between consequences with can ACT upon, consequences we can INFLUENCE the outcome of or consequences that are out of our control but could affect the product so we should understand better and MONITOR.

The exercise was done using Whimsical which is a great resource we are loving and using loads at the moment, and you can see our results here.

On Monday we also had a Technical Kick Off session, focusing on sustainable frameworks of development, levels of re-use, user-testing and deployment tools.

On Tuesday we had a Clinical Progress meeting with our Project Clinical Lead, Elizabeth Nightingale, and we discussed and continue working on the best ways to assess user engagement and content effectiveness, as well as planning user testing sessions, evaluating data for clinical reports, and mapping of a given user journey, among other important elements that link the technologic development, research and clinical areas.

Wednesday was another busy day, with an inspiring Landscaping Session in the morning, looking into style and design for our platform. It's so exciting to start visualizing this product we have been working so much on! We covered colours, illustrations, flow, onboarding strategies for the different users, data safety assurance, among other things.

Here's our landscaping session plan.

In the afternoon we had another hands-on session on User Journeys. Again, Whimsical was a great resource for this exercise, and Yalla and CMT joined forces in coming up with as many items for every user journey as we could think of, taking time to analyse each of them, and ultimately categorize them under different levels of priority with the minimum viable product (MVP) in mind.

Thursday found CMT, Yalla and the Catalyst team together in our Development Catch Up meeting, getting everyone up to speed on the fast paced progress we make week by week. We also had an interesting conversation about shared resources and being connected with similar projects.

Finally, it's Friday! Today we had another amazing User Journey Mapping session, going more in depth into prioritization strategies, mapping and planning our next moves. We've found the mapping exercise so revealing into how the platform will look like for our users and run through every step from our users perspective.

We can't wait to see what week 3 brings.

Irene

# data[].attributes.attachment_link.description
We started with a Consequence Scanning session on Monday that led to very interesting findings. The exercise was based in three main questions 1- What's the intended/unintended outcome of our project 2- What's the positive consequences we want to focus on 3- What negative consequences we want to mitigate And we develop these in three phases (I know, the number three seems to be a trend, but did you know numerologists consider number three the number of creativity, energy and possibility?)

# data[].attributes.attachment_link.readable_text
Well, we knew from previous similar programmes (EXPLORE was our digital "baptism of fire" so to speak) how fast things move once you get started... but oh my, the amount of work and progress achieved in the first week only has been nothing short of amazing.

Yalla Coop's team lead us fantastically through the several sessions we run this week, from initial Ways of Working overview, to Problem Development Part I and II, and Users Discovery. Some of the content previously drafted by our team was very helpful for this work, enabling us to go deeper into these items and presenting our newly appointed digital partner with a thorough overview of our project, problem, users and journey so far.

In the first day we covered essentials like:

Working processes and timelines

Communication channels

User Manuals: absolutely loved this way of introducing ourselves to the rest of the team and getting to know each other in a friendly and efficient way!

Roles, involvement and availability

Existing resources

Introduction to GitHub, our selected hub for all things related to this project.

Jargon: Yalla Coopwrote a very helpful list of tech development jargon that is easy to find pretty much everywhere and that after a week of extensive communication we have started to use ourselves!

Design thinking and sessions that we will go through in the next weeks, including personas, user journeys, crazy 8's and many more.

Definition of done agreement, such an important element to tackle on the very first meeting.

On the following days we went deep into items including:

Project planning

Introduction to landscaping

User testing planning

Users discovery

Among other things.

Lots of ideas and question marks seem to light up in every conversation, and it's exciting to see it happening. We know already from EXPLORE experience that at the start of such a journey things can feel a bit confusing and overwhelming. We certainly recognize that feeling again... it's time to wind the bobbin up and untangle the yarn.

See you next week!

Irene

# data[].attributes.attachment_link.description
Well, we knew from previous similar programmes (EXPLORE was our digital "baptism of fire" so to speak) how fast things move once you get started... but oh my, the amount of work and progress achieved in the first week only has been nothing short of amazing.

# data[].attributes.attachment_link.title
Digital Platform Research - Initial Findings.pdf

# data[].attributes.body
WOL Workshop Exercise III

# data[].attributes.headline
What we learned and what we are yet to ask

# data[].attributes.subject
What we learned and what we are yet to ask

# data[].attributes.body
WOL Workshop exercise II

# data[].attributes.body
WOL Workshop Exercise I

# data[].attributes.body
I am the Project Lead but I work alongside an amazing team, including Rebecca, Tim, Elizabeth and our fantastic developers at Yalla Coop