# data[].attributes.body
Sustain: center the Fellow's experience/voice throughout the design and programming.

Different: time/timing for planning is a tricky balance when we are allowing for the emergent and bound to very specific institutional deadlines. It would be great to start the planning/design process early enough that we could more fully include feedback/collaboration with ESP.

# data[].attributes.headline
Trust and Intimacy builds transparency in sharing what people know and are coming to know. When I think about our expectations for the Fellows to really give us access to their personal and professional learning edge, I just don't know if they were ready up until know to trust us with that. In retrospect, they are still deepening their relationships with us as a Program team, and starting to feel like we are a trusted learning partner.  I think the Co-Design process helped this trust, community building a lot.  I wonder if our beliefs and expectations about what and how much the Fellows would share with us about themselves and their work were in proper range.

# data[].attributes.subject
Trust and Intimacy builds transparency in sharing what people know and are coming to know. When I think about our expectations for the Fellows to really give us access to their personal and professional learning edge, I just don't know if they were ready up until know to trust us with that. In retrospect, they are still deepening their relationships with us as a Program team, and starting to feel like we are a trusted learning partner.  I think the Co-Design process helped this trust, community building a lot.  I wonder if our beliefs and expectations about what and how much the Fellows would share with us about themselves and their work were in proper range.

# data[].attributes.body
I think the biggest thing I wished we had done differently was in relation to managing our time. I feel like we spent a lot of time conceptualizing and discussing and then when we started bumping up against deadlines we hadn't necessarily adequately finished those convos. Not sure if it's the timing of the meeting (Thurs right before end of week) or if our ideas about the convening event ultimately were more separate than summer experiments and convos should have happened simultaneously instead of sequentially.

I do want us to sustain bringing the creativity we have into the room - I deeply appreciate and have learned from everyone on this team and feel like we each bring perspectives/skills that others need. I want to sustain us bringing that into our work together.

# data[].attributes.headline
Milano H. In retrospect, I think we made some great calls to anchor the WORK in the Fellows' Stories of Self, to prioritize trust and community building to create a foundation underneath us. Still, I would deploy our Design and Evaluation team efforts differently. In this first year, trying to co-design the actual Program architecture and program activity with Fellows, and also trying to co-develop the Evaluation developmentally is very challenging to add to the Program team's plate. Not sure how to do this differently, but - for me - really keeping the Fellows in the center, makes it challenging to work together this way. 

# data[].attributes.subject
Milano H. In retrospect, I think we made some great calls to anchor the WORK in the Fellows' Stories of Self, to prioritize trust and community building to create a foundation underneath us. Still, I would deploy our Design and Evaluation team efforts differently. In this first year, trying to co-design the actual Program architecture and program activity with Fellows, and also trying to co-develop the Evaluation developmentally is very challenging to add to the Program team's plate. Not sure how to do this differently, but - for me - really keeping the Fellows in the center, makes it challenging to work together this way. 

# data[].attributes.headline
it's important to call out both what's working and what's not

# data[].attributes.subject
it's important to call out both what's working and what's not

# data[].attributes.body
I think we've been able to identify and reiterate certain tools/practices (notes templates, Emergent Learning tables, AAR/BARs, opening meetings intentionally, etc) that are working but haven't necessarily been able to make time to figure out what's not. Ultimately co-design (at least how I define it) takes a lot more time than maybe we actually have available...

I think also something I've learned is that we are all continually improving and committed to figuring it out, which leads to further trust and iteration

# data[].attributes.headline
Milano H. For me, I think our group could be careful not to over-depend on upfront, deductive reasoning vs. some courageous, thoughtful but loose learning experiments. Finding that just right balance between Learning by Doing approaches vs. a more traditional hypothesis driven design process is key. With so many different variables at play, ultimately the knowing came in the GOING/DOING vs. standing separate from the people and the process, hypothesizing.

# data[].attributes.subject
Milano H. For me, I think our group could be careful not to over-depend on upfront, deductive reasoning vs. some courageous, thoughtful but loose learning experiments. Finding that just right balance between Learning by Doing approaches vs. a more traditional hypothesis driven design process is key. With so many different variables at play, ultimately the knowing came in the GOING/DOING vs. standing separate from the people and the process, hypothesizing.

