Where Does This Live?
What this is: the four-question test I ran on every page before touching its structure, plus the three-tier path a document takes once it’s cleared to go wider. Walk it yourself; this is an independently rebuilt, representative version of the method I used on the engagement; the names are fictionalized.
Findable isn't enough; it has to be trustworthy, too.
01 · Classify it
Answer honestly. The default is always the more conservative bucket, it's far easier to promote a doc later than claw one back.
Default rule: anything that doesn't clearly resolve by Question 4 stays Internal. It's far easier to promote a doc to Shareable later than to claw back something that went wide and shouldn't have.
RESTRICTED
Separate permissions & handling. Not just hidden, locked down.
INTERNAL
Stays within team or dept. Default bucket when unsure.
SHAREABLE
Ready to surface org-wide, as-is, today.
02 · Then it moves outward
Every piece of knowledge starts on a team page. The further it travels, the wider its audience, and the more structure it needs to earn that reach.
Tier 1
Team Space
Your team's own page
Audience
Your team only, not shared externally
Naming
Not required, recommended for your own sanity
What lives here
Final, editable versions of team docs
→
Tier 2
O+T Space
"The Relay", enterprise hub
Audience
Cross-team / enterprise-wide, not external
Naming
Required, a clear, consistent tag so other teams can find and trust it
What lives here
Final versions, the shareable, locked copy
→
Tier 3
Foundry
Technical knowledge, owned & maintained
Audience
Enterprise-wide technical audience
Naming
Required, use the reference doc as the example to follow
What lives here
Technical knowledge only, owned and actively maintained
Rule of thumb: knowledge moves right when someone outside your team needs it to do their job. It never skips a tier, and Foundry content is never copy-pasted elsewhere, only linked to.