Expanded story: Schoolwide toolkit/parent connector network
From Oneville Wiki
Schoolwide communication toolkit, particularly the Parent Connector Network: Communication ahas, implementation ahas, and turning points!
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 in 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 (7-8).
In fall 2009, with parents from across the first three programs whose children shared a Kindergarten hallway at the Healey, we began creating Reading Nights to link parents in face to face efforts to build relationships and share information on reading with young children.
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 creating a monthly multilingual coffee hour and holding some parent dialogues. In 2010-11, a subset of bilingual parents forged forward to create the Parent Connector Network.
From the beginning, we wrestled with the particular issue of connecting English-speaking parents and staff with parents speaking other languages -- and with getting information written in English translated. Over time, we realized the particular need for improving the communication infrastructure for translation and interpretation and focused fully on the Parent Connector Network in winter/spring 2011. But let us share the story of how we got there! It's a story of friendships sparking school improvements and vice versa.
SCHOOLWIDE COMMUNICATION EFFORT 1: READING NIGHT
In fall 2009, Mica and Consuelo, both parents in the Kindergarten hallway at the Healey School, met at a parent coffee hour with the principal and discovered a mutual interest in starting conversations across language and program. We immediately started talking to other parents about the idea of “OneVille” -- in this case, linking families who shared a pretty divided school. With that, a design partnership at the Healey began to sprout!
In conversations with the principal and other parents in the hallway, we came up with the idea of holding a monthly Reading Night designed to link parents across programs in communications about supporting children’s literacy. We sat with other parents in the PTA room and talked about what might pull us together. Tracy and Dave, Maria, Jen, Carrie, Consuelo, Michelle, and others started brainstorming a first Reading Night focused on baking words (Tracy, a parent in the hallway’s “Neighborhood” classroom, had a cookie business and her husband Dave worked in a pizza restaurant).
In doing the work of holding Reading Nights, we built friendships between us parents that would make a difference in the years to come -- and we encountered a bunch of schoolwide communication issues that would shape our thinking about the “infrastructure” needed at the Healey!
AHA: the success of any school event relies on school-home communication.
To get parents in the hallway out to Reading Nights, we had to advertise events in multiple languages and test ways of getting people back to school in the evenings. A listserv linked the school’s K-6 magnet program parents (though less so, the program’s lower-income and recent immigrant parents) but not the Special Education and "Neighborhood" programs. To include everyone, we moved forward with paper and face to face communication.
We put up multilingual signs outside of the classroom doors, where parents would see them. Some did, but not all parents dropped off their kids at school themselves. Consuelo's giant pizza, put up on the wall a few days before each Reading Night, worked particularly well to attract kids -- who then brought their parents!
Had we known that we could record calls on the school's "robocall" system (ConnectEd) to target parents in their language, perhaps we could have used that to invite more people! 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 direct channel-home was often used only for the "most important" of communications, so we may not have been allowed to use it. We only used it twice in these two years -- once to invite people to a schoolwide dialogue and once to invite parents to PTA night.)
Face to face invitations on the playground before school were often the thing that brought some parents to Reading Night. But face-to-face invitations were really time-consuming, and our energy for standing outside to invite parents personally to events waned over the year. Beyond sending fliers home and putting up Consuelo’s pizza, at teachers’ urging we continued to announce Reading Nights to kids in classrooms, who would then invite their parents. One of our most well-attended Reading Nights involved an entire “Neighborhood” class, who did a play together with their teacher.
AHA: Sharing info and building relationships with busy parents often requires face to face contact, despite the fact that it’s time-consuming.
AHA: Bringing kids along to parent events helps glue together parents in a common experience -- even as it also distracts them from sharing information with other parents!
Reading Nights were in part about getting families excited about reading together in new ways (parents told us their children left talking all night about reading). But as it turned out, what many parents most needed (or wanted!) was a chance to talk quietly to other parents. We learned to make time in Reading Nights to get parents together on the side to talk together about our children’s reading struggles, as our children did activities. (This required parents who could interpret for others.) In part from listening to parents who ended up taking care of the kids, missing the parent-to-parent conversation, and getting frustrated, we realized parents really needed opportunities to become and make friends.
As we tried to share out tips from Reading Nights, though, we again realized the need for better communication infrastructure for connecting parents to each other to share information. We tried to post our reading tips as paper sheets on a hallway bulletin board (we used Google Translate, which garbled some of the words) and we stuck the same fliers in every backpack. But this never turned into a conversation that ran in between our Reading Nights -- whoever didn’t come in person didn’t really benefit.
AHA: There’s no way that all parents will or can show up to face-to-face events. So, any event needs a plan for getting information to parents who didn’t show up.
Prepping for Reading Night took more time than we wanted, because we tended to prepare materials from scratch (LINK TO CONSUELO'S DOCUMENT HERE).
But at the same time, we knew our kids loved the events, and the work did create friends and leaders among us. One organizing parent (Maria) later became the head of the PTA and two others (Tracy and Dave) its vice presidents, and others (Michelle) won spots on the School Site Council in a year that would turn out to be very important for the Healey’s future (see below). We saw other benefits to parent-parent connections: since our first Reading Night focused on sharing words about baking, one mom got word of Tracy’s cookie business -- and hooked her up to a reporter in the Boston Globe for press!
We burned out on Reading Night after holding about six of them that year, because it took too much face to face work to create materials from scratch. We sort of reached the outer limit of volunteer time and energy. We also realized that since we weren’t experts on reading, it was more effective for us to focus on venues for gathering parents to talk, period, than on guiding other parents in the content of teaching reading. We also didn’t yet know how to “seed” events so they would replicate without us. But we knew we had created an important space for parents to gather together -- and the friendships we made carried us through our next innovations.
AHA: If prepping face to face events from scratch takes too much volunteer time from people, they lose momentum. At the same time, the slog of preparing for face to face events can build friendships that can seed real change.
SCHOOLWIDE COMMUNICATION EFFORT 2: MULTILINGUAL COFFEE HOUR
While designing Reading Nights, we also focused on improving an existing "slot" for parent-parent and parent-administrator communication: the typically English-dominated "coffee hours" with the principal, held monthly on Friday mornings in the PTA room. Relatively few immigrant parents came regularly to this event, and English-speaking parents almost always dominated the conversation.
In partnership with the principal in fall 2009, we created a slot for a multilingual coffee hour model, a brainstorm of Consuelo (PHOTO), always committed to finding creative ways of empowering and including immigrant parents. We thought about having language-specific coffee hours but the principal asked for a combined coffee hour, which in the end offered its own benefit -- valuing multilingualism. In the multilingual coffee hour, parents voluntarily translated for other parents wanting to ask questions and hear information from the principal. Enjoying the sound of multiple languages became part of the event.
[JPEG HERE OF COFFEE HR INVITE]]
The experience quickly clued us into a key local resource:
AHA: The massive local resource of parent bilingualism!
At several points over that school year and the next, we considered combining the multilingual coffee hour back into the "regular" coffee hour with the principal. In fall 2010, the Healey's next principal first suggested that every coffee hour should de facto be multilingual. But, then he decided to keep a distinct "multilingual" coffee hour. Since typical coffee hours were still dominated by questions and rapidly-launched comments from 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. Main needs: a coffee pot; some Brazilian sweet bread; the principal; and parents with questions or ideas!
AHA: making parent gatherings explicitly multilingual encourages speakers of languages other than English to ask questions and offer opinions.
(ADD MINI COMMENT BLURB OR VIDEO INTERVIEW HERE WITH LUPE OR IRMA and DAVE, ON WHAT IT HAS MEANT TO HAVE AN EXPLICITLY MULTILINGUAL COFFEE HR? ANA, CAN YOU PLAN TO GET THIS?)
SCHOOLWIDE COMMUNICATION EFFORT 3: PARENT-PARENT ISSUE DIALOGUES
New community developments at the Healey in 2009-10 shaped our next ahas about needed improvements to communication infrastructure. Halfway into the 2009-10 school year, the Somerville 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 multilingual coffee hour for a number of parent dialogues and “Q and A with the principal” dialogues to facilitate conversation about this choice. link to OV blog post here We also held an organized parent dialogue on a Saturday at the nearby Mystic Housing Development’s activity center link to blog post here.
In our work to support such organized parent dialogues, we realized how irregular it was for parents to just speak to each other across "groups" about their children's education. Many parents had never talked to parents from the other programs, or across lines of language or social class.
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.
It became important later in the Healey's unification debate to be able to report that everyone we talked to - across lines of class, race/ethnicity, and language - said they wanted a more rigorous learning experience for their children. That’s because so few people had heard these voices before.
In the parent dialogue work, we also realized again some structural barriers of communication that held back many parents from being fully involved in the school. School committee members used the magnet program's listserv to advertise school committee meetings about the Unification debate. The parents who came to the meetings to speak their minds were disproportionately those on the listserv. Those on the listserv also emailed the superintendent or principal regularly with their opinions about whether the programs should integrate. Three months into the debate, when we walked around the nearby Mystic Development (the housing project literally down a flight of stairs from the school) to invite parents to a school committee meeting on the upcoming decision, we realized that many parents – again, those not on the listserv -- were unaware that the possibility of integration was even up for debate at their school at all. Some parents, particularly immigrant parents struggling to communicate in a new language, were so “out of the loop” of school information that they didn’t understand there were multiple programs at the school to begin with.
AHA: If tech channels for dialogue are available only to some in a school, those not on the channel don’t get equal access to the dialogue. (Example: a listserv that only some parents are on.)
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. Parents were invited into the process as partners.
TURNING POINT: With the Healey in the midst of brainstorming all sorts of changes to its everyday structures, we parents focused for 2010-11 on improving infrastructure for schoolwide communication -- and on including immigrant parents in particular.
MAIN SCHOOLWIDE COMMUNICATION EFFORT: THE PARENT CONNECTOR NETWORK
In the cafeteria one morning in fall 2010, Consuelo and Mica were sitting with several parents from the PTA (Maria and others), talking about how to improve schoolwide communication. Consuelo, whose phone was constantly ringing with calls from Spanish-speaking parents with questions and needs (how to get a wheelchair? How to deal with a social service organization? Where to get a public service?) took out a piece of paper and started to draw triangles, linked to other triangles in a pyramid structure. Parents could be links to other parents, she explained, just as she was. In the car together going home, Mica named the role: "Connectors."
AHA: parents can be organized as communication links --”connectors” -- to other parents.
We began to share out the basic idea of “parents linking to other parents” with the school council and other school leaders, to see what people thought of it. People immediately liked the idea: many Healey parents often spoke of the need for better translation of information and “inclusion” of immigrant parents but hadn’t been sure how to facilitate it. There were already "room parents" in the magnet program, but these parents primarily had signed on just to email other (disproportionately middle class) parents in their classroom once in a while, about things like parent breakfasts, field-trip chaperones, or school supply needs -- not to explain the more important issues going on at the school.
Importantly, we learned from others that paid Parent Liaisons for each major language in each school had existed previously in Somerville, under a grant. When the grant finished, the Liaisons had ended too. We agreed to see what parent volunteers could do with their bilingual skills – without carrying the burden of paid employees. The Connector project took the idea of “liaisons” and asked parents, as friends, to “liaison” to a few other parents at a time.
Slide1.jpg)
We started brainstorming the components of the Connector project with the principal, at meetings with a "Parent, Student, and Teacher Partnership" working group of parents and teachers at the unifying Healey, and with those parents who came to our Multilingual Coffee Hours. Parents from our first Reading Nights also remained key brainstorming partners.
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?
Even as one focus was getting information “out” to all parents, a first question of the Connector project was how the principal would respond to serious complaints coming “in” from parents. This was Consuelo’s concern in particular, since her phone was often ringing with calls from parents with serious needs (e.g., parents seeking advice about how to handle confusing social services agencies and even bewildering arrests). In particular, we figured, parents with issues had to know that there was a point person to go to and, a point person then responsible for reporting back what was going on. But this “loop” couldn’t overburden any individual -- the principal was already answering streams of parent emails each day!
TURNING POINT: Focus on the most-blocked communication first. In this case, language barriers making communication particularly difficult. That meant Connectors had to be bilingual.
For a bit, we wondered: should all parents (including English-speaking parents) have a “Connector”? After Consuelo’s departure, we decided to focus the Connectors first on supporting communication with immigrant parents, who seemed the most blocked from information flow in both directions. And that meant Connectors had to be bilingual.
AHA: To build trusting relationships, consider connecting parents to specific groups of other parents -- and when possible, build on the social relationships parents already have!
A related concern was logistical: how would volunteers connect to a reasonably sized group of parents? Should they just post their pictures in the hallway, showing they were willing to take calls at any time from whoever? Knowing that this would make information flow chaotic, we decided to link each Connector by phone to 10 parents who spoke their language.
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 in translating public information so others could access it. We also recruited bilingual parents who had shown some interest in parent-parent events, such as our coffee hour, Reading Night, and public dialogues! Soon, we had Sofia, Lupe, Tona, Angela, Marcia, Maria, and Veronaise (PHOTOS IF POSSIBLE!), all parents, plus Gina, a young staff member and Creole speaker who as it turned out wanted to develop a career as a parent liaison. We used some Ford funding to stipend Gina to help coordinate the project.
As a team of Connectors, we met with each other in one of the school's conference rooms and started using our multilingual coffee hours to get ongoing advising from parents schoolwide.
The Parent Connector concept was approved early, in the school's formal unification plan in early spring. 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 decided that in particular, we also had 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 (robocalls, listserv, backpack handouts) or create new simple tools for parent outreach, and what to do with parent issues that came back “in.”
AHA: innovation requires experimenting with communication solutions -- in our case, for getting school info “out” and parent input “in,” across boundaries of language.
Our first parent-parent communication experiment -- to get info “out” and parents themselves “in” to school events -- was a new use for the school’s “robocalls.” As parents, we had received many robocalls for snow closures (!) and school events in the district’s four main languages: typically English, Spanish, Portuguese, then Creole, in that order. (Some of our answering machines still cut the messages off after English!). Somerville’s call-home robocall system, ConnectEd, typically was used by principals who asked Parent Info Center staff to record each translated version. One Connector, Lupe, had suggested we “flip” that typical script in two ways: we’d ask a parent to record a message targeted directly to speakers of a single language. It turned out that ConnectEd could do this and the principal, Jay DeFalco, was excited to try it. So, Lupe, Gina, and Marcia recorded a targeted invitation in Spanish, Creole, and Portuguese in the Healey principal’s office, using his phone. In the robocall, we invited parents to a gettogether to introduce the Connector project before a Healey PTA night. Nearly 30 parents showed up, some saying they had come because they heard Lupe’s voice! We ate food from Somerville’s Maya Sol (pupusas), Fiesta bakery (Haitian patties) and the Panificadora Modelo (Brazilian pastry). Two students from the Mystic Learning Center babysat for parents while they then attended parent-teacher conferences.
AHA: it matters whose voice is heard over a public channel! Consider letting parents invite other parents to school events by recording the robocall in their language, so that listeners who speak that language feel more socially welcome.
In a diverse group of Healey parents and the principal at our next multilingual coffee hour, we shared some information needs immigrant parents had expressed at the PTA Night event (How do I get my child tutoring or help with homework? How do I find scholarships and slots for afterschool? How do I enroll my child in an afterschool sport?) and brainstormed ways Connectors could respond.
One goal people shared was to make all parents feel more comfortable approaching school staff themselves to ask questions. But we also knew that parents approaching staff one by one would be an inefficient way of getting basic answers out -- it was also often impossible, because parents needed interpreters to approach school staff in the first place.
AHA: Schools need systems for responding efficiently and publicly to common parent questions as they come up. Parents approaching staff one by one to ask basic questions isn’t efficient -- especially if parents need intepreters to do it.
At the time, we had another core concern as well: how to avoid a situation where parents mentioned needs to Connectors and never received a response? In xxx (date), we modified a district form for reporting bullying incidents and created this Googleform (LINK TO IT OR SHOW JPEG?) for Connectors (and Connector coordinator/principal) to use to keep tabs on parent calls. We edited it together, adding more detailed information on how to tell parents to request translators.
But the system for “input in” still didn’t feel right. For one thing, we realized we were still advising Connectors to tell non English-speaking parents to approach English-speaking staff to share their needs and arrange interpreters!
We were heading toward understanding the need for “systems” for info flow and translation in both directions.
One implementation stumbling block clued us in to a need for a system:
AHA: better systems are needed to get parents’ contact numbers to other parents! Otherwise, parent partnerships can’t easily happen.
Because our Connector project started mid-year, we had no beginning of the year form that parents felt compelled to fill out, saying “do you want a Connector? Check here to release your number to them!” Only staff were allowed to have all parents’ numbers automatically. So, it took weeks to figure out how to get Parent Connectors other parents’ phone numbers.
We first tried handing out paper permission slips at the PTA Night. They trickled in with signatures: way too time-consuming. So, we asked district Parent Information staff to call all of the parents and get their permission to release their numbers to Parent Connectors. (And we used some Ford funding to stipend them). To facilitate the calls, school staff first tried to figure out how to download a spreadsheet of parents’ numbers for PIC staff from X2, the district’s “student information system.” That took some time. 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 of approved parent numbers and could start calling. A month or more to get parents’ numbers, to other parents!
Notably, the magnet program had a great directory with parents’ phone numbers, home addresses, and emails in it, collected via paper sign-ups in classrooms when school began. Whenever we raised the issue of getting more parents' numbers to other parents, particularly from immigrant and low income parents, somebody would relate that many working-class parents were afraid of sharing personal phone numbers with other parents because of restraining orders and personal safety fears. This wasn’t totally true: many immigrant and low income parents put down their numbers on signup sheets at Reading Nights or coffee hours.
Issues of distrust are understandable: who is willing to share basic personal information with other parents, strangers, especially in an era of ramped-up deportation and legal interventions in households? But if unaddressed, what do such barriers to parent-parent contact mean? Children unable to be invited to birthday parties or playdates; parents who can’t be invited personally to gettogethers or hear important explanations of school issues; missed opportunities to pull parents together as partners. It’s just a basic tension.
AHA: Privacy and trust are key issues to be navigated carefully in broadening school-home communications. But, issues of privacy do mean that at times, it takes much longer for people to partner than they would otherwise. Consider an info form easily allowing parents to permit the use of their phone numbers for approved parent-parent contact.
All this is an important example of the need for infrastructure to normalize communications between school and home. One example is an official form allowing parents to easily offer permission to have a Connector, at the beginning of the year.
AHA: volunteers need communication infrastructure themselves, in order to make their own work easier. But it can’t be too techy or some volunteers will get turned off!
As we started to link Connectors to parents and make calls, we may have turned off a few Connectors by immediately using technology in our own infrastructure to communicate. For example, at the end of one face-to-face meeting we decided that Connectors might want to “get assigned” parents with whom they had a prior personal relationship, so we chose to use a Google Spreadsheet to divide up the names from home. This cost us several weeks as some confusion reigned: 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!
Some Connectors took immediately to using the Google spreadsheet to choose "their" parents and get their numbers, and to take some notes on each call. Other Connectors needed multiple phone calls to get them to come to training sessions on the Google spreadsheet, and some may have turned off to the project thinking that tech savviness was a requirement to participate. (One Connector has her daughter help her get her email; another uses her husband's computer to check her email account. Another checks email regularly but doesn't write back often.). One Connector tried the Google forms and in the end, wanted to use paper and asked Gina to retype her notes.
So, over time, we've realized what training is needed (how to use a Google spreadsheet!), and, which tech uses aren't really that necessary (possibly, the complex Googleform. This fall, we’ll record parent issues right on the spreadsheet of parent names, until the volume of parent needs increases).
AHA: only use tech tools if they truly enable participation. If they raise the barrier to participation, either don’t use them just yet or, train everyone to use them.
We emailed a lot between Connectors to discuss next steps, and unsurprisingly, such emails linked Connectors who used email for their jobs far more successfully than those who didn't access it routinely (this broke down along class lines, as well). Some Connectors who spoke primarily in Spanish were fine to read long emails in English, but didn’t want to write back in English. Some Connectors themselves required regular phone calls to stay glued to the project. Gina, our youngest member, preferred texts, as well (or a text saying she had an email!). And, we all needed occasional face to face meetings to brainstorm ideas more effectively and to stay interested in the project. Our core fall 2011 plan: a Connector party, with tequila.
As we began our calls home, we realized that Connectors were getting asked key resource questions that were time-sensitive (e.g.: can I enroll my child in summer school voluntarily, or does she have to be referred?). So, a key "information loop" became how to get such FAQs answered regularly on public channels when so many parents weren’t regularly on email. At a multilingual coffee hour, we asked people how to get basic information out to a lot of parents at once. Michael Quan (PHOTO) suggested a hotline as an immediate solution. So, rather than wait for everyone to get computer literate or computer access immediately, we decided to make a hotline, to get translated information more easily to all parents. At the same time, we started planning “email nights” to try to get more parents email access.
AHA: Go with the common denominator of parents’ tech skills to reach the highest number of parents most quickly with resources and information. Blockages to quick information flow really do mean that children don’t get opportunities. In the meantime, train parents on tech!
No free or open source hotlines seemed to exist in “plug and play” form, so Seth (PHOTO) prototyped a hotline using open source software and the Twilio API. The goal: create a tool that could let you “press 1 for Spanish,” and leave a message too in that language.
Tona, Maria, and Gina came in to record updates from the principal in Spanish, Portuguese, and Creole, and they also translated answers to parents' Frequently Asked Questions that had been collected by the Connectors. [FIRST SET OF FAQS HERE] They recorded their messages by speaking into Seth’s computer (see photo!). We then honed the hotline over the summer, so that translators can record to it from home.
After Seth prototyped the hotline, the question became how to regularly get translated school information, on to the hotline! As piles of paper in backpacks demonstrated, the school had a giant wave of information heading toward parents at all times; parents willing to translate information were chaotically being asked to do that. How to triage this information so that there wasn’t an overwhelming amount to translate? The school typically referred most important documents to the PIC for paid translation, and, parents holding events sometimes informally asked other parents to translate info on the magnet program’s listserv or on fliers. But because of the glut of info and the cost and effort of translation, most of the everyday info coming from the school via fliers or from parents via the listserv wasn’t translated.
AHA: A key need in public information-sharing is TRIAGING information so it’s not overwhelming. Another is ORGANIZING the information that goes out, so that others can quickly digest it. Our solution: a Googledoc and Translators of the Month!
In late spring, 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 needed to know that month for the Hotline into Haitian Creole, Portuguese, and Spanish. This was to lessen the chaotic requests for translation. Bilingual parents and staff noted at our coffee hour that translating material into their languages verbally – so, speaking it on to a hotline -- was actually easier than doing it word for word from paper to paper. But if Translators of the Month did put their translations on paper, we realized the same script could then go out via other channels (the listserv; in backpacks). And, the same basic info could also be referenced in Connector calls home.
We came up with this infrastructure plan: school leaders would dump information for possible translation onto a Googledoc. Then, the Principal and lead Connectors would triage it in a monthly meeting and decide what should be translated for the Hotline and what might require more explanation in a Connector call. Volunteer Translators of the Month would then translate the top priority information for the Hotline and share that script for other school media. In their monthly calls, Connectors would tell parents the highlights and refer them to the Hotline, along with explaining anything that required more one to one conversation.
We decided that Connectors also needed a standing info page Googledoc with links of local resources, so they knew what to tell parents looking for public services (e.g., legal or family services.) We’re still making that!
In those early Connector calls, we experienced the following incidents, convincing us of the final need for additional infrastructure for handling serious parent needs coming “in”:
- a mom who said she had been trying to set up a meeting with her child’s teacher for a year
- a mom who needed legal advice and then asked the Connector to go with her as an interpreter/ally to an IEP (Special Education services) meeting on her child
We decided that in such cases, we had reached the boundary line of what volunteers could do. Translating IEP information is a paid skill; and scheduling a meeting with a busy teacher could take a Connector hours of back and forth calls. It was time to consider actual paid staff for these aspects of school-parent connection.
AHA: Creating “infrastructure” for interpretation and translation requires figuring out who to pay for what. Communication on individual parents’ serious personal needs may have to be covered by paid staff, freeing volunteers to be friends, info-sharers and links TO paid staff.
We also kept hearing ongoing stories from parents who lacked interpretation and translation at the teacher meetings when they most needed it. Figuring out this piece of the infrastructure became another goal. Many parents didn’t know how to request translators for scheduled meetings with teachers. Some educators didn’t know how to find translators to talk in emergencies to parents. (As afterschool staff, Gina herself couldn't find a Spanish speaker one day to explain to a mother her son's injury). At other times, both told us, both parents and educators requested interpreters, but they were not actually present in the final meeting for reasons unknown.
AHA: a key aspect of effectively using the local resource of bilingualism is creating infrastructure for scheduling interpreters. It’s really about getting the resource of bilingualism in the right place at the right time.
While the District has a list of interpreters to call and also has bilingual staff at the PIC, getting bilingual interpreters to the right place at the right time is the core resource-use problem, rather than any lack of bilingualism in the community. Distributing the resource in a cost-effective way is also crucial: one Portuguese-speaking Connector, Maria, suggested based on her experience working in hospitals that the schools try an interpreter "on call" to do phone-based translation during certain hours. Parents have recommended that our dashboard family view also have a calendar at its end, helping parents schedule meetings with teachers themselves. We’re trying it!
Organizing translation and interpretation is of course far more cost- and time-effective than a scattered process where no one knows who is translating what or interpreting what for whom!
The resource of bilingualism also has to be actively tapped: Our colleagues at the Welcome Project in Somerville have pointed out other details of using local bilingual resources effectively for translation and interpretation. Interpreters at public meetings need to announce their availability in audible ways!
And, if interpreters go to PTA Night to interpret the big meetings, they also need to be on call for impromptu one on one meetings throughout the night between parents and teachers. The Healey principal had interpreters use walkie-talkies for this purpose!
In the end, we pressed for a part-time Parent Liaison slot at 10 hrs/week and advocated for Gina to play that role. We decided that in each call home, Connectors would also ask parents if they had individual questions or personal needs, and document those needs for Gina on the Google spreadsheet or on paper. If parents needed personal meetings with teachers or others, Connectors would get some of parents’ preferred meeting times and then pass the scheduling to Gina via email.
By fall 2011, we had finished our set of diagrams of components of the "infrastructure" for low-cost translation and interpretation in a school.
We now hope to join brainstorming forces with a parent group from Somerville's Welcome Project (housed in the Mystic Housing Development down the hill from the Healey school) that also wants to focus on translation and interpretation in Somerville (one mom in the group is also a Connector).
Slide7.jpg)
AHA: Today, systems for getting information to multilingual families and input from all families can absolutely be improved using some very basic technology – if people are shown how to use it.
Even in our own efforts to translate documents and call parents, we saw that technology could help us get organized so we didn’t waste each others’ time. Having an archive of googledocs where people kept old fliers so they didn’t have to be translated again saved us hours. So did an online spreadsheet where we collectively chose point Connectors to call a bounded set of families, and provided their numbers. (When one Connector was using a paper spreadsheet of her “assigned” families’ names and numbers, it kept getting misplaced and at one point was lost.) Google Translate helped some of us quickly translate a document and then check it for accuracy; we made a Googledoc to collect school information because we needed one place where school leaders could put the many things that ideally would get translated (and then triage that information in a face to face meeting). But people need to know how to use each tool! Otherwise, glitches in training slow things down even more.
AHA: Tech -- even a phone -- just helps extend the ultimate resource: relationships. 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.”