Thomas Barnes

Thomas Barnes

Head of Observability Global Payments
Thomas Barnes

Thomas Barnes is Head of Observability at Global Payments, where he leads the strategy for ensuring reliability, transparency, and insight across complex, distributed systems. A self described lazy engineer who would rather automate away toil than repeat the same task twice, Thomas has built a career on finding smarter, simpler ways to make every other engineer just as lazy as he is. Before joining Global Payments, he worked in automation consultancy and later served as an SRE Engineering Lead at a major UK bank - an experience that taught him that observability isn’t just about keeping systems reliable; it’s about giving teams the data they need to focus on what actually matters to customers. When he’s not evangelising metrics, traces, and logs, Thomas is usually figuring out how to convince finance teams that reliability isn’t a cost centre - it’s an investment that pays for itself.

CONFERENCE DAY 2

11:00 AM Presentation: The Most Expensive Question in Incident Management: "Who Knows This?"

Payments don't pause while 90 people pile onto a bridge to work out who owns a failure. Traditional L1 triage is an expensive bottleneck which consumes valuable engineering capacity where operations and engineers piece together what happened, who is affected, and who needs to respond. Meanwhile, customers are feeling the impact.

We're using AI to change that: turning observability data, operational knowledge, and business context into actionable incident intelligence before the bridge even starts.

  • Ending the guessing game: Using AI to map service dependencies, identify affected customers, and establish the likely blast radius in seconds
  • Replacing the bridge: Bringing together telemetry, historical incidents, ownership, and operational knowledge to give responders evidence-based hypotheses and get the incident to the right team faster
  • Making expertise scalable: Reducing our dependence on tribal knowledge and individual muscle memory by turning years of operational experience into intelligence
  • Proving the business value: Reducing MTTI and MTTR, minimising unnecessary incident mobilisation, and giving leaders earlier visibility of customer and revenue impact

This isn't about replacing the people who know how to fix incidents. It's about making sure we only need to call them when they're actually needed.


12:00 PM Panel Discussion: Standardisation vs Freedom: How Much "Platform" Should Observability Be?

Standardisation accelerates teams when it removes friction - but over-centralisation creates bottlenecks. The goal is consistent telemetry and governance without preventing teams from shipping.

• Deciding what's central: standards, pipelines, guardrails, and minimum baselines
• Keeping teams moving with paved paths, not ticket queues
• Handling exceptions without breaking consistency, cost control, or security

Check out the incredible speaker line-up to see who will be joining Thomas.

Download The Latest Agenda