About Cluster Pulse Point

Origin

Cluster Pulse Point began in Sydney when a handful of operations leads grew tired of handing executives dashboards that explained nothing about why a cluster kept stumbling. The practice formed around a simple habit: sit with the evidence, write the reliability story in language both engineers and sponsors can use, and leave the tooling decisions to the people who own them.

Mission

Deliver application analytics and cluster reliability reporting that survive contact with real production constraints — partial access, incomplete runbooks, conflicting incident memories — and still produce findings a team can act on within a sprint.

How we work

We prefer shorter engagements with sharp boundaries over vague retainers that blur into unpaid advice. Evidence first, narrative second, recommendations last. We do not sell monitoring licences, and we will not pretend a report replaces the hard work of remediation.

People

Helen Okonkwo — Reliability analyst

Helen spent a decade in payment and logistics estates before turning to independent reliability reporting. She leads most flagship assessments and insists on reading raw incident notes before any metrics export.

James Whitford — Second reader

James reviews every final report for clarity and overclaim. His background is capacity planning for multi-region application clusters; he challenges any finding that cannot point to evidence gathered in the engagement.

Values

• Specificity over polish — a plain paragraph that names the failing retry path beats a glossy slide
• Respect for operators — we write about systems, not about blaming the people who keep them up
• Australian context — engagements assume local business hours, AU privacy expectations, and the reality of teams split across Sydney, Melbourne, and Brisbane

Community

We share anonymised field notes through our journal and occasionally host short roundtables in Sydney for reliability writers and SRE leads. Attendance is free; pitches for tooling vendors are not.