← All selected work
Product architecture
A durable editor path for an AI-enabled collaborative product
Challenged a risky implementation direction with a roadmap, estimates, prototype, and an executive decision package.
Primary evidenceC-level
decision and delivery
Situation
What the system needed to change
A Notion-like product needed rich editing, collaboration, and future AI integration. The current editor direction was accumulating DOM and extensibility problems.
Constraints
The boundaries mattered.
- 01
The product already had working editor behavior
- 02
A change affected roadmap, collaboration, and AI capabilities
- 03
Leadership needed evidence rather than a purely technical opinion
Decisions
The important engineering choices
- Compared the current Quill path with a Tiptap-based architecture
- Built a demonstration and migration roadmap
- Presented product, engineering, timeline, and cost tradeoffs to the CTO, CPO, and CEO
- Improved current rendering behavior while the longer-term decision was evaluated
Outcome
What the work left behind
- Turned an engineering concern into an executive product decision
- Reduced heavy editor rendering and DOM work in the existing implementation
- Created a clearer path for collaboration and AI-enabled editing