Outcomes, honestly framed

Measurement never got the priority I argued for. I pushed for Hotjar in 2024 and watched real sessions a couple of times a week until a portal release removed it; my request to put analytics back stayed a backlog item; a structured CS capture I designed was proposed as a two-week pilot and never ran. When an engineer finally ran my eight questions against the portal’s event logs in September 2026, four could be answered, two came back null, and two couldn’t be asked of the data at all.

What I claim

ClaimSource

Customers misread untapped revenue; CS watched it happen while presentingdocumented

The team agreed it was a marked improvement on what existedrecollection

Whether it reduced the misreading in productionnot measured

In September 2026 an engineer checked the portal’s event logs: the summary has no event of its own, and the dashboard’s view event counts API calls, not page loads, so the data can’t say.

What I would have tracked: how often CS had to correct the reading mid-presentation, whether the untapped figure changed what a customer did next, and the count of “why is this number what it is” support conversations.

Documented rows have a dated artifact I can produce on request. Recollection is mine, undocumented.

What I claim

ClaimSource

The system is published in Claude Design and set as Orita’s org defaultdocumented

I retired orita-slide-design on August 4, 2026, once the system outperformed itdocumented

Slide output lands roughly 80% of the way to the ceiling I could seerecollection

Whether it reduced the design work a deck takes, or kept the people who tried itnot measured

The numbers that would settle it: the share of decks that ship without a designer touching them, correction time per deck before and after the system, and how many people generate something in their first month against how many come back.

Documented rows have a dated artifact I can produce on request. Recollection is mine, undocumented.

What I claim

ClaimSource

Only one of five beta testers practiced as often as we recommended, and only one reported any real change in her migraine activitydocumented

Three months later I specced the program that answered it: nine modules of ten days, stated goal usage and retentiondocumented

Whether the program moved usage or retention once it shippednot measured

I resigned in May 2021, and that September the company shipped it as the 12 Week Plan, built from the files I handed over; no adherence or retention data for it has ever been in my hands.

What my own beta report named as the measure: empirical evidence of migraine frequency and reduction, and frequency of use.

Documented rows have a dated artifact I can produce on request.