--- title: "Web3 Governance Case Study Exercise" description: "Diagnose a real DeFi governance failure, hold a vote under pressure from three stakeholders and write a recovery proposal in this Web3 governance case study." canonical_url: "https://builderscamp.com/guides/challenges/web3-pm-governance-crisis-response" date_published: "2026-09-16" date_modified: "2026-09-16" author: "Andre Albuquerque" publisher: "Builders Camp" guide_class: "challenges" --- # Web3 governance case study exercise for product managers **TL;DR:** This is Builders Camp's Web3 Product Management practical challenge: diagnose a DeFi governance failure modeled on Compound Finance's real 2021 Proposal 62 incident, hold your position under pressure from three competing stakeholders, and write the recovery proposal. It runs about 90 minutes and is rated advanced. ## What is the challenge scenario? A governance proposal just passed with 62 percent approval, introducing a bug in a smart contract's drip function that lets users drain tokens from a protocol reserve, an estimated 62 million dollars in exposure over 48 hours if nothing changes. The code review had flagged the edge case, but the flag was never escalated. Only 16.6 percent of eligible supply participated in the vote, and a single delegate's 412,000 tokens carried more than a third of the winning side alone. The community is now fractured across three narratives. One voice calls it a whale concentration problem, since a handful of large delegates effectively decided for hundreds of thousands of token holders who have no idea the governance system exists. Another calls it an engineering process failure dressed up as a governance story, since the bug was flagged and simply not escalated. A third calls it a UX and notification problem, since ordinary holders had no way to know the vote was even happening. A patch proposal is live and needs 400,000 tokens to reach quorum, and the clock is running. ## What are you asked to do? Decide which of the three diagnoses, whale concentration, engineering process, or UX and notification, is the actual root cause, which are contributing factors, and which you would rule out, being specific about the mechanism rather than a general label like low participation. As a delegate holding 500,000 tokens, respond honestly to three separate DMs, one pushing you to vote yes on the patch immediately, one pushing you to vote no on principle to force accountability, and one from a small holder who could not afford to vote at all, stating your actual position and reasoning to each. Propose exactly one structural change to the governance mechanism, explaining what failure mode it addresses, what it costs in complexity or speed, and how a bad actor could try to game it. Close by writing a formal recovery proposal, with a summary, motivation tied directly to the incident, a precise specification, and an honest discussion of risks and trade offs. ## What does a strong answer cover? This bootcamp does not publish a rubric for its practical challenge, so check your own draft against the curriculum's own questions instead of a worked solution: - Does the diagnosis commit to one root cause rather than treating all three community narratives as equally central? - Does each DM response state an honest, specific position rather than simply agreeing with whoever is asking? - Does the proposed structural change name what it costs and how a bad actor might try to exploit it, not just what it fixes? - Does the recovery proposal reference the actual incident directly, rather than describing governance reform in generalities? ## Skills this exercise practises Diagnosing a root cause among several plausible, competing explanations, holding an honest position under pressure from stakeholders with conflicting incentives, designing one targeted structural fix rather than an unworkable overhaul, and writing a formal proposal that a skeptical community would actually trust. ## Which bootcamp does this challenge come from? This is the practical challenge from [Web3 Product Management](https://builderscamp.com/bootcamps/web3-pm), Builders Camp's two week bootcamp on applying solid product thinking to wallets, on chain UX, token incentives and governance, led by Andre Albuquerque across four 120 minute live sessions. Completing it counts toward that bootcamp's certificate. The [RICE prioritization framework](https://builderscamp.com/guides/other/rice-prioritization-framework) and [North Star metric examples](https://builderscamp.com/guides/other/north-star-metric-examples) guides both help with the trade off reasoning this exercise demands, and [how to get promoted to senior PM](https://builderscamp.com/guides/path/how-to-get-promoted-to-senior-pm) covers the judgment calls under pressure this challenge is built around. The [product strategy case study](https://builderscamp.com/guides/challenges/product-strategy-series-b-board-memo) exercise elsewhere in this series practises writing a defensible recommendation under a similarly tight, high stakes deadline. Builders Camp runs live and self paced bootcamps in product management and AI product building. [See the Web3 Product Management bootcamp](https://builderscamp.com/bootcamps/web3-pm?utm_source=guide&utm_campaign=web3-pm-governance-crisis-response) for current cohort dates and the full self paced curriculum. ## Frequently asked questions ### Is this exercise based on a real DeFi incident? Yes. The scenario is modeled on Compound Finance's real September/October 2021 incident, where a passed governance proposal (Proposal 62) introduced a smart contract bug that incorrectly distributed roughly $90 million in COMP tokens, and a fix required a second governance vote to reach quorum. Builders Camp's curriculum adjusts the specific figures and stakeholder details for the exercise rather than reproducing an audited account. ### Why does the exercise give three different, plausible diagnoses of what went wrong? Because real governance failures rarely have one clean cause. A whale concentration problem, an engineering process gap, and a notification and UX problem can all be true at once, and the exercise asks you to name which one is the actual root cause rather than treat all three as equally central. ### Do I have to respond to all three DMs from competing stakeholders? Yes, and honestly. The exercise is explicit that you do not have to agree with any of them, but your response should state your actual position and reasoning, since these are framed as real people whose trust you would be managing in an ongoing community. ### How many structural changes am I allowed to propose? Exactly one. The exercise is deliberate about this constraint: governance changes that try to fix everything at once tend not to pass, so you have to choose the single change most likely to have prevented this outcome and defend that choice. ### How long does this practical challenge take? Builders Camp lists it at 90 minutes and rates it advanced difficulty, the most demanding difficulty rating in this bootcamp's challenge, reflecting that it moves through diagnosis, stakeholder pressure, mechanism design and a formal proposal in one sitting. ### Does completing this exercise count toward a certificate? Yes. It is the practical challenge for the Web3 Product Management bootcamp, and submitting it counts toward that bootcamp's completion and its LinkedIn integrated certificate. ## Sources - [Builders Camp: Web3 Product Management bootcamp](https://builderscamp.com/bootcamps/web3-pm) - [The Register: Smart contract bug gives away $90m in COMP cryptocurrency](https://www.theregister.com/2021/10/01/compound_crypto_bug/) ## How this guide was made Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.