First app hackathon

Hello!

I’m almost three weeks into a new role with the app team and today took part in my first app hackathon.

At first I was slightly alarmed that we were all going to be taking a day out of delivery with an important deadline on the horizon, but I thoroughly enjoyed the day and found it surprisingly valuable to step back mid-Sprint and think about what the future holds beyond July.

I joined a group looking at homescreen personalisation, which I was particularly keen on as I’d already done some thinking around this in preparation for the interview and was pleased to see the team were thinking about opportunities in this area themselves.

Our app as it stands is like a scaled down version of the website. The homescreen lists all the products we offer, which in turn direct users through category screens and article screens, through the creation journey and onto the checkout. It’s functional and in many ways easier to manoeuvre than the website, but there’s a missed opportunity there for our return customers.

The biggest pain point we identified early on was that every customer has the same experience of the homescreen. Whether it’s their first time opening the app or they’ve been an active customer for many years, they each need to navigate through a catalogue-style layout to find and create a product.

As an alternative to this, we set about imagining a more personalised model where customer behaviour and preferences are utilised to craft an individual experience.

Hypothesis: If we can replace uncertainty with inspiration we will achieve higher conversion rates and increased order value per customer.

Once we had our goal of increased personalisation defined, we were able to brainstorm ideas around how this might play out for customers on the homescreen, map dependencies and group each idea into effort versus impact buckets. This step enabled us to define a now, next and future roadmap with the quick wins prioritised upfront and the bolder features identified for later in the year.

Happily, all the features in the ‘now’ column could be coded up into an on-the-day POC for sharing immediately with the wider domain and soon with customers in our first round of user testing.

Altogether I had a great day and I’m glad to have joined the team at such an interesting point in their journey!

There are now crypto ETFs

Something extraordinarily ironic happened in crypto this week: you can now buy ETFs through major financial institutions like Fidelity and BlackRock.

Interestingly you can’t buy them with Vanguard, who termed crypto a ‘non-productive investment’ and against the company’s ethos of thoughtful risk management on behalf of investors.

The backlash from the crypto world against Vanguard’s decision is quite astounding when you consider what’s actually happening here.

Bitcoin, for example, launched in 2009 as a disrupter to the ‘Big Finance’, the entire principle behind its existence is as an independent alternative to traditional banking institutions. You could mine it independently, store it independently, trade it independently, it’s really a remarkable concept when you think about it.

That’s what makes the full-circle news this week so interesting – not only can you now buy a piece of the action through these established financial giants, but crypto investors are actually expressing outrange at Vanguard for not offering similar funds to their customers.

To make things even more interesting, the approval of the funds this week caused crypto value to go down quite significantly, up to 17% at time of writing, and Vanguard were called out for this in some circles for appearing to delegitimise the integrity of the crypto ETF market. Now read that sentence again, isn’t that amazing?

The ceaseless march of establishment capitalism is so strong and pervasive that it can even orchestrate a swallowing of its competitors whilst creating a market to profit from them on the way down, all the while provoking calls for a more thorough execution of the downfall from those who stand to lose.

What a world.

Writing posts with Chat GPT

I used Chat GPT to write my last two posts, partly because I was busy, partly because one of them was a fairly boring topic, and partly because it would presumably be perfectly suited to the task and I wanted to see that in action.

I’ve never been interested in SEO. I know what I should about it because I’ve had to for every role, but I find it not only tedious but also a bit morally questionable. The internet at its best is a level playing field, there is a barrier to entry in terms of coverage and access to connected devices, but for those who are fortunate enough to overcome these hurdles, content is available fairly readily to anyone who wants it.

The idea of companies such as Google creating a product that sifts through the everything and hones in on the best and most relevant match to a user’s search is also a theoretically great idea, however as we all know, we’ve been way past that for some time now and into the realm of winner takes all. 

As a result, I wasn’t too excited about investing any time writing about the many months my team and I spent pleasing Google, so I gave Chat GPT the basics and asked it to write the post for me. 

It did a great job. In under a minute it turned my simple prompt into a 500 word article that was well structured, made complete sense and included everything I wanted it to. Aside from rewording a small number of Americanisms, I posted it exactly as it was and surprisingly felt the same sense of achievement I usually do when I spend an hour or two writing a post myself. 

The second post I asked Chat GPT to write was more personal and creative. Life had felt quite hectic over Christmas so I’d been putting it off and my assumption that an LLM would perform worse at this type of article discouraged me from considering Chat GPT sooner. 

