product manager, degree apprentice graduate, open source advocate, bookworm, flautist, heavy-metal fan | views are my own

  • TechWomen100 & South Coast Tech and Innovation Awards

    What a brilliant few days. I have been fortunate enough to be shortlisted for the South Coast Tech and Innovation Awards for the Rising Star of the Year category and I have won the TechWomen100 individual award.

    The South Coast awards were held in the Leonardo Royal in Southampton on Thursday 15th October, and I turned up for the drinks reception at about 6.15pm before the awards started at 7pm. I didn’t know anybody but Lauren, the lady that runs Women in Tech Hampshire, so Lauren introduced me to a few people and off I went. My table included LABL.IT, Lloyds Bank, and EntustIT which was interesting, totally different types of companies that I would usually deal with. Jason Bradbury announced the awards and had a brilliant skit that involved re-creating a rollercoaster that mimics Moores Law on Minecraft and then giving us a potted history of computing in the time it took him to build it. Absolutely hilarious and incredibly niche which I enjoyed.

    Unfortunately, I didn’t win the category, but I did have a great evening – the company was brilliant, the food was great, and the laughs I got around my table were well worth the travel. I’m proud to have gotten to the shortlist nonetheless.

    On Friday 16th October, I went to the TechWomen100 awards in Mansion House in London. I went with Emma Dawson, also an IBMer, and it was great to spend time with her. We turned up at 12pm and the reception had a large queue around the corner of the building. The drinks reception was great – a choir sung in the background, the Apps for Good charity were taking raffle tickets, and we were able to get some photos earlier before the ceremony. It was highly packed and busy though, with the beautiful chandeliers of the house.

    The awards ceremony was in one of the main halls, with over 300 people in the audience. We had Julia Streets as the M.C., and then Vanessa Vallely as the founder of WeAreTechWomen which have organised the awards. We then had a few speeches before calling up the groups of women which was great to see. We had people giving the awards from all sorts of companies – PWC, KPMG, HSBC, Lloyds Bank, Accenture. It was great!

    I feel totally overwhelmed with how excellent the entire experience was, to see all the inspirational women there and because you had no idea why they were there, it was great to see the Champion of the Year and the Editors Choice of the Year too which were more individual awards. There was just a lot of warmth and celebration coming from the end of Women in Tech week and a lot of discussion about how we’re not moving quickly enough on bringing diverse talent into IT. We have more work to do.

    What a brilliant couple of days. I’m incredibly fortunate that it feels like a brilliant end to this chapter. I’m excited about what lies ahead! Onwards and upwards.

  • The Organisation Behind the Organisation

    It was deep into winter, and dark on my drive home. I’d finished another days’ work, leaving late due to a presentation up to my senior management for a cross-departmental project I was running. As I was driving home, avoiding the blinding lights of the oncoming cars, I was pondering whether I’d been influencing the right people. The radio playing in the background, and I was replaying a presentation I had made to the steering committee in my head. The steering committee was formed of the senior executives, both business and technical, across the large department to keep abreast of the latest technology changes. This was the fourth update I’d given since the summer and despite all the presentations, status reports, and alignment meetings, the project still felt stuck. As I drove home, I wondered whether I was spending time with the right people. 

    We were struggling to gain momentum, the project was across 4 different teams, each with competing priorities, and I thought that the best way to get the teams together was through the management. I was under the impression that authority through management was the best way to go. The next week, after spending half an hour attempting to find a slot across three time zones and calendars that were packed with half an hour meetings, I found a slot for five managers and myself to get together to discuss alignment. The agenda sent out beforehand, and I’d personally reached out to all attendees to ensure they’re aligned before going in. The meeting was a success on paper. Everyone agreed with the direction, committed their teams, and supported the objectives. Yet when I left the room, very little had actually changed. I still owned the roadmap, the communication plan, the alignment across teams, and the challenge of turning agreement into action.

    I was under the impression that management would be the ones to help me drive this forward. In fact, they were the people that were accountable for the results, not responsible for creating the day-to-day momentum. The managers were accountable for their products roadmap – delivery of certain features for their customers, new versions, making sure their bosses were happy. They weren’t going to help me influence the people working on the project to get the cross-departmental deliveries across the line. I then hit a crossroads. How was I to influence those in the project if their managers were generally supportive, but not there to provide direct guidance? How was I supposed to drive a project where I needed to influence the team, not deliver through authority?

    I began to do a few things. The first, being that I went to the technical leadership, we had several alignment documents and meetings to discuss and agree the higher-level strategy. Secondly, I began to build relationships across the delivery team and those that were key stakeholders in getting the project written and delivered. I spent time with them individually, ensuring that the team were all aligned and happy. Thirdly, I began to shift my thinking from ‘how do I use authority to get what I need’ to ‘how can I influence the hidden network to get this achieved’. 

    That was something I hadn’t realised. There are two organisational charts in a company or group. There’s the official organisational chart – individual contributors, first-line managers, and then up to the CEO. That type of authority was all centred around the specific outcomes that the team were accountable for. The second, you discover over time. The architect that everybody trusts, the engineer who knows where the bodies are buried, the product manager who connects teams, the person everyone calls before making a decision.

    I had assumed that if I found the reporting line, then I would find how decisions were made. What surprised me was that the most important people in the room were rarely the ones with the biggest titles. It would be the longest-serving employee that has deep and in-depth experience into how to solve a problem, the connector who knows the right person to solve a difficult technical problem. Alternatively, it could be the person that everyone stops and listens to. The engineer that hasn’t got a fancy title but has command of the room in a meeting.

    As we approached the first beta release, the project gradually found its feet. Not because I became more senior, gained more authority, or found the perfect steering committee presentation, but because I learnt where influence actually lived. The deadlines only started to become real when the people doing the work believed in them. Momentum came from building relationships across the team, understanding different priorities, and creating enough trust for people to challenge the plan rather than quietly disagreeing with it. I also discovered that driving a project wasn’t about telling people what to do, it was about creating direction, removing obstacles, and giving the team confidence that the work mattered.

    Early in my career, I assumed that if I could understand the reporting line, then I would understand how decisions were made. What I eventually discovered was that reporting lines explain accountability. Relationships explain influence. The organisations that move fastest understand the difference. The managers were responsible for outcomes, alignment, and ensuring the right decisions were made. The momentum, however, came from the architects, engineers, product managers, and connectors who carried ideas between teams and turned agreement into action. Once I understood that distinction, the project became much easier to navigate.

  • Reflections on the First Term as a Degree Apprentice

    It’s September, and a time where many apprentices will be facing their first term, so I thought this blog would be timely. Before starting my degree apprenticeship, I had no idea what university would be like for a professional. I had always assumed university was for 18-year-olds, until I walked into the University of Winchester at 25, ready to start a four-year degree. Our cohort of degree apprentices, around 15 of us, sat in the large lecture room of the old business school with the head of the department, dark wood panelled walls lining the ornate carvings and floor to ceiling windows surrounding us. We were sat on individual exam tables, and I immediately had a flashback to my GCSEs at 16 sitting in a cold exam room.

    “Time is moving anyway, so you might as well do something useful with it,” the head of department stated matter-of-factly as she wrapped up her induction. I looked around, with a mix of ages around me, all thinking the same thing – what have we got ourselves signed up for. 

    I was overwhelmed, working a demanding role within mergers and acquisitions to deliver short-term projects, and a day a week out to attend class and write essays was overwhelming. Within the first year, Mondays were our university days, so we all attended class from 9am to 6pm with an hour break for lunch in the university canteen. We studied modules from marketing, HR, business functions, and academic and professional skills. The workload was intense, with our first term deadline 12 weeks from sitting in the lecture hall, with three essays due, each of around 3,000 words. 

    The structure of class would be a mix of lectures (sitting in a room of 300 students all listening to a lecturer for an hour talk through academic content on that module) and seminars (classroom sized groups of exercises and discussion together on the content of the weeks’ lecture). As a normal student, these classes would be spread over the entire week to give breathing room for studying, working, or relaxing. However, as a degree apprentice, this was crammed into one day – so a lecture might be happening at 3pm, with a seminar on the topic at 11am. The intensity meant that we had no time during the day to write essays or read the assigned reading. Tasks like that were done outside of the university halls, crammed on tables at Starbucks or on the sofa at home on the weekends.

    One of the most memorable modules that term was the academic and professional skills module, which involved a mix of academic learning and reflective essays. The module was designed to be a safe introduction to academic skills for students – the assignment at the end of term being three things: an essay on a subject of your choice, a reflective essay for a book review, and a reflective essay for the first semester. The lecturer taught us about academic referencing, report writing, academic reflection models, and critical thinking. As a mature student, I felt like I was starting from zero, having no idea how write an essay – work had never required that I read an academic report.

    We could choose a subject for our report, and the quirk of a degree apprenticeship meant that it had to relate to our workplace (or for other reports, directly about our workplace), and I chose whether COVID impacted workers mental health. I was still in my infancy as a student, with most of my references being websites and clearly missing the point of an academic paper which I developed over the next three years.

    The reflective essays were easier for me, being a naturally introspective person, but reading back, they were probably too honest for a university lecturer. A particular note being that I commented on my lack of confidence and perfectionism as a barrier to writing essays, and I combated that through breaking it down into smaller chunks.

    The university gave us plenty of prompts and guidance, with the module handbooks including detailed information on how to gain a first, what they expected in the report structure, and even hints on what to include in the essay. As a mature student, my researching and writing muscles hadn’t been exercised for 7 years, and so it did take most of the first year to understand what the lecturers were after.

    Most of our lecturers and seminars were taken with other university students paying for their degree, which felt odd when I was getting my education for free through my employer. However, we did have modules that were different. For example, in the first term we had work based studies modules. These were designed to focus on how our role in the business contributed to business success, personal development plans, reflective essays on our workplace, and analysis on our department. It was a way to bridge the academic and workplace worlds that felt very far apart. We had at least one of these modules in each academic term. 

    These modules were part of the criteria for the apprenticeship, and it meant we were asked to write reflective diaries and goals, which was a lot to ask when you were doing a full-time job as a mature student. My day-to-day role was demanding and I was a professional, not an apprentice learning to adapt to the workplace which made the process significantly harder. I was dealing with acquisition founders, developers, and senior executives daily and the stark contrast to a university did cause my head to spin at times.

    The largest challenge that we had was that I began my degree in 2020, during the height of the COVID lockdowns. This meant that I was frequently in online classes and unsure whether university was open in person, but that got easier as the course went on.

    Looking back, the first term felt overwhelming. The essays were harder than expected, balancing work and study was exhausting, and I often felt like I was playing catch up academically. However, by the second term things began to get easier. The challenge wasn’t intelligence, it was adapting to a different way of thinking. 

  • Organising the Agenda

    What happens when you get a group of people together to organise a conference? Well, it turns out it’s mostly a mix of Diet Coke, pastries, and long table with keyboard tapping being heard faintly in the background.

    The GS UK conference committee got together this week to organise the conference for their flagship event in November 2026. I’ve been part of the committee since 2023, and it’s been a blast. The conference is unlike anything else – a group of highly diverse individuals that are passionate about all things IT – observability, security like ACF2 and RACF, operating systems like TPF and z/OS, databases from DB2 to Adabas, and AI covering MCP, agents, and LLMs. The platform is growing rapidly, and the conference is having to adapt at a rapid rate to accomodate.

    When I joined, the process for submitting papers was to email each individual track with your submissions, meaning it felt like an underground network of submissions with a small subset of people submitting that knew. After a couple of years of testing the waters, we have finally moved to Sessionize, a way to view all the conference submissions in the same place – the same is used for conferences such as the Linux Foundation. Bringing change to an organisation that has been working in a particular way for many years has been difficult – we have been through education sessions, video walkthroughs, and emails to make sure that we were all rowing in the right direction.

    There was something oddly satisfying about seeing all the submissions in one place. For years, conference planning had felt a little bit like everyone disappearing into separate rooms, emerging months later with a finished agenda and hoping it all fitted together. Suddenly we could see everything. The good ideas, the accidental duplication, the emerging themes, and occasionally two track chairs realising they had both accepted almost exactly the same session. It turns out visibility is a wonderful thing, even if it occasionally means discovering you’ve all had the same idea at the same time.

    This year, we decided to get together as a group and go through the agenda together – going through each stream and discussing the agenda as a whole, looking at the clashes, and working as a whole event to ensure that we are doing the same thing together. What I found particularly interesting, was that as a group, we have slowly exposed how each stream thinks about how their stream is being put together. Looking around the room, it struck me that everyone had arrived with the best intentions for their own area. Nobody was deliberately creating clashes between sessions or gaps in the agenda. Yet when you put twenty passionate people together, each optimising for their own audience, somebody has to step back and optimise for the whole conference.

    A stream chair cares about the depth and technical credibility, but the attendee cares about a coherent experience, enough variety, and breadth covering beginners through to experts.

    There is a hidden depth to conference organisation. On the surface it’s about ensuring that the lunch is served, keynote sessions are delivered, the slide content, there are no hiccups with the sessions. Below the surface, it’s balancing the agenda across all tracks and days, difficult decisions between one speaker and another, and a trade off between streams. Like many organisational changes, the tooling change from email to Sessionize wasn’t about the technology, it was about helping people understand why we were changing, and how to bring them along for the journey. This took significantly longer than first anticipated.

    The day was brilliant, and I felt like we were more like a team than I’ve ever seen. As I drove home, I found myself talking to Joe, less about the tooling and more about the people. A conference agenda is ultimately just a reflection of the community behind it. The technology helps, the process helps, but neither replaces a room full of people who care deeply about creating something worthwhile. Looking around the room, listening to debates about session clashes, audience levels, and emerging topics, I was reminded why I’ve stayed involved. The best conferences aren’t built by software or committees. They’re built by communities willing to spend a day eating pastries, drinking Diet Coke, and arguing passionately about what their peers need to learn next.

    I’ll look forward to the conference in November!

  • Mentors, Networks, and the Space Between

    My role is broad. I’ve spanned over seven projects around the mainframe in the last four years, from enterprise integration, transaction processing, and acquisitions. This has required a growth mindset, bouncing between teams, executives, and context. The trend has followed me through my entire career – different roles and accounts in Consulting, different acquisitions in my technical lead role – a strength of mine being the breadth and variety of the projects I’m involved in.

    This level of volatility in my career has meant that the people I surround myself with become incredibly important. Reminders like my long-term career strategy, settling my emotional volatility, and listening to help me problem solve issues that crop up. I vividly remember being in my early twenties and listening to an executive all hands making an off-handed comment about having mentors in and out of work to talk to, and I was confused. How does someone get a mentor outside of the company I’m employed by? Where do I find one?

    This was reinforced by the book Lean In by Sheryl Sandberg, which I’m aware is a controversial book, whereby she tells a story about a woman that repeatedly asks her for advice over a series of months, and then one day turned around and asked Sheryl how to find a mentor. Sheryl reminded her that mentoring isn’t always about a formal relationship between two people every month with strict boundaries, it can be asking for help and learning from each other over time.

    Networking, to me, is a dirty word. Overused, underexplained, and setting younger people up with the daunting task of working out how to game the system. How can I meet as many people as possible? How can I collect as many people and mentors as possible? What does it even mean to have a network? 

    When I first joined IBM, within a few months I became incredibly curious. In my lunch, I would scour the intranet for information – what companies did we work with? What jobs did people do? What sectors do we work with? I stumbled upon Richard, who at the time worked in media and television, we met over the phone as I was a keen apprentice he replied to my note quickly. I had no understanding for how senior he was, and we began talking about all sorts – what I spent my time doing, how I was enjoying working in IBM, and learning about IBM’s strategy at the time. Richard remained a mentor of mine throughout the next decade, until he retired a few years ago and we try to keep in touch when we can.

    Another example is around 2 years later, my third role in IBM and I had a personal development plan review with my second line manager, I had a list of 15 people I wanted to speak to about areas of the business I was interested in, articles to read, books to read. I remember his quote “you’re overboiling the ocean here, Louisa, you could scale it down slightly,” and I scoffed, confused as to why he thought that was too many. I was ambitious, and not afraid to cast my net wide.

    Mentoring isn’t built through structure, it’s built through repeated moments of curiosity and connection.

    At the time, I was an apprentice and I had no idea how many doors that would open, and that what I was building was a personal brand and a network. I was building a rolodex of people to call when I needed help choosing my next role, deciding on how to approach a problem, understanding the business strategy. Although I never felt like I had enough. Looking back, I now believe that feeling was due to the hype around a network and nobody truly describing what it meant. 

    To me, there is a difference between networking and mentoring. For example, I have mentors that have been by my side for over a decade, seeing me through management changes, house moves, marriage, and in turn, I help them navigate their own challenges, even if they are generally much senior than I am. I have also had mentors that come and go, I see them once in a blue moon when we work on a project together, it’s like working with an old friend, and then they go back to their day job. Some mentors which I meet monthly, quarterly, we text when there’s a problem or we want to get a coffee, or some mentors, I see in the corridor or when they get a coffee from the coffee shop near my office. It’s a flexible relationship and one that for me, has turned into genuine friendships.

    Networking however, is the ability to meet people and build knowledge, understanding, or context.

    For example, now I’ve been to GS UK for a while, I have a network within the conference. I know many speakers by sight or name, I build a friendship with those I see regularly, like the committee, and I seem to have an amazing capacity to meet one person, and for them to introduce me to twenty other people. Networking is about knowing how an organisation or group of people operate, having the interest to understand who is friends with who, how decisions are made, and often, networks aren’t always useful, they are people that you meet and maintain relationships with. It doesn’t mean that you would have every person in your network as a mentor, that would be crazy, but it means you have a group of people that you know and that provide you a range of opinions, thoughts, and perspectives.

    Coming back to my original note, even though my role is broad, and my network has morphed and changed, my mentors have come and gone, I see it as a privilege to have spent time with those that have guided me in one way or another. I’ve been through a lot of loss from mentors leaving roles or companies, and I’ve found that relationships and friendships morph to fit the circumstances. A mentor that I would never text, we now send each other articles and exchange opinions regularly, however, others have drifted away.

    I spend time and energy keeping those relationships that mean something, and often, I don’t want anything from them because that isn’t my main goal. Go into mentoring with curiosity, interest, and the desire to find out more. Don’t let the ‘we haven’t got a monthly calendar invite’ or ‘I don’t know when I’ll next see them’ stop you from having a crew around you to help when you’ve broken down.