Skip to main content

What You’ll Learn

  • How knowledge connects across projects
  • What kinds of insights become visible
  • How to access cross-project intelligence
  • Practical use cases

What Is Cross-Project Intelligence?

Most knowledge platforms keep everything in silos. Project A doesn’t know about Project B. But your work is connected - decisions in one initiative affect another. Cross-Project Intelligence breaks these silos. It enables:
  • Pattern detection across initiatives
  • Contradiction identification between projects
  • Knowledge reuse from past work
  • Strategic synthesis across your portfolio

How It Works

Each project builds its own Knowledge Graph (entities, relationships, observations). Cross-Project Intelligence connects these graphs:
  1. Entity matching - Identifies when the same entity appears in multiple projects
  2. Relationship mapping - Finds connections between entities across projects
  3. Pattern analysis - Identifies recurring themes, decisions, or concerns
  4. Contradiction flagging - Spots when projects contain conflicting information

Accessing Cross-Project Intelligence

Cross-project knowledge is available through Master Projects (see Master Projects). When you ask a question in a Master Project, the AIs search across all your project knowledge.

What Becomes Visible

Contradictions

“In your Product project, you decided to focus on SMB. In your Sales project, you’re building enterprise features. These may conflict.”

Patterns

“You’ve mentioned ‘time to value’ as a concern in 4 different projects. This seems to be a core theme in your work.”

Reusable Insights

“The competitive analysis you did in Project A is directly relevant to the positioning question in Project B.”

Resource Conflicts

“Project A needs 2 engineers for Q2. Project B needs 3 engineers for Q2. You have 4 total. There’s a conflict.”

Use Cases

Quarterly Planning

Ask: “Looking across all projects, what should be our top 3 priorities for next quarter?” The AI considers product roadmap, marketing plans, sales pipeline, and engineering capacity from their respective projects.

Risk Assessment

Ask: “Are there any risks that span multiple projects? Dependencies or single points of failure?”

Decision Consistency

Ask: “Have I made any contradictory decisions across projects that I should reconcile?”

Knowledge Transfer

Ask: “The research I did in my Competitor Analysis project - how does it apply to my Product Strategy project?”

Tips

  • Cross-project intelligence gets more valuable over time as each project accumulates knowledge
  • Keep project names and descriptions clear - they help the system understand how projects relate
  • Use Master Projects when you need cross-project thinking. Use regular projects for focused work.
  • Periodic cross-project reviews (monthly or quarterly) help catch contradictions early

Still Need Help?

Reach out to us at [email protected] or use the feedback button in the app.