1. Overview Problem StatementProposed Work2. Stakeholders, Dependencies & RisksStakeholdersDependenciesRisks 3. Success Criteria
1. Overview
Problem Statement
A brief description of the problem we're trying to solve. Why is this valuable to work on?
- Users want to associate database columns with columns in other databases on Notion.
- This is valuable because it would make Notion more powerful for all users.
Proposed Work
A high-level overview of what we're building and why it will solve the problem.
- Add a new complex property type to databases that points to columns in other databases.
2. Stakeholders, Dependencies & Risks
Stakeholders
Who are the critical internal stakeholders?
- Leslie Jensen - how would this impact product growth and user retention?
- Harrison Medoff - what would design for the relational view look like?
Dependencies
What are the dependencies? Include both internal (other teams) and external (partners).
- Design signoff
- Engineering signoff
Risks
What are the risks?
- Increased product complexity for databases.
3. Success Criteria
What criteria must be met in order to consider this project a success?
- Once this project is complete, document editors will be able to relate database properties in database A to a separate database property in database B. We expect this to lead to overall increased user retention.