# data[].attributes.headline
To refine the Story Canvas into an inviting "breakthrough" framework/tool  for helping the Fellows share more of the intimate details and nuances of their individual Stories of Work.  (mh)

# data[].attributes.subject
To refine the Story Canvas into an inviting "breakthrough" framework/tool  for helping the Fellows share more of the intimate details and nuances of their individual Stories of Work.  (mh)

# data[].attributes.body
To continue to innovate each learning engagement/experiment at a time even more powerful ways for the Fellows to engage, connect, share, challenge and deepen their work and development; and build out the larger Community of Practice. (mh)
To set a strong process of Co-Design in place that inspires the Fellows to share their best thinking and wisdom for novel ways to engage each other in October, November and culminate in December Convening. (mh)

# data[].attributes.body
Better access to data and insights into Fellow work and context and into the larger Community of Practice growth and development for the purpose of informing program design, addressing learning questions about the change process and inequality, and to create sense of proximity to Fellows' work.

# data[].attributes.body
Develop a more strategic approach to gathering feedback from Fellows on the program design and learning priorities and then closing that feedback loop with Fellows by sharing back our learning through a shared sense-making process.

# data[].attributes.headline
Co-design sessions with maximum engagement with fellows. (SE)

# data[].attributes.subject
Co-design sessions with maximum engagement with fellows. (SE)

# data[].attributes.body
Create an open and encouraging space where Fellows can build on and improve the Story Canvas framework.

# data[].attributes.body
The co-design sessions are the week after the cohort call and one challenge could be scheduling/allocating time on their calendars. We can include a number of reminders/reinforcements for the session and also include ways for Fellows to contribute even if they cannot attend this session.

# data[].attributes.headline
Multiple ways for Fellows to enter co-design

# data[].attributes.subject
Multiple ways for Fellows to enter co-design

# data[].attributes.body
All together and in small groups during the cohort call, specific targeted outreach, Fellows to partner/pair on ways to engage.

# data[].attributes.headline
Have the majority of Fellows launch w/coaches (MS)

# data[].attributes.subject
Have the majority of Fellows launch w/coaches (MS)

# data[].attributes.body
Start to build a more visible feedback loop on the coaching themes.

# data[].attributes.body
We are seeing some challenges with Fellows not responding to the launch for coaching.

# data[].attributes.headline
Multiple contacts/touch points to nudge Fellows (MS)

# data[].attributes.subject
Multiple contacts/touch points to nudge Fellows (MS)

# data[].attributes.body
Emails from Mary, Samera, WhatsApp contact have worked in the past to support Fellows to engage.

# data[].attributes.headline
Collab among FGF team about communicating with Fellows

# data[].attributes.subject
Collab among FGF team about communicating with Fellows

# data[].attributes.headline
It has gratifying to see us move to a wonderful concept and framework, and brilliant design, for the Story Canvas.  All of the work Milano and Samera did with the graphic designer brought together the excellent collaborative input that came from the entire team.  So I think the deep discussions we have all had at partner meetings and in other discussions has lead us to the result which we are excited to share with the fellows soon. 

# data[].attributes.subject
It has gratifying to see us move to a wonderful concept and framework, and brilliant design, for the Story Canvas.  All of the work Milano and Samera did with the graphic designer brought together the excellent collaborative input that came from the entire team.  So I think the deep discussions we have all had at partner meetings and in other discussions has lead us to the result which we are excited to share with the fellows soon. 

# data[].attributes.headline
In terms of co-design, for me I think the October 28 call was a big step forward.  The session created space for fellows to identify their learning goals for the SoTW and some initial ideas for moving forward.  I think one big contributing factor in what caused the result is the work we have all done so far to focus on keeping the container strong for fellows' relationship and trust-building.  Each week I see fellows being more comfortable - whether in large or small groups - with expressing their vulnerabilities, and more expressions of care for each other and delight in meeting more deeply with folks they have not met before.  

