This framework should guide all but the simplest proposals that can be put to vote straight away.

Note: if your idea doesn’t require guild funds or addition/revision/depreciation of a guild role or active program then you probably don’t need to use the rigor of this process and can probably do temperature and awareness checks via messages in the appropriate Discord channel(s).

1. Ideation - Ideate in the open!
   1. Share an idea in #bd-opportunities to get some quick feedback
   2. Conduct a quick @seshbot poll to get a sense of what people think
2. Proposal Draft - Work in the open!
   1. Use the DizDev Guild proposal template when drafting a new proposal
   2. Signal in #bd-opportunities that you’re working on it so that co-authors can signal interest in collaborating
3. Discussion/Revision - Provide & receive feedback in the open!
   1. Receive comments directly in the proposal template
   2. Option: LettuceMeet to coordinate feedback/advice calls where needed
   3. Redraft the Google Docs and communicate in #biz-dev when changes happen
   4. Option: Use a @seshbot poll to see if it’s ready for voting if unsure
4. Consensus Checks and Voting - Every vote counts!
   1. Champion to update the proposal status to ‘Voting’ with a link to the sesh poll
   2. Use a @seshbot poll w/ emoji react as the voting poll in #biz-dev.
      1. Be sure to clearly label it as a ‘consensus vote’ and use the @BizDev tag when posting so guild is notified for maximum participation
      2. Vote poll should be open for minimum 3 days to maximize participation
   3. All binary (yes/no) type votes require a 60% consensus to pass, all non-binary votes or variations required must be defined in the proposal and clearly state thresholds/mechanics for a successful consensus.
5. Closing and Treasury Distributions
   1. Champion to update proposal to status ‘Closed’ and write a decision summary
   2. Champion to work with Governance Coordinator to rally the Multi-sig signers
   3. Signers sign transaction(s)