Andrew Wood

Tags show how I was involved. Led: I owned the outcome. Co-led: I owned it jointly. Contributed: I was a substantial part of a shared result. Supported: I helped others deliver.

  1. Six Degrees2022-05 to present

    Head of Technical Delivery

    Case studies: Proactive problem management across a managed customer base, Ransomware recovery for a national distribution business

    I lead a function created in 2022 when managed services was split in two, covering second and third line Cloud, Data, Connectivity, Unified Comms and Workplace support. The team spans onshore and offshore locations, with one layer of team leads.

    • Led Converged separate technical teams into one blended operating model while holding live SLAs
    • Led Designed and embedded a proactive problem management framework, applied across a large managed customer base, with an engineer kept in the loop where automation cannot decide
    • Co-led Worked with Professional Services leadership to formalise how customer requests move between support and projects, writing the principles and building an AI-assisted triage workflow with decisions kept with people
    • Led Proof of concept, piloted, not rolled out Designed and built a knowledge-base pipeline using Python and AI-assisted coding against Cosmos DB and Azure AI Search
    • Led Out-of-hours major incident manager and senior escalation point, and technical lead for zero-day assessments on the vulnerability management committee
    • Contributed Championed proactive automation that contributed to a steady run of improvements and a reduction in major outages
    • Led Mentored engineers across complex hybrid platforms and built a culture of psychological safety, so people feel able to learn, ask and try things without fear
    • Contributed Contributed to bid responses and service design, aligning technical architecture proposals with commercial strategy
    • Led Recognised with Above and Beyond awards and company all-hands mentions for leadership in vulnerability management and incident response
    • Contributed Helping drive a sustained improvement in customer satisfaction scores
    • Lesson: People can accept a hard decision they understand. Broken promises and shifting direction are what lose them.
    • Skill: The value of disagree and commit. Most people can disagree with a decision and still get behind it if they can see where it leads, so establishing the bigger picture early is key. Without it, decisions get reopened, direction keeps changing and trust goes fast.
    • Lesson: Successful backups and successful recovery are not the same thing
    • Lesson: I naturally look for the best in people and try to help them improve. I've also learnt that when someone is in the wrong role, or the organisation has moved on and they haven't, you have to move quickly. Form has to follow function.
    • Skill: Get the data somewhere trustworthy first, then automate on top of it
    • Lesson: Governing AI is less about restricting people than giving them safe tools that are easier to use than the alternatives
    • AI with oversight
    • Automation
    • Commercial strategy
    • Cyber recovery
    • Leadership
    • Major incident management
    • Operating model
    • People and mentoring
    • Problem management
    • Security
    • Service delivery
    • Service design
  2. Six Degrees2021-05 to 2022-05

    Head of Managed Services

    I brought legacy technical teams together into one proactive managed services operating model, moving towards ITIL-aligned governance and modern monitoring and cross-skilling engineers for hybrid infrastructure.

    • Co-led Provided technical leadership through the consolidation of multiple monitoring tools onto LogicMonitor, driving migration completion and the retirement of legacy platforms
    • Led Kept hands-on accountability for tier-three major incident escalations through a team realignment to protect live SLAs
    • Contributed Provided technical evidence supporting the company's Microsoft Azure Expert MSP status (2021)
    • Led Harmonised the morning stand-ups across teams around common goals, and refreshed objectives so they linked to wider organisational goals
    • Skill: Moving to managing managers meant delegating more and coaching each person differently. Some were strongest on the people side and others on delivery, so I brought those strengths together and encouraged people to learn from each other across teams.
    • Lesson: Teams can keep their own routines as long as they share the same goals
    • Lesson: Data and objectives have to line up, with dashboards to work from. Not having them was what made the case for transforming our monitoring.
    • Lesson: Accurate monitoring can make a service look worse before it gets better, because it exposes what the old tools were hiding
    • Cloud
    • Leadership
    • Major incident management
    • Monitoring
    • Operating model
    • Platform transformation
    • Service delivery
  3. Six Degrees2020-01 to 2021-05

    Centre of Excellence Manager, Secure and Public Sector

    I ran technical escalations and support for secure public sector cloud environments under UK OFFICIAL and NCSC guidance, including secure VDI on VMware Horizon, VMware vCloud and PSN networks, bridging platform build and live service.

    • Led Built 24x7 hypercare monitoring for critical national public sector platforms through peak periods
    • Led Owned technical remediation for penetration testing, ITHC, ISO 27001 and SOC 2 for central government and secure clients
    • Led Hardened Linux and Solaris base images against CIS benchmarks, and designed secure bridging and proxy architecture later signed off through external accreditation
    • Co-led Rebuilt load-balancer configuration and helped restore service during a prolonged hosting outage on end-of-life infrastructure
    • Lesson: We had built our internal platforms close to zero trust before 2020, so moving to remote working was the easy part. Managing people remotely was the hardest.
    • Lesson: A workaround under pressure has to be checked against every tenant on shared infrastructure
    • Skill: Working to external accreditation, from ISO 27001 and SOC 2 to ITHC and NCSC guidance
    • Engineering
    • Major incident management
    • Regulated environments
    • Security
    • Service transition
  4. Carrenza2017-02 to 2020-01

    Service Desk Manager

    I ran the consolidated service desk through Carrenza's integration into Six Degrees, as the main technical escalation point across networking, servers and VMware. That included peak-load support for major ecommerce sites and televised charity events.

    • Led Migrated the service desk onto ServiceNow during the integration, carrying across customer contacts, SLAs and the knowledge base
    • Led Sustained SLA performance through the integration into Six Degrees
    • Lesson: Bringing a small, scrappy team into a larger, more structured organisation means keeping what made them good while taking on the structure
    • Skill: High-traffic events are won in the preparation. We ran 24/7 cover for days at a time without a dedicated 24/7 team, so everyone needed a runbook, a shift they had agreed to, the right contacts and regular checkpoints. Any new tool or third party went into that plan too, because that's often where the surprises came from.
    • ITSM
    • Service delivery
    • Service transition
  5. Carrenza2016-03 to 2017-02

    Service Desk Team Lead

    I was a technical escalation point across customer estates and mentored junior engineers, helping turn the support function into a structured ITIL operation during rapid client onboarding. Carrenza was acquired by Six Degrees in 2016.

    • Contributed Part of the technical rollout and customer planning for Jira Service Management, which let the team measure SLAs for the first time
    • Led Built a billing API and a status dashboard so a key client could see their usage, costs and environment health for themselves
    • Lesson: Once we measured SLAs, the service became more than a list of tickets. People started talking about the service, not just the technology.
    • Skill: Supporting live televised charity nights, from the build to watching the systems through the night
    • Engineering
    • ITSM
    • Monitoring
    • Service delivery
  6. Carrenza2013-09 to 2016-03

    Systems Engineer

    I joined as a graduate systems engineer, working hands-on across customer VMware, Linux and Windows estates.

    • Led Managed configuration and orchestration with Chef and Ansible across customer estates
    • Contributed Rebuilt our Nagios instances as part of a wider hardening project, moving to SNMPv3 and splitting a central instance into isolated ones without losing a single view of alerting, and saw the rebuild through to completion
    • Contributed Evaluated open-source monitoring alternatives including Zabbix and Icinga, built a proof of concept, and settled on Thruk with the Livestatus API as one front end across our existing Nagios instances
    • Contributed Helped a customer's website scale for big launches using configuration management, after it buckled under peak load in my first weeks on call
    • Lesson: My first big outage on call taught me when to ask for help, how to keep a customer updated under pressure, and what can safely wait until Monday
    • Lesson: Early cloud taught me that customers should pay for capacity only when they need it. Once they could deploy through an API themselves, a managed service could be layered to suit each one, from infrastructure only to fully managed.
    • Skill: From painful experience, always take a dated backup before any change. Then compare it with the result and write the change back into configuration management code like Chef or Ansible, so the next run doesn't undo it.
    • Skill: Designing for predictable results through idempotency, which I still apply well beyond servers
    • Lesson: Pragmatism beats complexity. A light open-source front end gave us one view of every monitoring instance without a costly rebuild.
    • Skill: Linux at scale and VMware, learnt on the job from generous senior engineers
    • Lesson: You get out what you put in, and it's always better to work in a great team
    • Automation
    • Engineering
    • Monitoring
    • Platform transformation
    • Security
  7. University of East Anglia2009 – 2013

    Bachelor of Science (BSc), Computer Science

    I studied Computer Science before joining Carrenza as a graduate systems engineer in 2013.

