Kroots: mapping a graph nobody else could see
A one-person kids'-media venture with no team still needed an org chart, so a single map-of-content page (four clusters of working documents around one hub) had to do the job instead. Trace the clusters back to the hub.
The page is called a map of content and looks like nothing: a title, a mission line, four short lists of links. It's the closest thing my kids'-media project has to an org chart. There's no team to chart — one person, and a folder of notes that had to behave like a company anyway, so the map stands in for departments that don't exist yet. The first cluster is the one a founding team would usually split three ways: a foundation document, a go-to-market strategy, competitor research, an accelerator application — four different jobs, one person, the same week. Nothing hides that; the map just lists the links side by side and lets you notice. The second cluster is where the map earns its name: notes on two established kids' properties studied for structure, a note applying a framework about how ideas spread, and one link away, the actual launch newsletter copy. Research and shipped material sit together because they're the same activity — there was never a separate research phase to split from production. The other two clusters are thinner by a full document each, and a folder wouldn't show you that; scrolling past three files feels the same as scrolling past four. The graph shows the gap as a gap. What the map is for isn't remembering where things are. It's seeing the shape of the work from above, including which cluster stays thin because I keep finding reasons to work on strategy instead of outreach.