AI-Generated Content Warning: This documentation contains AI-generated content. Verify information before depending on it for decision making.
Understanding how users first experience GraphDone's unique approach to project management.
journey
title New User Journey
section Discovery
Visit landing page : 3: User
Read philosophy : 4: User
Watch demo video : 5: User
section Trial
Create account : 3: User
Join demo workspace : 4: User
Create first node : 5: User
See spherical visualization : 5: User
section Learning
Tutorial: Priority system : 4: User
Tutorial: Dependencies : 4: User
Tutorial: Community rating : 5: User
Invite team member : 3: User
section Adoption
Create real project : 5: User
Set up workflows : 4: User
Integrate AI agent : 5: User
Achieve first milestone : 5: User
How teams use GraphDone for ongoing project coordination.
sequenceDiagram
participant TL as Team Lead
participant DEV as Developer
participant DES as Designer
participant AI as AI Agent
participant SYS as GraphDone System
Note over TL,SYS: Morning Planning
TL->>SYS: Check high-priority nodes
SYS->>TL: Display center-sphere items
TL->>SYS: Add executive priority to critical bug
SYS->>DEV: Real-time notification: Priority increased
SYS->>DES: Real-time notification: Priority increased
Note over TL,SYS: Work Execution
DEV->>SYS: Update node status: In Progress
SYS->>TL: Status change notification
DES->>SYS: Create dependency: "Design review needed"
SYS->>DEV: Dependency notification
Note over TL,SYS: Community Validation
DEV->>SYS: Propose new performance optimization
Note over SYS: Node starts at periphery
DES->>SYS: Anonymous boost: +0.3 community priority
TL->>SYS: Anonymous boost: +0.2 community priority
SYS->>AI: Priority change: Performance optimization
AI->>SYS: Analysis: "High impact, recommend resources"
SYS->>SYS: Migrate node toward center
Note over TL,SYS: Resource Allocation
SYS->>TL: Node reached resource threshold
TL->>SYS: Assign developer to optimization
SYS->>DEV: New assignment notification
AI->>SYS: Offer automated testing support
How ideas migrate from periphery to center through community validation.
graph TD
START[💡 New Idea Created] --> PERIPHERY[📍 Positioned at Periphery<br/>Priority: 0.1<br/>Resources: Minimal]
PERIPHERY --> VISIBILITY[👁️ Visible to Community<br/>Anonymous rating enabled]
VISIBILITY --> COMMUNITY_CHOICE{Community Response}
COMMUNITY_CHOICE -->|Positive Feedback| BOOST1[⬆️ Community Boost<br/>Priority: 0.3<br/>Moves closer to center]
COMMUNITY_CHOICE -->|No Feedback| STAGNATE[⏸️ Remains at Periphery<br/>Gets idle resources only]
COMMUNITY_CHOICE -->|Negative Feedback| DECLINE[⬇️ Moves further out<br/>Reduced visibility]
BOOST1 --> ATTENTION[👀 Increased Visibility<br/>More team members see it]
ATTENTION --> VALIDATION{Continued Validation}
VALIDATION -->|Strong Support| BOOST2[⬆️⬆️ Major Boost<br/>Priority: 0.7<br/>Enters inner sphere]
VALIDATION -->|Mixed Response| PLATEAU[➡️ Stabilizes<br/>Middle sphere position]
VALIDATION -->|Support Wanes| DECLINE
BOOST2 --> RESOURCES[💰 Substantial Resources<br/>Team assignment<br/>Active development]
RESOURCES --> EXECUTION[🔨 Active Development<br/>Regular updates<br/>Progress tracking]
EXECUTION --> SUCCESS{Outcome}
SUCCESS -->|Delivers Value| REINFORCE[🔄 Reinforced Position<br/>Continued high priority]
SUCCESS -->|Fails to Deliver| REASSESS[🔍 Community Reassessment<br/>May lose priority]
PLATEAU --> EVOLUTION[🔄 Continuous Evolution<br/>Based on changing needs]
EVOLUTION --> VALIDATION
style START fill:#e1f5fe
style BOOST2 fill:#c8e6c9
style RESOURCES fill:#fff3e0
style DECLINE fill:#ffcdd2
How humans and AI agents coordinate as peers in the graph.
graph LR
subgraph "Human Activities"
H1[👤 Create Strategic Goals]
H2[👤 Design User Experience]
H3[👤 Make Creative Decisions]
H4[👤 Validate Community Needs]
end
subgraph "AI Agent Activities"
A1[🤖 Code Review & Testing]
A2[🤖 Performance Analysis]
A3[🤖 Documentation Generation]
A4[🤖 Risk Assessment]
end
subgraph "Shared Graph Space"
N1[Strategic Outcome]
N2[Feature Implementation]
N3[Quality Assurance]
N4[Performance Metrics]
N5[User Documentation]
end
H1 --> N1
H2 --> N2
H3 --> N2
H4 --> N1
A1 --> N3
A2 --> N4
A3 --> N5
A4 --> N1
N1 -.-> N2
N2 -.-> N3
N3 -.-> N4
N2 -.-> N5
style H1 fill:#e3f2fd
style H2 fill:#e3f2fd
style H3 fill:#e3f2fd
style H4 fill:#e3f2fd
style A1 fill:#f3e5f5
style A2 fill:#f3e5f5
style A3 fill:#f3e5f5
style A4 fill:#f3e5f5
Different ways priority can change in the system.
graph TB
subgraph "Executive Influence"
EXEC_FLAG[🏛️ Executive Flag<br/>Strategic priority signal]
EXEC_GRAVITY[🌟 Creates Gravity Well<br/>Attracts related work]
end
subgraph "Individual Influence"
PERSONAL[👤 Personal Priority<br/>Individual importance]
CONTRIBUTION[🔨 Active Contribution<br/>Working on node]
end
subgraph "Community Influence"
ANONYMOUS[👥 Anonymous Rating<br/>Peer validation]
BOOST[⬆️ Community Boost<br/>Collective energy]
NETWORK[🕸️ Network Effects<br/>Connected node priority]
end
subgraph "Algorithmic Influence"
DEPENDENCY[🔗 Dependency Priority<br/>Inherited importance]
TIME_DECAY[⏰ Time-based Decay<br/>Prevents stagnation]
USAGE[📊 Usage Patterns<br/>Actual engagement]
end
EXEC_FLAG --> EXEC_GRAVITY
PERSONAL --> CONTRIBUTION
ANONYMOUS --> BOOST
BOOST --> NETWORK
DEPENDENCY --> TIME_DECAY
TIME_DECAY --> USAGE
EXEC_GRAVITY -.-> PRIORITY_ENGINE[🧮 Priority Calculator]
CONTRIBUTION -.-> PRIORITY_ENGINE
NETWORK -.-> PRIORITY_ENGINE
USAGE -.-> PRIORITY_ENGINE
PRIORITY_ENGINE --> SPHERICAL_POSITION[🌍 Spherical Position Update]
How users stay informed about relevant changes.
sequenceDiagram
participant U as User
participant S as System
participant N as Notification Hub
participant P as Push Service
participant E as Email Service
Note over U,E: Subscription Setup
U->>S: Configure notification preferences
S->>N: Store user preferences
Note over U,E: Priority Change Event
S->>N: Node priority increased significantly
N->>N: Check user preferences & relevance
alt High relevance + immediate preference
N->>P: Send push notification
P->>U: Real-time alert
else Medium relevance + daily digest preference
N->>E: Queue for daily digest
E->>U: Daily summary email
else Low relevance
N->>S: Update in-app feed only
end
Note over U,E: Dependency Change Event
S->>N: Node you're working on has new dependency
N->>P: Send immediate notification
P->>U: "Your work is blocked by: X"
Note over U,E: Community Validation Event
S->>N: Your idea received community boost
N->>P: Send encouragement notification
P->>U: "Your idea is gaining traction! 🚀"
Touch-optimized interactions for mobile devices.
graph TB
subgraph "Touch Gestures"
TAP[👆 Tap<br/>Select node<br/>View details]
LONG_PRESS[✋ Long Press<br/>Context menu<br/>Quick actions]
PINCH[🤏 Pinch/Zoom<br/>Navigate graph<br/>Focus areas]
SWIPE[👈 Swipe<br/>Change priorities<br/>Quick rating]
end
subgraph "Voice Interactions"
VOICE_CREATE[🎤 "Create task..."<br/>Quick node creation]
VOICE_PRIORITY[🎤 "Boost priority..."<br/>Priority adjustment]
VOICE_STATUS[🎤 "Mark complete..."<br/>Status updates]
end
subgraph "Contextual Actions"
FLOATING_MENU[⚡ Floating Action Button<br/>Common operations]
BOTTOM_SHEET[📋 Bottom Sheet<br/>Node details & actions]
QUICK_ADD[➕ Quick Add<br/>Add related nodes]
end
subgraph "Offline Capabilities"
LOCAL_CACHE[💾 Local Cache<br/>Recently viewed nodes]
SYNC_QUEUE[⏳ Sync Queue<br/>Offline changes]
CONFLICT_RESOLUTION[🔄 Conflict Resolution<br/>Merge offline work]
end
TAP --> BOTTOM_SHEET
LONG_PRESS --> FLOATING_MENU
VOICE_CREATE --> QUICK_ADD
BOTTOM_SHEET --> LOCAL_CACHE
FLOATING_MENU --> SYNC_QUEUE
QUICK_ADD --> CONFLICT_RESOLUTION
How AI agents join and participate in projects.
journey
title AI Agent Integration Journey
section Discovery
Agent scans available projects : 3: AI Agent
Analyzes skill match : 4: AI Agent
Requests project access : 3: AI Agent
section Onboarding
Human approves agent : 4: Human
Agent reads project context : 5: AI Agent
Agent identifies contribution areas: 5: AI Agent
section Contribution
Agent proposes optimizations : 4: AI Agent
Community validates proposals : 4: Community
Agent begins automated work : 5: AI Agent
section Collaboration
Agent requests human input : 5: AI Agent
Human provides creative direction: 5: Human
Agent adapts to feedback : 5: AI Agent
section Value Delivery
Agent delivers consistent results: 5: AI Agent
Human focuses on high-value work: 5: Human
Team velocity increases : 5: Team
How the system handles conflicting priorities and dependencies.
flowchart TD
CONFLICT[⚠️ Conflict Detected] --> TYPE{Conflict Type}
TYPE -->|Priority Conflict| PRIORITY_RESOLVE[🎯 Priority Resolution]
TYPE -->|Dependency Cycle| CYCLE_RESOLVE[🔄 Cycle Resolution]
TYPE -->|Resource Conflict| RESOURCE_RESOLVE[💰 Resource Resolution]
PRIORITY_RESOLVE --> COMMUNITY_VOTE[👥 Community Voting<br/>Anonymous conflict resolution]
CYCLE_RESOLVE --> DEPENDENCY_ANALYSIS[🔍 Dependency Analysis<br/>Find minimal cuts]
RESOURCE_RESOLVE --> CAPACITY_PLANNING[📊 Capacity Planning<br/>Resource reallocation]
COMMUNITY_VOTE --> WEIGHTED_DECISION[⚖️ Weighted Decision<br/>Based on expertise & stake]
DEPENDENCY_ANALYSIS --> RESTRUCTURE[🔧 Graph Restructuring<br/>Break cycles safely]
CAPACITY_PLANNING --> SCHEDULING[📅 Smart Scheduling<br/>Optimize resource usage]
WEIGHTED_DECISION --> IMPLEMENT[✅ Implement Resolution]
RESTRUCTURE --> IMPLEMENT
SCHEDULING --> IMPLEMENT
IMPLEMENT --> MONITOR[📊 Monitor Outcome<br/>Learn from resolution]
MONITOR --> FEEDBACK[🔄 Feedback Loop<br/>Improve future resolution]
How teams transition from small to large scale usage.
graph LR
subgraph "Small Team (2-10)"
S1[Direct Communication<br/>Informal coordination]
S2[Simple Priorities<br/>Personal + executive]
S3[Manual Dependencies<br/>Visual connections]
end
subgraph "Medium Team (10-50)"
M1[Structured Communication<br/>Notification system]
M2[Democratic Priorities<br/>Community validation]
M3[Automated Dependencies<br/>Smart suggestions]
end
subgraph "Large Organization (50+)"
L1[Federated Graphs<br/>Department boundaries]
L2[AI-Assisted Coordination<br/>Intelligent agents]
L3[Advanced Analytics<br/>Pattern recognition]
end
S1 --> M1
S2 --> M2
S3 --> M3
M1 --> L1
M2 --> L2
M3 --> L3
style S1 fill:#e8f5e8
style S2 fill:#e8f5e8
style S3 fill:#e8f5e8
style M1 fill:#fff3e0
style M2 fill:#fff3e0
style M3 fill:#fff3e0
style L1 fill:#f3e5f5
style L2 fill:#f3e5f5
style L3 fill:#f3e5f5
These user flows demonstrate how GraphDone's unique approach to project management creates natural, intuitive workflows that scale from individual contributors to large organizations while maintaining the core principles of democratic coordination and human-AI collaboration.