CONTENT SYSTEMS 8 ACCESSIBILITY

Explaining an invisible product with a 15-panel comic

Explaining an invisible product with a 15-panel comic

ROLE

Ridgeway

compANY

2025

SCOPE

year

↘ BRIEF

The problem

API Control Plane watches API traffic and health across every gateway and runtime a company runs. The catch is that its value only shows up when something is missing: visibility you never had, or an outage you can't pin down. New users opening the docs got architecture diagrams and a glossary long before they got a reason to care.

So, I set one bar. After a single read, a first-time reader should be able to explain the product in one sentence without being prompted.


Abstract subject


No single screen shows "one view of everything." The benefit is that the chaos stops.


Skeptical readers


Engineers who already juggle three monitoring tools and don't want a fourth.

Docs-shaped docs


The old onboarding opened with concepts and jargon and got to the stakes last.

↘ APPROACH

↘ APPROACH

The solution

Click here to view the entire comic

Get in touch

Why a comic? - Stakes before concepts

Docs answer "how does it work?". A first touchpoint has to answer "why should I care?". A story is the simplest way I know to put the stakes first: an outage on a Friday night, three dashboards giving three different answers, and a fix found in twenty minutes. Each product idea only shows up when a character actually needs it.


  • Concrete stand-ins for abstract ideas: A "fragmented API landscape" became three delivery apps built by three different teams. "Unified visibility" became a city map lighting up. The main analogy, Google Maps, but for every API we own, is easy to repeat to a colleague, and that's the whole job of an analogy.


  • Color tells part of the story: Panels 6 to 9 fade to gray during the outage, and Blue 60 only comes back once the product is online. Someone skimming the thumbnails can still follow the arc.


  • A tone that suits enterprise readers: Warm and dry, but never silly. I kept to the Carbon palette and IBM Plex, and saved red and green for system states. The humor comes from understatement ("Keep Fridays boring") rather than mascots.


Figure 1 - Reading load to first full explaination

Accessibility - a comic that works with the images off

A comic is visual first, which raises an obvious question: what about readers who can't see it? I treated that as a content design problem with its own deliverables, planned from the start instead of patched in after launch.


Panel-level alt text

Each panel's SVG has an aria-label written like narration rather than a list of objects. It says "Ria's glasses reflect the error codes," not "woman, monitors, plant."


Reading order

Each panel sits in a labeled section, so a screen reader follows the story in the order it's meant to be read: caption, then dialogue, then scene.


Full transcript

A prose version that works as a short story on its own, with the same arc, stakes, and one-sentence takeaway, and no reliance on the pictures. It's also the version people can search, quote, and translate, which the comic can't offer.


Intent doc

A short note on what each panel has to get across. It works as the comic's content model, so translators, localizers, and anyone redrawing a panel keep the meaning intact.



Color never carries meaning on its own. You can tell there's an outage from the error codes and the copy; the shift to gray just backs that up.

↘ The outcome

↘ The outcome

Outcome - the one-sentence test

Outcome - the one-sentence test

Outcome - the one-sentence test

In read-throughs, every reviewer could describe the product afterward without prompting. Most said some version of "it's a single control plane that discovers and monitors every API across all our gateways." That sentence is the metric I cared about. Everything else in the comic is there to get people to it.


~ 6 min


to a full product explanation you can retell, compared with four-page docs path

73%


fewer words than the docs onboarding path it sits in front of (~=1000 vs ~=4500)

3


personas served by one piece: engineer, PM, and architect, each with their own payoff in the final panel

What I would do differently:

I'd cut two of the setup panels, since 13 would tell the same story more tightly. I'd also give governance its own moment in the story instead of one line on the payoff card, so the product doesn't come across as just monitoring.

Get in touch

OPEN TO NEW OPPORTUNITIES

Let's talk about what's next.

Email

mahimashastryux@gmail.com

Get in touch

OPEN TO NEW OPPORTUNITIES

Let's talk about what's next.

Email

mahimashastryux@gmail.com

Get in touch

OPEN TO NEW OPPORTUNITIES

Find my work interesting? Let's talk

Email

mahimashastryux@gmail.com

MAHIMA SHASTRY

BANGALORE, INDIA

MAHIMA

Mahima. All rights reserved.

No templates were harmed in the process of making this portfolio

MAHIMA SHASTRY

BANGALORE, INDIA

MAHIMA

Mahima. All rights reserved.

No templates were harmed in the process of making this portfolio

MAHIMA SHASTRY

BANGALORE, INDIA

MAHIMA

Mahima. All rights reserved.

No templates were harmed in the process of making this portfolio

Create a free website with Framer, the website builder loved by startups, designers and agencies.