Idea Implementation - Make it more structured

[Niall]

I've posted this is the IV-MP ideas and Suggestions section but I am proposing it for all servers, I just don't want to make duplicate topics.

When a person suggest an idea, a lot of people disagree, a lot of people agree and most of the time the person who started the topic never knows if the administration accepted the idea until he/she sees it in the server. It's really unorganised and we don't even know who exactly is responsible for accepting it.

At work we have this system. People fill in a card and write down an idea they have, put it in a box, at the end of the week someone collects the ideas of the week and a team of managers accept or reject at a weekly meeting. The person who suggested the idea and the person who collects the ideas work then work together to implement it. We should do something similar. I propose the system below.

1. Create different boards in each servers idea section something like the following:

- Ideas (This board is already on the forum, this is where people suggest ideas)
- Accepted Ideas
- Rejected  Ideas
- Ideas that are accepted but not possible to implement yet - Scripting restricted, This board will be revised with each new client release e.g If they are not possible in IV-MP T3 but might be in IV-MP T4.

2. Have a weekly staff meeting that includes all the servers administration(Admins, Scripters, Managers and maybe even QA Testers etc).

3. Have someone who chairs the meeting, that person is responsible for gathering all that weeks ideas, setting a time for each meeting and asking all members present at the meeting to vote on the idea, that person gathers the positive and negative votes from all the staff and tells the result. The chair of the meeting then posts in the idea topics accepting or rejecting them and moves them to the appropriate board. Scripters will then know which ideas they need to implement and which ones to ignore.

Btw it doesn't have to be every week it could be every two weeks or even month but it would build up and longer you leave the meetings the longer they will last.

[Bilbo]

Well the trouble is that ideas are suggested faster than any of them can be added to the server.
All ideas are viewed through and added to the server if they are seen to fit into our agenda and the Argonath Vision.

All ideas suggested on the board also have to get the agreement of server developers as well as community owners before they can be added onto the server.
Also, once a meeting is being held between server developers and scripters all new ideas are shared and decided upon. Last time we did this was a week or so ago when planning for Rock Stars 2.0.

[Niall]

Well the trouble is that ideas are suggested faster than any of them can be added to the server.
All ideas are viewed through and added to the server if they are seen to fit into our agenda and the Argonath Vision.

I'm not saying to add a time limit to when they need to be added, just make people aware which ones eventually will be added and which ones will not be.  Also if people see their ideas being accepted, they will feel good about it and probably suggest more.
 

At certain times a suggested idea may be rejected because it is impossible to script, but then become possible - which then would create a hassle if you want to actually keep the board organized and
ideas in places where they belong.

That is why I suggested the fourth board that I have listed.

If you assign one person do be the ideas co-ordinator for each server, he could:

 - Gather all the ideas up for each week.
 - Chair the meetings.
 - Liaise with scripters.
 - Count votes to decide outcome of idea.
 - Keep boards updated.

All ideas suggested on the board also have to get the agreement of server developers as well as community owners before they can be added onto the server.

That's why they should be in attendance of the meetings.