This time I gave it far less context, simply “write a 500 word article in the style of my other posts on how being a minimalist helps me to be a better product manager.” And since GPT-4 now sits behind a paywall, I used Copilot, which offers part GPT and part other AI products (image technology, etc).

The article Copilot wrote for me was fine, but much more obviously LLM generated than the previous post. It began surprisingly well with a great introduction about what minimalism was, its core principles and how they could be effectively applied to product management. It also gave the introduction a personal voice that I felt was pretty in keeping with the general tone I usually aim for.

The structure and composition of the post overall also made perfect sense and I was surprised that it managed to pull out three quite sensible crossover themes between minimalism and product management: prioritisation, communication and innovation. 

Where it fell down for me though was in the language and cadence. This was a much harder challenge than the technical post I’d asked it to write previously and I felt that really came through in a way that perhaps was to be expected. 

I’d given Copilot the instruction to write the article in the style of my other posts but felt overall that it failed to achieve this. Although every sentence was structured ‘correctly’ it was very repetitive, as if it believed the words between the ideas didn’t matter as long as they did the technical job of stitching everything together.

It also introduced a quite strange crescendoed metre, which was fine once or twice but felt a bit silly being used in every sentence, as if I was giving some dictatorial national address, circa 1933.

The post then ended fairly abruptly, without a conclusion. This was interesting as conclusions are generally a fundamental structural component rather than something stylistic and more difficult to teach.

Overall I’m glad I ran this experiment and chose two articles that were quite different. Going forward I’d be really confident continuing to use Chat GPT for technical posts or to summarise existing material, but for more creative content and without a paid subscription, I’ll stick to writing them myself for now! 

The benefits of minimalism in product management

Minimalism is a lifestyle that embraces simplicity, clarity and intentionality. It is about reducing the clutter and distractions in our lives and focusing on what matters most. Minimalism is not only a personal choice, but also a professional one. As a product manager, I have found that applying minimalist principles to my work has helped me to become more effective, efficient and creative.

Minimalism helps me to prioritise

One of the most important skills of a product manager is prioritisation. There are always more features, bugs, requests and ideas than we can handle. How do we decide what to work on first? How do we communicate our decisions to our stakeholders? How do we avoid scope creep and feature bloat?

Minimalism helps me to prioritise by forcing me to ask myself: What is the essential problem we are trying to solve? What is the simplest and most elegant solution we can offer? What is the minimum we can deliver in order to start gaining meaningful user feedback and make informed decisions for improvement?

By applying these questions, it helps me to filter out the noise and focus on the signal. I can eliminate the unnecessary and the nice-to-have and concentrate on the must-have and the most impactful areas of delivery. I can also avoid over-engineering and over-complicating products, which can lead to wasted time, resources and frustration for my team and our users.

Minimalism helps me to communicate

Another key skill of a product manager is communication. I need to communicate our vision, strategy, roadmap, requirements, feedback and results daily with multiple users and stakeholders clearly, concisely and convincingly.

Minimalism helps me to communicate this way by forcing me to keep explanations simple and straightforward so that everyone feels confident and informed about work that impacts them. It helps me to avoid technical jargon, buzzwords and acronyms that can confuse or alienate colleagues and customers. It helps me to use visuals, diagrams and examples that can illustrate and explain a change or direction in a way that builds trust and reduces uncertainty.

By applying these techniques, I can communicate more effectively and efficiently. I can make sure that everyone is on the same page and understands the key principles and actions that my team will take. I can also inspire and motivate engineers and stakeholders to share in the vision and support ambitious goals.

Minimalism helps me to innovate

The final skill that I want to highlight is innovation. As a product manager, I need to be constantly looking for new and better ways to solve problems, create value and increase customer conversion. I need to be creative, curious and experimental in order to implement new ideas and improve existing experiences for users.

Minimalism helps me to innovate by forcing me to question my assumptions and biases. It helps me to look for the root causes and underlying needs in the problems I’m looking to solve. It helps me to explore different perspectives and possibilities that may have been overlooked or dismissed in the past. It helps me to test and iterate ideas quickly and economically, using feedback and data to guide decisions and improvements.

By applying these practices, I can innovate more effectively and efficiently. I can discover new opportunities and solutions that can differentiate our products and offer customers clean and positive experiences that encourage them to want to return in the future.