# data[].attributes.subject
In terms of co-design, for me I think the October 28 call was a big step forward.  The session created space for fellows to identify their learning goals for the SoTW and some initial ideas for moving forward.  I think one big contributing factor in what caused the result is the work we have all done so far to focus on keeping the container strong for fellows' relationship and trust-building.  Each week I see fellows being more comfortable - whether in large or small groups - with expressing their vulnerabilities, and more expressions of care for each other and delight in meeting more deeply with folks they have not met before.  

# data[].attributes.headline
In terms of the Learning Log, we are still not seeing fellows engage with it as we had hoped.  In reflecting on what is influencing this result, I wonder if we still haven't anchored well enough for them in a way that is valuable to them.  I don't think continuing to remind them to put things in the log is useful.  I'm holding a question about this as we move further into the SoTW.

# data[].attributes.subject
In terms of the Learning Log, we are still not seeing fellows engage with it as we had hoped.  In reflecting on what is influencing this result, I wonder if we still haven't anchored well enough for them in a way that is valuable to them.  I don't think continuing to remind them to put things in the log is useful.  I'm holding a question about this as we move further into the SoTW.

# data[].attributes.headline
It feels like the pace is picking up - there have been weekly calls to design and activities to implement more quickly than before.  Sustaining our good partner communications and especially bringing our various thoughts to the all partner meeting is so helpful.  I think communications and expectations have improved and we are clearer with each other.  

# data[].attributes.subject
It feels like the pace is picking up - there have been weekly calls to design and activities to implement more quickly than before.  Sustaining our good partner communications and especially bringing our various thoughts to the all partner meeting is so helpful.  I think communications and expectations have improved and we are clearer with each other.  

# data[].attributes.headline
Keep highlighting and involving fellows in calls -- highlight their work, involve them in sense-making, etc.  I think more of this will be happening in the next several weeks as they get more involved in co-design.

# data[].attributes.subject
Keep highlighting and involving fellows in calls -- highlight their work, involve them in sense-making, etc.  I think more of this will be happening in the next several weeks as they get more involved in co-design.

# data[].attributes.headline
I'm wondering if we are getting timely feedback on documents we put up on Google Docs or Slack or email.  I know I sometimes have trouble managing all of these different portals and wonder if it's just me.  

# data[].attributes.subject
I'm wondering if we are getting timely feedback on documents we put up on Google Docs or Slack or email.  I know I sometimes have trouble managing all of these different portals and wonder if it's just me.  

# data[].attributes.headline
I think there is already a lot of innovation going on - the wonderful work Samera and Milano did, with input from so many, on the Story Canvas is a great innovation -- taking a concept and adapting it to this context.  I think we will stay nimble with innovation as we listen more to what fellows bring to the table in the coming weeks.  

# data[].attributes.subject
I think there is already a lot of innovation going on - the wonderful work Samera and Milano did, with input from so many, on the Story Canvas is a great innovation -- taking a concept and adapting it to this context.  I think we will stay nimble with innovation as we listen more to what fellows bring to the table in the coming weeks.  

# data[].attributes.headline
Co-design process is off to a great start

# data[].attributes.subject
Co-design process is off to a great start

# data[].attributes.body
The FGF Partner team as a whole is beginning to engage is co-creation with Fellows in a way that invites Fellows' ideas and contributions to shape the content of the learning for the Fellowship. Specific practices: creating sessions with sufficient scaffolding and real spacious timing to allow for co-thinking and creation; focusing on what we are asking ourselves and Fellows to accomplish in a given setting; prioritizing relationship over task as we are building the CoP container for the long haul

# data[].attributes.headline
Extended grant agreements with Fellows through Aug 2022

# data[].attributes.subject
Extended grant agreements with Fellows through Aug 2022

# data[].attributes.body
Intended programmatic result: This will hopefully support continued and more active virtual engagement from Fellows as we created explicit "asks" for this virtual context to continue through 2022
What caused this result: careful stakeholder enrollment over the summer

# data[].attributes.headline
Learning Framework made significant progress

# data[].attributes.subject
Learning Framework made significant progress

# data[].attributes.body
Result: With IREX team and Subarna, refined the L&E framework and began to move it towards its final draft form....recognizing that it is an iterative document. What caused this result: IREX team lead multiple discussions and moved forward incrementally with each conversation.

