Click here to listen to the podcast version of this post.
All too often in special education, those of us who have been working at it professionally for more than a few years have increased our vocabularies to include terms of art, acronyms, and legally significant phrases that mean a whole lot to us, but not a whole lot to professionals new to the field and parents. I find that a lot of my job as a lay advocate is translating SpEd-Speak into plain language.
It was actually during a case I’ve been working with a family that moved to the U.S. from Thailand that brought this point home for me. I found that by simplifying my language for the benefit of the translator, who knew nothing of special education, I made it lot easier for everyone else in the room to follow the logic of what I was saying. The meeting was also attended by the school district’s lawyer, who was actually pretty awesome once she realized what was going on. It was one of the most amicable and constructive IEP meetings in which I’ve participated in a while.
What I found worked best was to use simple language to communicate with most of the IEP team members, then sum up my point to counsel for the district in language she would appreciate in light of the regulations and the applicable science, if needed. In the end, what we figured out was that our 9th grade client qualified for special education as having autistic-like behaviors pursuant to 5 CCR Sec. 3030(g) and that his speech-language impairments for which he had originally been found eligible were features of his autistic-like tendencies as well as bilingualism coming from an Eastern tonal language to English.
I already knew from experience that throwing a bunch of jargon at people during a meeting where you’re trying to make things happen is not particularly constructive if any of them are unfamiliar with the lingo. Having non-English speaking clients only made the point more vivid. But, then I ran across an article in an old issue of Entrepreneur magazine that drove the point home even more, and, combined with my prior knowledge, inspired this blog post and corresponding podcast.