I really like this!
From a more general perspective, having guidelines about how you think about the project and what direction you want to take it is a really helpful metric for deciding whether to accept or reject a feature request, and gives you a very clear way to communicate why you might not be including someone’s idea.
My thoughts on the specific traits themselves:
-
Duh. This is very clear and makes super sense.
-
I can see this being an area where it might be hard to figure out what counts as following the trait or not. A lot of GMs who use similar tools are probably often hardcore power users, so I can imagine them wanting a lot of things that would not be user friendly. But maybe (a justification might go) if features are hidden in an “extra features” panel then it’s not preventing people from “getting started in moments”. I guess I’m curious how you’re planning on preventing feature creep that could be argued to not be preventing ease-of-use, which then turns into “you really need to use the extra features in order to get anything out of it”. Maybe you’re totally against special “power-user features”? Or maybe there’s some balance that will just take some time to figure out?
-
I really like the analogy, I think it demonstrates what you’re thinking well. I think this is probably the place where you’re going to get a bunch of feature requests and going to have to say no.
