@shazow.eth

Suggestion to try when doing a release like this next time: Offer a timeline for the "experiment" or "evaluation", any timeline. Example: We're changing how channels work, this is a community experiment that we'll evaluate in 60 days, primarily looking at X, Y, Z metrics and secondary effects. Here are the changes: ... Note you don't need to shut down after N days, it just sets expectations of how things are evaluated and when we can expect some more reflection on whether the changes were good or bad. Realistically you can keep iterating, but I think people will be much more open minded about changing their behavior if framed like this. Open ended changes feel scary and arbitrary (despite you doing tons of work gathering feedback and ideas ahead of time), this gives a bit of rails for people to hold onto.

1 reply

0 recast

0 reaction