Case studies

Case studies and technical projects across managed services and infrastructure.

Insights and thoughts

Notes on running managed services, from the operations side.

  • Insights and thoughts

    AI policy

    A policy written in 2023 for basic chatbots has very little to say about an agent that can read a ticket and query a monitoring API. So it says no.

    Read the post

  • Insights and thoughts

    The short letter

    AI has made the long letter free. The short one still costs what it always did, and now the reader pays for the difference.

    Read the post

  • Insights and thoughts

    Ticket data

    Ticket data is a good record of the work that fits neatly into a ticket. A lot of what keeps a service running doesn't.

    Read the post

  • Insights and thoughts

    The wrong targets

    A team can hit every target it's given and still be measuring the wrong things. Goodhart's Law applies to service desks too.

    Read the post

  • Insights and thoughts

    Automation and headcount

    Pitch automation as a way to need fewer engineers and you lose the people who know where the real problems are.

    Read the post

  • Insights and thoughts

    Patching when AI finds the bugs first

    Bug discovery has been industrialised. A monthly patch cycle behind a slow approval queue was built for a slower world.

    Read the post

  • Insights and thoughts

    Building with what you already have

    You probably don't need a new platform to start using AI in service governance. You need the data you already have and someone willing to wire it together.

    Read the post

  • Insights and thoughts

    Breadth

    I don't have a wall of vendor certifications. I have a long career following problems from the routing table to the contract to the boardroom.

    Read the post

  • Insights and thoughts

    Recruitment

    A hiring freeze that lasts one quarter can leave an operational team short for most of a year. Budget for the recovery, not just the saving.

    Read the post

  • Insights and thoughts

    When the plumbing makes the Ten O'Clock News

    After every major outage the instinct is to buy more redundancy. For most mid-market businesses, the commercial case has to be made before the technical one.

    Read the post

  • Insights and thoughts

    What railways got right about change control

    A checkbox in a change ticket only proves that someone intended to be careful. An interlock is what stops the outage.

    Read the post

  • Insights and thoughts

    Rewarding the quiet

    In managed services, a flat ticket graph can leave a finance director wondering what they're paying for. Service reviews should make prevention visible.

    Read the post

  • Insights and thoughts

    Where managed services is heading

    Managed services is splitting in two: low-margin generalists selling reactive tickets, and specialist partners selling operational resilience.

    Read the post