Jupiter DAO WG Proposal Guidelines

Jupiter DAO
1

This is meant to serve as a guide, not law. It is made as a reference to help future WG applicants and aspirants to know where to get started when drafting a proposal.

However, they are at liberty to use this as a reference piece, although generally it is a good idea to touch on everything included in here.

The sections are as follows:

INTRODUCTION

This is where you introduce your proposal in short form. Give the readers an idea what the proposal is about, who it affects and why the proposal is needed. Also include any necessary background or historical information about the group. Link to any retrospectives or former work here.

PURPOSE / PROBLEM

The purpose of your proposal in expanded form. Explain why there is an issue and how it affects the Jupiverse. Explaining the problem and/or purpose of your proposal helps the reader to form their own opinion on whether or not this proposal is needed. Defining your purpose or problem will help put your solution and/or deliverables into context.

SOLUTION / DELIVERABLES

The core of your proposal. This is where you describe your solution and/or deliverables for the proposal. A well formulated solution with deliverables will give the reader a concrete impression of how your proposal will solve the problem or purpose you defined in the above section.

ENVIRONMENTAL CONTEXT:

What is the global state of comparable items to your proposal like at the moment? IE if doing a podcast, what is the trend for podcasts? What about web3 specific podcasts? Is there a vacuum? Is there a niche?

RISK / CHALLENGES

Any potential risk or challenges in relation to executing the proposal. Alternatively, if no risks or challenges exist this section can be skipped.

TEAM STRUCTURE / QUALIFICATIONS

If your proposal is in relation to a grant, trial or workgroup it is encouraged to present the team members responsible for carrying out the tasks described within your proposal. Explain who they are, what they will be responsible for and how you will work together as a team. It is also important to highlight the qualifications of the workgroup members to attest to their ability to perform the tasks.

FINANCIALS / COST

Any potential costs or benefits from your proposal must be described in detail. Examples include salaries, operating budgets, reserves, purchases such as software, licensing and external services.

POTENTIAL DAO IMPACT

If this works, how will the DAO and Jupiter benefit? What kind of impact can you project going into the future? We achieved XYZ with the grants amount, we believe we can achieve XYZ with the trial.

CONCLUSION / SUMMARY

Summarize by highlighting the flow of your proposal. What’s the problem? How are you going to solve it? Who’s going to solve it? What are the risks involved? What are the challenges to overcome? What does it cost? Summarize in short form to further imprint the message of your proposal on the reader’s mind.

16 Likes
3

Good summary, hope it brings some structure to some others genuine attempts for a WG

5 Likes
4

Thanks Slorg and Morten! This will help lots of cats with their future proposals.

3 Likes
5

No less than perfect. Very nice.

3 Likes
6

Thank you for your time and work. Good proposal to guide the next descendants of the groups on how to formalize a proposal well. It is more difficult to connect with the reader when something is written, but nevertheless when something is expressed with a podcast or video it is easier to connect with the contributor. :grinning:

2 Likes
7

Looks great. Nice work @Morten

The outline is quite easy to follow and covers all the essentials without being too overwhelming.

One suggestion though: From thr “Potential DAO Impact” section onwards the guidance is offered as questions and not statements.

Perhaps we can use that as a consistent format in the preceding sections too, especially since they trigger thoughts and ideas and all that.

Thoughts?

4 Likes
8

I agree, and we try our best to communicate through multiple microphones leading up to a proposal. Unfortunately Jupresearch as a forum does not support video.

4 Likes
9

The reason we did this is largely because the latter sections are more ambiguous than the former, and framing it through questions will as you say trigger some thoughts and ideas.

4 Likes
10

That is why I appreciate the work of all the groups, both in X and in Discord there are multiple conversations about the proposals that contain videos. So far I am happy with all the proposals written here. There are practically voice events every day where multiple things are talked about, if anyone misses it they can come here to investigate. :grinning:

3 Likes
11

Yes that makes total sense.

3 Likes
12

I like the format and do agree that the proposal should have clearly outlined the 3 main pillars:

+ what the problem is,
+ how this will be solved
+ what benefit will it bring to the Jupiverse

The more details the better, hereby as well easier for the teams to give a good evaluation. :nerd_face:

4 Likes
13

It’s always good to have a guide rather than nothing, especially when you don’t know what you’re getting into. It will be useful to all those who want to get started, while ensuring transparency for others.

Thank you for producing this document.

1 Like
14

Educative thread with nice methodology use for proposal creation. :owl:

4 Likes