Arbitrum Strategic Objective Setting (SOS) – Defining the DAO’s Interim Goals

Non-Constitutional

Abstract

Following the passing of the Unifying Arbitrum’s Mission, Vision, Purpose (MVP) proposal, we’re moving to the next step in aligning the Arbitrum DAO on its end-state goals and the more granular strategies through which these will be reached. Arbitrum Strategic Objective Setting (SOS) is an initiative through which DAO members will be able to propose and vote on a cohesive set of short- to mid-term objectives in a collective, inclusive, and adaptable way.

Through the SOS, any contributor can submit a set of short-term (1-year) and mid-term (2-year) objectives and related tangible key results for the DAO. The set of objectives should directly drive the DAO closer to reaching its vision, and align with the mission and purpose, as listed in the MVP proposal. The DAO will then vote on the proposed sets of objectives to select a single collection for implementation.

Every 12 months, the chosen objective set will be reviewed and, if needed, revised based on changing market conditions, the competitive environment, progress made in the past year, etc. In order to keep the DAO up to date with the progress towards each strategic objective, we suggest the research member of the ARDC be tasked with providing quarterly reports assessing how the DAO has improved through proposals and initiatives as well as suggesting what areas require more attention while recommending solutions to address these areas.

Once a set of objectives and related key results has been approved, Entropy will strive to build a budgeting framework where each high-level objective is allocated a certain amount of capital on a yearly basis, with interested contributors having the ability to request a share of this capital through a standardized structure. It’s important to note that contributors will still maintain the ability to post standalone proposals outside of this structure and are not forced to tie their initiative to the MVP/SOS/budget framework. Having said that, as the established objectives should be regarded as one of the DAO’s highest priorities, contributors should expect more friction when it comes to passing a proposal that doesn’t reasonably demonstrate that it fits within the established short- to medium-term objectives. In other words, while the freedom to make proposals that fall outside the SOS will not cease to exist, we expect that the DAO will discourage it via the creation of a social contract among delegates.

Motivation & Rationale

Diversity is undeniably one of Arbitrum DAO’s strengths. We have hundreds of delegates from all around the world with varying perspectives, cultural behaviors, interests, incentives, etc. This is a double-edged sword, however, as it makes it more demanding to converge on unified goals and interim focus areas. The absence of concrete and agreed-upon goals today makes it challenging for the DAO to review progress and facilitate accountability, while it may be unclear to contributors what deliverables they should be prioritizing. Similar to the MVP proposal, the SOS takes inspiration from Lido’s approach to materializing short- and medium-term objectives for the DAO.

By establishing clear short- and mid-term strategic objectives and key results, the outcome of the SOS will serve as a roadmap that will bring cohesion and direction to the DAO’s activities. This structured approach will enable the DAO to move beyond reactive governance and toward proactive strategic development. Having well-defined objectives allows the DAO to measure progress better, identify operational gaps, and adjust course when needed.

These objectives will create a shared foundation for evaluating opportunities across the DAO’s diverse contributor base. When assessing new initiatives or responding to market developments, delegates and contributors will have tangible criteria to inform their choices. This alignment will help prevent the dilution of efforts that can occur in DAOs, ensuring collective resources and energy are directed towards Arbitrum’s most important goals. A regular review cycle ensures the DAO’s objectives remain responsive to changing conditions while maintaining momentum toward the mission, vision, and purpose. If the MVP helps to define the DAO’s long-term vision, then the SOS allows Arbitrum DAO to chart the course to get there.

Specifications

This proposal can be considered to have two distinct phases. The first phase comprises a ~7-day forum review, feedback, and edit period after which the SOS framework will move to the 7-day offchain voting period. If passed, Entropy will consider the structure of the SOS accepted by the DAO, and the second phase will be initiated. In phase two, contributors will submit their strategic objectives matrices with one matrix finally chosen through a Snapshot vote. The periods making up the second phase are described below.

