Notion

What do you like best about the product?

I like that Notion brings facility-related information into one place. We can organise maintenance logs, vendor details, asset records, SOPs, inspection checklists, project updates, and meeting notes in a structured way. The database and page system is flexible, so it can be adjusted for different sites or operational requirements.

What do you dislike about the product?

Setting up a useful structure takes planning at the beginning. If databases, properties, and permissions are not organised properly, the workspace can become difficult to manage. New team members may also need some guidance before they are comfortable using the system.

What problems is the product solving and how is that benefiting you?

It reduces the issue of keeping facility updates in separate spreadsheets, email threads, and documents. Having maintenance information, vendor records, tasks, and documentation together improves visibility and makes follow-ups easier. It also helps maintain a more consistent record of open issues and completed work.

What do you like best about the product?

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 place for me to plan and work on everything in one spot, without having to switch between multiple apps for different needs. I’ve performed very well because of the features Notion provides to help me manage myself, whether for personal or educational purposes. I can also share my pages with others and collaborate easily.

It also has an AI that helps with every single task - how amazing is that! I just outline what I need, and the AI creates pages and fills in the details. The UI/UX makes it easy to navigate, and the speed of the application is quite good; I haven’t faced any latency even when using the AI. Overall, this makes the product feel like it has an excellent ROI. The onboarding was also very clear, illustrative, and easy to follow.

What do you dislike about the product?

There is nothing as such that I dislike about Notion.

What problems is the product solving and how is that benefiting you?

I have benefitted majorly with my planning, scheduling and checklisting.
I have used it majorly for my academics - courses, assignments, deadlines, project timelines. I have used it for four years so far and will continue using it as long as I can.

What do you like best about the product?

The JSON integration means the AI is shockingly effective at its tasks. I am consistently impressed at how well it interprets my prompts and correctly rejects a task or reports a negative, instead of providing false information simply to satisfy a perceived want. I have not integrated it but would be VERY interested to learn whether it can read slide decks effectively for downstream annotations/citing/etc

What do you dislike about the product?

Billing structure is a little unclear, as are team organization and workspace member capabilities.

What problems is the product solving and how is that benefiting you?

Database creation and management. I use it to organize published scientific literature for personal reference and informal meta-analysis and it does a phenomenal job of that, at least from my perspective as a writer (not an AI or LLM expert by any means).

What do you like best about the product?

I run a research lab juggling four or five prototypes at once, and Notion is what keeps that legible instead of scattered. Setting up structure for a new prototype takes seconds: a linked database for specs and experiment logs, rolled up into one status view, without a separate tracker to maintain by hand. The part that's paid off most is how AI fits into that setup. We've connected Claude directly to the workspace so it reads and writes pages in place, pulling context from a prototype's history or drafting a spec without anything getting exported elsewhere first, and we've built small automations that route other LLMs into Notion through the API, so documentation happens as a byproduct of the work rather than a separate task. Notion's own AI answers questions against our existing docs, which is often the fastest way for someone new to a project to find out what we already tried instead of relying on someone's memory.

What do you dislike about the product?

Our oldest, heaviest pages start to lag once they accumulate enough embedded databases and history, and we've had to manage that by archiving finished prototypes into a lighter workspace rather than letting any single page grow indefinitely. Support has also been slow to respond once a question gets specific, such as permissions or API behavior at our scale, often slow enough that we solve it ourselves or through the community first. Onboarding new hires has been easier than that might suggest, since the structure tends to explain itself. We're on the Business/Enterprise tier with a team above fifteen people, and the value shows up less as a number and more as time we're not spending every week reconstructing context that already exists somewhere, which only grows as we run more prototypes rather than fewer.

What problems is the product solving and how is that benefiting you?

Before this, prototype knowledge lived wherever a given team member kept it: a doc here, a spreadsheet there, decisions that only existed in someone's memory. With four or five prototypes running at once, that meant every meeting started with reconstructing context instead of using it, and a new hire joining a project needed someone to walk them through history that was never written down anywhere central. Now that work sits in one workspace with linked databases per prototype, and because Claude is connected directly to that workspace, documentation gets written as part of doing the work rather than as a task someone has to remember to do afterward. When someone needs to know what we already tried, Notion AI can answer it from our own docs instead of pulling a person off their work to explain it verbally again.

The benefit compounds with how many prototypes we're running, not how many we used to run. A status update that used to take a recurring meeting now takes a glance at a rolled up view, and onboarding a new person onto an existing prototype takes a fraction of the time it used to, since the context is already sitting there searchable rather than locked in someone's head. The clearest measure is time we're not spending: fewer meetings that exist purely to re-explain where something stands, and less of a tax every time our headcount or prototype count grows.

Recommendations to others considering the product:

Before this, prototype knowledge lived wherever a given team member kept it: a doc here, a spreadsheet there, decisions that only existed in someone's memory. With four or five prototypes running at once, that meant every meeting started with reconstructing context instead of using it, and a new hire joining a project needed someone to walk them through history that was never written down anywhere central. Now that work sits in one workspace with linked databases per prototype, and because Claude is connected directly to that workspace, documentation gets written as part of doing the work rather than as a task someone has to remember to do afterward. When someone needs to know what we already tried, Notion AI can answer it from our own docs instead of pulling a person off their work to explain it verbally again.

The benefit compounds with how many prototypes we're running, not how many we used to run. A status update that used to take a recurring meeting now takes a glance at a rolled up view, and onboarding a new person onto an existing prototype takes a fraction of the time it used to, since the context is already sitting there searchable rather than locked in someone's head. The clearest measure is time we're not spending: fewer meetings that exist purely to re-explain where something stands, and less of a tax every time our headcount or prototype count grows.

What do you like best about the product?

Notion is a great knowledge database, and it feels far superior to Salesforce when it comes to quickly finding information or related articles for specific tasks in the customer support and insights industry. My company is paying for Notion, and so far, my experience has been positive. The AI features included in the paid version are good but still need some improvement. Overall, I believe this was a worthwhile investment of the company’s resources.

What do you dislike about the product?

The writing tool feels somewhat limited and isn’t very intuitive to use. The AI feature doesn’t always return accurate feedback when I search for something, so I often end up having to look up the information manually.

What problems is the product solving and how is that benefiting you?

We have a large, cross-functional team, so having a wiki where our entire knowledge base lives in one place is a big plus. It also helps that we can follow consistent patterns for finding and updating articles, macros, or projects, which makes sharing and maintaining information much easier.