[tracyhenry]

I had to stop reading after the first three bullet points. Maybe the rest is reasonable, but first...

When sharing to colleagues you get to choose if you allow them to edit/comment/view. That, to be honest, is the first thing I check when I share docs (be it Google Docs, Quip or Notion). I won't rely on the defaults of the software because it's too costly to not get it right.

Second, you don't have to lock the document. As long as you disallow editing, you as the owner of the document still can edit the document. Am I missing something?

Third, notifications shoot as soon as you enter colleague names. I get this might be annoying at first. But don't many great UX stuff need some kind of getting-used-to? When switching from Windows to OSX, I was shocked that you get to rename a folder when you hit ENTER, rather than open it. Guess what? I got used to it. I have my alternative to opening a folder and it's not slower. In this notification case I'd then just see entering the colleague names as the last step. Problem solved.

All the first three bullet points are not inherent bad UX issues "built into the DNA" as claimed by OP. Notion is great. It's more powerful Google Docs and easy to use in general. The article is written in a way as if the author has not had any positive experiences from using Notion. That's unfortunate.

[SCLeo]

OP does not want to disallow their colleagues from a editing a page altogether. They want to prevent accidental edits.

[tracyhenry]

I think it's apparent that OP wants to disallow editing but allow commenting (see quotes down below). Notion provides exactly this feature when you share a doc but OP seems to have missed it and instead uses "lock a document" to do what he wants, which created all the problems in the first two sections. This feature is easy to find and is similar to what Google docs offers and so fairly learnable.

> First thing you learn when getting used to Notion is that every page you share should be locked from editing!

> The next problem with edit lock is that you can't unlock the page just for you. So you are a good user of Notion and keep all pages locked from editing. But every time you want to modify a page, you unlock it and everyone can (unintentionally) modify it while you're editing.

> Adding or editing content isn't the only case when you need your page to be unlocked. It is impossible to add comments on locked page.

^^^ These quotes are all wrong. You don't lock your document. When you share a doc, configure the access rights (edit/comment/view only, similar to what you do when sharing a Google doc).

[g7r]

No, I don't want do disallow editing. I do want to allow it but protect the content from accidental edits. Every time I publish a Notion page and forget to lock it, it is being accidentally modified. Some people notice it and undo. Some don't. In the combination with useless page history it is very difficult to reason whether the edit was accidental. The page could remain in accidentally modified state for a long time until author notices it.

[tracyhenry]

Does "lock it" both allow editing and prevent accidental editing? What's the magic going on that distinguishes between real edits and accidental edits?