Notice Period (14 days)

At the beginning of the 14-day notice period, announcements will be made on the forum and all the other relevant communication channels (e.g., Twitter, Telegram, etc.), giving delegates and contributors enough time to prepare for the upcoming submission period. This announcement will include:

  1. The expected start and end dates of all the subsequent periods (submission, feedback, and revision).
  2. Guidelines on how to submit a proposed set of short- and medium-term objectives as well as related key results.
  3. Link to an FAQ forum thread where delegates can ask questions about the program.

Entropy Advisors will facilitate the end-to-end process in cooperation with the Arbitrum Foundation and any other relevant parties.

Submission Period (30 days)

This submission period lasts 30 days, during which delegates and contributors are invited to make their submissions. Those interested in participating will have to create a forum post under a designated Strategic Objective Setting (SOS) subcategory. The goal-setting methodology utilized will be the Objectives and Key Results framework, where each objective (high-level, inspirational goal) is accompanied by key results (specific, measurable outcomes) that once reached, represent an objective having been completed. As a reminder, these objectives should indisputably align with the DAO’s mission, vision, and purpose. At a minimum, a valid submission must include the following information:

  1. View of Arbitrum’s current state and what its strengths/weaknesses are
  2. Short-term objectives (1 year)
  3. Mid-term objectives (2 years)
  4. Key results, i.e., measurable success metrics, for all objectives
  5. Risks connected to all objectives
  6. Rationale explaining how the objectives align with Arbitrum’s MVP and why they were chosen given Arbitrum’s current state

The format for a SOS submission post on the forum is as follows (note, while the Title and headers should follow the below format, the information under each header is up to the author; this is a non-exhaustive list):

  • Title

    • Format: [SOS Submission] {Delegate} – Strategic Objectives
    • Example: [SOS Submission] Entropy Advisors – Strategic Objectives
  • Summary

    • A brief summary of the strategic objectives
    • High-level explanation of their impact on Arbitrum.
    • Main focus areas for each proposed objective (i.e., Stylus, Orbit, Gaming, etc.)
  • Rationale

    • A general overview of Arbitrum’s current state, including where the author sees the ecosystem’s strengths and weaknesses.
    • Explanation of how these objectives are aligned with Arbitrum’s MVP, why they were chosen given Arbitrum’s current state, and what risks and expected outcomes are related to the objectives.
    • Key assumptions and strategic reasoning behind chosen objectives.
  • 1-Year Strategic Objectives & Key Results

    • A clear and specific statement of each objective.
    • ~2-5 measurable key results/success metrics per objective.
  • 2-Year Strategic Objectives & Key Results

    • Same format as 1-year strategic objectives.
  • Further Details

    • Anything else the author feels as though relevant to include in their submission.

Condensed Example of a 2-Year Strategic Objective (figures are illustrative):

Objective: Arbitrum becomes the indisputable leader within a selection of onchain finance-related verticals: stablecoins, RWAs, and lending.

Alignment with the MVP: As onchain finance-related verticals continue to grow in usage, importance, and impact, it is imperative for Arbitrum to achieve a market-leading position in a certain set of these sectors. Doing so ensures that the ecosystem stays aligned with its vision of being the home for the universal shift onchain, with Arbitrum rollups as the first stop in crypto for users and the default platform for developers.

Key Result 1: Arbitrum One becomes the second largest blockchain in terms of stablecoin volume traded on onchain exchanges.

Key Result 2: RWAs (excluding stablecoins) held within the Arbitrum ecosystem grow by 20x from when the DAO chooses its set of objectives.

Key Result 3: The Arbitrum ecosystem reaches a 30% market share of all outstanding onchain loans.

While the number of strategic objectives in a matrix is not limited, proposers should consider the DAO’s capacity to effectively focus on multiple areas simultaneously. Moreover, while the objectives should be aspirational, they must also be attainable. When providing feedback or choosing a specific objective matrix, we encourage delegates to evaluate their feasibility critically. Implementing unrealistic objectives and key results would most likely result in wasted efforts and be counterproductive.

