About

• Outcomes rarely begin where they become visible.

  A cost that surfaces in an operating budget may have been created years earlier, by a decision taken somewhere else entirely. The interesting question is usually not why the number is high now, but what it is evidence of.

• Systems accumulate.

  A temporary fix acquires a procedure, an operating routine, a spares position and a group of people who understand how it behaves. At some point it stops being an exception and becomes the way the work is done, usually without anyone deciding that it should.

• Evidence and interpretation are different things.

  What was observed, what was calculated from it, and what was inferred are kept apart here. So is what the evidence does not establish, which is published alongside what it does rather than quietly omitted.

• Context before prescription.

  A case sets out a situation; it does not hand down a method. Describing an operating condition accurately is more useful than recommending a fix that travels badly.

Five registers, each doing a different job. A piece belongs to one of them, and the register sets what it is allowed to claim.

Essay

Develops an argument — a single line of reasoning followed far enough to be useful.

Field Note

Captures an observation: a pattern, an anomaly or a tension recorded while it is still small enough to see clearly.

Idea

Defines a recurring concept, connects it to the work that develops it, and revises it as the thinking changes.

Series

Investigates one question across several pieces, in the order the inquiry decides rather than the order of publication.

Case Study

Demonstrates a bounded operating situation: what happened, what the evidence establishes, and where the evidence stops.

Operations Corner is written and edited by Patrick Chike, an operations and infrastructure practitioner. His work has spanned telecommunications, technical operations, program delivery, governance, vendor systems, and cloud and AI transformation.

That range is the reason for the publication rather than a credential for it. The same structures recur across environments that otherwise have little in common: obligations created by one decision and carried by another, temporary conditions that outlive the justification for them, and reporting that describes a system more neatly than the system behaves.

The writing here is concerned with those structures — how operating systems, incentives, evidence and decision-making produce consequences that arrive long after the choices that caused them. The publication does not reproduce an organization’s internal operating record. Identifying and proprietary details are generalized or omitted before publication.

Operations Corner is published here only. Writing that appears elsewhere, and any professional profiles worth pointing at, will be listed in this section rather than scattered through the publication.