In France, participatory democracy is constantly developing. Today, over 50 cities have adopted a participatory budget, and a large number have also launched citizens’ assemblies. Direct Democracy, however, remains a taboo.
Through the attempt made by the Grenoble City Council in 2016 to experiment with Direct Democracy, it is possible to identify the obstacles that several cities might encounter in testing such a project. It was eventually cancelled by an administrative court for several reasons, some of which are specific to French law. But there were also political obstacles.
The most obvious obstacle is the loss of power of political decision-makers: as long as it is only about consultations on limited subjects, elected officials have the last word and the systems of citizens’ participation can be designed as an aid to the decision-making process. But a system that allows for binding decisions on all subjects becomes an instrument of contestation or even counter-power.
In Grenoble, this obstacle, however, proved relatively easy to overcome. The coalition, led by the Greens, that had won the majority had done so for the first time. Most newly elected officials were more used to challenging power than to exercising it. Yet, two fears were particularly persistent: first, the fear of being forced, by a vote, not to respect the programme they had announced during the campaign. Some considered this aspect not very threatening, as long as their own voters were willing to take this risk. Others, however, saw this possibility as a real danger, so they advocated, without success, for the issues of their programme to be excluded from the popular vote. The second fear was that the opposition parties – already largely critical of the new team – would use this tool to delegitimise the majority.
Both fears however proved to be unfounded. On the one hand, the two petitions that were put to vote in this context were intended more to force the majority to respect their programme than to abandon it. On the other hand, the right-wing opposition, which had launched four petitions to challenge the majority previously, withdrew them all when the programme was put in place. The new majority then discovered that by giving the opposition tools to challenge, it made them more responsible: the opposition could no longer challenge everything, otherwise it would be systematically disowned by the voters.
All the same, these two fears led to a system where it was simple to trigger a vote, but very difficult to win it, mainly because of an approval quorum: to win a vote, the “yes” vote had to have at least as many votes as the majority had received in the previous elections. This is a very strong requirement for a vote, especially for a new system. During the vote, no one was surprised that the vote largely failed because of the quorum. Even before the judge got involved, the system was in danger of dying because, by leaving too few chances of winning to the petitioners, it discouraged them from using this instrument. Despite this failure, the public inquiry and vote gave great visibility to the city of Grenoble, which remains a pioneer in direct democracy in France.
XThis website uses cookies. Some cookies are necessary for the proper functioning of the website and cannot be refused if you wish to visit the website.
Other cookies are used for Advertisement and Analytics (Sharing on social networks, video playing, analysis and statistics, personalized advertising ...) You can refuse them if you want to. REJECTACCEPTCookie settings
Manage consent
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
csrftoken
past
This cookie is associated with Django web development platform for python. Used to help protect the website against Cross-Site Request Forgery attacks
JSESSIONID
session
The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
__cf_bm
30 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
S
1 hour
Used by Yahoo to provide ads, content or analytics.
sp_landing
1 day
The sp_landing is set by Spotify to implement audio content from Spotify on the website and also registers information on user interaction related to the audio content.
sp_t
1 year
The sp_t cookie is set by Spotify to implement audio content from Spotify on the website and also registers information on user interaction related to the audio content.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
CONSENT
2 years
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
iutk
session
This cookie is used by Issuu analytic system to gather information regarding visitor activity on Issuu products.
s_vi
2 years
An Adobe Analytics cookie that uses a unique visitor ID time/date stamp to identify a unique vistor to the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
NID
6 months
NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.
VISITOR_INFO1_LIVE
5 months 27 days
A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSC
session
YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devices
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-id
never
YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextId
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requests
never
This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.