A given year’s objectives are expected to be limited to a specific focus area and not to overlap with each other. As such, we recommend submitters refrain from proposing objectives that are too high level since the potential for overlap increases. Having said that, the sets of 1- and 2-year objectives can be the same as long as key results across years are different.

See this example from Hasu’s proposed goals for Lido. When objectives form a cohesive, well-documented strategy, it is more likely to gain support from delegates. Just giving the DAO a list of objectives likely will not be sufficient; the expectation is for the objectives to make up a holistic strategy with a well-reasoned rationale.

Feedback period (21 days)

Once the submission period is over, no new objective matrices can be put forward. The submission period is followed by a 21-day feedback period. During this time, submitters are prohibited from making changes to their submissions to allow delegates to examine each submission, provide feedback, and propose edits. This period ensures that all delegates have ample time to familiarize themselves with each submission and that everyone is commenting on the same submission versions.

Revision Period (14 days)

During the revision period, submitters may amend their objective matrices based on community feedback if they wish to do so. Apart from making edits, this period enables submitters to merge their proposals with others, mixing and matching objectives across submissions (note that a given year’s objectives should still have no overlap). If two or more proposals are merged, proposers should post the final version as a new submission in the SOS subcategory and modify the original submissions’ titles to indicate that they have been merged as well as include a link to the merged version at the top of the original submissions. If a proposer feels as though their objectives and key results are already adequately covered by another submission, they are also free to withdraw their submission during the revision period. At the end of the revision period, submissions will be locked and considered as the final versions, which will be the ones put up for a Snapshot vote to choose the DAO’s strategic objectives matrix.

Voting period (7 days)

Finally, the voting period. Entropy will be in charge of creating a Snapshot vote with a list containing all finalized strategic objective matrices in a single proposal, with delegates voting on which matrix they are the most aligned with and see as optimal. The Snapshot will utilize single-choice voting with an option to abstain. Quorum is reached when at least 3% of all votable tokens have participated in the Snapshot, with the option that has received the most votes being implemented. A strategic objectives matrix proposer is free to vote on their own submission.

For the avoidance of doubt, delegates will vote on standalone matrices formed by sets of 1- and 2-year objectives and key results. Please note that if there is a vast amount of submissions going to a Snapshot vote, Entropy reserves the right to postpone the initiation of the vote following the revision period to ensure that delegates are given some additional time to examine the final versions of submissions. If there is any confusion in navigating the forum throughout this process, e.g., where to post, how to title posts, how to merge proposals with another author/similar proposal, etc., Entropy Advisors will be available to answer any questions from the community.

Review Phase & Ad Hoc Strategic Objective Adjustments

After the initial strategic objectives matrices are defined and one has been chosen, the DAO is encouraged to review the chosen matrix on a yearly basis. This ensures the objectives and their key results remain relevant and aligned with the DAO’s evolving needs and the overall market dynamics. The process is similar to the second phase described earlier, but delegates can propose to modify existing objectives/key results, add new ones, or remove those that are no longer relevant.

A review phase should be initiated 12 months after the previous voting period has ended. Ideally, OpCo has already been operationalized by then, meaning that the DAO can instruct the entity to manage the review phase. As stated earlier, we propose that the research member of the ARDC is initially tasked with providing quarterly reports assessing how the DAO has progressed with respect to its strategic objectives. Once OpCo is operationalized, this responsibility could also be transferred to the entity if the DAO chooses to do so.

The review phase is initiated by passing a Snapshot vote. In the proposal, the proposer must define who is in charge of managing the review phase. Given the review phase Snapshot vote passes, there will be a 14-day notice period. This will consist of a forum post updating delegates on the current state of the strategic objectives and informing them on what this review phase consists of. Among other things, this forum post should include:

  1. A summary of the strategic objectives and how successful the DAO has been with respect to fulfilling them.
  2. The expected start and end dates of all the subsequent periods.
  3. Guidelines on how to submit an amendment.
  4. Link to a FAQ forum thread where delegates can submit questions about the program.