Improving Core Web Vitals by 43%

Core Web Vitals have become increasingly important in recent years as they play a significant role in determining a website’s search engine ranking. Core Web Vitals measure the user experience by looking at how quickly a page loads, how quickly it becomes interactive, and how visually stable it is while loading. By optimising Core Web Vitals, businesses can improve user experience, reduce bounce rates, and ultimately drive a higher rate of conversion.

At Photobox, we realised we were trailing behind competitors in this area and that by improving our performance scores we were likely to see improvements in key metrics such as conversion, engagement and retention, e.g:

My team run the ‘Shop’ portion of the Photobox website, which is a React based application serving the product selection part of the experience for customers.

We knew that to move our scores meaningfully upwards would require significant investment and so set about demonstrating to the business the importance of scoring well in this area and the likely returns we could expect from our efforts. After a successful internal campaign, we were given the go-ahead to invest 25% of our time into this work over the course of one financial year and given a target to improve of 20% in order to meet competitor benchmarks.

We then developed a long list of potentially impactful improvements and used the RICE formula to prioritise these, slotting them into the roadmap in a way that would ensure we delivered high value improvements early to reassure stakeholders of the difference we would make to our scores by the end of the year.

Our 17 most impactful improvements

  1. Upgrading Node: We upgraded to the latest version of Node, which allowed us to take advantage of the latest performance improvements and bug fixes.
  2. Removing Ramda: Ramda is a functional programming library that we were previously using, but we found that it was slowing down our site. By removing it, we were able to improve performance.
  3. Refactoring Extended Fetch: We refactored our extended Fetch API to improve performance and reduce bundle size.
  4. Refactoring KOA: We also refactored our KOA middleware to improve performance and reduce bundle size.
  5. Reducing bundle sizes: We used tools like Webpack Bundle Analyzer and Code Splitting to reduce bundle sizes, which in turn helped to improve page load times.
  6. Removing props: We removed unnecessary props from our components to reduce the amount of data that needed to be transferred between the server and client.
  7. Deprecating unused code: We went through our codebase and removed any unused code, which helped to improve performance and reduce bundle size.
  8. Delaying experiment code: We delayed rendering of custom experiment code to improve initial load time and First Contentful Paint.
  9. Resolving garbage collection errors: We resolved any large garbage collection errors that were causing our site to slow down significantly or in some cases timeout altogether.
  10. Refactoring Apollo Client: We refactored our Apollo client to improve performance and reduce bundle size.
  11. Implementing high fetch priority: We implemented high fetch priority for essential resources, which is recommended by Google and helped to improve page load times.
  12. Cleaning up Redux payload: We cleaned up our Redux payload to reduce the amount of data that needed to be transferred between the server and client.
  13. Optimising images: We optimised our images to reduce their file size, which helped to improve page load times without compromising the importance of images in showcasing our product catalogue.
  14. Extending caching: We extended our caching to reduce the number of requests made to the server, which helped to improve page load times.
  15. Removing unused JavaScript: We removed any unused JavaScript to reduce the amount of data that needed to be transferred between the server and client.
  16. Increasing lazy-loading: We increased lazy-loading where possible in order to reduce the amount of data that needed to be transferred between the server and client.
  17. Optimised ESLint: We optimised our ESLint configuration to improve performance and reduce bundle size.

As you can see, bundle sizes were the biggest contributing factor to our lower Core Web Vital scores and a significant proportion of the work we undertook was to reduce these across our stack.

Each quarter I reported on our progress towards the 20% target and was excited to see we were achieving beyond this every time thanks to the hard work of the team.

At the end of the financial year we had managed to achieve a huge 43% improvement in our Core Web Vital scores and we were now in the top performing quadrant against our benchmarked competitors.

Work is now underway from our SEO and Analytics teams to evaluate the commercial impact of our work this year. I’m looking forward to sharing the results!

Working from home changed my life

I am fortunate enough to be someone who benefited enormously from the shift to remote work that came from the COVID19 pandemic.

I had always found commuting to be a challenge for both my mental and physical health. When I worked for Mind, I commuted 4.5 hours a day from Brighton to East London. It was so exhausting that I was relieved to eventually move to London, only to find that the tubes are too packed in the morning to board, so I traded my long train journeys for a gruelling and hazardous cycle through central London each day.

