<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jennifer Rose on Medium]]></title>
        <description><![CDATA[Stories by Jennifer Rose on Medium]]></description>
        <link>https://medium.com/@JenniferRoseS?source=rss-8722b792fd48------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KrRlM6oiMC86Pu8cXxmJWg.png</url>
            <title>Stories by Jennifer Rose on Medium</title>
            <link>https://medium.com/@JenniferRoseS?source=rss-8722b792fd48------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:46:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JenniferRoseS/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From ‘getting it done’ to ‘making it happen’ — five stages on the road to becoming accuRx’s…]]></title>
            <link>https://medium.com/accurx/from-getting-it-done-to-making-it-happen-five-stages-on-the-road-to-becoming-accurx-s-2594bc98bb49?source=rss-8722b792fd48------2</link>
            <guid isPermaLink="false">https://medium.com/p/2594bc98bb49</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Jennifer Rose]]></dc:creator>
            <pubDate>Tue, 31 May 2022 09:21:20 GMT</pubDate>
            <atom:updated>2022-06-17T12:36:57.997Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>From ‘getting it done’ to ‘making it happen’</strong></h3><h3>Five stages on the road to becoming Accurx’s Product Director</h3><p>I’ve now been at Accurx for two wonderful years. For the first year, I was a Senior Product Manager, working within a team to ‘get things done’ — building products to solve the problems of our users.</p><p>After 12 months leading an amazing product team, I was promoted to Product Director and Clan Lead (I’ll explain this later) to focus on our products in secondary care — a new market for Accurx.</p><p>This meant I didn’t lead a product team anymore, but instead was overseeing lots of different teams. I had to learn how to ‘make things happen’ rather than execute them personally.</p><p>Having been in this leadership role for over a year now, it feels like a good time to reflect and to look back on the whirlwind of it all. Here are the five big stages I went through as I stepped out of my comfort zone, becoming Accurx’s Product Director.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FyzZ01WvwEJofDtY" /><figcaption><em>My emotional journey over the past year — as the great philosopher R. Keating once said — “life is a rollercoaster, just gotta ride it”.</em></figcaption></figure><h3><strong>My five stages on the road to becoming </strong>Accurx’s <strong>Product Director</strong></h3><h4>1. 😮 <strong>Woah, this is weird and different</strong></h4><p>In the days and weeks after taking on my new role, I felt adrift. Being in a product team means having the routine and comfort of your ceremonies. Every morning at 9.45 we’d have stand up together, and every Friday we’d have planning and a team retro. Nice and familiar. Suddenly, I was a Product Manager (PM) without a team. How would I know what to prioritise? What would anchor me if I didn’t have these rituals?</p><p>In reality, I was able to use a lot of the skills and techniques I’d used in my team to apply to the whole side of the business I was now leading. At Accurx, we’ve called them ‘Clans’. There’s a GP Clan, who work on all of our primary care products, and I was tasked with spinning up and leading the Trusts Clan — to extend our company into the secondary care market.</p><p>But I knew this wasn’t something I’d be able to do alone. I needed people who I could confide in, share my thoughts and sense-check my decisions. I needed a ‘first’ team — one whose time I would prioritise, just like I had with my product team. So my priority became building a strong Clan Leads team, recruiting my colleagues Mike and Satya (even pulling Mike with me from my product team into this new world of Clan leadership!).</p><p>Once they were by my side, we helped each other focus and understand what was important. We even ran a kick off, just the three of us, getting to know each other more as people, as well as talking through everything on our minds through a ‘<a href="https://hbr.org/2007/09/performing-a-project-premortem">pre-mortem</a>’. This <a href="https://medium.com/accurx/how-we-run-workshops-at-accurx-80cefb163c79">workshop</a> identified what was in our heads as we embarked on this new challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kc_luuWdbAkc3yfj" /><figcaption><em>Our pre-mortem — very interesting to look back a year later and see what we correctly predicted!</em></figcaption></figure><p>It was still hard to know whether I was spending time on exactly the right things… but with my Leads team set up, at least I knew where home was.</p><h4><strong>2. 😨 Oh no, I’m overwhelmed and underqualified</strong></h4><p>After the initial joy of finding my team, imposter syndrome started to set in. I started to doubt that I was cut out for the role, that my manager/mentor/all round good guy Benji had made a mistake in backing me for this step up. <a href="https://medium.com/accurx/my-career-move-within-accurx-4a5a803b4704">Starting a new role</a> that I hadn’t done before was <em>of course</em> going to move me out of my comfort zone — but how does anyone learn anything new if they stay doing what they already know how to do?!</p><p>I knew it would be even more important to make sure I was giving and receiving honest, actionable feedback from those around me: my Leads team, those within the Clan, and my direct reports, as well as senior stakeholders across the company. I made sure to ask for it and give it at every opportunity.</p><p>The constructive points I received helped me course-correct my approach, and the positive feedback was incredibly helpful to combat that imposter syndrome — which never disappears, by the way. I occasionally find myself reading back over positive peer feedback for reassurance on those days I feel like a fool who’s about to be found out. 😅</p><h4>3. 😬 <strong>The decisions are getting bigger</strong></h4><p>One of the hills I was worried about climbing was making the first ‘big decision’. I was now accountable and responsible for a large portion of the company, as well as for one of our top goals. And soon enough, there it was, right in front of me. Aaand… I made it. And the second one, and the third. I was used to having to make hundreds of decisions while <a href="https://medium.com/accurx/my-journey-to-becoming-a-great-pm-5dd711a9f965">product managing</a> a team. In my new role these were more or less the same.</p><p>The only difference? The decisions changed from team-level decisions of ‘should this go into our MVP or not?’ or ‘how many users should we include in the beta test?’. Instead, they became choices that had a bigger impact — on the products and the people within the Clan e.g. ‘should this <strong>team</strong> stop work on this product months after starting but before we’ve launched it?’, or ‘should we move <strong>these people</strong> to different teams where their skills are needed?’.</p><p>These questions required a lot more time and care to come to a decision, especially the ones that weren’t easily reversible. Once I had a couple of these bigger ‘people-affecting’ decisions under my belt, it built my confidence that I could make them… and a bit more confidence I could do the actual role!</p><h4><strong>4. 🤓 Learning how to work through others</strong></h4><p>It became clear to me that doing a role like this well would be impossible if you don’t love working with people. Luckily for me, I do. But the past year has taught me a lot about building and leading teams.</p><p>No team starts out as ‘high performing’. It takes time, effort and trust between those within it, and space from those around it. My role includes a lot of coaching — working through tough problems with the Product Managers in my Clan, helping them get to decisions or chatting through tricky stakeholder conversations to get them to plan their next move, rather than jumping in and solving problems myself.</p><p>It was a relief to find how much satisfaction I got from other people doing well — whether that’s someone smashing an important meeting with stakeholders, celebrating with their team after launching a product, or recently having the pleasure of promoting two of my wonderful direct reports to Senior PMs 🌟! If I was still trying to ‘get things done’, then I would probably feel quite dissatisfied in my role. We often talk about PMs being the ‘people clapping the people being clapped’ vs getting the applause themselves, or being the ‘<a href="https://medium.com/all-things-product-management/product-manager-you-are-664d83ee702e">janitor</a>’.</p><p>My new leadership role involved being even more in the shadows a lot of the time — and being comfortable with the fact that sometimes a sign of you doing a really good job is no one knowing you were even involved!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t7L47V2f3o72dfUM" /><figcaption><em>Some of the Clan at a recent offsite, discussing a chaotic hospital roleplay.</em></figcaption></figure><h4><strong>5. 😌 Oh, I get it now, it’s a lot like PMing a team, but there are more teams</strong></h4><p>Once I had found my groove a bit more, had my first team, and had set up regular catch ups across the Clan with key people, I could reflect on how many of my Product Manager skills I could bring with me into this new stage in my career. The differences between team and Clan came down to there being <em>more</em>. More people to align, more inputs coming in for decision making, and more and higher stakes in the decisions I did have to make.</p><p>I have to recalibrate how much to collaborate vs when to lead and make a decision solo. My default as a PM was collaboration to the max and I ‘put my foot down’ incredibly sparingly. In the Clan Lead role, I had to quickly pick up a new skill: forging ahead with decisions that not everyone got to have a say in, or even agreed with.</p><p>Because there were so many more people (today there are 60 people in the Clan), there’s no way I could get everyone’s opinions on everything. In fact, it was actually my job to have opinions on things and follow through on them! The Clan needs to be able to trust me and my decisions. If I over-index on getting consensus from everyone then I’d never get anything done. This was the case when writing our Clan strategy that laid out how we were going to approach secondary care.</p><p>On the one hand, I had to become comfortable talking about our ‘bets’ vs being 100% sure that what we were doing would be successful. On the other hand, I had to get the right balance between obtaining inputs from stakeholders vs being confident and forging ahead.</p><p>This is definitely something I’m still working on, as I am with the whole role!. But writing this blog has been a really great chance to reflect on how far I’ve come in the last year, and how grateful I am to have been backed so fully by Accurx to grow into my new life in leadership. If you have a similar story of progression and various stages on the way to becoming confident, I’d love to hear it! <a href="https://twitter.com/Jennifer_Rose_S">@Jennifer_Rose_S</a></p><p><strong>Interested in joining our team on </strong><a href="https://medium.com/accurx/why-healthcare-is-a-communication-industry-18241a49461e"><strong>our mission</strong></a><strong>? Check out our </strong><a href="https://www.accurx.com/careers"><strong>careers page</strong></a><strong> for the latest opportunities.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2594bc98bb49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accurx/from-getting-it-done-to-making-it-happen-five-stages-on-the-road-to-becoming-accurx-s-2594bc98bb49">From ‘getting it done’ to ‘making it happen’ — five stages on the road to becoming accuRx’s…</a> was originally published in <a href="https://medium.com/accurx">Accurx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How accuRx changed the course of vaccine booking across the UK in less than 4 weeks]]></title>
            <link>https://medium.com/accurx/how-accurx-changed-the-course-of-vaccine-booking-across-the-uk-in-less-than-4-weeks-b2dbca10503d?source=rss-8722b792fd48------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2dbca10503d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[nhs]]></category>
            <dc:creator><![CDATA[Jennifer Rose]]></dc:creator>
            <pubDate>Thu, 29 Jul 2021 13:51:32 GMT</pubDate>
            <atom:updated>2021-07-29T13:51:32.272Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Jen Rose, Product Director at accuRx</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/0*CSOH9j5uRlz5Hatz" /></figure><h3>“Vaccine is go.”</h3><h4>Back in November, this message from our Head of Product Benji would change the course of me and my team’s life for the next few months.</h4><p>In early November, it became clear that GP practices were to play a key part in delivering vaccines, alongside mass vaccination centres, hospitals and pharmacies. Once the government announced that the first vaccines were ready to go, we started discussing how we could help at accuRx. We had already built a fantastic messaging service used by over 98% of GP practices in the UK, and had extensive knowledge of the GP network across the country, but hadn’t yet built anything focused specifically on vaccines.</p><p>Speaking to our GP users, it became clear that they were worried they wouldn’t be able to participate in the national vaccination programme without supporting tech to help them deliver it. If they didn’t have a way to make the rollout more efficient, they risked neglecting their existing commitments to patient care.</p><p>We knew we needed to act quickly if we were to have a real impact. GPs across the UK were working out how they would book and administer vaccines, so once we decided “vaccine is go,” we wasted no time. Later the same day we ran a session to map out what we needed to deliver in an initial version — weighing up getting something live quickly whilst making sure it would do the job necessary.</p><p>We thought the biggest problem would be getting the right people to the right vaccine centres, so we decided to build accuBook — a product for GPs to easily invite patients to book their COVID-19 vaccinations via SMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fghjZTTeMx27SvMQ" /><figcaption>Mapping our MVP (Minimum Viable Product)</figcaption></figure><h3>The Minimum Viable Product (MVP)</h3><p>We came out of this session with 5 user flows that would be necessary to build for our first iteration if we wanted to enable people to book themselves in from the start:</p><ol><li>Setting up vaccination clinics and calculating how many appointments would be available for patients to book into</li><li>Uploading a patient list and invite them in bulk to book in for their vaccines</li><li>Patients being able to book themselves in by choosing from available appointments</li><li>Manually booking patients without mobile numbers in, and following up with non-responders</li><li>Being able to see which patients are booked in for a given day to receive their vaccinations</li></ol><p>Having set ourselves a deadline of having a working version by Christmas, we built the above and shipped our MVP in less than 4 weeks. This meant we were in time for practices to use our software to invite and book in patients for their first vaccination deliveries.</p><p>We’ve <a href="https://medium.com/accurx/how-we-built-a-vaccine-appointment-solution-in-4-weeks-ee820ab9069f">previously written about</a> how this was possible from a technical point of view, so as the Product Manager of the team I thought I could compliment this by walking through a few of the other factors that made it possible.</p><ol><li><strong>We had a strong team</strong></li></ol><p>We care a lot about team structures at accuRx, and put a lot of time and effort into making them great. My product team had been working together for a few months prior to November, and had already built two products together; <a href="https://support.accurx.com/en/articles/4970829-patient-triage-resource-centre">Patient Triage</a> and <a href="https://support.accurx.com/en/articles/4970919-batch-messaging-appointment-reminders-resource-centre">Batch Messaging</a>. We had a high level of trust, a real drive to support our users, and the whole team was keen to take on this challenge together.</p><p><strong>2. We didn’t have to start from scratch</strong></p><p>Before we pivoted to the vaccines work, our team had recently finished building a product for batch messaging, allowing our GP users to upload a list of patients to send out a text or personalised link to them all at once.</p><p>Once we started scoping the accuBook MVP, we were able to re-use some of the elements we’d already built for vaccine flows, such as the mechanics of uploading a patient list, and sending invites to patients in bulk via SMS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jwd4c9tQpM77bwHH" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rp26sqT2WnvuSjjy" /><figcaption><em>You can see how similar the patient list upload screen is for both batch messaging (left) and for vaccine invites (right)</em></figcaption></figure><p>Our team had also worked on Patient Triage, an online consultation product which enables patients to fill in a simple form to tell their GP about a medical or admin query online, versus waiting on hold on the phone for ages in the morning about something non-urgent. One of the main flows we had built was the patient-facing flow where they filled in details about their query, which we then used as the basis for the patient booking flow for the vaccines product.</p><p>Aleena, one of the engineers in our team, had already put a lot of effort into making sure we had baked accessibility in from the start for Patient Triage, for example ensuring that the pages could be read by a screen reader. Being able to lift the accessibility features from elsewhere was a real advantage. You can read more about why accessibility is so important to us in <a href="https://medium.com/accurx/web-accessibility-and-applying-the-pour-principles-to-our-products-410310efb530">Aleena’s blog</a>.</p><p><strong>3. We had the necessary infrastructure</strong></p><p>At accuRx we have a real bias for action, and the phrase ‘ship early and often’ has always been a principle our product teams have lived by. This meant we didn’t have to try and come up with a way in which engineers could be working on similar parts of the code in parallel to each other. We already had processes in place to be able to release sometimes multiple times a day, as our <a href="https://www.notion.so/accurx/PUBLIC-Product-improvements-Vaccines-b53149e6998046ca919e11c2aa01c7cd">public release notes</a> show.</p><p>‘Feature flags’ were also already in common use. This meant our engineers could be working and testing new things without fear of something being released too soon if someone else wanted to push a change live for users.</p><p><strong>4. We made sure our ways of working pivoted with us</strong></p><p>One of the key things that helped us build so quickly was close-knit communication. We were building the 5 flows I mentioned earlier in parallel, so there was a lot to keep track of.</p><p>Mike (our tech lead) and I already had a great working relationship… a good thing, because it was about to be put to the test! From the day after the story mapping session, we moved to daily syncs every morning, to check our progress, which was a great way to make sure we were on top of all of the moving parts.</p><p>We also moved to having daily goals within the team, vs our normal weekly ones. This helped keep everyone focused on the most important thing to do that day. Mike and I also continuously checked in on our ways of working and what we could be doing better — an example here below of us reflecting on an unproductive team planning session and realising it would be better to do individual check ins with the engineers to save everyone else time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y906qiOcIgQhSpM1" /></figure><p><strong>5. We knew our users REALLY well</strong></p><p>A really tricky part of building the accuBook MVP was that no one had run a COVID-19 vaccination clinic yet — our aim was to get the MVP live before they had to invite their first patients. Therefore it made our usual process of going out and researching this with our users really tricky. We still did it, but some of the first conversations we had before anyone had run a vaccination clinic went a bit like this:</p><blockquote><strong>“When you’re setting up your clinics, how far in advance are you going to know how much vaccine you’ll get”</strong></blockquote><blockquote><em>“We’re not sure yet, we’re getting told soon”.</em></blockquote><blockquote><strong>“How are you thinking about your DNA (did not attend) rate and ensuring vaccines aren’t wasted?”</strong></blockquote><blockquote><em>“We have no idea what the DNA rate will be yet. We’re thinking low? We’ll copy what we did for the flu and learn as we go”.</em></blockquote><p>This meant we had to make a LOT of assumptions at the beginning. It was important to make sure we were documenting these, so that we could go back once we (and primary care at large) knew more about some of the specifics and amend what we were planning to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5ESELwG9gD_frZfU" /><figcaption><em>A document tracking our assumptions — as we learned more we either ticked them off, marked them as incorrect, or deferred them until we had more info.</em></figcaption></figure><p><strong>6. We became comfortable with ‘regret work’</strong></p><p>A vaccination programme of this scale hadn’t been carried out before, so we had to enter into building the product aware and comfortable with the fact that we would have to iterate on what we released. In practice, this sometimes meant iterating within days after setting features live, due to the real-time feedback we were getting from our wonderful, engaged users.</p><p>We also had to be OK with the fact that some parts of the product may well have to be changed or scrapped depending on the ever changing nature of the vaccination programme and how little time we had to research beforehand. It wasn’t easy, but going in with this mentality made it easier to make these decisions as they came up.</p><p>And we did it! In just under 4 weeks, we went from ‘<strong>go</strong>’ to getting something live to help practices get their patients booked in a lot quicker than using pen and paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tuPGOgLSL0F8S2Ls" /></figure><p>None of the above would have mattered if it wasn’t for how hard the team were willing to work. Everyone put in late nights and gave up their weekends because they cared so much about delivering something that would make a difference to the pandemic and the healthcare of millions. It was a really challenging time for everyone involved, and we’re still feeling the after-effects as a company of that ‘<strong>go</strong>’ decision.</p><p>However, I think I speak for the whole team when I say that we’re all incredibly proud of what we achieved, and humbled at how we were able to help out our users when they needed it the most.</p><p>To date, over 21 million vaccines have been booked in and managed through accuBook, which is over ⅓ of all vaccines in England. Over 5,000 GP practices have used accuBook and the busiest days have seen 300,000 bookings. We’re proud that even amongst the over 80s cohort, an average of 70% booked their vaccine appointments through our mobile invites.</p><p>While we wouldn’t usually work at such pace, and we’re always thinking about how we can produce our best work to help our users and their patients without burning out our own teams, we certainly learnt an awful lot throughout this experience!</p><p><em>A couple of examples of our lovely users’ experiences with accuBook — we wouldn’t be here without their ongoing feedback and support:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KCSVZiuIFa6w92ud" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V_q_4CyaQAoqhrOg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2dbca10503d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/accurx/how-accurx-changed-the-course-of-vaccine-booking-across-the-uk-in-less-than-4-weeks-b2dbca10503d">How accuRx changed the course of vaccine booking across the UK in less than 4 weeks</a> was originally published in <a href="https://medium.com/accurx">Accurx</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>