After the notice period, delegates are invited to submit amendments to the initially chosen strategic objectives matrix during a 30-day submission period. Amendments are not limited to simply modifying strategic objectives and key results. They can also involve removing, adding, or replacing specific objectives and associated key results.

Once the submission period ends, amendment submissions go through a 21-day feedback period during which no changes can be made to the submissions. Finally, a 14-day revision period will take place during which proposers can make edits to their proposed matrices and merge them with other proposed matrices before being locked and put up for a Snapshot vote to choose the new objective matrix. If no amendment submissions are made, there is no need to move to the feedback, revision, or voting periods, and the old objectives matrix will remain effective.

Note that the review phase timeline given above can be modified at the discretion of the review phase proposer depending on the number of submissions made.

As mentioned earlier, the SOS review phase should be conducted annually, with each cycle beginning 12 months after the conclusion of the previous voting period. However, if there’s a pressing need to review the strategic objectives due to, e.g., changes in the market environment, competitive space, or the DAO’s financials, a delegate can create a forum post outlining extensive reasoning for ad hoc adjustments accompanied by the proposed strategic objectives and related key results. Allowing for a reasonable time for discussion, the forum post will then be put up for a Snapshot vote utilizing single-choice voting with the options of adopting the proposed objectives and key results, initiating a fast-tracked review phase with a similar structure as described above (again, the proposer has to define who is managing this phase), and leaving the current objectives and key results unchanged.

It’s important to note that a well-structured strategy objectives matrix should not be expected to be changed frequently. As such, a proposed ad hoc adjustment must be extremely rigorously argumented and only take place if most of the previous strategic objectives have been reached or given unprecedented/emergency circumstances. Moreover, delegates ought to be highly critical when such adjustments are proposed. For example, the proposer simply stating that they disagree with the current objectives should not be a strong enough reason to modify the objectives.

If an objectives matrix is changed on an ad hoc basis, the originally scheduled review phase will be pushed back. This phase should only be initiated once 12 months have elapsed since the previous vote to change the DAO’s strategic objectives and related key results has passed. Additionally, the DAO’s strategic objectives and related key results can be removed by creating a forum post explaining the reasoning to do so. Once a reasonable time for discussion has passed, the post will be moved to a single-choice Snapshot vote with the voting options “For”, “Against”, and “Abstain”, requiring a simple majority with at least 3% of all votable tokens voting either “For” or “Abstain” for the proposal to pass.

Timeline

  • First Phase (Ratification of the SOS Framework):
    • Review, Feedback, & Edit Period: ~7 days
    • Snapshot Period: 7 days
  • Second Phase (Ratification of a Strategic Objectives Matrix):
    • Notice Period: 14 days
    • Submission Period: 30 days
    • Feedback Period: 21 days
    • Revision Period: 14 days
    • Voting Period: 7 days
  • Review Phase (Potential Amendments to the Strategic Objectives Matrix): Initiated 12 months after the previous voting period has ended or as a result of an ad hoc adjustments proposal as described above.

Note that any of the time periods in the first and second phases can be shortened/extended at Entropy’s discretion depending on the number of submissions received.


Entropy has already gathered feedback from various Arbitrum delegates and stakeholders, based on which we will submit a strategic objectives matrix. If you have certain objectives and related key results in mind but don’t want to create a full-fledged submission, feel free to forward these to Entropy and we’ll consider them for our submission.

4 Likes

Thank you for this proposal. It’s a long-anticipated initiative and will undoubtedly be a massive undertaking. I wonder if it would be beneficial to define some indicative categories for these objectives. This could prevent certain areas from being overlooked while also helping proposers efficiently identify similar proposals and foster collaboration.

