00ohDstruct, on 24 July 2014 - 04:23 PM, said:
Dear PGI, Why so vague about new module slot functionality?
Sincerely, Those of us who are tired of guessing games and reading conjecture.
(re-sized an snipped, because if you haven't read the OP, it fills up two screens above)
In my observation ... part of the problem is that PGI has a different yardstick for measuring "successful communication". Their "let's get some community feedback" process seems to be ...
(1) Float an idea (like a revamped module system) and see what the community thinks
(2) Watch the forum firestorm for a few days, sort out the good ideas, positive and negative feedback, ignore as much extra noise as possible
(3) (new step added this year) if something is particularly contentious or if there's a nugget of brilliant wisdom in the feedback, acknowledge it and return to step (2)
(3.a.) Forum firestorm continues
(4) When it makes the agenda at a scheduled meeting (this might take a few weeks), revise the design document
(4.a.) Forum firestorm starts dying off
(5) Start programming the change (this might take weeks)
(5.a.) New issue replaces previous forum firestorm, excpet for guys who just can't stop bitching about it, or those who keep a list of all the things they've ever bitched about and just won't get over it
(6) QA testing (this will take weeks)
(7) Build into patch
(8) If it's a big change, document it in patch notes or a Command Chair post
(9) Go back to step (2)
Part of the problem is patience. This particular thread is only three days old, and they've already fixed, kind of, my biggest gripe, which I sincerely appreciate. I do wish the process was faster, and that they would communicate with us more, but I would rather that they spend more time actually doing development work than talking about it (although I sincerely appreciate it when they do talk to us about it).
For the record, I completely agree with Cimarb that PGI has improved in this area, but still has a way to go.