Michael Q
New member
Who am I?
I’m a Silicon Valley technical advisor and engineering leader, most recently with LinkedIn as a Director of Engineering. I have lots of experience in shaping ideas from teams into prioritized lists and product roadmaps. I am also experienced in applying iterative approaches to learn cheaply and quickly, as well as in building online communities and zero-to-one product development.
Introduction
As a relative newcomer to the Dash DAO world, I have had a hard time telling what projects most need to get done to advance Dash. There also seems to be a lack of a crystallized list of strategic priorities from the leadership (beyond those for core team). These are impediments to capable newcomers like me making meaningful proposals.
In the open source software world, a best practice is for the core team to publish a prioritized list of projects they would like to get done but don't have time to do. This gives new contributors ideas for high impact projects to tackle, and it helps the core team get more important work done through the proposal process.
Why should Dash fund this?
The Dash ecosystem needs a prioritized wish list of projects to drive higher quality and higher impact proposals. This proposal is a modest one to test the concept before we build any software to support the process. If it works well, I have the know-how to complete a high quality website in a subsequent proposal.
At the end of this test, we will have a prioritized wish list of projects that will be useful for 3-6 months. And we will have a good understanding of what sort of process will work well to keep an evergreen list going forward.
How Will It Work?
We will take a Lean Startup approach to test this out (design a simple test to test a hypothesis before investing further). Our hypothesis is that having a prioritized wish list will be relatively easy to assemble and will be a highly valuable asset to the Dash ecosystem.
Test Phase (this proposal):
We will have a 30-day period in which Master Node Operators (MNO’s) can submit and vote on ideas. We will use dot voting (multi-voting) to prioritize the list, where each participant gets a bunch of votes to cast for ideas they like the most. Then the best ideas (those with the most votes) float to the top of the prioritized list.
Timeline:
Website Build Phase (separate proposal, later):
If the test phase works well, we can build a website that will automate this as a repeatable process.
Cost: 45 DASH per month for two months
Questions
-Michael
I’m a Silicon Valley technical advisor and engineering leader, most recently with LinkedIn as a Director of Engineering. I have lots of experience in shaping ideas from teams into prioritized lists and product roadmaps. I am also experienced in applying iterative approaches to learn cheaply and quickly, as well as in building online communities and zero-to-one product development.
Introduction
As a relative newcomer to the Dash DAO world, I have had a hard time telling what projects most need to get done to advance Dash. There also seems to be a lack of a crystallized list of strategic priorities from the leadership (beyond those for core team). These are impediments to capable newcomers like me making meaningful proposals.
In the open source software world, a best practice is for the core team to publish a prioritized list of projects they would like to get done but don't have time to do. This gives new contributors ideas for high impact projects to tackle, and it helps the core team get more important work done through the proposal process.
Why should Dash fund this?
The Dash ecosystem needs a prioritized wish list of projects to drive higher quality and higher impact proposals. This proposal is a modest one to test the concept before we build any software to support the process. If it works well, I have the know-how to complete a high quality website in a subsequent proposal.
At the end of this test, we will have a prioritized wish list of projects that will be useful for 3-6 months. And we will have a good understanding of what sort of process will work well to keep an evergreen list going forward.
How Will It Work?
We will take a Lean Startup approach to test this out (design a simple test to test a hypothesis before investing further). Our hypothesis is that having a prioritized wish list will be relatively easy to assemble and will be a highly valuable asset to the Dash ecosystem.
Test Phase (this proposal):
We will have a 30-day period in which Master Node Operators (MNO’s) can submit and vote on ideas. We will use dot voting (multi-voting) to prioritize the list, where each participant gets a bunch of votes to cast for ideas they like the most. Then the best ideas (those with the most votes) float to the top of the prioritized list.
Timeline:
- 7 days initial setup
- 15 days to publicize to MNO’s to get them to participate
- 15 days for idea submission
- 15 days for voting
- 3 days to prepare and publish the list
- Milestone: list is published
- Then I promote the published list on forums/slack and by getting links on all the main sites
- Set up online assets (description of process, ideas/surveying page(s), participant mailing list for communication)
- Publicize test to MNO’s - forums, getting links added in appropriate places. Follow-ups on forum questions.
- Handle MNO access requests.
- Oversee the idea/voting community process.
- Publish top ideas list and publicize the list on forums/slack and getting links added in appropriate places.
- Customer support / individual Q&A.
- Run survey and publish survey results of quality of project outcome
Website Build Phase (separate proposal, later):
If the test phase works well, we can build a website that will automate this as a repeatable process.
Cost: 45 DASH per month for two months
Questions
- I wonder whether this should be open to all MNO’s or be more focused on the Dash Foundation team and more experienced MNO’s. I think it’s better just to keep it open. Will this approach include the foundation team enough?
- How many MNO’s will want access to test phase? 100?
- What the best simple way to qualify participants as true MNO’s?
- If supported here, should I submit this for current cycle ending in ~5 days or wait for next round? @paragon on slack suggested that I go for this cycle as long as I get my proposal up before Ryan posts the core budget proposals. But $500 fee is non-trivial risk.
-Michael
Last edited: