Context Map

Purpose

A Context Map captures the external landscape surrounding a project, product, or organization. By mapping trends, forces, stakeholders, constraints, and uncertainties in a single visual, the team creates a shared understanding of the operating environment — essential before defining strategy, setting priorities, or launching initiatives.

At a glance

• Group size: 4–12
• Duration: 30 minutes
• Difficulty: Beginner
• Facilitation style: Guided collaborative mapping
• Setting: In-person or virtual

How to run

1. Place the project at the centre (2 min). Write the project, product, or organization name in the centre of a large canvas.
2. Define categories (3 min). Arrange sectors around the centre: Economic trends, Technology, Regulation, Competitors, Customer behaviour, Internal culture, Political/social forces.
3. Brainstorm contextual forces (12 min). Participants write one force per sticky note and place it in the relevant sector. Encourage both obvious and non-obvious forces.
4. Discuss and connect (8 min). As a group, identify the most impactful forces. Draw connections between forces that reinforce or counteract each other.
5. Implications (5 min). For the top forces, ask: “What does this mean for our project? What should we do about it?”

Materials needed

• Large paper or digital whiteboard
• Sticky notes and markers
• Pre-drawn sector template (optional)

Pitfalls & common mistakes

• Listing only the obvious. Push past “our competitors” to subtler forces like cultural shifts or regulatory changes.
• No prioritization. Not all forces matter equally. Highlight the top 5 that most affect the project.
• Treating it as a one-time exercise. Review and update the context map quarterly.

Inclusion & accessibility

• Explain each sector aloud before brainstorming.
• Allow written and verbal contributions.
• Share the final map in accessible digital format.

Variations

• PESTLE overlay: Use Political, Economic, Social, Technological, Legal, Environmental as sectors.
• Trend radar: Plot forces by time horizon (now, near, far) and uncertainty level.
• Competitive context map: Focus specifically on competitive forces (Porter’s Five Forces overlay).

When NOT to use this

• When the team needs to focus inward on execution rather than scanning the environment.
• When the external context is stable and well-understood by all.

Source & further reading

• Gray, D., Brown, S., & Macanufo, J. (2010). *Gamestorming.* O’Reilly Media.
• Osterwalder, A. & Pigneur, Y. (2010). *Business Model Generation.* Wiley.