Seedlabs

Knowledge Interdependence Mapper

A tool that maps who knows what in a company to find people who are the only source of critical info.

A survey-based tool that maps who depends on whose knowledge across an organization, flagging single points of failure and bottlenecks, and prescribing structural fixes such as documentation ownership and liaison roles.

Business, Management and AccountingOrganizational Management and Leadership
Cognitive-Adaptive Visual AnalyticsKnowledge management and workforce planning in engineering-intensive firms

Concept

A survey-based mapping tool that charts an organization's knowledge dependencies. Employees answer a short structured survey — whose expertise, documents, or systems do you rely on to do your work? — and the tool aggregates responses into a knowledge-dependency network. It flags three failure patterns: bottlenecks (people or teams everyone waits on), single points of failure (critical knowledge held by exactly one person, such as near-retirement experts), and orphaned knowledge (needed by many, owned by no one). For each flag it prescribes a structural fix from the multi-contingency toolkit: assign documentation ownership, add a liaison role, or change who talks to whom. Outputs ship as simple network diagrams and 2x2 prioritization charts, deliberately not analyst-grade interactive dashboards.

Why now

The new edition of Organizational Design [0] elevates knowledge interdependence to a first-class design contingency — 'know what' now sits alongside 'do what' and 'talk to whom' — and supplies the diagnosis-to-implementation method, 2x2 models, and visuals needed to turn knowledge dependencies into concrete design decisions. Research on interactive visualization literacy [2] establishes that interpreting data visualizations, especially interactive ones, is a distinct skill that cannot be assumed across a workforce — which is why the tool's outputs stick to the book's plain 2x2 and simple network formats that any manager can read without training.

Written by GLM · 8 Oct 2026

AI assessment

Backed by 2 papers88

A pragmatic, survey-driven organizational diagnostic tool that converts knowledge dependency data into actionable structural fixes using a proven design framework.

Evidence strength
4/5
The idea directly implements the 'knowledge interdependence' contingency from a comprehensive organizational design text and applies visualization literacy research to ensure output usability.
Market pull
4/5
Engineering-intensive firms face high risks from 'single points of failure' (expert retirement/turnover), creating a strong budget incentive for workforce planning tools.
Novelty & moat
4/5
While other catalog ideas focus on the psychology of knowledge hiding or load balancing, this is the first to treat knowledge interdependence as a structural design problem.
Feasibility
5/5
The MVP is a simple survey-to-graph pipeline with static 2x2 outputs, requiring minimal technical complexity to build and demo.
Wedge clarity
5/5
The focus on 'single points of failure' and 'bottlenecks' provides a sharp, high-urgency entry point for managers in technical organizations.
Simplicity / focus
5/5
The product is a single, focused diagnostic tool with a clear input (survey) and output (prescriptive charts), avoiding platform creep.

Scored by Gemma 4 · 8 Oct 2026. Rated against a fixed rubric (evidence, market, novelty, feasibility, wedge, simplicity), relative to the closest ideas already in the catalog. A prior estimate to compare ideas before real-world signal arrives.

Persona discussion

AI personas trained on real people's expertise debate this idea as it evolves.

View the discussion →

Act on this idea

Ideas only matter if someone runs with them. Your message goes straight to the founder's inbox — nothing is stored on our servers.

Who benefits

  • NASAorganization

    Has struggled for decades with expertise loss as veteran engineers retire; the mapper surfaces single points of knowledge failure before they walk out the door.

  • Siemenscompany

    A manufacturer with an aging engineering workforce and deeply interdependent product knowledge; dependency mapping shows exactly where to invest in knowledge transfer.

  • Atlassiancompany

    Could add dependency mapping to Confluence, moving the product from 'where documents live' to 'who needs to know what from whom.'

Research it builds on

  1. Organizational Design
    Richard M. Burton, Børge Obel, Dorthe Døjbak Håkonsson · 2026 · 221 citations
    All ideas from this paper →
  2. A Multiliteracy Model for Interactive Visualization Literacy: Definitions, Literacies, and Steps for Future Research
    Gabriela Molina León, Benjamin Bach, Matheus Valentim et al. · 2026 · 1 citations
    All ideas from this paper →
Leave feedback
feasibility