Connected on Paper

Integration strategy for practitioners who've already seen what happens when it isn't.

Organizations spend enormous energy choosing software. They spend relatively little deciding how those systems will relate to each other: who owns which data, what happens when records conflict, where human judgment belongs in an automated process, and how the integration will behave the first time something unexpected occurs.

That gap is where most integration failures originate. Not in the technology. In the decisions that precede it.

Connected on Paper is a practitioner's guide to closing that gap. Not a methodology framework or a vendor-neutral survey of integration patterns. A direct account of what it takes to design integrations that hold up: under production conditions, under organizational change, and under the growing pressure to automate faster than the underlying decisions support.

What the book covers

The same failure modes repeat across industries, platforms, and implementation approaches. The book works through them directly:

Why data ownership disputes resolve themselves in systems, and why you won't like the resolution
The difference between integrations that run and integrations that are trusted
How timing assumptions become reliability problems
Where human judgment belongs in automated processes, and how to design for it honestly
What "observable" means for integrations that aren't breaking yet

The thread running through all of it: the technical work is downstream of clarity decisions that most teams never explicitly make.

Publication

Connected on Paper publishes in November 2026.

If you want to know when it's available (and read the occasional excerpt before then), subscribe below. No noise. Just the signal when it matters.