When the pandemic hit and everyone who could was required to work from home, I was initially worried that mixing my work and home environments would be lonely and difficult to switch off from, but I soon found the benefits outweighed the downsides so significantly that the transition eventually began to feel absolutely life-changing.

Suddenly it was 5pm and I was already home. I could say yes to things I’d previously considered to be for people without jobs. I became more community orientated. I could stay out later in the evenings without fear of the early alarm. I could wake up to natural light and casually sip coffee while I checked my morning Slack messages from a desk at the end of my bed.

Eventually I also became aware of the financial benefits too. As the months rolled by, I noticed my bank account looking significantly healthier than usual. I was awake for fewer hours and the physical demands on my mind and body were reduced, so the recommended three meals a day which I’d always found weren’t enough to get me through suddenly made sense. Coffee was now something I could enjoy for pennies rather than pounds and exercise was a safe lunchtime run rather than a pricey after hours gym membership.

Throughout the pandemic, I noticed business leaders fearing the trend to working from home would lead to a decline in productivity for employees. I was surprised by this as I found the very opposite to be true – I was more productive than ever and finally enjoying my working days. Rather than battling through the constant distractions and piecing together a functional work station each morning, I suddenly had instant access to a peaceful, comfortable and productive work environment from home. Collaboration with colleagues had never been easier as the time-wasting palaver of looking for private space and usable stationary had become a thing of the past. Co-working was now an effective and fully digital experience, a simple click away.

Since the threat of COVID19 has gradually reduced, the ‘return to work’ discussion is beginning to emerge, with many companies expecting employees to return to the office at least a couple of days a week. For me though, there’s no going back to that life now I know how positive and productive the alternative can be.

Side hustling towards financial independence

Like many semi-nomadic tech workers, I’ve recently become interested the FIRE movement, not necessarily with the intention of retiring early, since I love my work, but with the option to have financial security and freedom from the constraints of having to work in the future.

One common approach to the wealth building phase of FIRE is the concept of a side hustle, a job that fits around the 9-5 and provides extra resources for savings and investment.

Early last year, I gave a lot of thought to the kind of side hustle that would make sense for me. My criteria were:

  1. It had to fit neatly around my full time job – I didn’t want to be in the position where I felt stressed juggling the two or trading one off against the other
  2. It had to be simple enough that it wouldn’t require any additional mental energy to complete – again I didn’t want to be in the position of sacrificing my commitment to one in favour of the other
  3. It had to pay enough to make the additional tax worthwhile, either by being infinitely scalable so that I could choose to invest more time in order to maximise output, or by offering a high enough wage in itself

The first side hustle I tried was sports umpiring. This fit my first criterion easily as games took place after work. I would arrive at a nearby venue with my whistle and scorekeeping app, then spend an hour or two sprinting up and down various South London sports halls trying to keep track and accurately administrate the play.

Although umpiring offered what I was looking for from a timing perspective, it didn’t meet my second or third criteria. It was much more difficult than I imagined it would be to see and mentally calculate gameplay in real time, even for the sports I knew well. For those I wasn’t so familiar with, it was even more challenging still. The pay was also minimum wage, which although higher in London, didn’t feel worth it for how stressed I felt at the end of each match.

The second side hustle I tried was freelance user research. Being freelance meant I could theoretically dedicate time to it on a schedule that suited me, it was something I knew well and could deliver value for my clients, and I set the pay so was able to calculate a rate that made sense for my goals.

Although this work certainly felt a better fit than umpiring, it eventually began occupying more space in my life and mind than I wanted. I found myself working late into the evenings and giving up numerous weekends, I felt annoyed when I received client emails outside of the times I’d committed to working with them and although the pay to output ratio was significantly more favourable than umpiring, I couldn’t simply leave the stress on the court and go home.

Finally, I found what’s since felt like the perfect solution – user research as a participant rather than a researcher via usertesting.com. As a participant, I can choose when I have a free slot and would like to participate in a test. As I’m invariably talking about my own experiences with everyday issues, I’m rarely required to do any advance prep, which means the time spent logged into the test is contained and if a topic suggests it might take more from me than I want to give, I can simply decline that instance. The pay is usually around $60 an hour, but it’s infinitely scalable and the scaling is even compounded overtime by the number of positive reviews you receive as you participate in a greater number of studies.

Having tried three different side hustle options in 2022, user testing as a participant with usertesting.com has been the most successful by far and I’m looking forward to reviewing its contribution to my financial goals in the summer, once my first year of participation is complete!

