Proposed framework for receiving projects' proposals

The purpose of this is solely requesting feedback!

  1. Who is going to be affected by this proposal?
    TEC Scouts, Soft-Gov, New and old submitted proposals and Onboarding.

  2. Who are the experts of the proposed subject?
    @liviade (as Soft-Gov), @Tamara (for understanding how effective this could be), @Suga (for understanding if it can be incorporated to Onboarding processes).

The Hatch has closed, and we have some weeks to understand how to analyze, receive and give proper feedback to the incoming proposals.

For this situation there are possibilities like:

  • Wait until the commons upgrade and then focus on what do to with proposals: From my perspective, not very efficient, with the previous experience on the Hatchers, building trust with them across the months, was a key factor, at least based on an open conversation and dialogue. But, on the other hand, this approach will allow us to focus and have more information by the time the submission to the Commons is possible.

  • TEC Scouts: TEC Scouts can continue to do soft-outreach for the next month and half, focused on communities that have related projects, ideas, values or with previous conversations such as being featured on the weekly highlights. This will allows to stay on the loop, while keep inform of where we are at with projects, so they will have access to information and be easier/aware for them to know when to submit their proposals. Right now TEC Scouts is formed by Lauren, Chuy and Eduardo, and we will probably need a few more people connected to the ecosystem in order to spread the word and make it effective.

For this part, I propose the following framework and understanding of the “Proposal Journey”

  1. TEC Scouts takes care of creating and curating a database of Projects (this has started already), as well as a value exchange for both, and to identify how we can take a 360º view and integration of their proposal.

  2. Once the outreach is done, the members that will submit the proposal could/will have a session of Onboarding with Suga, in order to make sure they have the right information/tools and access to them. This could be a fixed time or a personalized meeting. (This also refers to technical information and cultural information of the TEC)

  3. Once they have been introduced to the community, Soft-Gov could take a look to the submitted proposal on the forum, and provide feedback if needed, if no feedback is possible, then just the “we have read it” check should be given.

  4. TEC Scouts takes again the proposal that was submitted and takes care of distribution and potential linking of that proposal within the community, using the TEC Lounges, to introduce them to hatchers and contributors bringing another layer of feedback.

So this may sound a bit to corporate or too pre-defined, so I am requesting feedback from the community on this matter.

The main objective of this post is to come out with an aligned consensus on what would be the actions for the next month and half, regarding proposals, because it will affect the aftermath of the outreach done by TEC Scouts, as well as the unavoidable attention that will bring the success of the Hatch.

Consider that this proposed framework is not targetting what to do with the proposals that have been submitted already, but my intuition goes that we can just apply step 3 and 4.

We are at a momentum to spread the word, now how we become effective about it?

Sorry if my wording is incorrect at some points, feel free to correct it <3.

3 Likes

Thanks for bringing this up @vegayp!

I want to provide my feedback on developing a framework for receiving Project Proposals for funding by the TEC, but before I do, I would like to review what it is we actually NEED to be funding within the TEC, and that requires asking questions such as: “What does it mean to Advance the Field of Token Engineering?” or “What types of projects should we NOT fund?”.

From my perspective (and it may not be popular), the best things we can fund that further the mission of our organization is Education and Research in the field of Token Engineering. While there are many proposals that are going to be interested in developing new economic and governance primitives, I hold the assumption that most of these advancements will be achieved from “private-sector” projects who will generate far more revenue and have much greater incentives to develop these primitives. This doesn’t mean we cannot fund projects that seek to develop new mechanisms, but we must be very judicious in how we spend the funds we do have in the Common Pool and that means we must be very clear on what types of projects we are willing to fund, and what type of value (like many non-profits, our value will come in the form of organizational visibility, and the Impact the projects we do fund have on the industry) we receive from providing that funding.

As far as proposals go, I really like the idea of taking the “whole” DAO approach towards informing, guiding, evaluating, and approving proposals that go through whatever system we have set out. I think it is beneficial not only to TEC member cohesion, but also for integrating these projects into the TEC ecosystem and having access to the right people/resources for getting the most out of each project proposal.

For this part, I propose the following framework and understanding of the “Proposal Journey”

I love the Proposal Journey concept!

  1. TEC Scouts takes care of creating and curating a database of Projects (this has started already), as well as a value exchange for both, and to identify how we can take a 360º view and integration of their proposal.

While the TEC Scouts can develop a database for potential projects, it would be really nice to have some type of portal where potential projects can create their own Profiles and reduce the amount of administrative overhead it would take to constantly seek out potential projects, evaluate their potential and make contact with communities and individuals.

We also should have a way to establish that a project has a credible intent to apply for funding, and if they do, their project should be evaluated immediately for response on whether or not the proposal qualifies under our criteria for Funding. (These decisions will not be easy, and that approval process should be immediate and probably involve the Stewards WG or a dedicated Funding Committee)

  1. Once the outreach is done, the members that will submit the proposal could/will have a session of Onboarding with Suga, in order to make sure they have the right information/tools and access to them. This could be a fixed time or a personalized meeting. (This also refers to technical information and cultural information of the TEC)

This one is a no-brainer, and I love it! The onboarding group should be able to provide all potential projects any information they need to become successful, as well as create points of contact and notify them of any updates within the “Proposal Journey”.

  1. Once they have been introduced to the community, Soft-Gov could take a look to the submitted proposal on the forum, and provide feedback if needed, if no feedback is possible, then just the “we have read it” check should be given.

While I would like to see Soft-Gov involved in this area of the process, I find that it doesn’t really fit very well with the objectives of the Working Group. At this stage, I would like to see the evaluation of the potential proposal by Comms before they submit it to the Forum. Half the battle with these projects is making sure that the messaging around why they are creating the proposal and what it provides for TE is adequately described. Clear communication will limit any conflict around whether a project is worthy or not to be considered by the community.

  1. TEC Scouts takes again the proposal that was submitted and takes care of distribution and potential linking of that proposal within the community, using the TEC Lounges, to introduce them to hatchers and contributors bringing another layer of feedback.

This is a perfect fit for the TEC Scouts. Gathering feedback on the reception of the proposal and informing the needs of the TE community for further funding.

Each of these steps within the journey require certain processes that have not yet been developed and because they span so many different WG’s, we should approach them one by one so that we have a holistic understanding of the system we are creating around potential proposals. And while this post was focused on the Proposal Journey, I think its important to consider the entire funding process. Here is a list of things that I think are important to consider for this process.

  1. ) Develop a strict criteria around what types of projects qualify for funding that further our MISSION.

2.) Identify a list of NEEDS within the TE community. These needs should hold priority when we consider projects for funding.

3.) Explore the possibility of establishing rules around funding (should we fund a large project 100,000 wxDai all at once, or should we milestone each part of a large proposal?/Can we enter into contractual agreements with potential projects?)

4.) TEC Scouts need to list project characteristics (within a database) that are relevant to evaluating those projects according to our criteria for success. (how big is the community?/what type of experience do the developers have?/is this their first project?/etc.)

5.) Onboarding should have a detailed process that includes not only the proposal journey, but also the reporting, and evaluation process of each project. Informing potential projects on every aspect of the process and communicating will make the TEC an attractive place to get funding from.

6.) Soft-Gov to evaluate the “campaign” process around funding proposals and establish boundaries/rules.

7.) Comms to be dedicated to creating a narrative around each project proposal, and what they are doing for the field of TE.

8.) TEC Scouts to be actively involved in the success of the project even after funding has ended. TEC should be about creating value and the adoption of sustainable TE tools.

9.) We cannot ignore our own economy. Establishing utility for the TEC token, and being an active presence in every major crypto project should be a priority that will allow us to fund more and more projects, and to create a sustainable system in the long-run. Without sufficient activity, we will be limited in the projects we can fund and therefore the impact that we have.

Those are my thoughts on the topic. Like every major decision we are facing right now, I think its important for everyone reading these posts to engage, share your opinion, and give our Stewards the most information to make the best decisions possible within their respective Working Groups!

2 Likes

perhaps this question can be answered in the converse … what makes a project suitable for commons?

  1. high spillover effects … education case studies allow public to see what experts look at … eg post-token accident report (like airline crash)
  2. public interest value … a big project like China DCEP or Libra would have a bigger implication than private projects
  3. independence … sometimes you want a disinterested bystander rather than echo-chamber … this becomes more corporate communications so a bit harder to justify on public policy PoV

