The situation
New login security controls were being accelerated after the platform's security chief raised concerns about automated attacks on customer accounts, just before E.ON Next's highest-demand period of the year.
The problem
- Pressure to ship came from the security side too: the threat was legitimate, and so was the risk of the fix itself, which could lock real customers out of their energy accounts in winter.
What I did
- Ran a QA and data-driven readiness check that found regressions in features already signed off, and clear risks to customers.
- Presented the evidence to senior stakeholders, which led to a decision to pause until the new year.
- Agreed four interim safeguards instead (firewall rules, rate limiting, monitoring and incident readiness), so security wasn't compromised while the fix was done properly.
Sometimes the most valuable QA call is 'not yet', made with evidence and a plan B.