# Reading one map, a deck, sgit.ai

> Ten slides that read one Wardley map as a story: the afternoon of 10 October 2026 on sgit.ai, one release per frame, with one question per slide. Where is the user, what is new, what does it stand on, where did the movement happen, where would somebody else hook in, what is next. Prints to PDF in the browser.

*Source: <https://sgit.ai/articles/decks/reading-one-map.html> · site v0.7.82 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../../index.md) / [Newsroom](../index.md) / [Why I love Wardley maps](../why-i-love-wardley-maps.md) / Deck

A deck from Why I love Wardley maps

# Reading one map

One map, read as a story: the afternoon of 10 October 2026, one release at a time, with one question per frame. Ten slides.

10 slides. Arrow keys move; one slide per page when printed, landscape, nothing uploaded.

1 / 10

## Reading one map

A map is a way to tell a story. This deck reads one out, frame by frame: an afternoon on sgit.ai in which a reading meter, pay by depth, personas and an encrypted share shipped, drawn one release at a time.

Each slide asks one question of the frame. How do I think about this, what am I seeing, where do I focus.

The afternoon of 10 October 2026 as a Wardley map, finished. The next eight slides are how it got there.

2 / 10

## Before: where is the user, and what exists?

**Where is the user?** At the top: the reader, on every device.

**What exists?** Everything on the right: the articles and the build, git, browser storage, vaults, the sealed envelope, Stripe. Nothing on the left.

**What am I seeing?** A business whose user only touches mature things. Comfortable, and not a strategy.

Frame one: before today.

3 / 10

## A meter: is anything above the new dot?

The first new dot appears at genesis, close to the user, standing on browser storage.

**The question:** is anything above it? Yes, the user, directly.

**Where to focus:** this is the right altitude. A new thing the user touches is worth more than a better thing three layers down.

Frame two: a meter in the browser, a price for every page.

4 / 10

## Live: what was built, and what was bought?

Pay by depth, below zero with no block, a Stripe link. Three new dots.

**Look at the edges.** Every one runs to the right. Nothing new was built below the line.

**What am I seeing?** The build-or-buy reading, clean: custom at the top, commodity underneath.

Frame three: it goes live, on a Stripe link and the site's own storage.

5 / 10

## Personas: where did we hook in?

The dot that matters is not the persona. It is the edge: the persona connects to the articles, the oldest and largest thing the site has.

**Where to hook** was answered by the most mature component on the map.

**Where to focus:** a new feature that stands on the thing you already have most of is cheap and hard to copy.

Frame four: personas and a newsroom of your own, hooked into the articles.

6 / 10

## Versions: why was this one free?

A small dot, and it stands on git.

It cost almost nothing because its shoulder was a commodity that the site already stood on.

**What am I seeing?** The frame I use to explain why some features are free and some are not: look at what is under them.

Frame five: every article has versions, read from git.

7 / 10

## The encrypted share: is the chain ours?

The first dot that stands on a vault.

**What am I seeing?** The custom thing we had to build sits on the one product we made ourselves, so the chain under it is ours end to end.

**Where to focus:** this is where the map starts to pay for itself. Everything above the vault is now a reason for the vault.

Frame six: send us your reading, encrypted, and get a front page designed for you.

8 / 10

## The reader card: did the user notice?

Usefulness sets the price. Nothing new under it; it is a change at the top of the chain, where the user is.

**The flow reading:** everything below now has a reason to exist that the user can see.

**What moved the needle?** This one. It is the smallest dot on the map and the only one the reader would name.

Frame seven: the reader card, usefulness sets the price.

9 / 10

## Next: which dot moves first?

Dashed dots: real payments, a persona in your own vault, other sites.

The story's last line is always the same question: which of these moves first, and what does it stand on?

**Where did we walk back?** Not on this map; the two walk-backs of the following days are on the leverage map in the article.

Frame eight: next, drawn dashed because it is not built.

10 / 10

## Seven questions, one picture

- Where is the user?
- What is new?
- What does it stand on?
- Where did the movement happen?
- Where did we walk back?
- Where would somebody else hook in?
- What is next?

A reader who did not know the business now knows what it is. That is what a map is for.

The explanation deck, and the article both come from, are linked below.

The other deck: [Why I love Wardley maps](why-i-love-wardley-maps.md). The article both come from: [Why I love Wardley maps](../why-i-love-wardley-maps.md). Every map is a claim by its author, not a measurement.


---

*[Site index for agents](../../llms.txt) · [HTML version](https://sgit.ai/articles/decks/reading-one-map.html)*
