Sorry but your questions are off-topic and frame the feature I proposed in a negative way.
Although this doesn’t sound like you are genuinely curious and are welcoming sane discussion around the issue, I can still elaborate a little bit for the readers.
First of all, this is nowhere being a question about trust. We don’t have any such issue, and I’m not asking for any help with establishing trust in the team, and am not interested in any discussion digression in that direction.
Secondly, I do know that checking a checkmark equals editing a post. This doesn’t automagically make my request invalid or useless.
So, to address your question (that I for some reason found a little bit insulting and questioning our internals rather than the technicalities of the proposed subject matter):
-
it is an extra step to make some post a wiki; and it is easy to forget too, which is happening quite often to me;
-
making all posts with checkboxes wikies is conceptually incorrect; but that’s what I have been doing in the absence of a better way to do it
-
my ask is for the workflow that we found out to be very natural, enjoyable, useful, and having minimum noise; while sharing the workflow itself, I’m proposing some improvements to checkboxes that we empirically found out could be useful
-
it is not about trust and/or micromanagement; checkboxes are about having a tool that makes everyone plan while discussing, and then execute while being more confident that nothing is missed/lost/forgotten. Had not I put those checkboxes in places, the team mates would have to go through the conversation on themselves, and simply create those checkboxes somewhere on the side, linking back to the forum posts; and also distract everyone in some other channel by posting messages like “done this and done that”.
Hope this clarifies things much better.