# data[].attributes.body
Adria has continued seeking guidance on best practices from Otto Scharmer/Presencing Institute, Bill Snyder/CoP expert, and other leaders of fellowships

# data[].attributes.headline
Slowing down to assess foundational decisions

# data[].attributes.subject
Slowing down to assess foundational decisions

# data[].attributes.body
At several points, we have slowed ourselves down to ensure we are really understanding the concepts and design decisions we are making, especially ones that will be foundational for the underlying values and assumptions for the fellowship. This included:
- care packages for Fellows
- assessing the most effective communications channels (FGFellow Community WhatsApp)
- determining the best facilitators/process decisions to ensure we are holding the community relationships at the center of our work
- continuing to refine and interpret what we are learning about effective virtual engagement

# data[].attributes.body
We are in an innovative space by the very nature of building a completely virtual Fellowship for the next year. I think this context will continue to call upon us to release "what we know" about F2F convening and build and test ideas in this new context.

# data[].attributes.body
How are we best able to see each others' workflows and track where our work is in relation to others? I see lots of qualitative information flowing via Slack and Padlets, but I am not sure if we have a collective line of sight into the work we are currently doing and where we are headed. I propose that in Dec after the convening (but before December breaks) we have a "state of the work" meeting to get fully on the page for first and second quarter 2021.

# data[].attributes.body
It was very meaningful to have Milano join the October coach call to gather insights/reflections on the Story Canvas which I think resulted in some valuable adjustments to the design

# data[].attributes.headline
Regular links between Program & Coaches (MS)

# data[].attributes.subject
Regular links between Program & Coaches (MS)

# data[].attributes.body
Charles joined the November call and we are starting to see the value building more intentional links between the coaching component and other components.

# data[].attributes.body
We are happy with the progress made with the Learning and evaluation framework. There is more clarity in how the different pieces (questions, ToA, change sketches, data collection) come together. The feedback we got from Subarna and Libby really helped us get it to the next level.

# data[].attributes.body
Took early steps to identify how and when we will engage Fellows in the co-design of tools. An SNA survey was drafted.

# data[].attributes.body
To fully embrace that we can't do as much as we might have thought was realistic pre-pandemic. Reducing the number of agenda items per meeting, building longer runways so there is room for adding meetings for co-design. "Simplify and Focus", perhaps have some framing questions before we say yes, "Is this critical?" "How much time will it take, adding in more time than we would previously estimate."... etc.

# data[].attributes.body
We have been curating hypothesized outcomes and emerging learning questions that have come up during all partner calls.

# data[].attributes.body
We've started collecting new learning questions about the selection process and implications for the cohort expansion that impact Ford learning.

# data[].attributes.body
Continue conversations with woodrow wilson and start regular calls with Ford Comms (Marc) to understand how Fellows and FGF is influencing Ford and vice-versa.

# data[].attributes.body
Through working on a data management strategy and dashboard tool, we were able to use data to inform pairings during Cohort call

# data[].attributes.body
We developed a timeline for Fellow-facing data collection that can integrate with other Fellow communications and gives us a sense of what we want to measure, why and when

# data[].attributes.body
Our communication this month around pushing aspects of the work forward felt like it clicked more than previous times. The agenda planning felt more in sync & able to balance different streams of work, as well as specific communication about engaging Fellows across diff activities

# data[].attributes.body
We started with a great co-design call but figuring out the "how" of co-design with fellows when the co-designing activities have to be designed is an innovation. How to find the balance and figure out how to include Fellows (& balance our input/voices/expertise as holding the container with keeping theirs central) while still driving the work forward is something we can continue innovating

# data[].attributes.headline
Managing our time in meetings & process for decision-making

# data[].attributes.subject
Managing our time in meetings & process for decision-making

# data[].attributes.body
We are a verbose crowd and meaning-making is often much better in "face to face" meetings than asynchronously. BUT we often run out of time/go over. Can we either anticipate needing more time & scheduling as such and/or a standing follow-up call if needed for Fridays to help finalize decisions that didn't quite get made?

# data[].attributes.body
We figured out a strategy that works to capture what happens in calls - notetaking templates!