Usage of the current TID (tom.riik.ee) has been analyzed from the technical side: number of users, number of ideas, answered ideas etc. Although these could be considered valid indicators of success we need to go deeper to understand what participants (both citizens and civil servants) expect from an application like TID and does it perform in expected way or could it be changed to perform in a way that helps to mediate involved parties with minimal effort and friction.

TID provides us with ca 900 ideas from past years that can be used to understand typical issues citizens would like to influence using a system like this. Categorizing them together with answers from state (where present) should provide us with information about present success and conflicts -- which kind of ideas have received positive answers, which have been dismissed, which could have gone to second round with change of wording etc.

Methdodology described below is based on Peeter's hypothesis, if anybody wishes to propose different approach please feel free to do so, starting with your own hypothesis.

Peeter's hypothesis

• few ideas have had real effect (weak wording of idea, friction)
• a lot of repeating issues (no easy tools to track what has been already proposed)
• answers are not taken further (does it answer the proposal? should the idea be reformulated? etc)
• serious pain to use for both citizens and state
• we need to ease the pain and provide a tool that ensures effective communication for both parties

Proposed methodology for analysis

• tag tom.riik.ee ideas for subject, participation, voting result, if answered, result of answer etc (using URL-tagging tool like del.icio.us; tagsonomy to be decided based on reviewing sample set of ideas)

• filter out "junk ideas" (offensive etc)

• group by subject, group repeating ideas to find typical topics

• group by result of answer to find topics that are more likely to get solution or dismissed, determine typical reasoning for dismissal (already solved by law? solution would be unconstitutional?)

• identify ideas that have passed current TID and received positive answer, describe reason of success or interview participants to understand

• identify 10 ideas that have passed current TID, have sizeable support and good reasoning but have been dismissed with formal answer; interview participants to understand reasons and find possible ways of improvement

Result of analysis

Result of analysis should describe the scope of ideas that have higher probability of success and possible ways of improving success rate and should be used to describe usage scenarios for both software development and documenting it.

 Create your own business wiki!Help Add to Del.ici.ousPublic, not yet premium Privacy Policy RSS