MERIDIAN · Case Study01 05

Chapter 01Why this exists

The Civic Premise

Why this exists

Length: 250–400 words. Asset: one editorial-grade hero photograph with treatment applied. No screenshot of any product, including yours, in this chapter. Tone test: if this could be the introduction to a magazine feature on civic design, it passes. If it reads like a portfolio voiceover, it fails.


Opening sentence

Begin with a fact about cities, mobility, or design that re-frames the problem.

Forbidden openings:

What works: a specific, named fact. A number. A city. A failure with a date attached.

Examples of the register (do not copy verbatim — these are tone references):


Body

Establish the cultural and political stakes. Three paragraphs is enough.

Paragraph 1 — the failure. Who is failed by today's civic technology design? Be specific. Name the population (commuters in a specific corridor, operators on a specific shift, citizens with a specific accessibility need). Cite real data. Resist abstraction.

Paragraph 2 — the cost of that failure. The cost is rarely "bad UX." It is missed buses, missed shifts, missed appointments, missed votes. Translate the design failure into the human cost. Use a number. Use a name where ethics permit.

Paragraph 3 — why most government dashboards look the way they do. Do not be polite about this. The honest answer involves procurement cycles, vendor capture, the path of least resistance for a contractor who will not be the user. Name it without contempt — civic systems are built by people doing their jobs inside constraints. The design failure is structural, not personal.


Closing

End the chapter on a note that sets up what MERIDIAN refuses to be. Not yet what it is — that is Chapter 3.

A single declarative sentence works best here. Resist the urge to qualify.


Draft notes (delete before publishing)