# data[].attributes.headline
I have a wondering which is not actually included in these two padlets so I'm taking a cue from Adria and putting it here  -- it's around what we learned from the week with fellows - how our expectations met the reality -- how much we expected from them, especially on the last day in sense-making and whether our expectations were a bit too high?  I hope we can find the time to reflect on such issues as timing, learning, and when to expect deeper reflection to come out of the processes we designed.  

# data[].attributes.subject
I have a wondering which is not actually included in these two padlets so I'm taking a cue from Adria and putting it here  -- it's around what we learned from the week with fellows - how our expectations met the reality -- how much we expected from them, especially on the last day in sense-making and whether our expectations were a bit too high?  I hope we can find the time to reflect on such issues as timing, learning, and when to expect deeper reflection to come out of the processes we designed.  

# data[].attributes.headline
I often say in our cohort calls and in our designs, that we often try to do too much in too little time.  I think this is true in our work together as well.  Is it possible to get more realistic in how we manage our meetings and make sure we prioritize what is essential for moving forward?

# data[].attributes.subject
I often say in our cohort calls and in our designs, that we often try to do too much in too little time.  I think this is true in our work together as well.  Is it possible to get more realistic in how we manage our meetings and make sure we prioritize what is essential for moving forward?

# data[].attributes.headline
Somewhat.  Referring to my expectations specifically, 

# data[].attributes.subject
Somewhat.  Referring to my expectations specifically, 

# data[].attributes.body
1) I think we can still use some reflection on our various expectations of co-design - how we do it together and how we do it with fellows;
2) Our meetings can sometimes get bogged down and topics can get bumped.  In preparing for this particular AAR exercise, I realized with Charles that we never did a BAR for the gathering and for co-design.  I think this contributed to some of the bumps in the road.
3) I have a sense that we still are not aligned in what works best for design of the program and design of L&E. Is it that our expectations are not aligned?

# data[].attributes.body
1) Have more clarity on what co-design actually means for all of us.
2) Get more efficient in how we work as a team and move more artfully together and use our time wisely, especially meeting time;
3) make progress on finding the right balance between program design and L&E;

# data[].attributes.headline
We need to honor that time is a very real parameter and we might not be able to do everything - we'll need to prioritize and put everything in context of space and time. (Samera)

# data[].attributes.subject
We need to honor that time is a very real parameter and we might not be able to do everything - we'll need to prioritize and put everything in context of space and time. (Samera)

# data[].attributes.body
If I could go back, I would have held us to our initial timelines around planning, communications, activities. The timeline was initially designed with more spaciousness for co-design with Fellows and more lead time for pre-convening activities. Moving forward, I'd like to see us to keep a level of flexibility, but I would like to see conceptual and theoretical conversations be paired with practical and operational aspects.  This may require us to make decisions and prioritize things.

# data[].attributes.headline
It's a continuous cycle of ideas and experiments (Samera)

# data[].attributes.subject
It's a continuous cycle of ideas and experiments (Samera)

# data[].attributes.body
I've learned that we need a cycle of initial brainstorm, then iterations of a creation for everyone to respond to, then more ideas, then more iteration. I also learned that sometimes we get stuck waiting in one aspect of the cycle and that can hold up the timeline.

I've learned that co-designing with a group of brilliant people has looked like saying yes to trying everything. However, the real limitations of time also require some practical prioritizing or limiting. We can't only say we want "more" of something, we must also acknowledge that it might mean less of something else, and we'll need to prioritize ideas.

# data[].attributes.body
We met my expectations because we held things open for Fellow brainstorms and priorities. Then, we gave them some foundational structure to respond and bring themselves to specific areas. And they all really showed up.
Amongst our partner teams, things happened as I expected - we brainstormed together, then the IIE team provided a basis for other teams to respond and build on.

# data[].attributes.headline
Driving ahead and also ready to pivot (Samera)

# data[].attributes.subject
Driving ahead and also ready to pivot (Samera)

