Profiling Key Entities
Understand each key ecosystem entity's real-world context, goals, growth potential, and capabilities
Strategic intent: Beyond knowing who the entities are, build deep empathy for each one — their environment, their goals, their growth trajectory, and the resources they bring.
Overview
After the Ecosystem Canvas has identified the key entities, this technique deepens the understanding of each one. You produce two complementary views per entity:
- An Entity Portrait — context, goals, potential, and participation gains
- A VRIO Analysis — how the entity's resources fare against Value, Rarity, Imitability, and Organizational support
Together these views reveal what each entity needs from the platform, what they bring to it, and where the strongest leverage points are.
When to use it
- After completing the Ecosystem Canvas
- When the team is making assumptions about "what users want" without evidence
- Before designing motivations and value exchanges (you need entity profiles to reason about motivations)
- When considering which entity to prioritize in MVP design
Composition
This technique uses two canvases in sequence:
Step 1 · Entity Portrait
For each key entity (PC, PP, PA), create a portrait covering:
- Context — environment, tools, constraints, daily reality
- Goals — explicit aspirations and latent needs
- Potential — growth trajectory and possible evolution
- Participation Gains — what the platform enables across convenience, reach, and evolution
Canvas: Entity Portrait Canvas · Duration: 3–5 hours per entity
Step 2 · VRIO Analysis (optional but recommended)
For your own entity (the platform owner) and for any entity offering critical resources, run a VRIO analysis:
- Valuable — does the resource enable the entity to capture/create value?
- Rare — is it controlled by few?
- Imitable — how hard is it to replicate?
- Organized — is the entity organized to exploit it?
Canvas: VRIO Analysis Canvas · Duration: 3–5 hours
Inputs
- Required: the Ecosystem Canvas with entities and platform roles assigned
- Recommended: interview transcripts, ethnographic notes, or research data for each entity type
- Recommended: internal documents on capabilities (for VRIO of own entity)
Outputs
- Enriched Entity profiles — each entity now has context, goals, potential, gains
- VRIO assessment — clarity on which resources confer durable competitive advantage
- A list of opportunity hypotheses for each entity, framed as "the platform could enable X to achieve Y by providing Z"
Process heuristics
Use real interviews when possible. A portrait based on assumptions becomes an exercise in confirmation bias. If you can't interview, mark the assumptions explicitly so you can validate later.
- One portrait per entity type, not per individual — if "Specialist Physicians" is a cluster, build one portrait for the cluster
- Capture the messy reality, not your idealized version — what frustrates them today, not what should frustrate them
- Distinguish explicit goals from latent needs — the gap between the two is often where platform value lives
- Cover at least 2 of 3 gain dimensions — convenience, reach, evolution. One alone is rarely enough
Validation criteria
- Each PC, PP, and PA entity has a portrait (Stakeholders and Owner are optional)
- Context is grounded in specific evidence, not generic assumptions
- Goals include both explicit aspirations and latent needs
- Participation gains cover at least 2 of 3 dimensions
- Growth trajectory ("Potential") is articulated, not skipped
Common mistakes
- Too generic — "they want value" is not a portrait
- Confusing your wants with theirs — what you want them to want is not what they actually want
- Skipping the Potential section — designing for a frozen moment misses the trajectory
- One portrait for multiple distinct roles — if your "Producers" cluster contains both indie creators and professional studios, split them
Used in pipelines
- Understanding Ecosystems — as Phase 2
Connections
- Requires: Scanning & Mapping the Ecosystem
- Feeds: Platform Value Propositions
- Complements: Wardley Mapping (used in scanning) — both shed light on competitive dynamics