What I mean is that we could predefine some categories within this proposal, such as governance, DeFi, grants, etc. This way, proposers could focus on reviewing proposals within their respective fields, reducing redundancy. Of course, this wouldn’t restrict proposers from suggesting objectives in new categories—they could simply be classified as “others.”

1 Like

I support this SOS framework and appreciate @Entropy’s work in designing it.

The combination of phased implementation, review cycles, and budgeting shows promise for moving Arbitrum from reactive to proactive governance.

A few suggestions to strengthen the framework if helpful:

  • Consider adding specific templates and metrics for quarterly progress reporting to help track outcomes consistently
  • The 30-day submission window might benefit from dedicated spaces where contributors can get feedback while crafting their objectives
  • Could be valuable to add ways to capture cross-DAO learnings during the feedback period, as many delegates have relevant insights from other ecosystems

Looking forward to seeing this framework evolve and helping advance Arbitrum’s strategic development.

Thanks again @Entropy for leading this initiative.

1 Like

This is a great continuation to MVP! From high level goals, to this, to then budget, was the proposed path and also the right one, to go to something tangible.

I have a question: when someone will provide a goal and this goal approved, alongside a budget, how will this be executed? Through dao delegates, opco, or whoever wants to fill the role? Because we might be in a situation in which we are short of people executing in case of a lot of submissions.

1 Like

Thanks for your proposal!

Regarding the proposal submission minimum items, I would like to suggest an addition.

  • Expected resources to be utilized.

In Lido’s case, we are talking about objectives for one protocol. When thinking about Arbitrum, the spectrum is broader and, two objectives, while perfectly aligned with our MVP, may be competing for the same resources.

My understanding is that the 1-year goals are effectively proposals/initiatives to achieve the 2-year objective (the beginning of the “how” to achieve the key results). When we think about objectives, it is “mandatory” to have a rough idea of what is required (at least, in our point of view) to achieve that. For that reason, I advocate for this “resources” item, as that will helpfully turn them into more actionable items, as you guys requested in the quote below.

When I mention resources, it is not limited to funding. Any coding, intervention of AF or OCL or manpower (in comittees or other structures), marketing or BD, etc. That would help a lot the delegates’ analysis/feedback and would give the proposer another layer of reasoning when crafting their submissions.

As a final note, as we are talking about an estimative, it would be ok to have “around 3m ARB”, “build a webpage with X, Z, Y features”, “The AF will be required to perform the KYC for around 300 participants within 2 months”, etc. “This will require ARB from the treasury” or “AF would be required to handle that” are not good examples.

My 2 cents in the matter.

2 Likes

Thank you for the proposal. Our team has some questions regarding the budget that will be used.

  • What is the total budget allocated to achieve the objectives?
  • Will this budget be approved through a vote?
  • Why isn’t the budget allocation included in the proposal?

We are not sure we fully understand how the process will proceed after the objectives set are approved. Thank you.

1 Like

I highly agree with the motivation behind this proposal: the current DAO lacks clear objectives, leading to scattered resources and difficulties in accountability. Establishing a unified goal matrix can enhance the sense of direction, improve resource allocation efficiency, and provide contributors with a clear priority framework.

After reading the full report, I have some questions I’d like to consult:

• This proposal is quite macro in its approach, but which areas will be prioritized for short- and medium-term goals? For example, will the focus continue on stablecoins and RWA for stability, or will new fields like gaming and NFTs be explored? How will these priorities be ranked?

• If the proposal is not approved, what is the DAO’s current development direction? Will it affect existing projects?

• Entropy’s role seems critical, as it is responsible for driving processes, managing goal evaluations, and handling voting stages. Could this lead to excessive centralization of power? For instance, if the community disagrees with Entropy’s recommendations, how will that be addressed?

• The proposal mentions detailed processes like submission, feedback, and revision periods. However, has it considered whether the participation threshold for ordinary community members might be too high? For example, if someone submits just one goal, will it be sufficiently considered, or might incomplete proposals be ignored?