# data[].attributes.body
- Among the team: A cycle of brainstorming, building, revising or pivoting based on initial plans, and addressing critical questions.
- Robust sloppy copies with a number of iterations based on expertise and experience.
- Starting somewhere with enough detail so that others can enter, but holding it loose enough to flow freely based on input
- Build a little so that Fellows would be able to have a foundation for their design and contribution, and being ready to change with their input.

# data[].attributes.body
It makes the learning and experience more relevant and rich for all of us.

# data[].attributes.headline
Do Differently: Increase clarity of the role of coaching in program design

# data[].attributes.subject
Do Differently: Increase clarity of the role of coaching in program design

# data[].attributes.body
-Is coaching only an individual Fellow experience that walks along side the gatherings and other collective touch points with Fellows
-Is coaching a more visibly integrated component of the Fellow experience that has the coaches more intentionally supporting the Fellows learning and integration of the components from the gatherings, example: Visualize, Story Canvas, and what is yet to come...

# data[].attributes.body
-It requires a lot of time and space to hear, understand and integrate all participants.
-there are many voices
-sometimes not all voices are heard
-often we run out of time
-decisions have to be made meet meet hard deadlines and it isn't always clear who has authority to make decisions, therefore they are revisited

# data[].attributes.body
-The integration of the Fellows voice in co-design guided some of design. There seemed to be adjustments when integrating strategic communications into the design. Some stalls on launching the visualize exercise with the Fellows because it was continuing to be modified and redesigned.
-there is still lack of clarity on how coaching is more visible and integrated in the overall Fellow experience and reinforces the learning that Fellows are gaining in the gathering space

# data[].attributes.body
We are still in the scanning phase, trying to identify all the different components and participants, not seeing all of the parts clearly, and discovering how they fit together.

# data[].attributes.headline
Sustain - frequent interactions with Fellows as part of co-design

# data[].attributes.subject
Sustain - frequent interactions with Fellows as part of co-design

# data[].attributes.body
Building conversations with Fellows and between Fellows that are actually part of the entire Fellowship program experience - I am hypothesizing that it was through these multiple co-design conversations that the Community trust was created....leading to such an authentic and rich exchange

# data[].attributes.body
I would have insisted on a nuts and bolts backwards planning conversation to ensure we had the co-design steps in the plan early on - this might have helped establish more accurate expectations around the co-design practice

# data[].attributes.body
I have learned that my long-ago question "what does co-design mean to you" which I posed to the full partner team was a good question and that we are still answering it and developing a shared sense of praxis around co-design for this program

# data[].attributes.headline
Co-design is emergent and interdependent

# data[].attributes.subject
Co-design is emergent and interdependent

# data[].attributes.body
My expectations about co-design:
- co-design would require more time and investment and a willingness to be open to changes throughout the process
- co-design would challenge our inclinations for "parallel play" rather than deep collaborative co-constructions which requires give and take both with Fellows and with in FGF partner tea
- co-design would yield more inclusive and more grounded experiences led by the Fellow
- co-design would require us as a partner team to trust and believe that collectively the Fellows already had everything they needed
- co-design would also requires Partner team members to actively engage with their own expertise in partnership with the Fellows
- co-design would prompt us all to learn the most about what we are creating together

# data[].attributes.headline
how can we continue to rich conversations around the program design frameworks and also leave enough time, space for the operationalizing

# data[].attributes.subject
how can we continue to rich conversations around the program design frameworks and also leave enough time, space for the operationalizing

# data[].attributes.body
Overall, my expectations about ambiguity and experimentation were met. Also the gradual trust-building we've had as a team.

I think where my expectations haven't been met have been connected to assumptions about scope and how L&E and program design co-exist and overlap - and ultimately what it takes to actually figure that out. I'm not sure we've gotten there yet.

# data[].attributes.body
My expectations, outlined to the left, to some extent were met.

- Expectations about time commitment, investment, toggling between theory and practice, building the foundation for the fellowship were consistent with what I expected.
- I was surprised that others on the partner team seemed to be surprised by the amount of time required to achieve true collective co-design
- I was surprised by what felt to me like vast differences in the very definition  of "co-design" and what that could look like with the Fellows
- I am delighted that the in the end we did implement co-design in which Fellows hopefully saw their hand in it while not being overwhelmed with the event architecture

