Deck Knight
Blast Off At The Speed Of Light! That's Right!
Approved in conjunction with Birkal*
Policy Review: Concept Driver - the Re-envisioned TL
Back in the other Policy Review Thread of Import I mentioned a proposal for re-envisioning the TL. This post will contain my proposal and begin a discussion about the role of the TL historically, what we should change, and how we should change it. I warn you, there will be a lot of background before I get to the proposal, get a drink first.
History of the TL:
Way back when in the olden days when CAP was a new forum, Cooper was our first project leader. After cobbling together a hodgepodge of threads we eventually managed to create the first CAP Pokemon, Syclant. From there, Cooper passed the baton to Hyra, who took over as we tweaked the process a little more and assembled Revenankh for playtesting in the CAP metagame. The first real topic leader wasn't established until CAP 3, where Gothic Togekiss was nominated and selected to run the next CAP Project. This was the beginning of this use for the Policy Review Committee, CAP's group of elite project members and moderators.
For CAPs 3 through 8, we had what is now referred to as the "weak TL." Basically what they would do is cull minimally from the selections put forward by the community in order to ensure maximum democracy, and exercise a minimum amount of control over managing and responding to posts in threads. Effectively they were managers of the process rather than visionaries.
The issue with this approach is that certain unscrupulous, boisterous, loud-mouthed medieval-handle-based users who shall not be named (among others) managed to gain ever more influence over various slates and choices by filling that vacuum with their own thoughts and arguments. This led to CAP 9, 10, 11, 1, and 2 being led under what is now referred to as the "strong TL." The key difference between the weak TL and the strong TL is that the strong TL was called to take a much more assertive role in taking initiative for the project and being much more discerning in slate choices to maximize competitive ability. There can be no doubt it succeeded. Colossoil and Krillowatt were so effective that a backlash occurred on how to handle the power creep that came with optimizing stats and movepool.
Under the new, more stringent regulation of stat limits and movepools along with strong TL leadership Voodoom, Tomohawk, and Necturna were created. These creations were much more balanced on paper and in practice than their predecessors.
Which brings us to today.
The Policy Review Committee as a mechanism has come under fire by various users over the years for being much less democratic than CAP is in general, and furthermore for basically being a circle of self-ingratiating praise for its own sake, picking insiders and long-timers and not necessarily following every tradition CAP otherwise embodies.
As such, I do not feel the Policy Review Committee should select a Topic Leader anymore. As to the Topic Leader itself, we had always had one because CAP tries to balance democratic means with high-quality competitive ends, and this is much easier to do when you put a single person in charge. The Topic Leader, especially in the strong model, was very undemocratic in many of the ways the position operated.
Moving Forward:
As we attempt to strike a new balance, the following thoughts come to my mind.
1. We still need to preserve the meritocracy of having someone specific as a guide and vision.
As anti-democratic as the TL position is, it's a necessary part of making sure the project doesn't lose focus. It is also the very embodiment of meritocracy, allowing users who have put a not insubstantial amount of time and effort to have a chance at shaping the next new test on the competitive metagame.
2. Moderators should remain as guides and equals to their peers, and share responsibility with topic leaders on the direction of each project.
CAP has always had a unique and special relationship between its moderators and the multitude of newcomers and creative people the project attracts. Under the new proposed system, moderators have more specific duties in each part of the process, but we should not forget that with the exception of disciplining flames, persons who don't read the FAQ, and general bad behavior, are basically on the same playing field as everyone else when it comes to submissions, polls, etc.
3. Given 1. and 2., although whatever we replace the Topic Leader with, if anything, moderators will now have generally more influence in each step of the project. We aren't just the peacekeepers anymore, but mutual facilitators who are trusted to keep the project going if there are unforeseen circumstances. The TL has been such a stressful job in the past that invariably people go through it, only to leave later for work, or family, or because we drove them bonkers. Hopefully we'll have less of that.
And so, with the background out of the way, here is my proposal for a replacement to the Topic Leader:
Concept Driver:
Concept is indisputably the most important part of CAP, especially if we're going to venture outside the OU metagame, as several proposals and arguments have suggested. Effectively what I want to do is give the person who wins the concept poll a higher level of discretion over the project's direction than they would have under the previous system. Rather than having a TL nominated by the PRC interpret a submitted concept, it will be discussed and followed-through with the source.
Pros:
1. Retains the meritocratic element of CAP, rewarding someone for having a unique or good idea that caught the attention of their peers and won in a forum-wide survey.
2. Allows the moderators to speak with the author and refine the concept into something much bigger, or more focused, or more comprehensive than it was initially, ensuring a high-quality product.
3. Removes the anti-democratic nature of the PRC process, as well as the time spent on that process since the Concept Driver will be chosen after the concept poll is complete, and the concept will be fully fleshed out in the Concept Assessment stage.
Cons:
1. People with brilliant concept ideas and people with lots of time to devote to CAP over the next two and a half months can quite easily be mutually exclusive. Even with moderators ensuring the process continues since they aren't completely reliant on a TL for a slate, it still places a significant amount of stress on anyone submitting a concept, and we don't want people to refrain from submitting because they don't feel they have the time or commitment to be a Concept Driver.
2. In such a case as 1. there are few meritocratic ways to go about finding a replacement. The person with the runner-up concept may have proposed one wildly different than the winning concept. While TL's chose ATLs in a top-down fashion, Concept Driver's out for inactivity or inability to commit is not that simple. That said, if the winning Concept Driver were to select an assistant, I don't imagine the drama level would be that high. It's still a concern.
3. While unlikely, it is possible the winning concept is really too vague for anything to be gathered out of it, even with a meeting of the minds between a potential Concept Driver and the moderators. A previous example would be something like Psychological Warfare, a concept that is interesting but has very few concrete parameters to work from. While a strong CAP project could still come out, the frustration of the process could repeat some of the problems of the TL system without the focused direction (even if thought wrong) of it.
Ultimately, I feel the Concept Driver would make for a fine experiment in replacing the TL despite some of its real and imagined drawbacks, and I seek the feedback of the Policy Review Committee in brainstorming new ideas.
- - - - -
Ballot:
Before completing your ballot, please read over the thread if you have not had the chance to follow it. The ballot motions can be vastly different in substance from the original proposal, and reading the thread provides context for how the ballot measures came to be.
Please provide a bolded YES or NO vote to each of the two motions proposed:
Motion 1:
The CAP Topic Leader Guide will be updated to
Remove the following:
Under Responsibilities:
Create and moderate all threads that pertain to the construction process—this includes polling, discussion, and submission threads
At the end of the article:
Once selected, the Topic Leader must pick an Assistant Topic Leader, whose job is to serve as a backup to the TL in cases when the TL cannot fulfill the responsibilities of the job. The ATL may also lend assistance to the TL when it comes to tallying votes and other tasks that require a lot of work.
Add the following:
At the end up the article, under a section titled Topic Leaders and Moderators:
YES
NO
Motion 2:
The Moderators will post a Topic Leader Nomination thread, and after selecting a slate of candidates, will hold a public bold vote (either IRV or direct vote depending on the number of candidates) to determine who will be the Topic Leader for the next CAP project.
YES
NO
This poll will be open for 48 hours starting from 04/01/2012, 9:00 PM EST.
Policy Review: Concept Driver - the Re-envisioned TL
Back in the other Policy Review Thread of Import I mentioned a proposal for re-envisioning the TL. This post will contain my proposal and begin a discussion about the role of the TL historically, what we should change, and how we should change it. I warn you, there will be a lot of background before I get to the proposal, get a drink first.
History of the TL:
Way back when in the olden days when CAP was a new forum, Cooper was our first project leader. After cobbling together a hodgepodge of threads we eventually managed to create the first CAP Pokemon, Syclant. From there, Cooper passed the baton to Hyra, who took over as we tweaked the process a little more and assembled Revenankh for playtesting in the CAP metagame. The first real topic leader wasn't established until CAP 3, where Gothic Togekiss was nominated and selected to run the next CAP Project. This was the beginning of this use for the Policy Review Committee, CAP's group of elite project members and moderators.
For CAPs 3 through 8, we had what is now referred to as the "weak TL." Basically what they would do is cull minimally from the selections put forward by the community in order to ensure maximum democracy, and exercise a minimum amount of control over managing and responding to posts in threads. Effectively they were managers of the process rather than visionaries.
The issue with this approach is that certain unscrupulous, boisterous, loud-mouthed medieval-handle-based users who shall not be named (among others) managed to gain ever more influence over various slates and choices by filling that vacuum with their own thoughts and arguments. This led to CAP 9, 10, 11, 1, and 2 being led under what is now referred to as the "strong TL." The key difference between the weak TL and the strong TL is that the strong TL was called to take a much more assertive role in taking initiative for the project and being much more discerning in slate choices to maximize competitive ability. There can be no doubt it succeeded. Colossoil and Krillowatt were so effective that a backlash occurred on how to handle the power creep that came with optimizing stats and movepool.
Under the new, more stringent regulation of stat limits and movepools along with strong TL leadership Voodoom, Tomohawk, and Necturna were created. These creations were much more balanced on paper and in practice than their predecessors.
Which brings us to today.
The Policy Review Committee as a mechanism has come under fire by various users over the years for being much less democratic than CAP is in general, and furthermore for basically being a circle of self-ingratiating praise for its own sake, picking insiders and long-timers and not necessarily following every tradition CAP otherwise embodies.
As such, I do not feel the Policy Review Committee should select a Topic Leader anymore. As to the Topic Leader itself, we had always had one because CAP tries to balance democratic means with high-quality competitive ends, and this is much easier to do when you put a single person in charge. The Topic Leader, especially in the strong model, was very undemocratic in many of the ways the position operated.
Moving Forward:
As we attempt to strike a new balance, the following thoughts come to my mind.
1. We still need to preserve the meritocracy of having someone specific as a guide and vision.
As anti-democratic as the TL position is, it's a necessary part of making sure the project doesn't lose focus. It is also the very embodiment of meritocracy, allowing users who have put a not insubstantial amount of time and effort to have a chance at shaping the next new test on the competitive metagame.
2. Moderators should remain as guides and equals to their peers, and share responsibility with topic leaders on the direction of each project.
CAP has always had a unique and special relationship between its moderators and the multitude of newcomers and creative people the project attracts. Under the new proposed system, moderators have more specific duties in each part of the process, but we should not forget that with the exception of disciplining flames, persons who don't read the FAQ, and general bad behavior, are basically on the same playing field as everyone else when it comes to submissions, polls, etc.
3. Given 1. and 2., although whatever we replace the Topic Leader with, if anything, moderators will now have generally more influence in each step of the project. We aren't just the peacekeepers anymore, but mutual facilitators who are trusted to keep the project going if there are unforeseen circumstances. The TL has been such a stressful job in the past that invariably people go through it, only to leave later for work, or family, or because we drove them bonkers. Hopefully we'll have less of that.
And so, with the background out of the way, here is my proposal for a replacement to the Topic Leader:
Concept Driver:
Concept is indisputably the most important part of CAP, especially if we're going to venture outside the OU metagame, as several proposals and arguments have suggested. Effectively what I want to do is give the person who wins the concept poll a higher level of discretion over the project's direction than they would have under the previous system. Rather than having a TL nominated by the PRC interpret a submitted concept, it will be discussed and followed-through with the source.
Pros:
1. Retains the meritocratic element of CAP, rewarding someone for having a unique or good idea that caught the attention of their peers and won in a forum-wide survey.
2. Allows the moderators to speak with the author and refine the concept into something much bigger, or more focused, or more comprehensive than it was initially, ensuring a high-quality product.
3. Removes the anti-democratic nature of the PRC process, as well as the time spent on that process since the Concept Driver will be chosen after the concept poll is complete, and the concept will be fully fleshed out in the Concept Assessment stage.
Cons:
1. People with brilliant concept ideas and people with lots of time to devote to CAP over the next two and a half months can quite easily be mutually exclusive. Even with moderators ensuring the process continues since they aren't completely reliant on a TL for a slate, it still places a significant amount of stress on anyone submitting a concept, and we don't want people to refrain from submitting because they don't feel they have the time or commitment to be a Concept Driver.
2. In such a case as 1. there are few meritocratic ways to go about finding a replacement. The person with the runner-up concept may have proposed one wildly different than the winning concept. While TL's chose ATLs in a top-down fashion, Concept Driver's out for inactivity or inability to commit is not that simple. That said, if the winning Concept Driver were to select an assistant, I don't imagine the drama level would be that high. It's still a concern.
3. While unlikely, it is possible the winning concept is really too vague for anything to be gathered out of it, even with a meeting of the minds between a potential Concept Driver and the moderators. A previous example would be something like Psychological Warfare, a concept that is interesting but has very few concrete parameters to work from. While a strong CAP project could still come out, the frustration of the process could repeat some of the problems of the TL system without the focused direction (even if thought wrong) of it.
Ultimately, I feel the Concept Driver would make for a fine experiment in replacing the TL despite some of its real and imagined drawbacks, and I seek the feedback of the Policy Review Committee in brainstorming new ideas.
- - - - -
Ballot:
Before completing your ballot, please read over the thread if you have not had the chance to follow it. The ballot motions can be vastly different in substance from the original proposal, and reading the thread provides context for how the ballot measures came to be.
Please provide a bolded YES or NO vote to each of the two motions proposed:
Motion 1:
The CAP Topic Leader Guide will be updated to
Remove the following:
Under Responsibilities:
Create and moderate all threads that pertain to the construction process—this includes polling, discussion, and submission threads
At the end of the article:
Once selected, the Topic Leader must pick an Assistant Topic Leader, whose job is to serve as a backup to the TL in cases when the TL cannot fulfill the responsibilities of the job. The ATL may also lend assistance to the TL when it comes to tallying votes and other tasks that require a lot of work.
Add the following:
At the end up the article, under a section titled Topic Leaders and Moderators:
- The TL is made into a project mod of CAP so that closing/deleting/etc. are available to him/her for the duration of the CAP.
- Moderators will open threads for each part of the process. Threads made by moderators start closed. The TL will be the first reply in every non-poll thread, and after their post the TL will unlock the thread for further discussion.
- The TL will close project threads with their slate.
- The TL is expected to maintain contact with moderators and alert them to any upcoming absences when possible, so that the CAP project can keep pace.
YES
NO
Motion 2:
The Moderators will post a Topic Leader Nomination thread, and after selecting a slate of candidates, will hold a public bold vote (either IRV or direct vote depending on the number of candidates) to determine who will be the Topic Leader for the next CAP project.
YES
NO
This poll will be open for 48 hours starting from 04/01/2012, 9:00 PM EST.