Launch Event
May 3, 2013 Connecticut Design Session #1
Thursday, May 18, 2017 www.BostonFed.org/WorkingCities @WorkingCities | Facebook.com/WorkingCities
1
Launch Event May 3, 2013 Connecticut Design Session #1 Thursday, May - - PowerPoint PPT Presentation
Launch Event May 3, 2013 Connecticut Design Session #1 Thursday, May 18, 2017 www.BostonFed.org/WorkingCities 1 @WorkingCities | Facebook.com/WorkingCities Introductions What 2-3 gifts or skills make you a good family member and friend? What
May 3, 2013 Connecticut Design Session #1
1
2
3
4
CT Design Session #1 Thursday, May 18, 2017 AGENDA
9:00 Opening, Agenda Preview 9:30 Insight into the Working Cities Challenge from MA 9:50 Refining your team’s problem statement Teams work independently; Break at team’s discretion 11:20 Data for learning & understanding your challenge 11:30 Defining Leadership Noon LUNCH 12:45 Symbols 1:15 Introduction to Adaptive Leadership Teams work independently; Break at team’s discretion 2:45 Adaptive Learning 3:30 Leadership Compass 3:50 Closing
5
AM – Problem Statement / Econ Growth Challenge & Root Causes – the ‘what’ Your teams have already identified a problem statement in your design
causes contributing to your problem.
also share how your team can make the most of the design phase
problem statement and discuss root causes
understand your problem statement, root causes and learning questions
6
PM – Collaborative and Adaptive Leadership – ‘the how’ Collaborative leadership is the ability to work together across the nonprofit, private and public sectors to achieve a shared, long-term vision.
– Help teams understand and practice how to approach adaptive challenges (vs. routine); importance of not jumping to action/strategies; test assumptions you have about your challenge. – Teams will work independently on addressing: how to approach your local challenge through an adaptive lens; identify who may be missing from your table; and learn what evidence do you need to better understand your root causes and who’s impacted by your problem
7
8
9
10
thriving, and safe community;
collaboratively building community resources, removing barriers;
and respect in the community;
retention and shift hiring practices.
public, private, and nonprofit culture to be inclusive and responsive.
11
12
The Working Cities Result Framework: The ‘WHAT’ of Working Cities
Why this framework?
going, but also to reflect why and how a team will get there
change and drivers of change diagrams; using this will should enhance a team’s readiness for implementation This framework is NOT intended to be:
implementation, and rework as needed
should be woven into a team’s thinking about these questions How we’ll use the Framework today: focus on problem statement & root causes
13
A sharp problem statement will consider:
problem and its root causes?
are their others we should engage on the team?
tells us this, and how can we keep track of these conditions over time?
term shared result we will set out to achieve? (session #2)
14
and biases about the problem and its root causes
related to perceptions or attitudes, for example), so begin thinking about how you will collect data and other evidence to measure the baseline
need to determine which of the root causes you will prioritize in order to achieve it – won’t be able to take them all on!
15
16
17
What is the problem and why is it happening (identify each ‘why’ as a concern, influence or control) 40% of Whoville’s lower-income children enter kindergarten not ready to learn, limiting school success *What is the evidence of this condition on the ground?
18
19
20
May 3, 2013 Connecticut Design Session #1
21
22
23
24
Session 2: Wednesday, June 21, East Hartford Focus: Community engagement / racial equity
Results statement & on-the-ground conditions
Session 3: Monday, Sept 11, New Britain Focus:
System change Strategies/actions
Session 4: Thursday, Oct 12, Middletown Focus:
Learning orientation/data for learning Feedback loops/governance
25
Hartford Bridgeport Torrington Waterbury East Hartford Danbury New Haven Middletown New Britain Norwich