Suggestions

  1. Since Entropy handles many critical aspects, could a third-party supervision mechanism be introduced? Additionally, the execution outcomes of each stage should be published on the forum to give the community greater say in the process.

  2. Ordinary users may not be skilled at crafting a complete proposal with detailed goals and key results. Could a simplified process be set up, allowing them to submit “goal ideas”? The community could then vote on which ideas are worth further exploration, better encouraging participation.

1 Like

This looks like a good process/protocol to define Arbitrum’s goals and objectives - and also to re-evaluate them every year. Based on these objectives, it will be easier for delegates to decide which governance proposals to support and which ones not (same goes for proposal authors).

I have one question though - Will the budget for each objective be defined in a separate proposal (after the SOS objectives are selected via Snapshot vote)?

1 Like

This seems like a pretty good start. A few suggestions having setup OKRs a couple of times:

6 months continue/change decision:
OKRs are often setup poorly the first time. EVen when teams had already setup OKRs before there’s a lot of organisational learning that happens. As way to mitigate this I’d suggest a 6-months confirmation vote. If the vote is favourable, the OKRs are kept for six more emonths. If the vote is negative, the whole process starts again.

Phase to improve the selected block of objectives (aka refine the selected Matrix)
I understand the rationale for having blocks of objectives proposed together is coherence. That being said, we could gain much through cross-pollination and the current process, although doesn’t prohibit this, doesn’t enable it well. Having people read each other objectives and then decide what to add to their proposed block is not the same as enabling the DAO to decide together on what should be exactly included in a block. And yet we need some opinionated take to set a direction! Are we between a rock and a hard place?
A solution is that after the initial block is selected, another 7 days period opens to propose “additional objectives” and then a multi-select vote is done where each objective (the ones from the selected block plus additional ones proposed after the block was selected) are either kept or not. This ensures the block acts as a directional force for coherence, but we don’t leave out (or in) the wrong objectives.
If needed, the initial submission period could be reduced to 3 weeks as it’s now less definitive.

I understand these suggestions add a bit of extra work, but they’re both aimed at ensuring we have the right objectives, as I’ve seen multiple organisations go into disaster when faith in the objectives dwindled and there was no efficient way to fix that.
If the proposed additions are found to be unnecessary after testing, they can be removed for the next cycle without much loss. On the other hand, if they were necessary and missing, it would take 12 months of having the wrong objectives (and potential DAO chaos or paralysis due to lack of alignment) as a result.
So low-cost add-ons for the proposal but mitigating big risks.

1 Like

Oh, one more thing. Why don’t we call this proposal “OKRs setting” so we have less (unique) acronyms in Arbitrum

Of course, a big protocol like Arbitrum needs a clear roadmap for short, medium, and long-term strategies to improve community engagement and help grow the ecosystem :slight_smile:

I really appreciate allowing delegates and community members to submit their strategic objective matrices, to makes Arbitrum more decentralized, transparent, and democratic.

That said, while Entropy has provided a solid timeline and process, I’m a bit unsure about the evaluation process. Since Entropy is deeply involved in collecting and assessing submissions (along with DAO members, yes), could this lead to bias when they are also a submitter?
—> My suggestion: Create a clear evaluation framework and involve multiple stakeholders to ensure transparency and fairness.

Plus, if too many proposals are submitted, voting might get tough and divide the community. Maybe we could gather ideas first and have groups combine similar ones before the voting stage.

Lastly, I understand crafting these strategies takes time and effort. The DAO could consider offering incentives for proposals that make it to the final voting round to encourage participation.

We might need a more detailed roadmap for how the matrices will be implemented. But for now, I fully support the formation of the SOS :slightly_smiling_face:

1 Like

