Quality & delivery · E.ON Next

Turning an undervalued QA practice into a function 11 product teams trusted

rating from 24 colleagues in the function's 360 review
4.71 / 5
product teams covered
11
leaders promoted to run it day to day
2

The situation

E.ON Next's digital team had 11 product teams and a QA practice that was undervalued, and often seen as the thing slowing releases down.

The problem

  • Bugs reached customers, and QA was blamed for slow releases rather than trusted to prevent them.
  • Good testers had nowhere to grow, standards varied team by team, and a bug a product manager chose not to fix had no route to escalate.

What I did

  • Built the backbone: a five-level career path with a management and a specialist track, job descriptions, a skills matrix and a hiring pack, with AI skills expected at every level.
  • Promoted a QA engineering manager and a principal engineer to run it day to day.
  • Set the rules that hold the line: mandatory test sign-off before major releases, an escalation route for serious bugs, and a weekly owner for every customer-facing issue.
  • Modernised test automation onto Playwright and Appium, with visual regression in the pipeline.
  • Stood up QA from nothing for the connected-home app, which controls real hardware in customers' homes (EV chargers, solar, batteries, heat pumps): a six-layer testing strategy from unit tests to real hardware, signed off by leadership and won from sceptical engineers with evidence rather than authority.
  • Was then asked by the go-to-market director to explore scaling the model beyond the digital team.
A QA function that is trusted rather than tolerated.

Contact

Got a problem like this?

A few lines is enough. Every enquiry comes straight to me, and you’ll get a considered reply: a straight answer, a question or two, or an honest “I’m not the right fit”.

Prefer email? hello@firstniyyah.com