Work and teams
Handbooks, runbooks, decision records, product specs, battlecards and research repositories, kept by one owner and read by the team.
A know.sh library has one owner. That suits the documents a team leans on but one person keeps: the handbook an operations lead maintains, the runbooks an on-call engineer curates, the decision log an architect writes. The owner writes and revises, often with an assistant doing the legwork; colleagues read a public, read-only link.
Keep secrets, customer data and anything under an NDA out of documents you share, and use the per-finding exclusion to leave internal notes off the public link.
Recipessix recipes
- 33 An employee handbook and onboarding guideFor the operations lead at a twenty-five-person design studioPut a studio handbook, a two-week onboarding plan and a tools guide into three documents, send new hires password-protected links, and have your assistant draft an FAQ and flag where policies disagree.
- 34 Incident runbooks and a postmortem libraryFor the SRE lead at a SaaS company who keeps the on-call runbooksHave your assistant draft a runbook per service from your alert rules, a finding per alert, and a postmortem per incident from your notes, linked to the runbook, with follow-up actions laid out as a campaign.
- 35 An AI release trackerFor an engineering lead who has to know which new models and features are worth trying this monthKeep up with AI releases without living on social media: a weekly scheduled task in Claude or ChatGPT gathers the announcements, your assistant files each as a finding linked to its official source, and you keep what matters.
- 36 A product requirements documentFor a product manager at a B2B software company writing the requirements for a new featureA requirements document whose findings are requirements, evidence, risks, open questions and decisions, drafted by your assistant from your notes, fixed up by you, shared with stakeholders and turned into a plan.
- 37 Competitive battlecardsFor a product marketer who keeps the battlecards the sales team reads before a callKeep a battlecard per competitor with each public claim sourced and dated, your answer beside it and the landmines reps should avoid, researched by your assistant from public pages and read by sales from a password link.
- 38 A user research repositoryFor a UX researcher at a software company with two years of studies nobody can findFile each study as a document of anonymised Evidence and the Insights it supports, on a shelf per product area, so Look up finds every theme and your assistant finds patterns, with citations you check.
Index to this shelf
C
Changelogs, 35
Company policies, 33
Competitive intelligence, 37
Competitive landscape, 36
Competitor claims, 37
Contradictions, 33
Contributing factors, 34
D
Deprecations, 35
H
M
Model licences, 35
P
Participant consent, 38
Password-protected links, 33
Postmortems, 34
Product requirements, 36
Public sources, 37
W
Watch lists, 35