A bit hard to add anything to this. The proposal is effectively a transition from mvp (abstract) to tangible strategies, policies and initiatives for the DAO. Execution will be key, meaning

  • the quality of proposals: how good they are, do they translate in proper PMF (we are not talking about products, still we need to do stuff that make sense in the real world, not only in our heads)
  • the quality of people executing these proposals: as usual, world and our dao is plenty of good ideas, plenty of capital, and lacks people able to do things.
  • the ability to anticipate proper narratives: crypto goes fast, we don’t want to have a short term goal that is compatible with 2024 trends but not future ones.

I’ll do an example even if it’s about going a bit ahead.

One of the goals might be (and will likely be) arbitrum as the home of defi. Might be too generic, but is also extremely compatible with our ethos, history, and products.
Is pretty clear now that AI is not only gonna play a role in crypto, but also in defi; on this, arbitrum is behind. So expressing arbitrum as home of defi, without having the end result of having a bucket to strongly finance ai developments natively in arbitrum would likely be a huge fumble.


All of the above are very general consideration, that don’t really influence this proposal.
But I have something that I think would be worth changing: while SOS sets short term (1y) and mid term (2y) goals, we should do it in 4/6 months epoch.

1 year, in crypto, is a lot. We didn’t had AI in crypto 1 year ago. We barely had it 6 months ago. Is the predominant trend now.
In an approach that is a bit monolithic, we risk to actualize the goals in a way that is backward looking. Few people are able to forecast future trends, and usually they don’t get listened by the crowd.

This could be partially solved by having epochs long 4/6 months in which

  1. we review the previous strategic goals established in the previous SOSs epochs: are they still compatible with the overarching goals of MVP? 9 times out of 10 the answer will be yes
  2. we review the initiatives tied to the specific goals that got approved in the previous SOSs epochs: are these initiatives an efficient, on trend, valuable actualization of the goals? likely 7-8 out of 10 the answer will be yes
  3. we review the landscape of crypto, in relation to the SOS goals: are there initiatives that we didn’t think about that are now prominent for that very specific goal? we might find that, yes, 4-6 months ago we decided that arbitrum is the home of defi, but we didn’t forecast the impact of ai on defi and we don’t have any initiative ai related to growth that verticle in relation to interaction with smart contracts, yield etc → ok here we reopen the discussion, likely starting at that level that is intermediate between sos and budget/marketing, to open a venue to develop AI framework and bot in relation to defi natively in arbitrum to attract developer.

Let me know if you think this makes sense. It is for sure more overhead, more time consuming, and requires more attention. I honestly think that we need some sort of agility and ability to adjust during the run.
Maybe this was already backed in the proposal tho and I misunderstood it.

Main opposition on the above would be: daos are slow, our dao can be slow, is difficult to find consensus and after finding consensus going back to it to rewrite part of the thesis adds a lot of friction. I could accept this, because is true, but we should at least try to strive for the process that gives us the best possible outcome.

1 Like

The core of this proposal is to establish clear short- and mid-term goals for the DAO, providing the community with a focused direction and avoiding resource dispersion. This approach is commendable, particularly with its periodic reviews and adjustments, making it more practical. However, the second phase of the process (from announcement to final voting) spans three months, and the entire procedure, including announcement, submission, feedback, revision, and voting, totals approximately three months. This lengthy cycle might not be favorable for the DAO’s decision-making efficiency, especially in a fast-changing market environment, potentially causing missed opportunities. I suggest introducing a rapid decision-making mechanism for urgent goals to shorten the process duration.
2. Although the proposal emphasizes measurable results for objectives, how can we ensure the feasibility of the submitted goals? I propose incorporating an initial screening stage involving experts or community technical members to make the objectives more grounded. If feasible, perhaps a discussion on the necessity of feasibility analysis and execution details is warranted.
3. Submitting and evaluating objectives might demand considerable time and effort. How can more people be encouraged to participate? For instance, offering rewards to contributors who propose excellent goals could be a motivating factor. I think it must be incentivised, to give incentives can’t fail people, it can be incentivised on a linear release basis
4. The role of Entropy in this proposal is pivotal. While I highly value their work—they have demonstrated their competence in many key proposals and are an outstanding team worthy of respect :saluting_face:—I wonder if this might overly centralize the process within a single team. Personally, I recommend involving more community representatives in the formulation and evaluation of SOS.
5. I’ve noticed many proposals mentioning RWA. Personally, I think it’s better to start with a pilot in a specific subfield, such as DeFi - RWA, gain experience, and then expand to a full-scale strategic objective framework for the DAO.
6. The proposal does not delve deeply into the execution process after goals are selected—for instance, who will be responsible for implementation, how the budget will be allocated, and how outcomes will be evaluated. I suggest supplementing a detailed implementation mechanism to ensure the goals not only remain at the strategic level but also effectively drive ecosystem growth. Additionally, the proposal does not address how to adjust if a goal fails to meet expectations. A dynamic adjustment mechanism, such as quarterly reports assessing the feasibility of goals and optimizing resource allocation, should be included.