Working out loud for lasting change

I’ve been thinking about this post for a while, as I realised it’s something I’ve really turned a corner on in the last few years of my career.

I’ve always been quite an introvert when it comes to my work, preferring the speed and focus that comes from designing, planning and executing product development with as few trusted colleagues and specialists as it takes to research, deliver and measure value for users as quickly and efficiently as possible.

However, a few years ago, as part of a mentoring session, I learned the mantra:

If you want to go fast, go alone. If you want to go far, go together.

This idea really stuck with me as I’d often found it difficult to communicate what I was working on and its importance as widely, frequently and collaboratively as I’ve since found to be vital for effective change.

The unintended consequence of my approach had often been that projects were deprioritised when I couldn’t successfully convey their value, or worse, had been duplicatively attempted by colleagues elsewhere in the organisation, unaware of my team’s isolated ambition to achieve the same outcome.

In the early stages of my career, I had been able to get away with this tendency as those above me played the leadership role I was neglecting to fill, but as I gained more experience myself, l became increasingly aware I had to step out of my comfort zone and embrace this skill if I was to make a meaningful impact in my role.

Since adopting this mantra in my day to day work, five lessons I have learned are:

  1. Every person I work with shares the same goal of wanting to deliver value to customers
  2. Working out loud from the very beginning drives the kind of analysis and perspective that is critical to true success
  3. Achievement is as much defined by the right conversations as it is by the end result
  4. Meaningful collaboration forms key relationships that allow more ambitious outcomes to be reached in future
  5. Shared ownership of success creates a culture of innovation that is necessary for long-term impact

At first, working out loud didn’t come as naturally to me as other aspects of product management. Now, it’s something I’m grateful to have realised and look forward to continuing to develop the skill!

Three surprising differences between the charity and private sector

Two years ago I made the decision to leave the charity sector and, due to Covid, I’ve actually managed to have three jobs in that time, so I thought I’d take the opportunity to reflect on my assumptions going in and share a few surprises I’ve found since making the change.

We value quantity over quality

The most surprising difference I’ve found is the tradeoffs in quality and best practice we are willing to make in order to increase our profits as quickly as possible. In the charity sector, we aim to do things cleanly and well, and we care less about how quickly value is returned for our efforts. We tend to be painfully diligent people, all too aware that our users are living with cancer, degenerative physical diseases or mental health problems and a good day in the office for us goes some way towards lightening that load for them.

In the private sector, however, the speed at which money is generated is the number one priority and we appear to be willing to sacrifice almost anything to get it. The consequence of this is the mounting of an endless and often prohibitive amount of technical debt. This is not only technical debt in the backend, for example in pipeline or service stability, but also in the frontend too. We worry little about bugs, broken UI, brand violations or fragmented user experiences. If a new feature will generate more money than fixing these issues, then that’s what we’ll work on, everything else is off the table until ‘quieter moments’, which of course never materialise.

We believe we deserve our jobs

Approach and attitude is another significant difference that continues to surprise me the more people I meet in the private sector. In charity, I always felt a sense that everyone around me believed they weren’t good enough and that even if they were, they were the luckiest people in the world to have that job and would work tirelessly to prove themselves and keep hold of it in the face of never-ending financial worry.

In the private sector, that sense appears reversed, people generally seem to feel the company they work for is lucky to have them and with that comes a strange sense of confident complacency that feels uncomfortable to me as someone coming in from a world dominated by anxious insecurity.

As a Product Manager, my job includes overseeing delivery and this is where I most notice the attitudinal disparity. If deadlines were threatened in the charity sector, people would be up all night, working at weekends or crying in private meetings with their managers, afraid that they were letting everybody down and would deserve to be fired as a result. Whilst in the private sector, deadlines often approach with a shrug as people casually state they didn’t achieve anything yesterday because they had to take their dog to the vet, it was already 5pm or they couldn’t see the value in the task.

There still isn’t enough money

One of the reasons I was initially interested in seeing what life was like on the other side of the fence was to see what could be achieved with much larger budgets. Working for a charity you become very creative, always looking for new ways to get around the fact that you can’t really afford to do what you need to. In the private sector I came in with the assumption that money would flow more freely and liberate teams to be bolder and more ambitious in their digital aspirations.

