Content Operations Engineering and Design

For the last fifteen years I’ve framed my work primarily as “information architecture”: I help make complex information spaces easy to understand and pleasant to use. This work has always been about communication—helping teams convey facts, concepts, and ideas so audiences understand what matters. Often, the focus has been on creating pages (despite my perennial efforts to move beyond that metaphor).

In the last couple years, we’ve witnessed seismic shifts in how content is created, communicated, and consumed. That we’ve moved past “pages” is a foregone conclusion. To communicate effectively online we now need models that treat content as a living asset, ready to flow wherever it creates value. Information architecture remains essential. The holistic operationalization of how content is planned, created, published, and managed, however, is now more crucial than ever. This is why I’m narrowing the scope of my practice to “content operations engineering and design,” with a focus on work on the Sanity platform.

I realize this is a bit of a mouthful, so let me unpack it piece by piece.

Content Operations

Content operations is the coordinated ensemble of people, process, and technology an organization uses to plan, create, govern, and measure the effectiveness of content. Purposeful, outcomes-focused content operations guide both human authors and generative algorithms in the creation of trustworthy, effective content.

In my practice, I’ve found that creating a successful approach to content operations relies on three interdependent activities:

  1. Discovery and alignment: uncovering an organization’s communication goals, domain language, and author realities
  2. Thinking in systems: designing models, services, and workflows that scale beyond individual pages and consider communication goals across contexts
  3. Engineering for intended outcomes: building structure and guidance into the content operations environment so that the creation of on-brand, on-purpose content is the path of least resistance for both humans and machines

If you follow my work at all, you know that this is the kind of work I’ve already been doing for years. By formalizing this focus, my goal is to more directly connect with organizations that need help uncovering what must be said, modeling it so it can move fluidly across channels, and embedding those models into workflows that create consistent value.

Engineering & Design

Jared Spool writes that "design is the rendering of intent.” I like to extend this truism by adding that engineering is the realization of design. To move from intent to operational reality, both of these elements must be carefully coordinated. When misalignment exists between engineering and design for content operations, organizations can end up with “technically correct” implementations that ignore business requirements and author needs, or visionary design recommendations that never survive handoff.

For nearly a decade I’ve been developing and iterating methods for bridging engineering and design. As part of my focus on content operations, I’ve brought together a set of time-tested frameworks and methods for uncovering and instantiating the requirements for an organization’s content operating systems. These tools allow me to lead projects in which:

The systems that emerge are ones that authors actually want to use because they speak their language, support their tasks, and provide effective tools for embracing new ways of creating and managing content.

The Sanity Platform

For the past five years most of my client work has been deep inside the Sanity ecosystem: I’ve launched studios, written plugins, and designed and iterated custom workflows and integrations. I’ve also had a front-row seat as the platform has evolved from a capable headless CMS into a full-featured “content operating system.” For organizations with specialized entities or domain‑specific complexity, Sanity’s customizable schemas and API‑first toolset make it uniquely suited for creating purpose-built content operations solutions.

Sanity’s openness and flexibility, however, can be a double-edged sword: Development teams new to composable content are just as free to create implementations that work against Sanity’s core value proposition as they are to build in a way that embraces it. By committing to understanding the platform and its features deeply, my goal is to help organizations using Sanity work with the grain of the platform to achieve the operational outcomes that best serve their needs and deliver lasting value over time.

Carrying On

Twenty years ago I pivoted from a career path as an English professor to the then budding field of “UX.” My goal then, as now, has been to understand and enable the creation and sharing of meaning between individuals. The changes wrought by generative AI in the last few years have tossed a lot of what we thought we knew about those practices into a kind of epistemological juice mixer. The outcomes I seek to support, however, remain the same: the communication of ideas from one mind to another.

I’m excited to carry on with this work in this new, weird world of ours. If any of what I’ve written piques your curiosity—or if you find yourself in the thick of any of the challenges I describe above—please do reach out. I’d love to start a conversation.

Related Resources