...
Step 1: Identify Product Phenomena | ||||
Phenomenon Type | Description | |||
Digital | Uses patented technology to linguistically analyze and compare aggregated compliance requirements across different documents | |||
Step 2: Identify Canonical Use Case | ||||
Core Product Capabilities | Top Use Cases (across all capabilities) | |||
|
| |||
Product + Phenomenon | Canonical Use Case | Main JTDB | Ideal User | |
CCH: Uses patented technology to linguistically analyze and compare aggregated compliance requirements across different documents | Compliance professionals can create custom portfolios of compliance requirements to fulfill compliance initiatives | Identify and analyze external compliance requirements to include in their compliance framework | Compliance manager | |
Canonical Case Orientation | ||||
Horizontal | ||||
Step 3: Identify Brand Insight | ||||
Brand Insight How does product phenonomon applied to the canonical use case improve User’s JTBD or reduce pain or add gain to the user? | ||||
Compliance Professionals find it difficult and time consuming to identify and compare all the compliance requirements from across different compliance documents. | ||||
Step 4: Build Product Offering | ||||
Core Product | Pricing | Commercial Terms | Services - Integration, Support, etc. | Network | Marketplace |
Core Product | Differentiated Offering Element 1 | Differentiated Offering Element 2 | ||
Step 5: Define Brand Promise | ||||
Step 6: Align GTM Trade-offs of Product Offering | ||||
Thickness | Coupling | GTM Tradeoff Quadrant | Why do you think so? | |
Your Current Product Offering | Select thickness | Select coupling | Select GTM Quadrant |
|
Product Roadmap - Implications
| Summarize here | Summarize here | Summarize here |
|
...