Key Finding
Effective collaboration tools must balance three competing needs: simplicity for user adoption, support for fast informal interaction between people, and intelligent automation of information capture. The tendency to prioritize process over people is a primary adoption blocker.
Dimension 1: Ease of Use for Adoption
Why It Matters
- Barrier to participation: Complex tools discourage participation and create friction
- Adoption blocker: High cognitive load delays adoption and limits effectiveness
- Contributor experience: Contributors (not just coordinators) need intuitive interfaces
- Strategic visibility: Simple tools enable better understanding at strategic/tactical levels
Design Principle
Simple and intuitive for contributors — the primary users who spend most time in the system should find it easy to participate without extensive training.
Example: Marijn’s Perspective (Novum)
- Emphasis on simplicity and intuitiveness as foundation for adoption
- Contributors need clear, easy paths to participation
- Complexity is acceptable at management/coordination level if hidden from contributors
- Simplicity enables adoption at scale
What to Avoid
- Over-engineered features that add process without adding value
- Terminology and mental models misaligned with how teams actually work
- Steep learning curves that create adoption resistance
Dimension 2: People-Driven, Not Process-Driven
Core Insight
Collaboration is fundamentally people-driven. Process, structure, and tools are secondary to human connection and informal interaction. The most important platform capability may not be a formal process at all—it’s enabling people to connect.
Critical Capability: Fast, Informal Interaction
Core need: Ability to quickly and easily ask questions and connect with others
Why it matters:
- This is at the core of effective teamwork
- Formal processes often impede rather than enable this
- Informal channels are often more effective than formal ones
- Early collaboration happens through questions and connections, not through process steps
Platform opportunity:
- Easy visibility: Who is working on what? Who has expertise in X?
- Frictionless communication: Asking questions should be easier than researching documentation
- Network visibility: Understanding who knows whom and who has worked together before
- Relationship building: Tools that support relationship formation and maintenance
What This Means
- Prioritize enabling informal interaction over enforcing formal process
- Make asking questions and connecting trivially easy
- Reduce friction in communication pathways
- Support serendipitous connections and knowledge discovery
What to Avoid
- Requiring formal process steps before collaboration can begin
- Making it harder to ask a question than to figure it out alone
- Hiding people and expertise behind formal structures
- Over-structuring what are inherently informal interactions
Dimension 3: Smart Information Capture & Automation
The Opportunity
While collaboration remains people-driven, there is opportunity to reduce burden on people for information management through intelligent capture and partial automation.
Current State: Manual Burden
- Much time spent manually creating reports and updating status
- Information is scattered across multiple tools and formats
- Knowledge is often lost when projects end or people leave
- Significant effort required to make information discoverable and reusable
Automation Opportunity
Capture from natural interaction:
- Extract commitments, decisions, learnings from conversations and meetings
- Update project status from team activity rather than requiring explicit reporting
- Capture lessons learned as they emerge rather than as formal post-project exercise
- Reduce “one more thing” syndrome
Make knowledge accessible:
- Searchable repository of past decisions, approaches, lessons
- Enable easy discovery of relevant past experience
- Reduce reinvention and rework
- Support pattern recognition across portfolio
Reduce process burden:
- Automation should simplify work, not add process steps
- Information capture should be byproduct of natural collaboration, not separate task
- Reporting should be generated, not manually created
Design Principle
Automate what can be automated; only ask people for information that requires human judgment or that they have not yet provided.
What to Avoid
- Automating in ways that add more work (e.g., “please confirm this automated capture”)
- Treating automation as an excuse to collect more data
- Over-capturing information that will never be used
- Requiring structured data entry as price of participation
Integrated Approach
Hierarchy of Design Principles
- Ease of use comes first: If tool is too complex, nothing else matters—adoption will fail
- People connection is central: Enable informal interaction before requiring formal process
- Automate to reduce burden: Only after first two are working, use automation to simplify further
Practical Implication
The most valuable feature may be the simplest: “Who is working on X?” “Can I connect with them?” This simple capability, executed beautifully with low friction, may enable more collaboration than elaborate process and reporting frameworks.
Related Insights
- Innovation collaboration is fundamentally relational, not systemic
- Facilitator role is multifaceted and highly demanding
- Three structural collaboration modes emerge across practice
- Portfolio managers need better tooling for helicopter view and lessons capture