Source Canvas Grid

The source map

A page of doors, not a gallery of charts.

The map is the document that comes out of our flagship engagement. It lists every path a first user can take into a new app, marks which paths join to first open today, and leaves blanks blank when we cannot honestly fill them.

Team reviewing notes and sketches on a table

Inside the document

Four columns the room can argue over

Door

The path in ordinary words: Malay store search, Meta burst A, Kluang food-page mention, staff operations group, campus booth at UTM.

Join

Whether first open can carry that name today. A yes is rare. A “only if we rename the campaign” is common. A no is written as a no.

Owner

Who can change the naming, the unique link, or the booth QR before Monday. Maps without owners become posters.

What a finished map looks like in practice

Two to four pages. A cover note with the launch date and markets. A table of doors. A short punch list ordered by how many installs would fall into unknown if ignored. An appendix with the burst calendar so windows can be judged against real days, not defaults.

We do not paste screenshots of vendor reports as the map. Those reports are evidence for a reading. The map is the shared language after the reading.

When the map is the wrong ask

If you only need a window changed on one burst, ask for the window advisory. If you launched six days ago and want a calm fortnight reading, ask for the first-window readout. The full map is for teams who still have time to rename doors before the next spend — or who need a document that survives a founder handoff.

See the mapping engagement

Ask for a map on your launch

Grey is not a mystery. Grey is a door nobody named.

From our field note on writing the source list before the first campaign

Read that note, then send the channels you already plan to use.