graph-thinking_skill

Overview

This skill applies graph-based thinking to visualize complex relationships and solve problems non-linearly. It helps map nodes, define relationship types, identify clusters and critical pathways, and produce actionable recommendations. Use it to reveal dependencies, bottlenecks, and opportunities across products, systems, and organizations.

How this skill works

I guide you to map relevant elements as nodes, label edges by relationship type and strength, and compute or eyeball centrality and clusters. Then we trace pathways and feedback loops to surface critical paths, bottlenecks, and leverage points. The output is a concise node map, relationship matrix, key insights, and prioritized recommendations you can iterate on.

When to use it

• Mapping feature dependencies during product planning
• Analyzing system architecture and single points of failure
• Exploring stakeholder influence and communication gaps
• Designing recommendation systems or knowledge graphs
• Identifying strategic opportunities through network patterns

Best practices

• Draw the graph — visual maps reveal patterns faster than prose
• Differentiate edge types (dependency, influence, conflict, synergy) and assign weights
• Measure centrality to prioritize remediation or investment
• Iterate the graph as new data or constraints appear
• Avoid over-connecting: keep relationships meaningful and evidence-based

Example use cases

• Feature dependency mapping for a launch to spot blockers and parallelize work
• System architecture review to locate single points of failure and reduce coupling
• Stakeholder analysis to tailor communication and escalation plans
• Designing a recommendation or knowledge graph by mapping entities and relation strengths
• Evaluating customer journeys as network pathways to identify churn and upgrade triggers