SOLVE Together: Collaborative Methods for Complex Challenges
Overview:
“SOLVE Together” is a framework for tackling complex, multi-stakeholder problems by combining structured problem-solving methods with collaborative practices. It emphasizes shared understanding, distributed ownership, iterative learning, and tools that surface diverse perspectives.
Core principles
- Shared purpose: Align stakeholders on a clear, measurable outcome.
- Diverse perspectives: Include people with different expertise, backgrounds, and lived experience.
- Psychological safety: Create an environment where participants can speak up, admit uncertainty, and challenge assumptions.
- Iterative learning: Use short cycles (hypothesize–test–learn) rather than one-shot plans.
- Transparent decision rules: Define how decisions are made (consensus, consent, expert, leader’s call) up front.
Key methods & tools
-
Structured framing
- Problem statement templates (context, stakeholders, constraints, success metrics).
- Stakeholder mapping to reveal power, interest, and influence.
-
Divergent + convergent sessions
- Divergent: brainstorming, design sprint ideation, affinity mapping.
- Convergent: dot-voting, impact/effort matrices, RICE prioritization.
-
Facilitated workshops
- Timeboxed agendas, clear roles (facilitator, scribe, timekeeper), and visual artifacts (Miro/Whiteboard).
- Pre-read materials and warmed-up stakeholders to maximize session effectiveness.
-
Prototyping & small experiments
- Rapid, low-fidelity prototypes or pilots to test assumptions.
- A/B tests, smoke tests, concierge MVPs to gather real-world feedback.
-
Decision frameworks
- DACI/RACI for clarity on responsibility.
- Clear escalation paths and criteria for course correction.
-
Communication rhythms
- Regular check-ins, sprint reviews, and asynchronous updates to maintain alignment.
- Publicly accessible logs of decisions and learnings.
Roles & governance
- Core team: Drives experiments, maintains backlog, reports progress.
- Advisory group: Domain experts who review major decisions.
- Community/operational stakeholders: Provide input, validate feasibility, and help adopt solutions.
- Facilitator/coach: Keeps process on track and manages group dynamics.
Typical process (6–8 weeks example)
- Week 1: Align on problem, success metrics, and stakeholders.
- Week 2: Research—interviews, data review, stakeholder mapping.
- Week 3: Ideation—divergent sessions and idea clustering.
- Week 4: Prioritization and selection of experiments.
- Weeks 5–6: Run pilots or prototypes; collect quantitative and qualitative data.
- Week 7: Synthesize results; decide scale vs. iterate vs. stop.
- Week 8: Document learnings and hand off to implementation or next cycle.
When to use SOLVE Together
- Problems spanning multiple teams or organizations.
- High uncertainty where assumptions need quick testing.
- Situations requiring buy-in from diverse stakeholders.
- Efforts that involve social, technical, and organizational complexity.
Risks & mitigations
- Groupthink: Mitigate with anonymous idea collection and external dissenting reviews.
- Scope creep: Use strict timeboxes and success criteria.
- Slow decisions: Set decision rules and keep small empowered teams for rapid experimentation.
Quick checklist to start
- Define a single measurable outcome.
- Invite 6–12 participants with varied perspectives.
- Assign a facilitator and scribe.
- Plan a 2-hour kickoff with pre-read materials.
- Choose 1–2 assumptions to test in the first two weeks.
If you
Leave a Reply
You must be logged in to post a comment.