We're done with Notion

Key Concepts:

• One-app-to-replace-them-all approach: Notion's strategy of offering a wide range of features.
• Half-baked features: The critique that Notion's new features are often incomplete or not fully functional.
• Notion API: The interface used to interact with Notion programmatically.
• Spaghetti mess: A term used to describe the complex and disorganized nature of their current Notion setup using the API.
• Self-hosting: Hosting software on one's own servers instead of using a third-party service.
• Plane: A project management tool.
• Noodb: A database solution.
• Doc most: A tool for internal documentation.
• Strappy: A headless CMS (Content Management System) used for blog posts and newsletters.

Problem with Notion's "One App to Replace Them All" Approach

The core issue highlighted is Notion's attempt to be a comprehensive solution for various needs, which the speaker argues is often problematic. Despite the excitement generated by new updates like calendar, forms, analytics, and automation, the speaker expresses disappointment upon closer inspection. These features are described as "half-baked" and not genuinely useful.

• Example: The speaker cites the automation feature, specifically the ability to create Slack notifications and change statuses, as an example of a feature that falls short of expectations.

Dependence on Notion API and Resulting Complexity

The speaker's team has relied heavily on the Notion API to perform essential operations. However, this reliance has led to a complex and disorganized system, described as a "spaghetti mess." This complexity is a key driver for their decision to migrate to other tools.

Migration to Specialized Tools

The speaker details their transition from Notion to a suite of specialized tools, each designed for a specific purpose:

• Project Management: Moving to "Plane."
• Databases: Switching to "Noodb."
• Internal Documentation: Adopting "Doc most."
• Blog Posts and Newsletters: Implementing a custom solution with the "Strappy" CMS.

Self-Hosting and Cost Savings

A significant aspect of this transition is the decision to self-host all the new tools. The speaker emphasizes that these tools are free because they are self-hosted.

• Practical Advice: The speaker suggests that even non-developers can set up self-hosting by hiring someone on Upwork for a one-time fee, resulting in long-term cost savings.

Conclusion

The speaker's experience suggests that while Notion offers a wide range of features, its attempt to be a "one-app-to-replace-them-all" solution can lead to limitations and complexities. The speaker's solution is to migrate to a suite of specialized, self-hosted tools, offering greater control and potentially lower costs. The key takeaway is that choosing the right tool for the job, even if it means using multiple tools, can be more effective than relying on a single, all-encompassing platform.