Personal tools

Overview and key findings: Schoolwide toolkit/parent connector network: Difference between revisions

From Oneville Wiki

Jump to: navigation, search
No edit summary
 
(379 intermediate revisions by 14 users not shown)
Line 1: Line 1:
==Summary==
''Written by Mica Pollock (2009-11 work), Jedd Cohen, Tona Delmonico, Gina d'Haiti, and Ana Maria Nieto for the Parent Connector project, with input from parents across the Healey School (particularly Consuelo Perez, Lupe Ojeda, Sofia Perez, Maria Carvalho, Ivanete Calmon, Veronaise Chaiki, Will Thalheimer, Tracy and Dave Sullivan, Adriana Guereque, Maria Oliveira, Manoj Archarya, Claudia Ramos, and Michele Arroyo-Staggs).


(Note to documenters: quickly tell the reader a, b, and c:
Click here for the '''[[Summary: Schoolwide toolkit/parent connector network|<font color=#0000FF>Summary</font>]] '''on this project; click here for the '''[[Expanded story: Schoolwide toolkit/parent connector network|<font color=#0000FF>Expanded story</font>]] '''on this project.


a. Communication we set forth to improve. (What aspect of communication did we set forth to improve, so that more people in Somerville could collaborate in young people's success?)
[[Image:Maria and Seth.jpg|thumb|Maria, Connector to Portuguese-speaking parents, and Seth, local technologist, working together on a hotline recording]]


b. Main communication improvement(s). (What is the main communication improvement we made? What new support for young people may have resulted?)
==Communication we hoped to improve==


c.  Main communication realization. (What's your main realization about needed improvements to the communication infrastructure of public education? Who needs to communicate what information to whom, through which media, in order to support youth in a diverse community? Which barriers are in the way of such communication, and how might these barriers be overcome?)
''What aspect of existing communication did we try to improve, so that more people in Somerville could collaborate in young people's success? How’d it go?
:''(Who was involved in the project and how was time together spent? What did the project accomplish?)


------------------
At Somerville’s Healey School (K-8), as in many U.S. schools, parents hail from across the globe and speak many languages. And as in many schools, language barriers often keep parents from being equally informed about school issues, events, and even educational opportunities. So do disparities in tech access, tech training, and time -- as well as gaps in personal relationship and connections. Lots of people at the Healey talked about needing better school-home and parent-parent communication, particularly to fully include immigrant families, families without computer access/knowledge, families with low literacy skills, and families who couldn’t or didn’t show up often in person at the school.


So, we operated from a central principle already core to the Healey School: a child can’t be educated as effectively if parents aren’t included as key partners in the project. So, schools should ensure access to school information and pull all parents into dialogue about improving their children’s school experience. Info out, input in.


This working group has evolved over the two years of OneVille's work. Over the course of two years, we found parents particularly committed to improving communication across their K-8 school. Throughout, we've been working together to help ensure that all parents in a multilingual and class-diverse school can access important information about and from their school, so that all can fully participate in the joint project of educating children.  
The Healey School enrolls a full U.S. range of families with different communication habits and needs. Some email the principal and Superintendent regularly. Some parents have no computers and no internet. A listserv has long enrolled only some. Robocalls home go in four languages; handouts home often don't. For many, parent teacher conferences require interpreters, and accessing those interpreters itself is a structural communication need, in part because some parents don't know how to access the service and in part because many of the parents who need interpretation are incredibly busy - sometimes working multiple jobs. One Portuguese-speaking dad worked such long hours he didn't even have time to come to school to post a sign saying he wanted to find and pay another parent to help him drive his daughter to school. In addition, parent and staff efforts to make an appointment to talk to one another with interpretation services can also get lost in the crush of meeting student needs: One Spanish-speaking parent told us she’d tried a number of times throughout the year, unsuccessfully, to meet with her child’s teacher in person.  


In the past year, we have particularly worked to include immigrant parents in the loop of school info and input. We particularly focused on creating a "Parent Connector Network," in which bilingual parents ("Connectors") use phones, Googleforms, and a hotline to help get information to more recently immigrated parents who speak their language.  
In contrast, some families, particularly English-speaking families, volunteer many hours in classrooms during the school day and so get regular access to their child’s teacher. Many such families also are on committees that meet after school and so, take the opportunity then to contribute ideas to the school. Over the years, we saw that families who saw each other regularly at face to face school events also made friends, joined listservs, signed up in directories, and showed up at next events.


We now are working with 3 Spanish-speaking, 3 Portuguese-speaking, and 2 Haitian Creole-speaking Connectors. Each Connector is calling approximately 10 other families once a month, to share key information from the principal and to ask questions about any issues parents are facing. The Connectors are also on call for questions from parents, at any time.  
As we describe below and in the '''[[Expanded story: Schoolwide toolkit/parent connector network|<font color=#0000FF>Expanded story</font>]] ''', when we began in 2009 we first worked on several strategies to support diverse parents to share ideas and information, and to build relationship (Reading Nights, Parent Issue Dialogues). Then, we focused on the challenge of multilingual communication, because language barriers particularly have excluded many Healey parents from full participation. The Multilingual Coffee Hour, begun in 2009, was our first explicitly multilingual effort. Then, in 2010-11 and 11-12, the Parent Connector Network has focused fully on parents reaching out to other parents who speak the district's three main languages other than English: Spanish, Portuguese, and Haitian Creole. We've also been working to build personal relationships between bilingual parents and recent immigrant parents, in order to bring more voices into school debates and more people into school events and leadership -- as well as help the school respond more quickly to parent needs.


The Connectors have also become key innovators of translation and interpretation infrastructure schoolwide. We spent late spring 2011 finishing a full list of [["infrastructure" for low-cost translation and interpretation in a school|components to such infrastructure!]]
Begun in Winter 2010, the Parent Connector Network now supports translation and parent-school relationships, by connecting bilingual parents (“Connectors”) to more recently immigrated parents face-to-face, and via a phone tree and multilingual hotline. The Parent Connector Network is now run largely by parents and community members, with coordination efforts by a OneVille community staff member handed to school staff; Connectors continue to innovate the Network model in partnership with school administrators and staff and with the blessing of District administration. Our hope is that new part-time Parent Liaisons being hired by the District for schools like the Healey will also help the volunteer Connectors coordinate their work.


We've had countless ahas about improving the communication infrastructure of public education, and particularly, about improving the infrastructure for interpretation and translation.
Beginning in spring 2012, Connectors started to use a multilingual call-in hotline (which our MIT friend Leo Burd made for us with open source VOIPDrupal software) to share out school information, to help ensure that information reaches English language-learning families and families with fewer tech and literacy skills. As Connector relationships and incoming parent requests and ideas grow in the future, Connectors may use Google forms to gather and prioritize school information. (Google forms are simple online forms that allow multiple people to input information that gets stored in a basic online database.) We tried that strategy briefly in 2010-11 but didn't yet need it: so far, Connectors have been able to handle individual parent needs by simply relaying requests and issues to appropriate staff.


Here's one main aha: improving translation and interpretation in a multilingual school and district in part requires getting more organized about effectively using a key local resource: bilingualism. At the same time, a key issue we’re trying to understand is where the line is between translation/interpretation that bilingual parents can/will do as volunteers to serve their community, and when the district has to pay professionals. Districts across the country say that they "can't" effectively communicate across language barriers, because it's too expensive. So how could districts efficiently fulfill parents' civil rights to needed interpretation and translation of important school information? It's a key issue for any multilingual community, and a host of parents and staff from the Healey School in Somerville set forth to work on it.
By spring 2012, we were working with 5 Spanish-speaking Connectors, and 1 Portuguese-speaking, 1 French-speaking (for Haitian Creole-speaking families), and 1 Hindi and Nepali-speaking Parent Connector. Each Connector is asked to call 3 - 5 other families once a month to share key information from the principal/school and to ask questions about any issues parents are facing. The Connectors are also on-call to parents during the school year to help them find answers to both general and specific questions or concerns they may have about their child’s school. (e.g., some Connectors have received calls about issues like summer school enrollment, or about how to reach the district’s Parent Information Center to enroll a new cousin in a school.)


==Communication we set forth to improve==
That spring, we also successfully tested a strategy of having volunteer Connectors wear "badges" as informal interpreters or contacts available to any school parent at the beginning of some school days, to enable more parent-parent connections and a clear route to get "on demand" interpretation for early morning conversations with staff.


What aspect of communication did we want to improve, so that more people in Somerville could collaborate in young people's success?
Connectors also are starting to act as volunteer “Translators of the Month” for each main language group, helping to translate a monthly set of school information for our Healey Hotline. This translated material can then be used for other school media (listserv, handouts, flyers, etc.). These Translators won't translate the official information the school or district is legally required to make accessible to all parents. (Civil rights law requires that all parents have an equal opportunity to access important school information; some such information involves specialized lingo and definitely requires formally trained professionals.) But so far, volunteers and, stipended Connectors ($15/hr) are willing to help produce an additional stream of translated material for the school. (As we describe below, we later found that in-person support to access interpretation helped ELL families to feel comfortable meeting with their teachers.)
------------------------
       
(COLORED TEXT BOX: We wanted to add infrastructure that could help equally include all parents in a multilingual, class-diverse school!)


At the Healey School in Somerville (K-8), as in many U.S. schools, parents hail from across the globe and speak many languages. In addition to barriers of language, disparities in tech access, tech training, and time -- and gaps in personal relationship and connections  -- keep parents from being equally informed about school issues, events, and even educational opportunities.  
In fall 2011, we also successfully argued for creating a part-time liaison role (five hours per week paid by the school) for staff already employed by the school to support the Connector Network. The liaison role provides a range of crucial supports for the network that a school employee is best positioned to do. For example, the liaison can help summarize school information for translation by the translators of the month, summarize parent needs for the administration, recruit new parents at in-school events, and respond appropriately to serious or ongoing parent needs -- beyond what a volunteer parent can or should do. The role requires not only a strong connection to local immigrant communities but skills in tracking and managing multiple relationships and projects simultaneously. Several staff members tried the role, and one particularly willing staff member volunteered her time.


In the Parent Connector Network, as in our broader [[schoolwide communication toolkit]], our goal was to figure out ways to better include all parents in a multilingual, class-diverse K-8 school.  
The role is currently distributed across the volunteer staff member, several parent leaders, and a OneVille community staff coordinator. Our final goal has been to transfer these responsibilities away from OneVille paid staff and fully onto staff and parent leadership, and we spent the spring 2012 semester building the staff skills to do this, supporting parent leadership, and piloting the full combination of multilingual hotline, connectors, and parent liaison work.


Because language barriers particularly exclude parents from full participation, the Parent Connector Network has focused on reaching out to parents who speak the district's 3 main languages other than English: Spanish, Portuguese, and Haitian Creole.


Begun in earnest in Winter 2011, the Parent Connector Network is a parent-led effort (in partnership with school administrators and staff) to support translation and parent-school relationships, by connecting bilingual parents (“Connectors”) to more recently immigrated parents via a phone tree. The Connectors have come to use phones, [[Google forms]], and a [[hotline]] to help ensure that information reaches immigrant and low-income families who share a school.
[[Image:(2)Slide1.jpg|Slide1.jpg]]
[[Image:(2)Slide2.jpg|Slide2.jpg]]
[[Image:(2)Slide3.jpg|Slide3.jpg]]


In the Parent Connector network, we operated from a central principle: schools should ensure equal access to school information and dialogue, in order to promote inclusive participation in school life. We've also been working to build personal relationships between bilingual parents and immigrant parents in order to bring more voices into school debates and more people into school events and leadership.
'''See the bottom of this Overview page for the final set of "components" we were implementing by spring 2012.'''


Because each innovation the Connectors started needed other components to work effectively, we have come to think in terms of an "infrastructure" for low-cost translation and interpretation in a school. Over the 2010-11 school year, we've been fleshing out a full list of such [["infrastructure" for low-cost translation and interpretation in a school.|systemic supports.]]  The Parent Connector Network is a key component, but it's not the only one!
==Our work, and our '''<font color=red>¡Ahas!</font color>==


==Process==
''What was the basic groundwork needed to support the current work? How did the project change and grow over time? At this point, what are our main <font color=red>¡Ahas!</font color> about improving communications in public education? What communication and implementation <font color=red>¡Ahas!</font color> and turning points did we have over time?
-------
Work informing the Parent Connector Network began in a 2009-10 series of Reading Nights and Parent Dialogues, and a Multilingual Coffee Hour that continued in 2010-11 as part of the Parent Connector Network infrastructure. We learned a huge amount in that work and we built relationships that enabled the development of the Parent Connector Network. '''Click [[Expanded story: Schoolwide toolkit/parent connector network|here]] for the full backstory!'''


How we realized and redirected things, over time.
As a multilingual group of parents and staff (a few of whom speak only English), it has taken us two years to fully understand:


===History===
1) The barriers in the way of adult English learners' participation in English-dominant schools;


The groundwork needed to support the current work. Offer a short description of key building blocks.
2) The sort of systemic communication "infrastructure" necessary to include more immigrant parents as partners in the project of supporting young people;


-----------------------
3) How to find and recruit people with the skills needed to implement the infrastructure, and how a volunteer-based project can delegate responsibility across available community members (and, stipend key people for leadership roles.)
Our design process has been fully collaborative. As a multilingual group of  parents (a few of whom speak only English), it has taken us two years to understand the detailed barriers in the way of English-learners' participation in English-dominant schools, and, the full communication "infrastructure" necessary to include more immigrant parents as full partners in the project of supporting young people.


Basically, as a rolling group of parents, we participated in both successful and unsuccessful communications in the school while trying to figure out how to improve schoolwide communication! Over time we came to focus on communicating with non-English speakers as one of the school's primary barriers.
Some main '''<font color=red>¡Ahas!</font color>''' over time have been these:


Before we started creating the Parent Connector Network in Winter 2011, we had worked with families and teachers in several other design efforts to improve connections between parents and school and parents-parents more broadly. Over time, we realized the particular need for improving the communication infrastructure for translation and interpretation. So, we want to describe some of the work that laid the groundwork for the Parent Connector Network.
'''<font color=red>¡Aha!</font color>  Overall, we’ve learned that committed and diverse parents can be expert innovators of communication infrastructure for including all parents because they have a full understanding of communication barriers.


====Starting in fall 2009, we tried several forms of face to face parent get-together, to connect parents across lines of language, income, and program.====
'''<font color=red>¡Aha!</font color>  In a multilingual school and district in particular, local bilingualism is a key resource for strengthening communications and relationships between families and educators.''' The key is tapping local bilingualism in strategic ways.


In fall 2009, we began building relationships among parents interested in schoolwide communication improvements. Mica and Consuelo, both parents at the Healey School, met at a coffee hour with the principal in fall 2009 and discovered a mutual interest in starting conversations across language and program. Mica invited Consuelo to help do parent outreach for the OneVille Project, and a design partnership at the Healey began!
'''<font color=red>¡Aha!</font color> To fully engage all parents in a multilingual and diverse school, each effort to engage parents requires multiple efforts to make communication fully inclusive. Barriers to full inclusion exist every step of the way. So, we have come to think in terms of creating a full "infrastructure" for schoolwide communication (and low-cost translation and interpretation in particular).''' For example, to reach parents across tech access barriers, a Reading Night linking three kindergarten classrooms and a Special Education classroom required advertising the event not only using the school's listserv, but also via paper handouts and displays on the kindergarten hallway's wall. Including all parents during the event also required actively tapping parents' own bilingualism, by engaging parents in translating conversation in multilingual groups. To get parents to a Multilingual Coffee Hour or PTA Night event, we needed to learn how to record multilingual invitation messages on the school's "robocall" system; then, we had to experiment with which recorded voices made the event seem most appealing to parents. We also experimented with recording targeted robocalls to one language group at a time, instead of recording all four at once. This was because on parents' home answering machines, robocalls often cut off after the first two languages  -- and because Portuguese and Haitian Creole translations were always last after English and Spanish, those languages often didn't get heard.


We say "across language and program" because in 2009 when we began our work, the K-8 Healey had 4 historically separated programs: a magnet K-6 program drawing disproportionately middle-class families from Somerville; a "Neighborhood" K-6 program disproportionately enrolling low income and immigrant families living around the school, including from the housing development a few steps away; a Special Education program, also disproportionately enrolling low income students of color and immigrants; and a middle school.
Before we started working on the Parent Connector Network in Winter 2011, we worked with families and teachers in other efforts to improve parent-school and parent-parent connections. Most of all, we had to build relationships across parents and staff who cared deeply about including everyone. These friends became key partners in innovation.  
 
With parents from across the first three programs in a Kindergarten hallway at the Healey, we began in fall 2009 creating [[Reading Nights]] to link parents in face to face efforts to share information on reading with young children.  Our events were social, and academic. Through early chance meetings in our hallway, we met Tracy and Dave, Maria, Michelle, Carrie, Jen, and many others -- (PHOTOS?). Several of these parents formed the early core of the parents who would continue to work on schoolwide communication for two straight years. We worked together on a multilingual coffee hour, some parent dialogues, and, finally, the Parent Connector Network.
 
From the beginning, the particular issue of connecting English-speaking parents and staff with speakers of other languages was on our minds, because so many immigrant parents in the hallway were possible attendees for Reading Night.
 
Consuelo and Mica focused additionally on another early effort: to supplement the typically English-dominated "coffee hours" with the principal. In partnership with the principal, we created a slot for a [[multilingual coffee hour]] model, a brainstorm of Consuelo (PHOTO), a parent partner particularly committed to finding creative ways of empowering immigrant parents. In the multilingual coffee hour, parents translated for other parents wanting to ask questions and hear information from the principal, quickly cluing us into a key local resource: parent bilingualism.
 
(COLORED TEXT BOX: MAJOR AHA! The massive local resource of parent bilingualism).
 
At several points over the two years to come, we considered melting the coffee hour back into the "regular" meeting with the principal (the Healey's next principal first leaned in this direction but then decided to keep a distinct "multilingual" coffee hour). But, since typical coffee hours are so obviously dominated by English-speaking parents, it still felt important to have a space focused actively on multilingual communication. The multilingual coffee hour with the principal is now an established place where people take extra time for translation and purposefully amplify languages other than English, by ensuring that speakers of other languages get priority in asking and answering questions.
 
(ADD MINI COMMENT BLURB OR INTERVIEW HERE WITH LUPE OR IRMA, ON WHAT IT HAS MEANT TO HAVE AN EXPLICITLY MULTILINGUAL COFFEE HR?)
 
New community developments at the Healey shaped the next building blocks of our work. Halfway into the 2009-10 school year, the school committee put on its agenda a key task: deciding whether to integrate the Healey's magnet and "Neighborhood" K-6 programs. In response, we used our coffee hour for a number of [[community dialogues]] to facilitate conversation about this choice, and, we held a [[large community dialogue]] on a Saturday (LINK TO SOME DOCUMENTATION FROM MAY 5 MEETING). In the end, the School Committee voted to "unify" the Healey's K-6 programs and hired a consultant to steer that process through the following school year.
 
By fall 2010, we were focused on the issue of fully including parents across barriers of language (and relatedly, disparities of tech access and training). Through the series of "ahas" described below, we came up with the Parent Connector Network concept and started to pitch it and brainstorm it with school council, principal and "unification" working groups. Starting in winter 2011, we recruited Connectors -- bilingual parents (and one young staff member) who had, over the prior year, shown particular interest in reaching out to immigrant parents or translating public information so others could access it.  As a team of parents, we met with the principal and started using our [[multilingual coffee hour|multilingual coffee hours]] to get ongoing advising from parents schoolwide. The Parent Connector concept was approved in the school's formal unification plan in xxx. But we still had to flesh it out by doing it!
 
Our goal became to "just start," so we could test ways parents could reach out to other parents. We needed also to figure out what info we would and would not translate for free, how many school-home communications were necessary a month, how to use existing school channels and create new simple tools for parent outreach, and more.
 
===Communication ahas, implementation ahas, and turning points!===
 
COMMUNICATION AHAS: In the process of doing the work, what did you learn about needed improvements to the communication infrastructure of public education? e.g.,
 
-Who needs to share which information with whom, via which media, to support a young person?
 
-What are the barriers to that communication, and how can those barriers be overcome?
 
IMPLEMENTATION AHAS: In the process of doing the work, what did you learn about implementing these innovations in education? Discuss stumbling blocks, solutions, and lessons learned!
 
TURNING POINTS: Describe moments when you redirected the project accordingly, after a communication aha or an implementation aha.
 
Please share examples of in-process products, with discussion!
 
------------------------------
 
Communication Ahas that helped us shape the Parent Connector Network actually began in Reading Night, our Parent Dialogues, and the Multilingual Coffee Hour. The first series of ahas led us to focus our work at the Healey on parent relationships and schoolwide communication infrastructure. Then, more ahas led to the intensive focus on translation and the Parent Connector Network.
   
   
====Learning to focus on parent relationships and schoolwide communication infrastructure: ahas from Reading Night, Parent Dialogues, and Coffee Hours====
===Communication and implementation <font color=red>¡Ahas!</font color>, and turning points!===


To get people to Reading Nights, we had to practice communicating between school and home, to advertise events in multiple languages. (LINK TO CONSUELO'S DOCUMENT HERE. . )
We had many ¡Ahas! in sequence on this project over two years. <font color=red>'''To read the full story of the efforts that gave us these ¡Ahas!, click [[Expanded story: Schoolwide toolkit/parent connector network|here!]]'''</font color>


(COLORED TEXT BOX: Communication aha: inviting parents to school events is hard and incredibly time-consuming if there isn't a great infrastructure for it.)
Additional <font color=red>¡Aha!s</font color> about schoolwide communication included the following.


Two classrooms of parents in the hallway were "allowed" to be on the magnet program's listserv, but the other two classes (Special Education and, the "Neighborhood" program) were not and many immigrant and lower-income parents in the magnet program weren't on the listserv anyway.
''READING NIGHT AHA:


We put up multilingual signs outside of the classroom door, where parents would see them, but, not all parents dropped off their kids at school themselves. Consuelo's giant pizza, up on the wall a few days before Reading Night, worked particularly well. So did advertising that we would actually serve pizza, when we did:
[[Image:Running up the Healey stairs to a Reading Night.jpg|thumb|Running up the Healey stairs to a Reading Night]]


PHOTO OF THE PIZZA HERE
[[Image:Consuelopizza.jpg|thumb|Consuelo, mastermind of the Multilingual Coffee Hour, and her OneVille pizza: our best Reading Night advertisement]]


Face to face invitations on the playground before school were often the thing that brought some people to Reading Night, because people felt they were coming to meet other friends. Those were particularly time-consuming, and our energy for standing outside to invite parents personally to events waned over the year. Teachers urged us to announce Reading Nights to kids who would then invite their parents; we did that too.
'''Reading Night was about building initial relationships and friendships between parents as much as it was about sharing reading tips.''' These relationships became crucial to all of the work we all did together at the Healey over the next three years.


Had we known that the school's "robocall" system could call a targeted subset of parents in their language, perhaps we could have used that to invite more people! Notably, nobody ever told us that the principal could use the system for whatever he wanted; it wasn't until the following year, with a new principal, that we realized we could help shape the content of robocalls. (But this most obvious channel-home is often used only for the "most important" of communications, so we may not have been allowed to use it.)
''MULTILINGUAL COFFEE HOUR AHAS:


MORE ON READING NIGHT HERE! (***TBD: HAVE A SEPARATE PAGE ON READING NIGHT OR NOT?)
The Multilingual Coffee Hour started in 2010-11 and then became a key piece of the Parent Connector Network infrastructure the following year. We realized:


Reading Nights were often about drawing together the families who came (parents told us their children left talking all night about reading, and, we as parents certainly came to be friends). But we also left with a lot of reading tips.  
'''<font color=red>¡Aha!</font color>  Making parent gatherings explicitly multilingual encourages speakers of languages other than English to ask questions and offer opinions. In addition, multilingual events -- events where people take the time to translate for one another and, encourage others to speak in their own language -- also help parents and staff appreciate their peers' language talents.


(COLORED TEXT BOX: COMMUNICATION AHA: We then realized that because of a lack of communication infrastructure among parents, we could not effectively share out the literacy tips we got at the Reading Nights!)
[[Image:Dave.jpg|thumb|Dave, multilingual coffee hour enthusiast and 2011 PTA president]]


We tried to post these tips as paper sheets on a hallway bulletin board, but somehow our use of the medium didn't excite viewing.
''PARENT-PARENT ISSUE DIALOGUE AHAS:


COMMUNICATION AHA: We also realized in doing Reading Night that what parents ourselves needed most of all was a chance to *talk to other parents* -- in this case, about our experiences trying to help our children read.
In 2010-11, several Parent-Parent Issue Dialogues helped a number of Healey parents debate a fundamental and controversial issue about their school's future: integrating several historically separate student programs. We realized the following in these efforts:


COMMUNICATION AHA: Perhaps most of all over the 2009-10 school year, we also realized that we were perhaps expecting too many face to face social events at the school, for parents exhausted by a glut of events. Our first Reading Night was very well attended, but attendance at the monthly events went down slowly as everyone became very tired. In particular, the organizers, who slowly got tired of the face to face time and effort it took to create and then debrief Reading Night, stopped advertising the event actively, which in turn cut down on attendance.
'''<font color=red>¡Aha!</font color>  Many parents have few or no opportunities to talk to each other or to decisionmakers in organized settings, about major issues in their school. This means that their ideas and energy for improvement go untapped. Parents with tech access and knowledge (e.g., parents on a school listserv), and English speakers, are often far better informed and included in such debates.


COMMUNICATION AHA: Children doing things worth watching, are themselves the best advertisement for parents! Our most effective Reading Night after the first night was the night when an entire class of children did a play; all of their parents came.  
:'''*TURNING POINT:''' With the Healey in the midst of integrating several historically separated programs, parents focused for 2010-11 and then 11-12 on improving infrastructure for schoolwide communication -- and particularly, on including immigrant parents in the loop of school information and input. We designed the Parent Connector Network.


COMMUNICATION AHA: requiring too much face to face organization may leave organization too reliant on parents who were not working.  
:'''*<font color=red>¡Aha!</font color>/TURNING POINT: Try focusing on the most-blocked communication first.''' In this case, after trying a number of efforts to link parents at the school in dialogue (another important barrier at the Healey was the need to build relationship between newer, higher-income English-speaking Somerville residents and older, lower-income English-speaking Somerville residents), we focused on addressing the language barriers making communication particularly difficult.


COMMUNICATION AHA: we realized that building friendships between parents was key to getting parents to participate further! The core organizers were willing to do lots of work together because, basically, we liked each other.
''PARENT CONNECTOR NETWORK AHAS:


TURNING POINT: so, we began to focus on two directions: improving "outreach" infrastructure inviting parents to school events, and parent dialogue more generally at the school. We held parent dialogues to discuss the unification process.
In addition to the main '''<font color=red>¡Ahas!</font color>'''above, we realized the following:


COMMUNICATION AHA: In our work to support parent dialogues, we had another communication aha: we realized just how irregular it was for parents to speak to each other across "groups," about fundamental desires for their children's education! It became important later in the Healey's work to be able to report, for e.g. to school council members, that everyone we talked to, across lines of class, race/ethnicity, and language, wanted a more rigorous learning experience for their children.
'''<font color=red>¡Aha!</font color> Innovation requires experimenting with communication solutions, even if strategies aren't guaranteed to work.''' In our case, we tested a number of solutions for getting school info “out” and parent input “in” across boundaries of language, and building relationships across those boundaries.


In the parent dialogue work, we had another fundamental COMMUNICATION AHA: We realized just how central problems of communication were to parents being fully included in the school. In the Unification debate, (xxx ADD MORE DETAIL ON THAT NARRATIVE HERE, school committee members used the magnet program's listserv to advertise the school committee meetings and more; those on the magnet program's listserv emailed the superintendent or principal regularly with their opinions about whether the programs should integrate. Three months later when we walked around the Mystic Development to invite parents to a school committee meeting, we realized that many  -- those not on the listserv! -- were unaware that the issue of integration was even up for debate at the school at all. And this, in a housing project literally down a flight of stairs from the school!
'''<font color=red>¡Aha!</font color> While asking how schools get info out, we also have to ask how they get input in. How do schools hear about and then respond to parents’ ongoing problems and concerns?


TURNING POINT: supporting communication of important school information, across lines of language and also tech access/training/use (a proxy for class, in many ways), became our key focus at the school. While we continued work on a [[schoolwide communication toolkit]], we focused first on questions of language barriers, and focused full force on the Parent Connector Network.
'''<font color=red>¡Aha!</font color> School-home communication relies in part on parents building relationships and connections with other parents.''' Parents said they came to PTA night or other such school events because someone they knew invited them -- that a friendly face would be waiting at the event ("Come to this event, and I'll be there to support you"). Tech tools like phones, hotlines, or listservs can amplify and extend that ultimate resource for parent-parent connection: relationship-building. One of our Connectors had an ¡Aha! that others echoed across the OneVille Project: “My main conclusion is that relationships matter and they are what makes everything work.”


====Learning to focus on translation and interpretation infrastructure: the ahas of creating the Parent Connector Network!====
'''<font color=red>¡Aha!</font color> Creating “infrastructure” that makes interpretation and translation more efficient requires figuring out who to pay for what.''' The people who share a school can, will, and should volunteer their time to help the school and other families communicate. But only up to a certain point. When workload is too heavy or when professional skills are necessary -- and, to embed the project into the core work of the school -- projects need to pay staff whose job it is to help include all parents. For example, communication on individual parents’ serious personal needs will have to be covered by paid staff, freeing volunteers to be friends, info-sharers and links TO paid staff. But making translation mechanisms more efficient (e.g., trying a hotline to get info to many parents at once; triaging info to be translated by volunteers or stipended parents on the hotline) can save staff time that otherwise is spent explaining things repeatedly.


GO BACK TO NOTES AND OTHER WIKI TO GET THIS SEQUENCE.
'''Some key turning points in developing the Connector role:'''


In the cafeteria one morning in xxxx, Consuelo and Mica were sitting with several parents from the PTA, talking about how to improve schoolwide communication. Consuelo took out a piece of paper and started to draw: triangles, linked to other triangles in a pyramid structure. Parents linking to other parents, she said. In the car going home, Mica named the parents: "Connectors."
By late January, 2012, we began to feel that phone calls pairing Connectors to a subset of families weren't enough. The Connector Network had grown to a total of nine bilingual Connectors paired with dozens of families for phone calls "out," but parents weren't asking much of their Connectors, and putting effort into getting parents to school-based events started to seem less profitable than perhaps scheduling events where parents themselves already were. Parent Connectors met together to brainstorm next steps on information-sharing and relationship-building:


We began to share out the basic idea with the school council, and other school leaders, to see what people thought of it. People said there were already "room parents" in the magnet program but that these parents primarily had signed on just to tell people once in a while about things like parent breakfasts or school supply needs -- not about the more important issues going on at the school.
'''TURNING POINT: In spring 2012, we pursued a deepened focus on face-to-face, rather than phone-to-phone connection. '''The Connectors brainstormed several sites of rich communication in daily school life to build on next:


TURNING POINT: Consuelo's experience -- drops out -- need for pinpointing "loops" of response to parent needs.
:*Often, we saw ELL (English language learning) parents waiting before and after school to ask questions of a single bilingual staff member. To support these face-to-face connections, we found it useful to stipend three connectors to spend additional hours before and after school, to help connect parents directly to the staff member they wanted to talk with.
 
TURNING POINT: Communication confusion: which parents should each Connector link to, and how? Mica brainstorms the idea of linking each Connector to 10 parents and focuses the Connectors first on bilingual communication
:*Parents also find that communication about their child’s classroom, rather than about the whole school, is much more engaging and rewarding. So next year, Connectors will begin to pair up with grade level teams or even with particular "classroom parents" to share classroom-level information with families in their child's class or grade.
 
We started brainstorming the components of the Connector project with the principal, and also at meetings with other Working Groups at the Healey School (e.g., a "Parent, Student, and Teacher Partnership" working group and a School Climate working group that formed in 2010-11) and with those parents who came to our Multilingual Coffee Hours. Parents from our first Reading Nights also remained key brainstorming partners.
 
Starting in January xx, we met as a force of Connectors and decided xxxx
 
Then, we emailed each other multiple times weekly.  xxxxx
 
AHA: our experiment in personal calls. the robocalls. xxxxx
 
 
Our core concern was how to avoid a situation where parents mentioned needs to Connectors that never received a response (a classic situation in many schools!). In xxx (date), we created this [[Googleform]] for keeping tabs on parent calls.  We edited it together, for example, adding information on how to tell parents to request translators. Tona reworked it so it wasn’t set up as if there was a serious issue each time, but is more of a general recording space.
 
Meeting face to face with the Principal has always been a key infrastructural piece of the Connector model. Many Connectors began hearing stories from parents who lack interpretation and translation when they need it. So, our next goal became to meet w/ the principal and Welcome Project to share these stories and, rather than just critique, brainstorm the full "system" of infrastructure components needed to get interpreters in the right place when they are needed! A key aha has been that a) schools need more help to be nimble in setting up face to face meetings with translators. Many times, translators were requested but not actually present in the final meeting!
 
COMMUNICATION AHA: if parents need help with setting up translators or getting into afterschool programs, etc., it's not enough to just find the right "contact person" to send immigrant parents to. The problem is that parents have trouble approaching that contact person, in their language!


COMMUNICATION AHA: in order to get resources for their children, parents need resource questions answered as they come up.  
:*Next year, Connectors plan to hold monthly multilingual coffee hours outside of the school, at places where parents already gather -- e.g., at the Portuguese Club, the Haitian Coalition, or the Mystic Housing Project.


We've also realized that Connectors get asked key resource questions that are time-sensitive (e.g.: can I enroll my child in summer school voluntarily or, does she have to be referred?). Connectors don't have time to call all parents to share these FAQ answers, so, a key "information loop" is to get such FAQs answered regularly on public channels. We've chosen for now to answer them on our hotline and in the most common existing channel for school-home communication, the "purple calendar." They have to be translated in order to be useful to parents, and so, we may tap "Translators of the Month" for this!
'''Some key turning points in developing the Connector Network's technological infrastructure:'''


A standing info page for Connectors is also necessary, so that Connectors themselves know what to tell parents looking for legal or family services.
:*Leo Burd, a new friend from MIT's Center for Civic Media, finished an improved version of our '''hotline''' in spring 2012. We stipended three Connectors each month to translate the info update into three languages and record it on the hotline. The Connectors began to call families simply to let them know the hotline was a resource, and Connectors sent out a robocall in the school's main languages to announce the hotline via the school’s automatic messaging system. We think the hotline may relieve the Connectors of having to share schoolwide information with families. This, in turn, would allow Connectors to focus all their energy on more personalized outreach.


Lead Connector and Information Coordinator are planning to organize a summer training for Connectors, by principal, on how the school functions.
:*During the 2011-12 schoolyear, we also created a '''Googledoc''' of basic contact info/citywide parent services info all Connectors need to know: https://docs.google.com/document/d/15eF7hZP5DUCwl92WTYcOrElUWDICTdx69WjDgs8UfOI/edit


IMPLEMENTATION STUMBLING BLOCK: GETTING PARENTS' PERMISSION TO RELEASE THEIR NUMBERS TO OTHER PARENTS! Because our Connector project started mid-year, we had no beginning of the year form for all parents, saying “do you want a Connector? Check here to release your number to them!” So, it took us weeks to work through the Parent Information Center (PIC) to get parents to release their numbers to other parents! (School staff had to figure out how to download a spreadsheet of language-specific numbers for PIC staff from X2, the district’s “student information system”; then the PIC staff had to make the calls home to get parents’ permission to release numbers to the Connectors; then, finally, Connectors got lists and could start calling. This was an important example of the need for infrastructure: a form enabling parents to easily offer permission to have a Connector, as they signed off on other school needs.  
:*We helped Purnima Vadhera, the 2011-12 principal, make a '''fall parent communication form''' (see [[File: Healey School Communications Sign-Up Form 2011.pdf|Healey School Communications Sign-Up Form 2011.pdf]]) that will help parents sign up to get a Connector, make it easier to get parents’ phone numbers, and allow parents to record their preferences for contact (texting? listserv? classroom listserv?) and indicate whether they need email training.


IMPLEMENTATION STUMBLING BLOCK: USING TECHNOLOGY AMONG THE CONNECTORS THEMSELVES.  One implementation issue to consider was whether we turned off a few Connectors by immediately using technology we knew would help. For example, some Connectors took immediately to using a [[Google spreadsheet]] to choose "their" parents and get their numbers, and a [[Googleform]] to keep records on parents' needs. Other Connectors needed multiple calls to get them to come to training sessions on the Google spreadsheets, and some may have turned off to the project thinking that tech savviness was a barrier to it (one Connector has her daughter help her get her email; another uses her husband's computer to check hers. Another uses email regularly but doesn't write back via it!). One tried the forms and in the end, wanted to use paper and asked the Information Coordinator to retype her notes.  
:*Finally, we began teaming up with parent leaders and local community organizations to explore offering '''computer, internet, and email listserv training''' to parents. In a multilingual community where not everyone uses computers, some lack access to information because of translation gaps and some because of a gap in basic tech knowledge. We learned early on in our work in Somerville that the problem for parents was often not necessarily one of computer access (the nearby housing project has many computers) as much as one of training. Even English-speaking parents in the school’s magnet program didn't know how to get on its listserv; many parents didn't know how to use a computer's basic functions. Now that the school’s programs have merged and the Healey school is creating a schoolwide listerv, these issues will rise to the fore. And having parents develop and participate in a multilingual school listserv could be a powerful new frontier for parent inclusion.


Other glitches got in the way, but some Connectors figured them out: Connectors who had Yahoo accounts rather than gmail accounts couldn't open the Google spreadsheets and for a couple of weeks, didn't know why or ask! But over time, we've realized what training is needed (how to use a Googleform!), and, which tech uses aren't really that necessary (possibly, paper notes, quick emails to the Lead Connector/Information Coordinator/principal, or a monthly meeting for reporting parent needs could work as well as the Googleform, but not if the volume of parent needs increases). We'll see over time whether the Google form for recording parent needs is useful, or not.
In our 2011-12 work, we've also gleaned some very practical lessons about '''how to implement the Parent Connector infrastructure:


We Connectors need to communicate regularly with each other as well (to determine monthly scripts for calls, for example), and we've also found that unsurprisingly, email links email-obsessed Connectors far more successfully than those who don't like to access it routinely (this breaks down along class lines, as well). Some Connectors themselves require regular phone calls to stay glued to the project. Our youngest partner and some of us prefer texts, as well. And, we all needed occasional face to face meetings to brainstorm ideas more effectively and to stay interested in the project! In one face to face meeting, for example, a discussion of several "lack of interpreter" stories that Connectors had heard from parents led us to agree that we should put those stories at the top of our agenda in a meeting with the principal focused on our translation and interpretation infrastructure ideas.
*'''<font color=red>¡Aha!</font color> Bilingual volunteers may engage parents more effectively in school activities if they reach out to parents with a specific offer or request rather than a generic offer that requires parents to actively seek their help.''' For e.g., the generic offer "to provide school information and help answer your questions whenever you need it" may be less effective than “I’ll come with you to parent-teacher conferences next week,” or “Come to a Brazilian dance performance at the school on Friday."
*'''<font color=red>¡Aha!</font color> In order to engage ELL families with the most excitement in schools, a focus on traditional school activities that simply include parents in “business as usual” (i.e., Parent-Teacher conferences) can be complemented by the creation of school activities that actively honor these families’ languages and lives,''' e.g., a monthly Multilingual Coffee Hour that actively invites multilingualism, or an International Week that actively incorporates heritage activities in the classroom and after school.
*'''<font color=red>¡Aha!</font color> Parent availability changes, so it's important to develop a strategy for recruiting new parents to school efforts early and often.''' In addition to doing outreach and holding multicultural events at the beginning of the school year, when parents' hopes and energy are high, recruitment can also target parents whose children are in kindergarten, help the families become acclimated, and eventually tap them as leaders and mentors to next parents.


COMMUNICATION AHA: by xxxx, we were seeking a method for getting information out to a lot of parents at once, so that Connectors didn't become inundated with work. Michael Quan (PHOTO) suggested a [[hotline]] as a solution at one [[multilingual coffee hour]].
===Our products: Concrete communication improvements and next steps===


TURNING POINT: Seth (PHOTO) then prototyped a hotline (using open source software and the Twilio API), even as he smiled that it was a low-tech solution he wouldn't have thought of himself.
We are proud to say that the Parent Connector vision and project is now part of the Healey School's school site plan. We have a core of volunteer Connectors reaching parents in-person and via phone, and lead Connectors in Spanish and Portuguese. Two current/former Harvard graduate students, Jedd Cohen and Ana Nieto, worked as support coordinators in 2011-12 to support the effort while it solidified. The 2011-12 principal, Purnima Vadhera, worked with us to submit a contract to Human Resources for the five hrs/week liaison position to handle parent needs forwarded by the Connectors -- and to oversee the multilingual communication process we’ve come up with. While we waited for the liaison position to be approved, we filled in the gap by combining Jedd and Ana's efforts with that of a bilingual staff member, Adriana Guereque, who volunteered her time to follow up on individual family needs, and a very engaged Healey parent, Laura Pitone, who triaged monthly information and ensured that the district translated it.


Then, we started recording updates from the principal and answers to parents' Frequently Asked questions, with Tona, Maria, and Gina (PHOTO OF MARIA AND LINK TO THE FIRST SET OF FAQS?)  
Together, the Connectors (with advice from many other parents and staff consulted over the two years) fleshed out a list of components of the necessary “infrastructure” for multilingual communication. The Connectors themselves have become seen as a key local resource, as people willing to be on call to answer other parents' questions in their language and to (monthly) share information that requires more explanation:


After Seth prototyped the hotline, the question became how to regularly get translated information, on to it!
[[Image:Revisedinfrastructure.jpg|Revisedinfrastructure.jpg]]


COMMUNICATION AHA: We came up with the idea of asking volunteer Translators of the Month (also bilingual parents, and maybe, students) to verbally translate information all parents need to know (in Haitian Creole, Portuguese, and Spanish). Bilingual parents and staff noted at our coffee hour that translating material into their languages verbally – so, speaking it on to a hotline -- is easier than doing it word for word from paper to paper. So far, we have parents coming to speak into a computer (see photo!). We hope to hone the hotline so that translators can record to it from home.
In sum, this year we piloted the full infrastructure we developed for multilingual communication. We:


:a) piloted our Parent Connector Network, in which bilingual parents make monthly contact with immigrant and low-income families to get information to and input from them; Connectors also invite parents to our Multilingual Coffee hours and to the hotline.
:b) tested a model where a Parent Liaison and Lead Parent Connectors develop and implement the details of face-to-face and phone-based outreach, follow up on specific parent needs, and help parents access interpretation;
:c) piloted initial use of our open source hotline, on which parent “Translators of the Month” translate and record information about events, issues, and opportunities.


IMPLEMENTATION AHA: committed and diverse parents can be expert brainstormers in school infrastructure because they care about a full range of supports and have a full range of experiences from which to brainstorm those supports.
We're pleased to announce that next year the Healey School will have a district-funded, part-time parent liaison to manage volunteers, reach out to ELL families, and oversee a new Welcome Center, designed to provide a welcoming space at the Healey to all families. We're working with the incoming Principal, Jill Geiser, to  build on our insights from the Connector Network as she designs the responsibilities of this new position.


IMPLEMENTATION AHA: join with still other people who share the same focus/commitment and have knowledge for brainstorming that you might not have.
'''Final thoughts'''


In late spring, we joined brainstorming forces with parents from Somerville's Welcome Project (a nonprofit focused on empowering immigrants in Somerville, housed in the Mystic Housing Development down the hill from the Healey school). A parent group had formed there that also wanted to focus on translation and interpretation in Somerville, so we joined our conversations and kept fleshing out the [["infrastructure" for low-cost translation and interpretation in a school|full set of components of schoolwide translation and interpretation infrastructure]].
Overall, we’ve been exploring a cost-effective hybrid of volunteer efforts to connect parents to other parents and “infrastructure” that includes paid school staff. As mentioned above, a key issue we addressed in the Parent Connector Project was the line between translation/interpretation that bilingual parents can and will do as volunteers to serve their community, and when the district has to pay professionals. A parent in a federally funded district has a civil right to translation and interpretation if she needs it to access important parent information (including at parent-teacher conferences). But all districts are strapped for money and bilingual skills are true community resources. How to tap those resources without overtaxing volunteers, and without asking volunteers to do the sort of work that really should be done by paid professionals?


In June 2011, in a retreat with principal, Connectors, we finished this [[full list of components of the "infrastructure" for low-cost translation and interpretation in a school.]] The Parent Connector Network is one of the key "components" -- it's connection, human-style!
In our case, we isolated an aspect of the infrastructure that volunteers couldn’t cover and argued that a bilingual staff member be employed part-time to cover it. We reasoned that volunteers shouldn't be asked to ensure that parents get Special Education services for their children or be responsible for requesting paid interpreters from the district. Paid staff in any district should be on top of such “case management.” But volunteers may be able to do something no staff member can do so easily: build friendships that glue parents in as partners in student success.


Hear some words here from our Lead Connector and our Information Coordinator: (VIDEO INTERVIEW WITH TONA OR GINA?)
===Questions to Ask Yourself if You’re Tackling Similar Things Where You Live===
'''What big issues would we recommend others think about in their own attempts to improve communications in public schools? Contact us to talk more!
-------


Hear some words here from some of our Connectors (EVERYBODY ELSE? VIDEOTAPE AT THE NEXT CONNECTOR MEETING?)
Consider the current and needed schoolwide communication infrastructure at your school:
 
==Findings/Endpoints==
 
Please describe final outcomes and share examples of final products, with discussion!
 
===Concrete communication improvements===
 
What is the main communication improvement we made? What new support for young people may have resulted?
 
----------------------
 
We are proud to say that the Parent Connector vision and project is now part of the Healey School's school site plan. We have a core of Connectors ready for fall and two great leaders. We also have a meeting scheduled for the summer, to brainstorm the full set of translation/interpretation infrastructure components we think are needed for a multilingual school. We're way beyond the typical response, "we don't have the resources!"
 
===Main communication realizations and implementation realizations===
 
What's your main realization about needed improvements to the communication infrastructure of public education? (Who needs to communicate what information to whom, through which media, in order to support youth in a diverse community? Which barriers are in the way of such communication, and how might these barriers be overcome?)
 
What's your main realization about implementing these innovations in education?
 
-----------------------------
 
MAIN COMMUNICATION AHA: Improving translation and interpretation requires getting more organized about effectively using a key local resource: bilingualism! In a multilingual district, this resource will always exist.
 
The Healey School really does enroll a full U.S. range of families. Some are deeply empowered in their home-school communications (e.g., middle-class parents who emailed the principal and Superintendent constantly to get their attention throughout the Unification debate), and some are left out of the most basic communications of schooling (some have no computers and no internet.) A listserv has long enrolled only some. Sporadic robocalls home go in four languages; handouts home often don't. For many, parent teacher conferences require interpreters, and scheduling those interpreters itself is a structural communication problem.
 
Time is also of the essence: some families have time/resource to volunteer countless hours during the school day. In contrast, one Portuguese-speaking dad we knew of worked such long hours he didn't even have time to come to school to post a paper sign saying he wanted to pay someone to help him drive his daughter to school after he left for work. His "Connector" made the sign for him. (INTERVIEW WITH MARIA ON THIS?)
 
Communication from school to home is a huge issue in any diverse school, particularly across boundaries of language and tech access/training. In an era when most people work too much to talk face to face very often, getting information to all families and get input from all families requires a thoughtful infrastructure tapping (and in some cases, paying for) a key local resource: bilingualism.
 
The Connectors themselves are a key local resource, as people willing to be on call to answer other parents' questions in their language and to monthly, share information that requires additional explanation. We fleshed out other components of the necessary “infrastructure” to make schoolwide translation efficient, and to make the Connectors' volunteer role not overly time-consuming: a [[Googledoc]] as one organized place where principal, school leaders, put info that most needs dissemination/translation each month, by Translators of the Month and Connectors; [[Google forms]] for Connectors to record parents’ needs; [[Google spreadsheets]] for lists of approved parent numbers. [[Robocalls]] (ADD SCREEN SHOT?) home, using the district’s existing system for school-home calls, but targeting the calls to be specific to language groups and at times, recorded by friendly parent voices.
Small infrastructural “moves” can help: one parent noted that at another school, they put information at the top of every handout indicating where you can go to get a translation (over time, our Hotline).
   
   
COMMUNICATION AHA: A key issue we’re trying to understand is where the line is between translation/interpretation that bilingual parents can/will do as volunteers to serve their community, and when the district has to pay professionals.
:➢ Can everyone who needs to get and share important school information, get and share it? Do parents know who to talk to when they need information?
 
:➢ Where do you put school information so that everyone in the school can see it?
A parent in a federally funded district has a civil right to translation and interpretation if she needs it to access important parent information (including at parent-teacher conferences). But all districts are strapped for money and bilingual skills are true community resources. Some of this may be simply about organizing resources most effectively. Turlock Unified School District in California has a model where parents are trained and paid as professional interpreters and translators. Somerville’s Welcome Project already trains young people this way in their LIPS program, to translate at public events (http://www.welcomeproject.org/content/liaison-interpreters-program-somerville-lips). Which communications could trained adults handle particularly effectively, and at a lower cost than sending everything to the PIC?
:➢ How do you share parent ideas around the school?
 
:➢ What system do you have for translation and interpretation, in particular?
 
:➢ How can you tap local bilingualism, either paying people to translate material or organizing bilingual volunteers to pitch in on translation and interpretation in a way that doesn't take too much of their time?
MAIN COMMUNICATION AHA: The principal made clear that he needs to think in terms of “systems” for translation. Otherwise, disorganization means that things don’t get translated! Commitment to fully including all parents is key, but structural glitches certainly can block communication too.
:➢ How can you build on parent-parent relationships to pull all parents into school events and conversation?  
 
:➢ What tech training do parents need in order to get information? How could you help all parents get this training?
P.S.: In a multilingual community where not everyone uses computers, some lack access to information because of translation gaps and some because of a gap in basic tech knowledge. A listserv at the Healey had long enrolled only those in the magnet program, but even parents in that program didn't know how to get on it. In Winter 2011, we attempted to hold a [["get an Email" night]] at the Healey, but it wasn't well attended; this crucial puzzle piece needs further development. We learned early on in our work in Somerville that the problem is not necessarily one of computer access (the nearby housing project has many computers) as much as one of training. Especially in a community where there are many community-oriented technologists (LINK TO THEIR ORGS OR NOT?!), there's really no reason why everyone eventually shouldn't have basic tech skills. See [[Computer Infrastructure]]. But ironically, in a community where there isn't a good multilingual communication infrastructure, it's hard to get people out for any face to face training event! Combining the Connector network with email training may be a good solution, especially as the school goes from having a listserv only for the magnet program to a listserv for all. Currently, many of the people not on the school's listserv are still those who are low income or, speakers of languages other than English. And, having people speak up on the common listserv, in whatever language, will be the next frontier!
:➢ Which efforts at parent information should be a task for school staff rather than volunteers?
 
MAIN IMPLEMENTATION AHA: Nothing can stop a creative group of committed parents.


===Technological how-tos===
===Technological how-tos===
''Here's where we describe "how to" use every tool we used, so that others could do the same. We also describe "how to" make every tool we made!
-------


Describe "how to" use every tool you used, so that others could do the same. Describe "how to" make every tool you made!
We’re using a '''Googledoc''' as one organized place for a Connector list of resources relevant to Somerville's immigrant families:
https://docs.google.com/document/d/15eF7hZP5DUCwl92WTYcOrElUWDICTdx69WjDgs8UfOI/edit


------------------
See http://www.google.com/google-d-s/tour1.html for instructions on starting a Googledoc. (Note: to use googledocs, users need gmail accounts to view any googledocs that are set as "private.")
As a group of non-technologists, Googleform and Googlespreadsheet setup took us a bit of learning!
While some school systems get parents' permission en masse to release their information to other parents in a School Directory, administrators asked us to take care to ask each parent's permission for releasing information to their Connector (see '''[[Expanded story: Schoolwide toolkit/parent connector network|<font color=#0000FF>Expanded story</font>]] '''on this aspect of the project). We use '''Editgrid for secure lists of approved parent contact info''' for Connector use. See editgrid.com for instructions on starting and using Editgrid's spreadsheets. (At this time of this writing, Google spreadsheets don't allow sorting by any column, whereas Editgrid spreadsheets do.)


[[Hotline]] setup was a task for Seth. Learning how to record on it: In April, we were still sitting at the computer talking into it, or, those of us with Audacity on our computers could record from home and send Seth the files. Over the summer, we xxxxx.
We used '''Google Translate''' for some first-pass translations of material for the hotline or other school channels, but bilingual parents still had to correct the translations. See http://translate.google.com/support/ for tips on using Google Translate.


===Things we’d expand/do differently===
With the Healey's principals, Connectors have experimented with recording translated robocalls home, using '''Connect-Ed,''' the district’s existing system for sending calls to many families at once.  As described in the '''[[Expanded story: Schoolwide toolkit/parent connector network|<font color=#0000FF>Expanded story</font>]],''' in our case, we learned to target robocalls to one language group at a time instead of recording all four at once, because robocalls often cut off after the first two languages (and because Portuguese and Haitian Creole were always last). We also asked Connectors to record some robocalls in their friendly parent voices, which drew some parents to PTA night!


If you wanted to replicate any of this, what would you need to think about? Contact us to learn more!
On the '''hotline''': Local technologist Seth prototyped our first hotline, and in spring 2011, we were still recording voices or saving audio files onto Seth's computer -- see photo of Maria and Seth above. At that point, Leo Burd from the Center for Civic Media then made the professional version that we began piloting in 2011-12. (Here's Leo talking about his VOIPDrupal software: http://www.youtube.com/watch?v=C8NCRLCdPno&noredirect=1). See [[here]] for Leo's explanations of the programming. Leo's goal is for the software to be developed quickly by any community that wants to use it.


----------------------------
Click here for the '''[[Summary: Schoolwide toolkit/parent connector network|<font color=#0000FF>Summary</font>]] '''on this project; click here for the '''[[Expanded story: Schoolwide toolkit/parent connector network|<font color=#0000FF>Expanded story</font>]] '''on this project.
Tech training for the Connectors. Early forms for parents, to say "I want one!" to avoid the PIC month. Infrastructure is needed so that volunteers aren't over-taxed!

Latest revision as of 12:33, 22 July 2012

Written by Mica Pollock (2009-11 work), Jedd Cohen, Tona Delmonico, Gina d'Haiti, and Ana Maria Nieto for the Parent Connector project, with input from parents across the Healey School (particularly Consuelo Perez, Lupe Ojeda, Sofia Perez, Maria Carvalho, Ivanete Calmon, Veronaise Chaiki, Will Thalheimer, Tracy and Dave Sullivan, Adriana Guereque, Maria Oliveira, Manoj Archarya, Claudia Ramos, and Michele Arroyo-Staggs).

Click here for the Summary on this project; click here for the Expanded story on this project.

Maria, Connector to Portuguese-speaking parents, and Seth, local technologist, working together on a hotline recording

Communication we hoped to improve

What aspect of existing communication did we try to improve, so that more people in Somerville could collaborate in young people's success? How’d it go?

(Who was involved in the project and how was time together spent? What did the project accomplish?)

At Somerville’s Healey School (K-8), as in many U.S. schools, parents hail from across the globe and speak many languages. And as in many schools, language barriers often keep parents from being equally informed about school issues, events, and even educational opportunities. So do disparities in tech access, tech training, and time -- as well as gaps in personal relationship and connections. Lots of people at the Healey talked about needing better school-home and parent-parent communication, particularly to fully include immigrant families, families without computer access/knowledge, families with low literacy skills, and families who couldn’t or didn’t show up often in person at the school.

So, we operated from a central principle already core to the Healey School: a child can’t be educated as effectively if parents aren’t included as key partners in the project. So, schools should ensure access to school information and pull all parents into dialogue about improving their children’s school experience. Info out, input in.

The Healey School enrolls a full U.S. range of families with different communication habits and needs. Some email the principal and Superintendent regularly. Some parents have no computers and no internet. A listserv has long enrolled only some. Robocalls home go in four languages; handouts home often don't. For many, parent teacher conferences require interpreters, and accessing those interpreters itself is a structural communication need, in part because some parents don't know how to access the service and in part because many of the parents who need interpretation are incredibly busy - sometimes working multiple jobs. One Portuguese-speaking dad worked such long hours he didn't even have time to come to school to post a sign saying he wanted to find and pay another parent to help him drive his daughter to school. In addition, parent and staff efforts to make an appointment to talk to one another with interpretation services can also get lost in the crush of meeting student needs: One Spanish-speaking parent told us she’d tried a number of times throughout the year, unsuccessfully, to meet with her child’s teacher in person.

In contrast, some families, particularly English-speaking families, volunteer many hours in classrooms during the school day and so get regular access to their child’s teacher. Many such families also are on committees that meet after school and so, take the opportunity then to contribute ideas to the school. Over the years, we saw that families who saw each other regularly at face to face school events also made friends, joined listservs, signed up in directories, and showed up at next events.

As we describe below and in the Expanded story , when we began in 2009 we first worked on several strategies to support diverse parents to share ideas and information, and to build relationship (Reading Nights, Parent Issue Dialogues). Then, we focused on the challenge of multilingual communication, because language barriers particularly have excluded many Healey parents from full participation. The Multilingual Coffee Hour, begun in 2009, was our first explicitly multilingual effort. Then, in 2010-11 and 11-12, the Parent Connector Network has focused fully on parents reaching out to other parents who speak the district's three main languages other than English: Spanish, Portuguese, and Haitian Creole. We've also been working to build personal relationships between bilingual parents and recent immigrant parents, in order to bring more voices into school debates and more people into school events and leadership -- as well as help the school respond more quickly to parent needs.

Begun in Winter 2010, the Parent Connector Network now supports translation and parent-school relationships, by connecting bilingual parents (“Connectors”) to more recently immigrated parents face-to-face, and via a phone tree and multilingual hotline. The Parent Connector Network is now run largely by parents and community members, with coordination efforts by a OneVille community staff member handed to school staff; Connectors continue to innovate the Network model in partnership with school administrators and staff and with the blessing of District administration. Our hope is that new part-time Parent Liaisons being hired by the District for schools like the Healey will also help the volunteer Connectors coordinate their work.

Beginning in spring 2012, Connectors started to use a multilingual call-in hotline (which our MIT friend Leo Burd made for us with open source VOIPDrupal software) to share out school information, to help ensure that information reaches English language-learning families and families with fewer tech and literacy skills. As Connector relationships and incoming parent requests and ideas grow in the future, Connectors may use Google forms to gather and prioritize school information. (Google forms are simple online forms that allow multiple people to input information that gets stored in a basic online database.) We tried that strategy briefly in 2010-11 but didn't yet need it: so far, Connectors have been able to handle individual parent needs by simply relaying requests and issues to appropriate staff.

By spring 2012, we were working with 5 Spanish-speaking Connectors, and 1 Portuguese-speaking, 1 French-speaking (for Haitian Creole-speaking families), and 1 Hindi and Nepali-speaking Parent Connector. Each Connector is asked to call 3 - 5 other families once a month to share key information from the principal/school and to ask questions about any issues parents are facing. The Connectors are also on-call to parents during the school year to help them find answers to both general and specific questions or concerns they may have about their child’s school. (e.g., some Connectors have received calls about issues like summer school enrollment, or about how to reach the district’s Parent Information Center to enroll a new cousin in a school.)

That spring, we also successfully tested a strategy of having volunteer Connectors wear "badges" as informal interpreters or contacts available to any school parent at the beginning of some school days, to enable more parent-parent connections and a clear route to get "on demand" interpretation for early morning conversations with staff.

Connectors also are starting to act as volunteer “Translators of the Month” for each main language group, helping to translate a monthly set of school information for our Healey Hotline. This translated material can then be used for other school media (listserv, handouts, flyers, etc.). These Translators won't translate the official information the school or district is legally required to make accessible to all parents. (Civil rights law requires that all parents have an equal opportunity to access important school information; some such information involves specialized lingo and definitely requires formally trained professionals.) But so far, volunteers and, stipended Connectors ($15/hr) are willing to help produce an additional stream of translated material for the school. (As we describe below, we later found that in-person support to access interpretation helped ELL families to feel comfortable meeting with their teachers.)

In fall 2011, we also successfully argued for creating a part-time liaison role (five hours per week paid by the school) for staff already employed by the school to support the Connector Network. The liaison role provides a range of crucial supports for the network that a school employee is best positioned to do. For example, the liaison can help summarize school information for translation by the translators of the month, summarize parent needs for the administration, recruit new parents at in-school events, and respond appropriately to serious or ongoing parent needs -- beyond what a volunteer parent can or should do. The role requires not only a strong connection to local immigrant communities but skills in tracking and managing multiple relationships and projects simultaneously. Several staff members tried the role, and one particularly willing staff member volunteered her time.

The role is currently distributed across the volunteer staff member, several parent leaders, and a OneVille community staff coordinator. Our final goal has been to transfer these responsibilities away from OneVille paid staff and fully onto staff and parent leadership, and we spent the spring 2012 semester building the staff skills to do this, supporting parent leadership, and piloting the full combination of multilingual hotline, connectors, and parent liaison work.


Slide1.jpg Slide2.jpg Slide3.jpg

See the bottom of this Overview page for the final set of "components" we were implementing by spring 2012.

Our work, and our ¡Ahas!

What was the basic groundwork needed to support the current work? How did the project change and grow over time? At this point, what are our main ¡Ahas! about improving communications in public education? What communication and implementation ¡Ahas! and turning points did we have over time?

Work informing the Parent Connector Network began in a 2009-10 series of Reading Nights and Parent Dialogues, and a Multilingual Coffee Hour that continued in 2010-11 as part of the Parent Connector Network infrastructure. We learned a huge amount in that work and we built relationships that enabled the development of the Parent Connector Network. Click here for the full backstory!

As a multilingual group of parents and staff (a few of whom speak only English), it has taken us two years to fully understand:

1) The barriers in the way of adult English learners' participation in English-dominant schools;

2) The sort of systemic communication "infrastructure" necessary to include more immigrant parents as partners in the project of supporting young people;

3) How to find and recruit people with the skills needed to implement the infrastructure, and how a volunteer-based project can delegate responsibility across available community members (and, stipend key people for leadership roles.)

Some main ¡Ahas! over time have been these:

¡Aha! Overall, we’ve learned that committed and diverse parents can be expert innovators of communication infrastructure for including all parents because they have a full understanding of communication barriers.

¡Aha! In a multilingual school and district in particular, local bilingualism is a key resource for strengthening communications and relationships between families and educators. The key is tapping local bilingualism in strategic ways.

¡Aha! To fully engage all parents in a multilingual and diverse school, each effort to engage parents requires multiple efforts to make communication fully inclusive. Barriers to full inclusion exist every step of the way. So, we have come to think in terms of creating a full "infrastructure" for schoolwide communication (and low-cost translation and interpretation in particular). For example, to reach parents across tech access barriers, a Reading Night linking three kindergarten classrooms and a Special Education classroom required advertising the event not only using the school's listserv, but also via paper handouts and displays on the kindergarten hallway's wall. Including all parents during the event also required actively tapping parents' own bilingualism, by engaging parents in translating conversation in multilingual groups. To get parents to a Multilingual Coffee Hour or PTA Night event, we needed to learn how to record multilingual invitation messages on the school's "robocall" system; then, we had to experiment with which recorded voices made the event seem most appealing to parents. We also experimented with recording targeted robocalls to one language group at a time, instead of recording all four at once. This was because on parents' home answering machines, robocalls often cut off after the first two languages -- and because Portuguese and Haitian Creole translations were always last after English and Spanish, those languages often didn't get heard.

Before we started working on the Parent Connector Network in Winter 2011, we worked with families and teachers in other efforts to improve parent-school and parent-parent connections. Most of all, we had to build relationships across parents and staff who cared deeply about including everyone. These friends became key partners in innovation.

Communication and implementation ¡Ahas!, and turning points!

We had many ¡Ahas! in sequence on this project over two years. To read the full story of the efforts that gave us these ¡Ahas!, click here!

Additional ¡Aha!s about schoolwide communication included the following.

READING NIGHT AHA:

Running up the Healey stairs to a Reading Night
Consuelo, mastermind of the Multilingual Coffee Hour, and her OneVille pizza: our best Reading Night advertisement

Reading Night was about building initial relationships and friendships between parents as much as it was about sharing reading tips. These relationships became crucial to all of the work we all did together at the Healey over the next three years.

MULTILINGUAL COFFEE HOUR AHAS:

The Multilingual Coffee Hour started in 2010-11 and then became a key piece of the Parent Connector Network infrastructure the following year. We realized:

¡Aha! Making parent gatherings explicitly multilingual encourages speakers of languages other than English to ask questions and offer opinions. In addition, multilingual events -- events where people take the time to translate for one another and, encourage others to speak in their own language -- also help parents and staff appreciate their peers' language talents.

Dave, multilingual coffee hour enthusiast and 2011 PTA president

PARENT-PARENT ISSUE DIALOGUE AHAS:

In 2010-11, several Parent-Parent Issue Dialogues helped a number of Healey parents debate a fundamental and controversial issue about their school's future: integrating several historically separate student programs. We realized the following in these efforts:

¡Aha! Many parents have few or no opportunities to talk to each other or to decisionmakers in organized settings, about major issues in their school. This means that their ideas and energy for improvement go untapped. Parents with tech access and knowledge (e.g., parents on a school listserv), and English speakers, are often far better informed and included in such debates.

*TURNING POINT: With the Healey in the midst of integrating several historically separated programs, parents focused for 2010-11 and then 11-12 on improving infrastructure for schoolwide communication -- and particularly, on including immigrant parents in the loop of school information and input. We designed the Parent Connector Network.
*¡Aha!/TURNING POINT: Try focusing on the most-blocked communication first. In this case, after trying a number of efforts to link parents at the school in dialogue (another important barrier at the Healey was the need to build relationship between newer, higher-income English-speaking Somerville residents and older, lower-income English-speaking Somerville residents), we focused on addressing the language barriers making communication particularly difficult.

PARENT CONNECTOR NETWORK AHAS:

In addition to the main ¡Ahas!above, we realized the following:

¡Aha! Innovation requires experimenting with communication solutions, even if strategies aren't guaranteed to work. In our case, we tested a number of solutions for getting school info “out” and parent input “in” across boundaries of language, and building relationships across those boundaries.

¡Aha! While asking how schools get info out, we also have to ask how they get input in. How do schools hear about and then respond to parents’ ongoing problems and concerns?

¡Aha! School-home communication relies in part on parents building relationships and connections with other parents. Parents said they came to PTA night or other such school events because someone they knew invited them -- that a friendly face would be waiting at the event ("Come to this event, and I'll be there to support you"). Tech tools like phones, hotlines, or listservs can amplify and extend that ultimate resource for parent-parent connection: relationship-building. One of our Connectors had an ¡Aha! that others echoed across the OneVille Project: “My main conclusion is that relationships matter and they are what makes everything work.”

¡Aha! Creating “infrastructure” that makes interpretation and translation more efficient requires figuring out who to pay for what. The people who share a school can, will, and should volunteer their time to help the school and other families communicate. But only up to a certain point. When workload is too heavy or when professional skills are necessary -- and, to embed the project into the core work of the school -- projects need to pay staff whose job it is to help include all parents. For example, communication on individual parents’ serious personal needs will have to be covered by paid staff, freeing volunteers to be friends, info-sharers and links TO paid staff. But making translation mechanisms more efficient (e.g., trying a hotline to get info to many parents at once; triaging info to be translated by volunteers or stipended parents on the hotline) can save staff time that otherwise is spent explaining things repeatedly.

Some key turning points in developing the Connector role:

By late January, 2012, we began to feel that phone calls pairing Connectors to a subset of families weren't enough. The Connector Network had grown to a total of nine bilingual Connectors paired with dozens of families for phone calls "out," but parents weren't asking much of their Connectors, and putting effort into getting parents to school-based events started to seem less profitable than perhaps scheduling events where parents themselves already were. Parent Connectors met together to brainstorm next steps on information-sharing and relationship-building:

TURNING POINT: In spring 2012, we pursued a deepened focus on face-to-face, rather than phone-to-phone connection. The Connectors brainstormed several sites of rich communication in daily school life to build on next:

  • Often, we saw ELL (English language learning) parents waiting before and after school to ask questions of a single bilingual staff member. To support these face-to-face connections, we found it useful to stipend three connectors to spend additional hours before and after school, to help connect parents directly to the staff member they wanted to talk with.
  • Parents also find that communication about their child’s classroom, rather than about the whole school, is much more engaging and rewarding. So next year, Connectors will begin to pair up with grade level teams or even with particular "classroom parents" to share classroom-level information with families in their child's class or grade.
  • Next year, Connectors plan to hold monthly multilingual coffee hours outside of the school, at places where parents already gather -- e.g., at the Portuguese Club, the Haitian Coalition, or the Mystic Housing Project.

Some key turning points in developing the Connector Network's technological infrastructure:

  • Leo Burd, a new friend from MIT's Center for Civic Media, finished an improved version of our hotline in spring 2012. We stipended three Connectors each month to translate the info update into three languages and record it on the hotline. The Connectors began to call families simply to let them know the hotline was a resource, and Connectors sent out a robocall in the school's main languages to announce the hotline via the school’s automatic messaging system. We think the hotline may relieve the Connectors of having to share schoolwide information with families. This, in turn, would allow Connectors to focus all their energy on more personalized outreach.
  • We helped Purnima Vadhera, the 2011-12 principal, make a fall parent communication form (see File:Healey School Communications Sign-Up Form 2011.pdf) that will help parents sign up to get a Connector, make it easier to get parents’ phone numbers, and allow parents to record their preferences for contact (texting? listserv? classroom listserv?) and indicate whether they need email training.
  • Finally, we began teaming up with parent leaders and local community organizations to explore offering computer, internet, and email listserv training to parents. In a multilingual community where not everyone uses computers, some lack access to information because of translation gaps and some because of a gap in basic tech knowledge. We learned early on in our work in Somerville that the problem for parents was often not necessarily one of computer access (the nearby housing project has many computers) as much as one of training. Even English-speaking parents in the school’s magnet program didn't know how to get on its listserv; many parents didn't know how to use a computer's basic functions. Now that the school’s programs have merged and the Healey school is creating a schoolwide listerv, these issues will rise to the fore. And having parents develop and participate in a multilingual school listserv could be a powerful new frontier for parent inclusion.

In our 2011-12 work, we've also gleaned some very practical lessons about how to implement the Parent Connector infrastructure:

  • ¡Aha! Bilingual volunteers may engage parents more effectively in school activities if they reach out to parents with a specific offer or request rather than a generic offer that requires parents to actively seek their help. For e.g., the generic offer "to provide school information and help answer your questions whenever you need it" may be less effective than “I’ll come with you to parent-teacher conferences next week,” or “Come to a Brazilian dance performance at the school on Friday."
  • ¡Aha! In order to engage ELL families with the most excitement in schools, a focus on traditional school activities that simply include parents in “business as usual” (i.e., Parent-Teacher conferences) can be complemented by the creation of school activities that actively honor these families’ languages and lives, e.g., a monthly Multilingual Coffee Hour that actively invites multilingualism, or an International Week that actively incorporates heritage activities in the classroom and after school.
  • ¡Aha! Parent availability changes, so it's important to develop a strategy for recruiting new parents to school efforts early and often. In addition to doing outreach and holding multicultural events at the beginning of the school year, when parents' hopes and energy are high, recruitment can also target parents whose children are in kindergarten, help the families become acclimated, and eventually tap them as leaders and mentors to next parents.

Our products: Concrete communication improvements and next steps

We are proud to say that the Parent Connector vision and project is now part of the Healey School's school site plan. We have a core of volunteer Connectors reaching parents in-person and via phone, and lead Connectors in Spanish and Portuguese. Two current/former Harvard graduate students, Jedd Cohen and Ana Nieto, worked as support coordinators in 2011-12 to support the effort while it solidified. The 2011-12 principal, Purnima Vadhera, worked with us to submit a contract to Human Resources for the five hrs/week liaison position to handle parent needs forwarded by the Connectors -- and to oversee the multilingual communication process we’ve come up with. While we waited for the liaison position to be approved, we filled in the gap by combining Jedd and Ana's efforts with that of a bilingual staff member, Adriana Guereque, who volunteered her time to follow up on individual family needs, and a very engaged Healey parent, Laura Pitone, who triaged monthly information and ensured that the district translated it.

Together, the Connectors (with advice from many other parents and staff consulted over the two years) fleshed out a list of components of the necessary “infrastructure” for multilingual communication. The Connectors themselves have become seen as a key local resource, as people willing to be on call to answer other parents' questions in their language and to (monthly) share information that requires more explanation:

Revisedinfrastructure.jpg

In sum, this year we piloted the full infrastructure we developed for multilingual communication. We:

a) piloted our Parent Connector Network, in which bilingual parents make monthly contact with immigrant and low-income families to get information to and input from them; Connectors also invite parents to our Multilingual Coffee hours and to the hotline.
b) tested a model where a Parent Liaison and Lead Parent Connectors develop and implement the details of face-to-face and phone-based outreach, follow up on specific parent needs, and help parents access interpretation;
c) piloted initial use of our open source hotline, on which parent “Translators of the Month” translate and record information about events, issues, and opportunities.

We're pleased to announce that next year the Healey School will have a district-funded, part-time parent liaison to manage volunteers, reach out to ELL families, and oversee a new Welcome Center, designed to provide a welcoming space at the Healey to all families. We're working with the incoming Principal, Jill Geiser, to build on our insights from the Connector Network as she designs the responsibilities of this new position.

Final thoughts

Overall, we’ve been exploring a cost-effective hybrid of volunteer efforts to connect parents to other parents and “infrastructure” that includes paid school staff. As mentioned above, a key issue we addressed in the Parent Connector Project was the line between translation/interpretation that bilingual parents can and will do as volunteers to serve their community, and when the district has to pay professionals. A parent in a federally funded district has a civil right to translation and interpretation if she needs it to access important parent information (including at parent-teacher conferences). But all districts are strapped for money and bilingual skills are true community resources. How to tap those resources without overtaxing volunteers, and without asking volunteers to do the sort of work that really should be done by paid professionals?

In our case, we isolated an aspect of the infrastructure that volunteers couldn’t cover and argued that a bilingual staff member be employed part-time to cover it. We reasoned that volunteers shouldn't be asked to ensure that parents get Special Education services for their children or be responsible for requesting paid interpreters from the district. Paid staff in any district should be on top of such “case management.” But volunteers may be able to do something no staff member can do so easily: build friendships that glue parents in as partners in student success.

Questions to Ask Yourself if You’re Tackling Similar Things Where You Live

What big issues would we recommend others think about in their own attempts to improve communications in public schools? Contact us to talk more!

Consider the current and needed schoolwide communication infrastructure at your school:

➢ Can everyone who needs to get and share important school information, get and share it? Do parents know who to talk to when they need information?
➢ Where do you put school information so that everyone in the school can see it?
➢ How do you share parent ideas around the school?
➢ What system do you have for translation and interpretation, in particular?
➢ How can you tap local bilingualism, either paying people to translate material or organizing bilingual volunteers to pitch in on translation and interpretation in a way that doesn't take too much of their time?
➢ How can you build on parent-parent relationships to pull all parents into school events and conversation?
➢ What tech training do parents need in order to get information? How could you help all parents get this training?
➢ Which efforts at parent information should be a task for school staff rather than volunteers?

Technological how-tos

Here's where we describe "how to" use every tool we used, so that others could do the same. We also describe "how to" make every tool we made!

We’re using a Googledoc as one organized place for a Connector list of resources relevant to Somerville's immigrant families: https://docs.google.com/document/d/15eF7hZP5DUCwl92WTYcOrElUWDICTdx69WjDgs8UfOI/edit

See http://www.google.com/google-d-s/tour1.html for instructions on starting a Googledoc. (Note: to use googledocs, users need gmail accounts to view any googledocs that are set as "private.")

While some school systems get parents' permission en masse to release their information to other parents in a School Directory, administrators asked us to take care to ask each parent's permission for releasing information to their Connector (see Expanded story on this aspect of the project). We use Editgrid for secure lists of approved parent contact info for Connector use. See editgrid.com for instructions on starting and using Editgrid's spreadsheets. (At this time of this writing, Google spreadsheets don't allow sorting by any column, whereas Editgrid spreadsheets do.)

We used Google Translate for some first-pass translations of material for the hotline or other school channels, but bilingual parents still had to correct the translations. See http://translate.google.com/support/ for tips on using Google Translate.

With the Healey's principals, Connectors have experimented with recording translated robocalls home, using Connect-Ed, the district’s existing system for sending calls to many families at once. As described in the Expanded story, in our case, we learned to target robocalls to one language group at a time instead of recording all four at once, because robocalls often cut off after the first two languages (and because Portuguese and Haitian Creole were always last). We also asked Connectors to record some robocalls in their friendly parent voices, which drew some parents to PTA night!

On the hotline: Local technologist Seth prototyped our first hotline, and in spring 2011, we were still recording voices or saving audio files onto Seth's computer -- see photo of Maria and Seth above. At that point, Leo Burd from the Center for Civic Media then made the professional version that we began piloting in 2011-12. (Here's Leo talking about his VOIPDrupal software: http://www.youtube.com/watch?v=C8NCRLCdPno&noredirect=1). See here for Leo's explanations of the programming. Leo's goal is for the software to be developed quickly by any community that wants to use it.

Click here for the Summary on this project; click here for the Expanded story on this project.

Retrieved from "http://wiki.oneville.org/main/?title=Overview_and_key_findings:_Schoolwide_toolkit/parent_connector_network&oldid=3361"