Samara's Structural Elements

WhatIrina are- Not sure if we still want this chapter in, I added some content as a first draft with some basic content. 

The path to the elementscurrent phase of Samara

It took us a while in Samara to define de work that should go here? (irina)

Answeringneeds to myself,be done and where to start in order to create a DHO. Some of the initial steps that proved to be helpful on the way:

We start identifying some furtherkey missingresults pieces,(KRs) willwe addwould thoselike hereto forget now:to One KR became one pod (small team of 3-5 people to work on a specific topic)

-At organizinga worklater aroundstage KRs 
-we further evolved a new KRs becamemap: 

pods
-

podsKRs becamewere Primaryadded pods

Toolstogether thatin workedsome specific areas such as "Samara Game Guide", "Samara purpose, values and tools", "Samara Local Pilots", "Samara Offerings" Each member indicated the commitment (%) for us:
- Miro board with KRs, pods, contributors to each KR, Commitment to each KR
- ContributionsSome spreadsheetof the KRs become a priority, with a lot of members committed to that specific work

Yes,As the work on each area advanced, it become clear that there are a lot of connections between KRs and alsothat some conversations need to take place in the same time. 

KR pods transitioned to Primary Pods, each primary pod working on a specific area, with the work being focused on 3 main areas: "Samara Soil / Game Guide", "Roots / Samara Purpose Practice Tools" and "Branches" Each Samara member was part of one Primary Pod A space for knowledge garden was created for each Primary Pod

The Primary Pods with about 4 proved to be a good structure for being able to coordinate between members, schedule calls and do asynchronous work while keeping connection close.

 The Path forward

Samara will further asses how the Primary Pods can serve it on its future circlespath and holonshow -the JS


structure will evolve to other working teams and more permanent circles in the future.