Users are treating feature request tracking as a workflow bottleneck, often over-engineering tools like Notion instead of solving the core problem, indicating a need for simpler, purpose-built solutions.
Users acknowledge that Notion's flexibility leads to system perfectionism, which distracts from actually solving the problem, suggesting a market gap for a more guided, less customizable tracking tool.
Snapshot context
What makes this snapshot distinct
This snapshot is distinct because it combines reddit + g2 evidence within last 15 days, with 4 quote-backed signals around Feature Request Tracking remains a workflow bottleneck. It also references related products such as feature request tracking.
Most important finding
Users acknowledge that Notion's flexibility leads to system perfectionism, which distracts from actually solving the problem, suggesting a market gap for a more guided, less customizable tracking tool.
Suggested focus
Watch for user discussions on switching from Notion to dedicated feature request tools, and for feedback on the complexity of setup versus the value delivered.
AI feedback clusters
Over-engineering and system perfectionism
Users report that they and others often get caught up in perfecting their Notion setup instead of actually using it to solve the problem, leading to convoluted systems.
“The problem with Notion which has happened to me as well, is that most people try to perfect the system rather than actually solving the problem with the solution they thought they would get by using Notion lol so then people create all these convoluted”
Need for proper funnel tracking
A user mentions the need to track onboarding and paywall funnels properly to identify drop-off points, indicating a gap in current tracking methods.
“yeah i think that’s exactly what’s happening. gonna track the onboarding + paywall funnel properly and see where people are dropping instead of guessing.”
AI root-cause hypothesis
The root cause may be that general-purpose tools like Notion lack built-in guardrails, causing users to spend excessive time on configuration rather than on the actual feature request workflow.
Product implications
Simplify the onboarding and setup process, offering templates that work out-of-the-box to reduce the urge to over-customize.
Highlight the ease of use and immediate value of your tool compared to the complexity of DIY setups in Notion.
Focus on a niche solution that solves the core tracking problem without requiring extensive setup, appealing to users frustrated with Notion's complexity.
Source evidence supporting this signal
“yeah i think that’s exactly what’s happening. gonna track the onboarding + paywall funnel properly and see where people are dropping instead of guessing.”
“The problem with Notion which has happened to me as well, is that most people try to perfect the system rather than actually solving the problem with the solution they thought they would get by using Notion lol so then people create all these convoluted”
“Native Notion can get fairly close if the dashboard is treated as a navigation layer: keep one source database, then use linked views filtered to favorites, recent items, and each platform/category. Rollups and formulas can handle counts and simple stats,”
“I love that I can organize my schedule and plan my projects, assignments, and courses effectively. I’m able to integrate multiple applications into Notion (for example, a calendar), which helps me keep track of my availability and workload. It’s the best”feature request tracking· g2