Thread
Internal knowledge. Documentation. Processes. Learning. Onboarding.
Every project produces reusable knowledge.
Thread ensures that knowledge doesn't leave when people do. Documentation, process design, learning & development, onboarding — Thread weaves individual expertise into organizational capability. They are the reason Tribar gets smarter over time.
“Every project produces reusable knowledge.”
— If a project ends and no one else can benefit from what was learned, that project failed twice.
What we measure
Individual knowledge velocity — how quickly can a single person find what they need?
Knowledge sharing density — how much expertise flows between people?
Organizational forgetting — how much institutional knowledge are we losing?
Onboarding velocity — how fast do new hires become net-productive?
◷ Rhythms
Knowledge audit
Thread scans all critical documentation for freshness. Stale docs are flagged, owners are notified, orphans are adopted.
Prevents documentation rot.
Learning lunch
30-minute internal talk on any topic. Rotating presenter across all tribes. Recorded and archived.
Makes learning a visible, regular habit.
Onboarding check-in
Thread checks in with every new hire. "What's confusing? What's missing? What would have helped last week?"
Onboarding is not a one-time event — it's a continuous improvement loop.
Retrospective harvest
Within 2 weeks of any project ending, Thread facilitates a structured retrospective. Output: reusable patterns, anti-patterns, and process improvements.
Every project produces reusable knowledge.
Process review
Thread reviews every company-wide process for relevance, efficiency, and compliance. Remove what's not serving.
Process should enable, not constrain.
Tools & artifacts
Internal wiki
platformSingle source of truth for all internal knowledge. Every page has an owner, last-updated date, and freshness score.
Onboarding playbook
frameworkRole-specific onboarding checklists with milestones, resources, and success criteria.
Mentorship program
ceremonyStructured mentorship matching system with goals, check-in cadence, and success metrics.
Process library
documentEvery company process documented: purpose, steps, owners, review cadence. No process exists without a document.
Retrospective template
frameworkStandardized retrospective format: what happened, what we learned, what we'll change, what other tribes should know.
Responsibilities
- Internal documentation and wikis
- Process design and improvement
- Learning and development programs
- Onboarding experience
- Knowledge management systems
- Post-project retrospectives and pattern capture
- Cross-tribe communication standards
- Internal tool documentation and training
Deliverables
New hire time-to-contribution — how fast can someone become productive?
Relationships
How Thread connects to every other tribe — what flows, when, and through what ritual.
Research methodology documentation, user model updates, opportunity backlog archive
Strategic decision records, market analysis archives, roadmap historical context
Architecture decisions (ADRs), runbook updates, release documentation, project retrospectives
Platform documentation, developer guides, SDK reference materials
Operational runbooks, customer incident post-mortems, deployment guides, customer journey docs
Decision log entries, metric definitions, experiment methodology documentation
Research findings, failed experiment documentation, technology evaluation reports
Security policies, compliance documentation, incident response playbooks, training materials
To make memory durable enough that nobody can erase, distort, or devalue it.
This is a protective pattern, not a verdict. It describes what can happen when the tribe's gift is driven by fear, anger, grief, scarcity, or status.
Knowledge is lost, agreements are rewritten, or people dismiss documentation and process as secondary work.
Thread can withdraw into process, preserve grievances as records, or use documentation to prove who failed.
Memory becomes ammunition and process becomes passive resistance; people stop sharing unfinished knowledge.
Living memory: documentation that supports repair, learning, and safe change instead of prosecution.
What should future teams inherit?
Identifies knowledge gaps — what doesn't get written down that should?
Creates documentation systems, process frameworks, learning platforms
Refines processes, removes redundant documentation, improves discoverability
Ensures documentation stays accurate — prevents stale knowledge from becoming tribal lore
Makes knowledge sharing frictionless — embeds docs into workflows, not separate from them
Designs how knowledge flows through the organization in 5 years — AI-augmented, self-updating