Thanks for making this post @vegayp and for your reflections @natesuits. It’s great to read your thoughts on this. My opinion is that all of this steps can be helpful if they aren’t mandatory or hold a culture of permission for things to move forward.

I think the direction we should be aiming for is of a constant flow, where information is available, cultural practices are inclusive and easy to assimilate, and that we have the least steps possible for things to happen. There is a long way for us to get there still, but I believe we are moving in a great direction.

I think this is super valuable. Being in contact with projects that are aligned with our mission is great and being able to help them connect with other projects and people its something really cool we can offer. Other projects that are not in our database should feel free to propose as well.

As long as this is framed as a courtesy of the community and not a required step for participating I think is great. Some people might not feel the need of having a call. I also feel strongly about having fixed times that are open instead of scheduling one on one calls for something like this because the questions someone have might be valuable for others, its more transparent and also saves time.

Hopefully feedback will start happening organically by anyone who feels interested in the proposal. Stewards could be mindful of taking a a frequent look and we can include live proposals in our weekly community updates, but anyone who proposes in the CV section of the forum will be able to submit their proposals to the DAO. Conviction Voting will also help to curate the attention a proposal receives. If it has votes, probably more people will look into it. I don’t think a “we have read it” stamp is necessary - it creates a permission culture, when we want to be permissionless but held by a culture of mutual trust.

We could have a little flagging system, what do you think @Juankbell? Whenever a proposal or post seems inadequate to the community we can use the flag in the forum and check that with a certain frequency. Also Celeste will be in place in case misaligned proposals end up getting there.

This seems to me like a complement of point number 1. Which I think its cool for connecting projects and people, but we should be careful not to “promote proposals” and rather have a more neutral stance from the TEC perspective. We as individuals can vote on proposals and talk about them, but when it’s the TEC voice we should be careful not to give different treatments to different proposals, for example posting some on twitter and others not. We started this conversation in the Stewards call when talking about the future direction of the TE Spotlight @natesuits. The idea of turning it more into an educational spotlight once we have the DAO running and with funds sounded interesting.

2 Likes

My opinion is that all of this steps can be helpful if they aren’t mandatory or hold a culture of permission for things to move forward.

YES. Absolutely. This is not a mandatory framework, it’s more intended to be a internal DAO organization format, that we can “check” and have an understanding within the organization of what do to when someone proposed. As you mention, this has more of an intention of “good practices” manual for proposals.

This Good practices Manual, goes along the lines of what @natesuits mentioned.

This part is even more relevant:

I think this should go to vote, or consensus. (Or whatever system soft-gov think it could fit) @liviade. Before finishing this framework, our aim should be clear on what it’s the goal from funding, and target for example Education and Research and actively send TEC Scouts to dig within or out the community. I think aiming for cohesion and keeping “the personal touch” that we built with the community, should be maintained on the outreach, and for this to happen, having a clear goal, objective and targets would make it easier, and bring clarity for them and us.

Agree too, this is a courtesy but is also a way to bring transparency and clarity about our culture. A lot of people, hatchers or projects, aren’t fully present on our community, therefore they miss out a lot of our cultural builds, the intention of this is to make them feel welcome to the ones that are willing and feel the need of, but also to make sure that we are taking care of them, and not only caring about their proposal. A fixed time, would be ideal. But counting on peoples times and timezone, the idea of personal touch should be consider.

Agree, TEC Scouts shouldn’t be promoting proposals, but more about bring awareness to our community that this proposal exists, on the same way we did with parameters, so people were aware of what they were about. So it’s more about the educational aspect of it, and not counting on with people reading and engaging if by default it’s not part of our cultural build to give proper care and space for proposal besides the Highlights.

THANK YOU SO MUCH for your feedback <3

1 Like

Part of the nature of the DAO is having this consensus happening via vote every time something is proposed. I think its good to have it a little loose, and that we build our understanding together as the space evolves. We can also start talking more about things that would be interesting to see happening if there is a question there. I think our mission, vision and values are a great starting point of goals and objectives. Definitely cohesion is important, but it’s a living thing :pray: