The artifact isn't the deliverable

What the Rally Report taught me about why Product Operations work either justifies itself or doesn't.

---

There's a persistent critique of Product Operations as a discipline: that it creates process where none is needed, produces artifacts nobody asked for, and inserts a layer of overhead that good product teams shouldn't require. The critique has some merit. I've seen it play out. Process for its own sake is real, and it's wasteful.

But I've also seen what happens when the critique becomes an excuse to avoid a harder question: not whether an artifact is necessary, but whether the system it's meant to serve actually works. Those are different problems, and conflating them lets a lot of organizational dysfunction go unexamined.

The Rally Report is my clearest example of the difference.

The ask

In 2020, Rally Health's CEO and Director of Product came to my team with a request that was, characteristically, open-ended: put together "some kind of report or slide deck or something" that showed Rally's work in context for the enterprise executive leadership.

I could have built a slide deck. I could have produced a status update, formatted it nicely, and called it done. That would have been an artifact. What I built instead was a system — and the distinction matters.

The system question

Before designing anything, I spent time understanding what the audience actually needed, what existing artifacts were trying and failing to do, and what a sustainable communication system would look like over time — not just for a single deliverable, but for the ongoing work of keeping a complex enterprise informed and aligned.

That inquiry surfaced something important: the primary audience was enterprise leadership, yes. But there was a secondary audience that nobody had named — Rally's own internal teams. Product strategy leads, customer insights managers, client activation teams. People who needed to stay current with work happening outside their immediate line of sight, and who were currently getting that information piecemeal, inconsistently, or not at all.

Designing for both audiences simultaneously shaped almost every decision that followed. The 4 R's of product delivery — Research, Roadmaps, Releases, Results — weren't just an organizing principle. They were a deliberate argument about how Rally's work should be understood: we listen to the market, we plan deliberately, we ship consistently, and we measure what we do. Mapping every initiative to the company's Balanced Scorecard metrics turned a status update into a strategic accountability document.

The distribution list, the navigation structure, the all-hands walkthrough at launch — none of that was incidental. It was designed. The enterprise audience was the content focus; the broader organizational utility was the return on that investment.

What it actually produced

Within a few cycles, the Rally Report had stopped being a communication artifact and become organizational infrastructure. Product Strategy used it as the primary source for their Monthly Business Review, eliminating hours of verification work with individual product owners. Customer Insights used it to contextualize NPS movement. Client Activation used it to prepare for conversations with product leadership. Business Operations used it to understand work happening outside their line of sight. The report didn't add to anyone's workload. It retired work that was already happening badly — the verification calls, the one-off briefings, the piecemeal updates that were eating time across four or five teams simultaneously.

"We use the Rally Report to provide information about product releases in the Rally Portfolio Monthly Update rather than having to compile and verify the information with individual product owners." — Rally Product Strategy

That's not a communications win. That's an operational one. The artifact justified itself not because it existed, but because of the organizational behaviors it enabled and the redundant work it eliminated.

The regenerative lens

I think about this project now through what I'd call a regenerative operations lens: the goal isn't to produce outputs. It's to design systems where every input and output has a job, where nothing is generated that doesn't serve someone, and where the whole is more functional than the sum of its parts.

The Rally Report worked because it was designed for the full cycle — not just the delivery triad of Product, Design, and Engineering, but every team that depended on or supported what the delivery triad produced. Sales. Support. Client Activation. Business Operations. Enterprise leadership. Each of them needed something different, at a different level of detail, for a different purpose. The report held all of that without collapsing under its own weight because the architecture was designed to.

In a healthy ecosystem, nothing is wasted — outputs become inputs. The Rally Report was built on that principle before I had language for it.

What this means now

The Rally Report as a format is already obsolete. A well-prompted AI can generate a monthly product summary using content from multiple sources, map initiatives to strategic objectives, tailor the terminology to the audience, and distribute it to a segmented list in a fraction of the time it took my team to do those things.

What AI cannot do — yet, and possibly not ever — is understand the organizational ecosystem well enough to know what to generate, for whom, at what level of detail, and why. It can't identify the secondary audience that nobody named. It can't recognize that the real problem isn't communication volume but information architecture. It can't design the system that makes the artifact worth producing in the first place.

That's the work. The artifact was always just the current best expression of it.

Product Operations done well doesn't add process. It identifies where the system is losing energy — where outputs aren't landing, where inputs aren't reaching the people who need them, where work is being duplicated because no one has built the connective tissue — and it designs for that. The critique of the discipline is fair when the discipline forgets this; it falls apart when the discipline remembers it.

---

The full Rally Report case study — including the strategic choices behind the 4 R's framework and the Balanced Scorecard mapping — is available to download from the Field Work section of this site.