1,000 engineering tickets in Notion

TL;DR; In this post you will hear about my evolved experience running delivery teams in Notion... 1,000+ engineering tickets and 12 months of convincing teams to trust me that a GitLab integration isn’t valuable.

This is a follow up to two posts I wrote in 2020 about moving away from Atlassian and to Notion and Notion for Delivery.

Context

Since my last post, I left BCG Digital Ventures and started my own climate tech start-up Cecil Earth — We’re on a mission to help teams restore land ecosystems. Our platform connects project developers, investors and landholders to drive better outcomes for all involved.

Our current team is a fully remote with members in Spain, Estonia, India, United States and Australia. We’re a small, full stack product team with diverse backgrounds from big tech to early stage start ups.

Since writing the first line of code in May 2021, we have shipped 1,000 engineering tickets and our product is live with 4+ enterprise organisations.

What’s working

What I have always loved about Notion is the blank canvas style. A great product team is defined by their ability to embrace diversity and develop the process to work for their specific needs.

Notion empowers teams with enough structure to get started (e.g. Roadmap Template). With a few clicks you have replicated the basic functionality of JIRA to view tickets in a Kanban view and a Backlog…