Instead, what I’ve largely experienced is a form of financial Parkinson’s Law in which premium capital leads to premium spending and what remains feels equally small and difficult to secure. This is particularly noticeable in recruitment where wages are vastly higher than in the charity sector and teams are comparatively very well staffed. This makes the case for additional resource and even the backfilling of existing roles surprisingly challenging.

And yet, I love it

Despite every surprising difference and every unusual challenge, I find it difficult to imagine going back to working in charity, at least for now.

Every day I come to work it’s interesting, fun and absolutely nobody is going to die.

Instead, the worst consequence of a bad day is a little lost revenue or a few disgruntled colleagues. I’m no longer fixated on the fact that what I do is too important for me to be doing it. Because it isn’t important, not really.

I like my work, I’m grateful to the tech industry for creating it and I take pride in what I do. But when I leave in the evening, I no longer lie awake at night wondering whether I did enough to alleviate the burden on someone living with stage four breast cancer or contemplating taking their own life.

Every time I lose a UX battle, a leadership debate or domain-impacting decision, I no longer torture myself with the potential implications for users whose lives are hard enough already. I can now finally afford not to place such heavy expectations on myself and those around me because, after ten years in digital, failing no longer feels to me like the end of the world.

Creating a digital breast cancer support course

Breast Cancer Now offers physical support courses to people living with primary and secondary breast cancer. One of these courses is Moving Forward, supporting people once they’ve finished treatment to cope with issues such as body confidence, returning to work and managing fear of recurrence.

As a charity, we can’t provide this free service to everyone we’d like to, we can’t run one in every part of the country, we can’t pay for people to travel up to 200 miles for their nearest service and we can’t offer much desired refreshers to previous attendants because it would take away a first time space from somebody else.

As a product manager, I was given the amazing opportunity to create a digital solution to these challenges with an online tool that would allow more people to access and work through the course material from home. It’s been one of the best projects I’ve worked on in this role, so I thought I’d share how it’s going so far!

First off I had research phase, I wanted to find out as much as I could about the needs of the course, the appetite for a digital version, feedback on the physical courses that I could factor into the development and I wanted to know more about what makes a successful online learning and support tool.

After that was a prototype phase, which allowed me to check the conclusions I was drawing in my mind were an accurate reflection of what the tool should be for users, course providers, content and health information specialists.

Then it was time to make an Alpha product which we could take ‘on the road’ to user groups around the country. This was the first time everyone had the chance to see what the tool could look like and how they might interact with it as a participant of a Moving Forward Online course. We’d got a lot of things right, people valued the usability, the content and the interactive nature of what we’d created, but the immense value the users provided as they participated in our workshops and feedback sessions was context.

As digital and health professionals, we were experts in how to technically make and deliver a valuable product, but most of us knew nothing about what it was like to participate as someone who had been through a breast cancer diagnosis. With insights from users with these direct experiences, we were able to identify what we hadn’t got right yet, which means by the time we create a Beta version of the tool for the New Year, we’ll know we’ll have created something that’s not only usable and informative, but also feels safe and empowering for everyone at home who’s been through the trauma of diagnosis and treatment and is looking to understand where to go from here.

The feedback sessions highlighted the importance of connection with others who are going through similar experiences, so we added a private and moderated group to the Breast Cancer Now Forum, which Moving Forward Online participants can connect to via single signon straight from the tool.

They also highlighted the importance of having a healthcare professional available as people worked through the material and worried about issues that might affect them, so we connected the tool to the Breast Cancer Now Helpline with a dynamic prompt, which means a phone icon displays when the Helpline is open, and an email icon displays overnight. That way users are always connected to the best way we can help them at the time they need it.

We knew managing fear of recurrence was what people reported to be most worried about when they came to the physical courses, so we’d made this the first section. But we hadn’t fully appreciated what an emotional trigger the topic would be for individuals participating in the course, so we reorganised the content and the language around this to much more sensitively and resourcefully guide people through valuable, informative and empowering modules and eventually towards issues around breast and body awareness after breast cancer.

After the Christmas holidays, we’ll deploy the sprint that includes these and many other new iterations of the tool, we’ll finalise the content, agree our evaluation strategy and be ready to launch a year long Beta with a select group of live users looking for support to Move Forward after breast cancer.

I’ve loved working on this project and while I’m leaving Breast Cancer Now in the New Year, I’m looking forward to checking in with the team on how the 2020 Beta goes!