Product Capabilities
This layer helps you keep the narrative clean: ask the right questions, involve the right people, and articulate value in business language.
Questions
- What capabilities unlock the operational gains above?
- What data is needed to make decisions fast?
- What needs to be automated to scale?
- What must be observable, measurable, and governed?
- What integrations and constraints exist?
Relations
- Architects
- Platform engineering
- Data / Analytics
- Security & compliance
- Tech leads / power users
Value
- Visibility & decision speed
- Automation & self-healing
- Governance & control
- Cross-team alignment
- Consistency across environments
Signals to look for
- Hiring surges (Eng/Platform/Data/Security)
- New executive hires or re-orgs
- Pricing changes / packaging shifts
- Major product launches
- High-profile outages or trust events
Metrics to watch
- Activation → Adoption → Expansion
- Retention / churn drivers
- Release frequency & lead time
- Incident rate & MTTR
- Unit economics: CAC, LTV, gross margin
Talk-track template
- Context: what changed in the business / market?
- Impact: what cost / risk / delay does it create?
- Decision: what must be true to win?
- Next step: define a proof + timeline.
Obsidian note structure
Create one note per layer and keep the same headings: Questions • Relations • Value. Your vault becomes a consistent thinking system.