[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@jacobcole / IdeaFlow Vision / wiki/layers/team-cognition.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- title: Team Cognition — the organization layer type: layer visibility: public audience: investors, builders related: - wiki/framings/graph-database-for-your-brain.md - wiki/pitches/for-investors.md - wiki/system-map.md --- # Team Cognition The team / organization layer. Many users, one shared graph, with privacy at node and edge granularity. ## What it does, in one line > "The **ultimate CEO dashboard** — and **collective brain for a company**." ## The enterprise wedge This is IdeaFlow's current revenue engine (2026). Teams have coordination pain acute enough to pay for the substrate. The wedge products: - **Slack bot that listens to conversations** and harvests unstructured team knowledge into a graph — then suggests connections between people who have related ideas. - **Meeting notes pipeline** — voice/text meeting capture producing structured knowledge with connection-provenance, not just summaries. - **Internal "Twitter" feed** that surfaces context relevant to whatever the user is currently working on. - **Innovation management** — mapping ideas and connections across an organization's actual thinking surface (not its org chart). ## Why teams pay Teams have three problems IdeaFlow solves that notes apps don't: 1. **Knowledge silos.** What's in one head isn't in another's. 2. **Context loss.** Every meeting re-derives the same context from scratch. 3. **Coordination drift.** People pursue subtly-different goals because the canonical goal isn't legible. The graph is the shared surface that resolves all three. Slack resolves none of them; docs resolve one with heavy overhead; IdeaFlow resolves all three because the substrate *is* the shared cognition. ## What a team's graph looks like - Projects as nodes, with goals, open questions, decisions, artifacts all attached. - People as nodes, with their responsibilities, interests, recent thinking. - Meetings as nodes, with structured takeaways and connection provenance. - Slack messages as edges (non-privileged, time-stamped, hide-from-main-timeline-by-default). - Customers, products, markets as nodes — importable from systems of record, bidirectionally linked. ## Related (on this wiki) - [[../framings/graph-database-for-your-brain]] — at team scale - [[../use-cases]] → "Team layer" - [[../pitches/for-investors]] - [[../pitches/for-builders]] ## Related (vision-convo cross-links) - [Collective Intelligence](https://wikihub.md/@jacobcole/vision-convo/wiki/concepts/collective-intelligence) — the conceptual parent - [IdeaFlow (project page)](https://wikihub.md/@jacobcole/vision-convo/wiki/projects/ideaflow)