In summary, a strategic framework of this significance, which involves the overarching design of the DAO, requires a clear strategic direction, making it essential.

1 Like

A solution here is using Harmonica.chat which we developed specifically for this purpose (funded by Arbitrum via the Research Fellowships).

It’s meant to be used to converge before there are proposals being voted upon. So that leads to less proposal and stronger proposals. The alternative is less democratic and less effective backchanneling and private convos.

5 Likes

Suggestion to Enhance OKR Gathering with Harmonica

Hi Entropy Team,

We believe Harmonica could be a valuable addition to your OKR gathering process by helping you efficiently collect, structure, and analyze community input. Harmonica is an AI-powered sense-making tool designed to gather actionable objectives and measurable key results from participants in a transparent and inclusive way. Developed during the RnDAO CoLab Fellowship funded by the Arbitrum DAO earlier this year, Harmonica is tailored to support community-driven initiatives like yours.

How Harmonica Could Support the OKR Process

  • For Participants: Each session asks participants to propose one specific objective along with 1-3 measurable key results. Sessions are designed to take only 2-5 minutes to complete, can be done asynchronously at the participant’s convenience, and support submissions in most popular languages.
  • For Facilitators: Input gathered can be clustered and prioritized to identify actionable themes and align goals with the DAO’s collective sentiment.
  • Transparency: Results can be easily shared with the community, fostering trust and accountability.

Example Session Ready for Use

To demonstrate its potential, we’ve set up an example Harmonica session tailored for the Arbitrum DAO’s OKR process, ready to use with your consent:

Access the session here

Benefits of Using Harmonica

  • Efficiency: Reduces the workload of collecting, sorting, and analyzing inputs.
  • Inclusivity: Enables submissions in multiple languages and asynchronous participation.
  • Clarity: Encourages high-quality, focused contributions by limiting each session to one objective and 1-3 key results.
  • Convenience: Sessions are quick and take only a few minutes, making participation simple and accessible.

Offer to Support You

If this approach aligns with your needs, we’re happy to:

  • Adjust the session to include any additional parameters or requirements.
  • Provide a walkthrough of the platform for your team.
  • Help analyze and interpret the results to ensure actionable outcomes.

Since the Arbitrum DAO’s funding helped enable Harmonica’s development, it’s only fitting to see it contribute back to the community. If you think Harmonica could enhance your OKR gathering process, we’d love to collaborate. Please let us know your thoughts!

Best regards,
ChrisB
On behalf of the Harmonica Team

3 Likes

Love the thought and effort put into this so thank you Entropy for the proposal.

We were looking at this portion of the proposal and are concerned that this statement is quite vague.

Rather than leaving this to the delegates, we believe this as well could fall into OpCo’s jurisdiction once they are operationalized. This way, we are sure someone is always on top of these ad hoc changes and how they affect the DAO’s objectives.

1 Like