<aside> đź’ˇ Below are the steps taken when formulating the importance of a proposal within a Whole System.

</aside>

  1. Is the proposal critical? (Critical solution)

In case an identified solution has misalignment on whether it’s critical or not, look at timelines, resources, roles and goals, and consider other options on the meta level before writing the proposal. Example we need roads to drive in the village. (as an identified goal or next step) however we should reconsider other transportation as a possible solution. If it’s already been decided cars are needed and they are needed in 2 months, then we have a very clear timeline which makes this critical.

  1. Related to Scope, is a Solution, but is not critical (emergent solution):

In these cases we use the advice process, panel of experts, pre-proposal table and if passes, then we create the official proposal.

Assuming it passes, and after proposal has passed: Emergent solutions always go through build phase, then test phase (if funding needed, funding pool or HART decides if it’s valid expense) before implementing. Even then, there is a test period again.

  1. Not related to Scope (we consider not a solution - Preference - apply preference protocol)
  2. Other preferences. Example: changing the wall color.
    1. Might be attached to the scope, but not critical and not solving a problem that has been officially identified by the collective.
    2. If a problem has been identified, then this can move from preference to solutio. In this case we would pass through the pre-proposal process and implement an 80% vote as well to ensure it’s considered by most a “Solution”. If passes, can be entered as solution. (A new next step would be formed in the Ecoplan that identifies the need for a solution to something)

Definition of Solutions and Preferences