# data[].attributes.body
I think we have made visible progress since June! And there is still undoubtedly a ways to go. Particularly in regards to coming to a shared understanding of what co-design actually means for this group. That being said, I think we've laid a strong foundation for what is to come in 2021.

In regards to success, I think repeatedly coming back to centering the fellow experience above all has paid off.

# data[].attributes.body
The whole premise of our work together so far is "building the plane as we're flying it" and that has framed my expectations. I had expectations of ambiguity and trying to figure things out and testing different ways to communicate or establishing best practices. But I also had assumptions that we had shared ideas about roles/scopes, which also framed some of my expectations related to working together process-wise and co-design wise..

# data[].attributes.body
Given that we are still getting to know each other as individuals/teams and begin to see how we might work as a whole, I expected us to still be in a learning /adapting phase.

# data[].attributes.headline
while its great to have partner meetings with everyone, it also seems that perhaps we should identify some sub-groups moving forward

# data[].attributes.subject
while its great to have partner meetings with everyone, it also seems that perhaps we should identify some sub-groups moving forward

# data[].attributes.headline
there are many moving pieces and stakeholders; this group is also moves deeply into theoretical discussion which is important however we then sometimes don't get to the more concrete action steps or even thinking through implications

# data[].attributes.subject
there are many moving pieces and stakeholders; this group is also moves deeply into theoretical discussion which is important however we then sometimes don't get to the more concrete action steps or even thinking through implications

# data[].attributes.body
There's a shared understanding of how these are useful for Team reflection and they were useful for connecting team learning to Ford learning questions.

# data[].attributes.body
Looking back, I wish we had mapped the Change Sketch outcomes to outcomes for each session and activity. We (IREX) could have provided a template for this. I also would have liked to go over the L&E Framework prior to the convening prep. (Charles)

# data[].attributes.body
The Theory of action was embedded in the program design brief which did help others engage and identify key outcomes and assumptions.  It was also very useful to have over email a list of learning questions and priorities to inform the post-convening survey.

My expectations for dialogue about what we wanted to evaluate and learn or how they connected to an L&E framework were only partly met. The time crunch contributed to that. A discussion of the L&E framework got bumped off of a partner call meeting as was a December BAR/AAR. (Charles)

# data[].attributes.headline
visibility into the program design & learning/evaluation design

# data[].attributes.subject
visibility into the program design & learning/evaluation design

# data[].attributes.body
I expected the thinking behind the program design -- the intended outcomes, expected challenges, and design considerations - to be visible so that everyone could more easily engage and contribute. This visible program design is also important for the Learning & eval design...to know what outcomes to evaluate, what assumptions to test, and what we want to learn, especially in relation to Ford L&E questions.

I also expected a dialogue about how the program design related to the learning & evaluation design. What were the most important assumptions and questions and how would we evaluate and learn?
(Charles)

# data[].attributes.headline
seems like we had a lot of good exchange, identified underlying assumptions. continuing to value this work together, centering the fellows and our relationships contributed.

# data[].attributes.subject
seems like we had a lot of good exchange, identified underlying assumptions. continuing to value this work together, centering the fellows and our relationships contributed.

# data[].attributes.headline
lots of thoughtful discussion, still figuring out what this means/how to do

# data[].attributes.subject
lots of thoughtful discussion, still figuring out what this means/how to do

# data[].attributes.body
ESP was a huge value add and felt like a big support for many team members.

# data[].attributes.headline
Continued learning about con-current translation

# data[].attributes.subject
Continued learning about con-current translation

# data[].attributes.body
-Nuances of facilitating small groups in main room
-Limitations on web-browser or phone (possibility of close captioning as solution or?)
-Need for adequate prep for translator team
-Need for reminders every time from breakout to reselect language channel
-Translation doesn't come through in Zoom transcript (is there another way to record this?)

# data[].attributes.body
Multiple team members noted that time with Hilary, Paula and Darren felt too short and that experiments with bringing them in during breaks need more thought

# data[].attributes.body
Several team members noted the lift of time in terms of Fellow-facing communication ahead of the event, as well as managing our time during the event