Abstract
When students cowrite with others who have different levels of proficiency with the English language, they can experience unproductive conflict related to feedback avoidance. The author interviewed 20 professionals with experience cowriting across such different English proficiencies and found three strategies that can facilitate feedback and collaboration: calibrate genre and reader expectations, establish protocols for reviewing texts, and frame feedback as a learning opportunity. She suggests that these strategies can be a step toward helping students mitigate their anxieties about feedback and feel more empowered to engage with linguistically diverse peers.
When students cowrite a text, their goal is to engage in âmeaningful interaction and shared decision making and responsibility between group members in the writing of a shared documentâ (Dale, 1997, p. 12). Because of the globalized nature of the workplace, one valuable context for such a collaboration is when writers who have different levels of proficiency in the English language cowrite a text. Many professional communication courses engage students in these types of collaborative activities with the goal that students will offer feedback to one another and potentially produce a text that represents a negotiation of writing approaches, genres, and linguistic features (Canagarajah, 2006; Herrington, 2010; Maylath et al., 2013; Wolfe, 2010).
While cowriting across different levels of English proficiency (EP) has valuable benefits for students, certain challenges can prevent them from meaningfully engaging with their peers. Namely, cowriting with peers who have different EPs can create unproductive conflict during the feedback process of producing a text. The aim of this study, therefore, is pedagogical: to explore the different strategies that professionals use when cowriting across EP differences and think about how teachers might use those strategies when preparing student writers to negotiate feedback and deliverables in productive and collaborative ways.
Research Background for the Study
The terms native English speaker (NES) and nonânative English speaker (NNES) have been much debated in the literature, particularly the extent to which they are put in opposition to each other in a static dichotomy (Lillis & Curry, 2010; PĂ©rez-Llantada, Plo, & Ferguson, 2011). Researchers have argued against these categorizations, calling for more nuanced understandings of language proficiency that acknowledge the fluidity of language practice (Koerber & Graham, 2017). In the following study, I attend to these important considerations by discussing language ability in terms of perceptions of proficiency. Specifically, I stray away from objective language criteriaâsuch as tests of proficiencyâand instead embrace the ways that cowritersâ perceptions of each otherâs linguistic abilities, or proficiency, influence their collaboration and feedback. Writersâ perceptions of their fellow cowritersâ proficiency can be influenced by factors such as their name, accent, education level and location, job title and status within an organization, years of experience with a language as well as the presence (or lack) of grammatical mistakes within a text.
At the same time, the labels NES and NNES do influence how participants view themselves and their peers; those identifiers factor into the larger equation of how they perceive proficiency. In some cases, the labels can suggest the contexts in which the English language was learned. In other cases, they can represent affiliations with a particular language group. Writers might also use these labels to suggest their own familiarity with a language without drawing attention to specific linguistic markers of proficiency. The complexity of these labels can be seen in the varied ways in which the participants in this study use them. Some participants used NES and NNES to suggest higher proficiency (HP) and lower proficiency (LP), respectively. But in some instances, NNES writers described helping both NES and NNES writers improve their writing, demonstrating that NES writers did not always have HP and that NNES writers did not always have LP. NNES participants also perceived their own proficiency as evolving and in some cases referred to themselves as nonnative speakers of English with native speaking proficiency. All of these situations illustrate the multifaceted nature of proficiency and its relativity in interactions.
The importance of taking a perception-focused approach to proficiency is that writersâ confidence in their own and their peersâ abilities is often influenced by assumptions based on their perceptions of EP. Specifically, peopleâs perceptions of another personâs linguistic ability often influence their assumptions about that personâs intellectual competency (Trahar, 2007), and when students collaborate on teams, those who exhibit a LP in English might be misperceived as potential threats to the success of students who have a HP (Le Roux, 2001). These misperceptions might cause writers who perceive themselves as having a LP to have less confidence in their own abilities or to view feedback from HP peers as more authoritative, constraining the dialogue and engagement between collaborators (Allen & Katayama, 2016; Allen & Mills, 2016; MacIntyre, Noels, & ClĂ©ment, 2002). Alternatively, writers who perceive themselves as having a HP might have less confidence in their LP peersâ abilities to perform writing tasks according to what they believe is the appropriate âstandardâ (Harrison & Peacock, 2010).
In a study on an international classroom in the United Kingdom, Harrison and Peacock (2010) explored how perceptions of EP negatively affected the collaboration between NES and NNES student writers. The researchers found that NES writers perceived their NNES peers as having a LP and therefore did not have confidence in the NNES writersâ abilities to perform a writing task. The NES students explained that texts written by their NNES peers were ânot to their [NESsâ] sort of standardâ and expressed concern over how that would affect the groupsâ grades (p. 889). Instead of using the situation as an opportunity to discuss linguistic differences and expectations for the text, the NES students avoided giving feedback to their NNES peers and rewrote the text that was âso badâ:
This is gonna make us sound really bad. Sven was in our group and I wrote his section for him becauseâŠwe were like, âthis doesnât make sense, this doesnât fit in with the rest of the reportâ and I dictated it.
I ended up writing it, I think.
It was like, so bad, but we were getting really stressedâŠ. But we spoke about it without him and said, âweâre not letting Sven write this,â âcosâŠ
Well, no, âcos he couldnât, because it was our marks. (p. 888)
Although the students did not indicate what their precise textual concerns were, this example shows that the NES students made assumptions about Svenâs ability to accomplish the writing task based on their perceptions of his linguistic competency. When we look at the NES studentsâ reflections on the situation, we can see that they struggled with the decision to rewrite their peerâs text. The NES students reflected on the problematic nature of their actions and used face-saving disclaimers, such as âThis is gonna make us sound really bad,â and justifications, such as âwe were getting really stressed.â But their anxiety over how Svenâs text could have threatened their grades and success trumped their desire to maintain collaboration throughout the project.
The feedback avoidance exhibited by the NES students in Harrison and Peacockâs (2010) study reveals a troubling and unproductive approach that is echoed in other research as well. Specifically, when NES students avoid giving feedback and communicating with NNES peers, the latter can often respond in a reciprocally unproductive manner by withdrawing from group discussions and decision making (Aritz & Walker, 2009; Gluszek & Dovidio, 2010; Poznahovska, 2016). For example, in a pilot study conducted with 37 students at my institution, a NNES student described a situation in which her NES peers decided to exclude her from editing the group project. She found the decision âa little off-puttingâŠbecause [she] had worked on a lot of other projects like this beforeâ and believed herself to be âpretty good at those kinds of tasksâ (Poznahovska, 2016, p. 15). Despite not agreeing with this decision, the student acquiesced to their choice without bringing her concerns to her peersâ attention. She explained that on one hand, she did not want to âmake it a big deal,â but on the other hand, she also âdidnât know what to do about thatâ (p. 18). When students do not know how to address issues around language expectations, they risk creating unproductive team dynamics that can suppress conversation and deliberation and potentially lead to their resenting both the project and the collaborative process as a whole.
These studies suggest studentsâ overall dissatisfaction and anxiety about working with peers who are linguistically different and their unawareness of how to address these situations in a collaborative way. Such anxieties over feedback are not unique to students who cowrite. Factors such as deadlines (Ding & Ding, 2008; Yu, 2012) and cross-cultural differences (Bokor, 2011; Kupka et al., 2009) can decrease studentsâ confidence and put unproductive pressure on them to balance collaboration with the demands of an assignment. Research on teamwork has already made great strides in addressing obstacles related to feedback during collaborations, providing students with valuable practices such as forming task schedules and team charters in order to structure feedback and manage divergent expectations (Wolfe, 2010; Yu, 2012) as well as encouraging students to actively deliberate participation and performance standards (Earley & Gibson, 2002; Goby, 2007; Starke-Meyerring, 2005; Wolfe & Alexander, 2005).
While research on group anxiety and team planning has provided students with strategies for scaffolding feedback and deliberation, much of the research has overlooked the role that EP differences play within a cowriting context. Specifically, when EP differences arise on a team, anxieties concerning efficacy, performance, and time management can often be exacerbated, making this context especially interesting to study. In the following example from an interview for this study, one professional (NES) reflected on the anxieties and dilemmas she faced when deciding to offer feedback to a NNES peer during a graduate school team project: I donât know that I have the skills to teach a nonnative English speaker how to improve their writing. Nor was I sure that that wouldâve been great if I had done thatâŠwas that my role as a student? And would he even want me to do that? Or would he be offended and be annoyed that I was trying to do it? (Participant 15, NES)
The participantâs comment suggests her anxiety about providing feedback without having adequate experience and ethos.
Research has previously touched on this resistance to feedback, finding that in situations in which feedback is perceived as unsolicited âteaching,â students are less likely to offer commentary to one another (Wolfe & Alexander, 2005). Students in Wolfe and Alexanderâs study noted that teaching collaborators takes too much time and that it is intrusive and not collaborative; therefore, team projects should not be spaces for that kind of instructive work. Such a perception of feedback limits what students can do in the face of EP differences, often leaving them with counterproductive options, such as avoiding communication with peers and usurping texts they perceive to be troublesome. We can see this side effect with Participant 15 (NES), who ultimately rewrote her peerâs text with her other NES teammates, taking an approach similar to that of the students in Harrison and Peacockâs study.
Scholars interested in the role that language plays in writing have been more consistently investigating how writers navigate EP within different academic contexts (Allen & Katayama, 2016; Allen & Mills, 2016; Koerber & Graham, 2017; Storch, 2005). Unfortunately, other than Koerber and Grahamâs (2017) research on proficiency in scholarly writing, much of this research has been out of the purview of professional communication. Furthermore, while existing research has been helpful in raising questions about how EP affects managing the writing process, to my knowledge, it has not given students concrete strategies for how to address perceived proficiency differences within their teams. The goal of this study, therefore, is to explore possible strategies that students can use to help them manage the challenges related to cowriting across EPs.
Toward that end, I interviewed professionals who have experienced cowriting across different EPs in order to investigate their collaborative practices. Turning to professional collaborators for advice about how to help college students is useful for two main reasons: First, professional communication scholars have frequently examined and found insightful the rhetorical practices used by professionals (Koerber & Graham, 2017; Lunsford & Ede, 2011), and their rhetorical practices have often provided foundations for pedagogical research and practices that have benefited students within the classroom (Blakeslee, 2001; Quick, 2012). Second, by turning to professionals for advice, we can offer students solace in knowing that professionals too encounter similar challenges when cowriting across EP differences but that they have approaches for managing those obstacles. To better understand professionalsâ collaborative practices and begin thinking about pedagogical implementations, this study explores the following research questions: What strategies do professionals use when they cowrite across EP differences? In what ways might professionalsâ experiences inform how writing instructors teach collaborative writing to students?
Based on the data collected in this study, I suggest three strategies that students can use in the classroom: calibrate genre and reader expectations, establish protocols for reviewing texts, and frame feedback as a learning opportunity. These strategies might look familiar to scholars and teachers of teamwork and professional writing. Although this exploratory study does not reinvent the wheel, it does shed light on the significance of using already established strategies in the context of cowriting across EP differences. And its findings provide insight into pedagogical approaches that writing instructors can use to help students mitigate their anxieties and feel more empowered to engage with diverse peers.
Method
Using my universityâs alumni directory, I recruited 20 professionals (12 female, 8 male) via e-mail from technical industries, the arts, nonprofit organizations, and higher education. These participants were chosen based on their experience with cowriting documents across different EPs and then compensated with a US$20 Amazon gift card. All participants in the study reported having experienced cowriting across different EPs within the past year, with 90% of them having had at least 3 years of experience. 1
Although this study looks at perceptions of proficiency difference, both the participants and I use the terms NES and NNES throughout the interviews. In those instances, the terms do not quantify the level of proficiency but rather serve as background information about the participants and signal the context in which they learned the English language. Readers should be aware that my recruiting e-mail used the term ânative English speaker,â which might have prompted participants to think in terms of the NES/NNES dichotomy. But I began the interviews by speaking about proficiency, asking participants to reflect on their experiences with writing with âpeople of different linguistic proficienciesâ; I did not begin using the terms ânative English speakerâ and ânonnative English speakerâ until after the participants mentioned them first in the interviews. Almost all the participants identified themselves as either NES or NNES, with only one participantâParticipant 16âperceiving himself to be both. He explained that his native language was not English but that he now has native EP after years of studying and working in the United States. Throughout the remainder of this study, I refer to him as NNES to NES.
My data collection consisted of 20 experience-based interviews. I used a semistructured, open-ended approach for these interviews, which started by asking participants to recall and describe a recent collaborative situation in their lives: Iâd like you to remember a recent example or recent situation where you had to cowrite a document with someone who had a different language proficiency. And once you have one, Iâd like you to walk me through the situation in as much detail as possible.
After I established the topic, participants directed the conversation, elaborating on the specifics of their examples.
The 20 interviews generated 16 transcripts and 4 detailed sets of notes that I took during the interview. To analyze the interview data, I used grounded theory (Charmaz & Belgrave, 2012; Glaser & Strauss, 1967), identifying patterns and salient responses through careful, iterative study and comparison of the codes within the transcripts. To facilitate the grounded theory analysis within this study, I used the software MaxQDA (Version 2018.2) to create, assign, and organize codes within the data. To initially sort the data, I used descriptive starter codes (Miles, Huberman, & Saldaña, 2014). Then, I used open coding (Corbin & Strauss, 1990) to identify more specific situations, attitudes, and behaviors within participantsâ interview responses, recoding the data based on the open-coding system. Finally, using axial coding (Corbin & Strauss, 1990), I looked for codes that appeared together frequently, identifying trends, patterns, connections, and relationships between the open codes. I then clustered the open codes, labeled the clusters with a broader axial code, and gave these axial codes a specific definition. Once again, I recoded the entire data set with the additional axial codes to both check the viability of the codes and identify any inconsistencies within the coding.
In the following section, I discuss my findings according to the most prominent themes that emerged from the axial coding of the data.
Findings
The participants in this study stressed the importance of planning for cowriting with peers with different EPs. Specifically, these professionalsâ plans comprised not only temporal dimensions such as timelines but also analytical dimensions such as genre analysis and the negotiation of feedback norms. Their experiences suggest three specific strategies that cowriters can use to plan for productive collaboration: calibrate genre and reader expectations, establish protocols for reviewing texts, and frame feedback as a learning opportunity. During interviews, the professionals described employing the strategies to different degrees and often in combination with one another.
Calibrate Genre and Reader Expectations
All 20 participants came across situations in which they or their cowriters did not meet expectations for deliverables. Often, this situation stemmed from a writerâs lack of exposure to and awareness of the genres, norms, and expectations that the organization valued. As Participant 20 (NES) explained, expert writers took for granted the steps they went through to learn expectations and practices in their current professional environments, so when novice writers were asked to perform and meet expectations that had not been defined, they often missed the mark on the deliverable: But theyâve [novice writers] never seen one of that quality.âŠThey didnât realize that they were way underperforming.âŠAnd if you havenât seen really well-written things and now youâre asked to do it, and you, youâre getting compared to that level, itâs a really highâŠbar to all of a sudden jump to.âŠNow all of a sudden youâre required to just come to the table with that end result.
In such situations, Participant 20 (NES) explained, it is âunrealisticâ to expect writers to perform and deliver when the genre and reader expectations were not clearly articulated.
Of 20 participants, 17 actively worked to calibrate genre and reader expectations throughout the course of their projects. In doing so, they were able to establish consensus between cowriters as to the goals, genre expectations, and style of a given text and help those who were unfamiliar with meeting those expectations. Specifically, when calibrating expectations with their peers, writers shared institutional policies and models and project guidelines from supervisors and clients. By using such criteria that came from authoritative sources outside of the teamâsuch as the institution, supervisors, or clientsâwriters avoided giving feedback that ran the risk of coming across as a personal interpretation.
One of the approaches that participants used to communicate genre norms was to reference company guidelines and institutional policies. In her work as a communications specialist, Participant 5 (NES) explained that she would avoid drawing attention to her cowriterâs âcolorful languageâ that emerged from her âSpanishâ background. Instead, she would focus her feedback on institutional standards for language, formality, and style: âThese are the stylistic guidelines that we have, and this didnât meet the guidelines for whatever reason.â Itâs easier for me to focus on black and white issues we have written down to follow the process versus bring[ing] your personal situation into it.
As Participant 5 (NES) explained, instead of focusing on individual stylistic differences, âI try to keep that in mind that just because itâs not necessarily the way I would write it doesnât mean itâs wrong.â She found it more productive to provide feedback that she could map onto concrete institutional criteria and guidelines.
According to team-conflict scholars, conflict caused by personal preferences tends to be the most unproductive conflict on a team (De Dreu & Weingart, 2003; Rentsch & Zelno, 2003). But conflict concerning tasks can be fruitful and generative for group members as they learn from each other about deliverables and different approaches for their project (De Dreu & Weingart, 2003; Rentsch & Zelno, 2003; Wolfe, 2010). Participant 5 (NES) explained that she was cautious about critiquing her LP peer for her âSpanishâ style in order to avoid conflicts created by a âdifference of opinion.â Instead, Participant 5 (NES) centered her feedback on the companyâs institutional policies, thereby generating discussions about deliverables and creating a more collaborative atmosphere with her teammate of a different EP.
In addition to referencing company guidelines, participants considered the needs of authoritative audiences when writing and revising. Recognizing the high stakes associated with how supervisors and clients perceived the text, participants took steps to try to meet expectations and requirements ahead of time. In some cases, participants would conduct audience analyses to predict how a supervisor or client would respond to a text. These participants were then able to provide feedback to their cowriters that was grounded in audience expectations rather than in personal preferences: [T]hereâs a serious group of people whoâs going to review [the text]âŠI have to adhere to the standards of the legal and compliance group rather than just my personal preferences for the writing. (Participant 5, NES) Iâll list the reasons why I think this words which is written, why it is better to present it to the clients. (Participant 11, NNES) [Iâll say,] âHey, this is good but I could never present this to the management teamâŠbecause you know theyâre coming from this perspective.â (Participant 20, NES)
During feedback, participants also used models to visually represent company genres and expectations for texts. Participant 20 (NES) mentioned that in his collaborations with writers from all over the world, writing issues could stem from a lack of exposure or âtrainingâ in a particular text. Because âa lot of different cultures [train] and teach differently,â he explained, writing expectations and genres could vary between countries and organizations. He summed up his rationale for using models like this: And so sometimes it has nothing to do with whether theyâre capable of it. It has to do with what theyâre used to seeing. And so, if theyâve never seen a really good quality report of how it should be broken out and itâs format and template, itâs very unlikely that theyâll create that from the get-go.
Participant 20 (NES) also explained that in his experience as a manager, he not only gave writers feedback and opportunities to rewrite a text, he used âexamplesâ and âtemplate[s]â to help them gain exposure to unfamiliar genres and improve their writing process: So we try to [have] a combination of giving them a second chance, giving them feedback but also giving them examples like, âThis is a well-done one. Read that. Look even if itâs not completelyâitâs not a duplicate, right? Itâs just similarââŠso we try to show themâŠâHey this is a good example. Use this as a template. Use this as an example of what weâre looking for.â
As Participant 20 (NES) stressed, a model is not a âduplicate,â it does not dictate to writers what to do or how to do it. Rather, models serve as visual representations of writing goals, as feedback in the context of desired deliverables. The goal of using models, then, was to both help writers identify the problems they have in their own writing (Participant 1, NNES) and provide an approved document that could help writers become familiar with company expectations.
Establish Protocols for Reviewing Texts
Participants experienced problems caused by poor timing and lack of feedback protocols. Thirteen participants described situations in which they and their group did not have a clear idea of when and how to give feedback. Unclear timelines, steps, and norms for providing feedback often led to conflicts that impeded constructive review and revision. One result of not planning out feedback and protocols was that cowriters tended to rush through the review process and not have enough time to revise and learn from mistakes. Participant 12 (NES) described a situation in which he and his peers waited until the last minute to look at a cowriterâs draft: There were plenty of times where heâs asked for our review and for our help with parts of the white paper.âŠPersonally me, I havenât looked at the white paper until this meeting we had the other night. AndâŠitâs been in drafts for months, right? So there had been plenty of times for us to look at it and give him feedback. And there was basically, was no feedback until this one night where we all came together and were just tearing away at it.
Then when the team finally came together to review the text, Participant 12 (NES) explained, the reviewers were âbasically giving too much feedback and making direct edits of something [the writer has] been working really hard on.â Instead of deliberating about the content and next steps for the text, the reviewers resorted to making corrections and revisions for the writer: Us coming in and critiquing [his text] and then directly making edits and moving things around was frustrating for [the writer]. And we had lots of time before to probably notify him about any critiques and tell him what things could be improved. But, the fact that we were all there just cutting things and tearing away at the white paperâthat definitely caused some conflict.
The group did not discuss priorities for feedbackânor did they discuss preferences or best practices for how feedback should have been delivered. If the goal of cowriting is to engage with and learn from other writers, Participant 12âs (NES) situation shows how poor timing can undermine that goal.
Although cowriting across EP differences can offer many opportunities to share perspectives and learn from cowriters, participants explained that deadline-driven environments can stifle learning and encourage an unproductive âget it done mentalityâ (Participant 4, NES). But deadlines are a necessary and unavoidable aspect of the workplace; therefore, to account for deadlines and still create spaces for learning, 14 of 20 participants set up protocols for when and how feedback should be provided. In particular, the participants explained that establishing timelines for writing, reviewing, and revising with their peers was particularly useful for scaffolding productive collaboration while adhering to deadlines: [We held] the first meeting to talk about the project and a timeline and a schedule and the approval process for the policy.âŠThat gave [cowriters] the information they need to understand how the process was going to work in the writing. (Participant 9, NES) I work very purposefully to set up timelines for somebody else.âŠI can review [the document] and then also provide more constructive feedback in a way that can actually teach them. (Participant 4, NES) I would like a person who is less proficient to understand that getting the English correct is really a big undertaking and to allocate the time to do a good job and to work with the editor to go through multiple reviews. (Participant 2, NES)
Participantsâ experiences illustrate three significant benefits of discussing timelines for cowriting across EP differences. First, by scheduling multiple feedback points throughout a project, these professionals were able to check in with cowriters and address any concernsâboth proficiency and nonproficiency related. As Participant 14 (NNES) explained, when collaborators come from different linguistic backgrounds, the group needs to allocate time for potential issues to be identified and addressed. In addition, participants explained that scheduling review points prevented cowriters from rushing to give feedback at the very end of the project when high stakes could amplify stress and generate tension between cowriters. Second, professionals indicated that by planning for feedback, they were also able to accommodate revision time for the writer to ârespond to issuesâ (Participant 14, NNES). And third, deliberating about timelines provided opportunities for participants to identify and discuss other parts of the project and plan for resolving potential challenges (Participant 9, NES).
Besides discussing timing for feedback, participants also deliberated and agreed on how to give feedback during review points. Specifically, they commented on the importance of having a review protocol in place that would provide writers with criteria for what to focus their feedback on. For example, Participant 12 (NES) and his team decided on a protocol that ignored grammatical errors until cowriters wrote and agreed on the content. Similarly, Participant 20 (NES) explained that at his company, multiple writers reviewed a text based on their expertise. Writers with different EPs were all able to contribute to a text, but the team made sure to decide on a protocol for how content versus grammar would be reviewed and revised. This protocol was agreed on and tracked on a spreadsheet that documented decisions, roles, and progress concerning the text.
Research on team writing suggests that when writers have an opportunity to discuss and agree on writing goals, deliverables, and constraints ahead of time, they and their team are more prepared to manage challenges that could arise later on (Wolfe, 2010). In Participant 19âs (NNES) experience, having a â20 minutes conversationâ at the beginning of the project allowed him and his cowriters to agree on the review and revision process for the text. Any decisions that were made regarding the review process were actively documented, such as who writes the drafts, who reviews the texts, how feedback should be given, what feedback should focus on, where members can find feedback, and how comments should be addressedâa protocol similar to that described by Participant 20 (NES). By setting up a review process ahead of time, cowriters could get âan earlier warning about [peersâ] writingâ and address any discrepancies that might come up before unconstructive conflict ensues (Participant 18, NNES).
Participantsâ data suggest that establishing a review protocol that discusses how to deliver feedback sets expectations for feedback, thereby reducing the potential for unproductive conflict later on. Participant 11 (NNES) and his team seldom faced conflicts that were face threatening or unproductive, mainly because they all expected feedback to be provided and had a concrete protocol in place for delivering that feedback: Usually what weâre doing is just open up a Google Doc whereâŠyou can cowrite stuff online and then everyone adds edits to it.âŠWe read each otherâs documentation and put comments on top, on the side of it, as you do via Google Doc basically. And then you do some changes accordingly, and then you resolve the issue.
When cowriters did not agree on the process for delivering feedback, Participant 9 (NES) explained, âthen you get all kinds of stuff, and it just makes the process longer.â For example, feedback might be inconsistent, unclear, face threatening, or difficult to find. When issues arose around how feedback was delivered, collaborators risked delaying the review process and the project as a whole. To avoid that, Participant 9 (NES) commented, it was important to agree on âwhat your expected outcome isâ for feedback: Like saying, âWe want you to use track changes.ââŠâWe want to use the comments [feature],â saying these are the types of comments that are helpful, these types that arenât helpful and why.
Participant 9 (NES) explained that she tried to standardize the review process with her cowriters by discussing the types of comments that would be useful for the group and agreeing on the best strategies for delivering that feedback. Having a standardized delivery method allowed Participant 9 (NES) and her cowriters to compare feedback in order to see âwhat the general consensus was from everyone on that particular documentâ and identify âcontradictory comments.â
Meanwhile, for Participant 2 (NES), having a review protocol also reduced the possibility of peers assuming that their cowriters had a LP because of their accent or cultural background. In other words, textual issues were not always related to proficiency; in some cases, problems in a text were caused by other external pressures or conflicts. To avoid the possibility of a face-threatening situation, Participant 2 (NES) explained, she and her team instituted a âpeer editing protocolâ that involved a second reviewer: [I would say,] âYeah there are actually some issues here.â And they may not be because of proficiency in the language; they may be because of the quantity of information and the deadline pressure. So we often try to have a peer editing protocol where someone besides the information developer also has to take a second look at it.
Participant 2âs (NES) experience, then, illustrates not only the value of a review protocol when managing high workload and deadlines but also the importance of layering and sharing feedback responsibility within a text. In writing across EP differences, a review protocol that calls on multiple reviewers can help avoid making faulty assumptions about peersâ competencies and writing abilities.
Frame Feedback as a Learning Opportunity
The third salient issue that participants experienced was trying to give feedback in a way that was not face threatening to the recipient. Face, or âthe public self-imageâ that collaborators want to claim for themselves, is bound up in the ways that feedback is given and perceived (Brown & Levinson, 1987, p. 62). If feedback either is too critical, undermines the writerâs expertise, or embarrasses the writer, it risks creating a face-threatening situation for both the writer and the reviewer in which conflicts might arise and collaborators might become defensive and closed off. Fourteen participants described situations in which they wished to provide feedback but were hesitant to do so because they feared overstepping hierarchical boundaries, coming across as âcorrectingâ a colleague, or damaging a colleagueâs self-efficacy (Participant 16, NNES to NES; Participant 4, NES).
Participant 20 (NES) explained that when writers received critiques on their text, they often responded in one of the three ways: They perceived the feedback as a âmajor offenseâ and refused to write in the future, they lost confidence in their writing abilities and refrained from taking risks in their writing, or they accepted the feedback willingly and used it to improve their writing. Although Participant 20 (NES) attributed feedback avoidance to the recipients themselvesâthey were not open to improvement, so they were ânot with us anymoreââhis experience showed that the type of feedback also played a role in writersâ responses. Feedback that challenges a writerâs expertise and character (e.g., when reviewers say they âdidnât like itâ or doubt a writerâs competence) can create a face-threatening situation. This type of feedback stifles improvement and progress because it targets a writerâs personal qualities rather than concrete textual issues.
Participants also brought up the role that power dynamics play during feedback. Power, or âthe vertical disparity between the participants in a hierarchical structure,â is intricately negotiated both between subordinates and superiors and between peers (Scollon, Scollon, & Jones, 2011, p. 52). Scollon, Scollon, and Jones explained this intricate negotiation of face in terms of marked or unmarked interactions. When feedback maintains the usual relationship and power dynamics, the interaction goes unmarked. In other words, the status quo is maintained between participants. When feedback becomes a challenge to power and relationship dynamics, the interaction becomes marked, or noticed. Status quo is no longer maintained, and participants might lose face in front of each other. Participant 20âs (NES) concerns about offending cowriters illustrate how power is bound up in the act of giving feedback. The challenge in these writing situations, therefore, is finding a way to present feedback that encourages cowriters to improve their writing rather than create a marked situation between participants that leads to personal conflict.
To reduce the possibility of feedback damaging a writerâs self-efficacy, 13 participants stressed the importance of maintaining a writerâs decision-making power over a text and presenting feedback as a learning opportunity. Participants explained that they would present feedback as suggestions and make sure that the writer was involved in the decision to change or omit parts of a text. For example, despite perceiving her cowriter as having a LP, Participant 7 (NES) was careful to not challenge her peerâs expertise by rewriting the text for him or even by giving unsolicited feedback. She instead created a space for dialogue and an opportunity for learning by offering to provide feedback and revisions: So in the case where I had, you know, peers [who] had written a section that I felt was unclear, then I would maybe just talk with them about it, to say, âWould you like me to help you revise that work?â or âCan I make some editing suggestions?â Because I feel that the bottom line is thatâŠeven the poorest English speaker still has a very solid grasp of whatever the technical concepts are, and whether youâre a writer or an editor, itâs critically important to not interfere with that, right?
Participants collaborated with a range of writers, such as supervisors, peers, and subordinates, but regardless of their cowritersâ hierarchical status, participants used similar approaches toward working together to improve texts. Participants would try to either âreconnect with that person after there have been significant changesâ (Participant 5, NES), or they would âleave comments on the sideâ (Participant 12, NES) that were suggestive: Instead of direct edits, we would rephrase our critiques and we would say things like, âWell, this section, I think you might want to use this word instead. And hereâs a sentence that might work. And I think you might need to be more clear in these parts.â So they were more constructive criticisms that were made as suggestions. So we werenât editing the paper anymore. (Participant 12, NES)
Similarly, Participant 8 (NNES) explained that his cowriter called him to offer recommendations and discuss his writing in order to maintain Participant 8âs (NNES) contribution to the text. He said, âThese are the recommendations that I have for your document. And I want to make sure that I preserve the spirit of what you wanted to write, so Iâm calling you to do this.â
The collaboratorâs approach to providing feedback, then, was to contact Participant 8 (NNES) in order to emphasize that he wanted to âpreserve the spiritâ of Participant 8âs ideas. Participant 8 (NNES) explained that he recognized the issues in his own text and knew that he needed to improve his writing. At the same time, he appreciated that his peer took the time to offer feedback and then gave him the opportunity to revise the text: âHe showed me [how to write] a better document for my project and also helped me to grow as a person. So I think it was great.â In this situation, the cowriters worked together to improve the document; the collaborator offered feedback, and Participant 8 (NNES) ultimately retained ownership of his ideas by revising the text. The goals became less about fixing a text or a writerâs language than about collaborating with one another to improve the project as a whole.
Discussion
The purpose of this study is primarily pedagogicalâto identify team strategies that students can use when cowriting across EP differences. Previous research has called for more exploration into collaborations across proficiency differences, but little work has been done in this area. In conducting this research, I identified three specific strategies that professionals used that can benefit students when they cowrite across EP differences: calibrate genre and reader expectations, establish protocols for reviewing texts, and frame feedback as a learning opportunity. By using the three strategies, professionals created avenues for feedback and discussion, thereby scaffolding productive conflict and collaboration with peers who have different EPs.
The findings suggest that calibrating genre and reader expectations is important throughout a project. By reviewing institutional policies, reader perspectives, and models, writers can set expectations for deliverables and provide each other with frameworks for proceeding on a text. These expectations are often recalibrated as the project proceeds and goals shift; hence, part of the success of calibration is also recalibration. That is, calibration is an iterative process; as writers progress on a project, different expectations might surface (Wolfe, 2010). Peers, therefore, need to check in with each other throughout the process. If they rely on a single calibration at the beginning of a project, they risk divergences that delay progress later on.
Establishing protocols for reviewing texts offers several benefits to cowriters, especially when there is the potential of face-threatening situations during feedback. Having an explicit protocol for review and revision processes means that cowriters know their role within a text but also can expect to receive feedback from other contributors. When review protocols are outlined and agreed upon, feedback becomes an expected part of the cowriting culture and is less face threatening because the team focuses on following protocols rather than critiquing individual writers. Because the writers have established that feedback and revision are part of the writing process, they anticipate being critiqued and are less likely to feel that it is a personal offense to their expertise or abilities. As Wolfe (2010) explained, âscheduling revision and feedback into the task schedule creates a team culture in which constructive feedback is simply part of what gets the project done and is not a negative reflection of anybodyâs workâ (p. 60).
The professionals in this study stressed that in order to reap the benefits of collaborating across EPs, cowriters needed to encourage a broader culture of ongoing learning within the workplace. Specifically, the interview findings suggest that when professionals and their peers framed feedback as a learning opportunity that is part of the cowriting process, they were more receptive to the feedback and engaged in dialogue about their writing. We see this echoed in research on college writing that suggests that students who cling to the writing habits and attitudes about their writing abilities that they had in high school tended to experience a more difficult time adapting to the new academic environment. Meanwhile, students who willingly accepted a ânovice statusâ in college opened themselves up to new learning opportunities, experimentation, feedback, and guidance that helped them improve as writers throughout their education (Sommers & Saltz, 2004). Such research and my findings, then, suggest that students should embrace a mind-set of career-long learning; the professionals I interviewed who took on such a mind-set perceived themselves as more adaptable to different writing environments, genre expectations, and linguistic standards.
Taking a grounded theory approach to the interview allows us to get a firsthand interpretation of professionalsâ experiences when cowriting across EP differences. Professionals reflected on their collaborative practices, differentiating between what they perceived to be productive versus unproductive responses. Furthermore, by using grounded theory in this study, I could track professionalsâ decisions and behaviors across a variety of disciplines, experience levels, cultural backgrounds, workplace environments, and genders, finding that these strategies are useful in a variety of contexts and collaborative situations. In taking this approach, then, we might also consider how other differences, in addition to language proficiency, play a role in fostering productive conflict. If professionals are able to negotiate EP in productive ways, then perhaps other differences can also be negotiated and deliberated in ways that foster productive collaboration.
This research also suggests an alternative framework for how team planning should be taught in the classroom and the role that planning plays during cowriting. On one hand, the study reaffirms the importance of team planning as it relates to setting deadlines, scheduling meetings, and making time for feedback and revision. On the other hand, this study asks teachers and students to further their perception of planning beyond its temporal forms and to consider its significance as an analytical process. Even though these professionals explained that time management was important for the success of their teams, much of the planning that they discussed emphasized conversations around genre and expectationsâexpectations for deliverables, feedback processes, and communication between team members as well as audience expectations. Such analytic and dialogic approaches to planning thus focus on using genre analysis and team deliberations to identify differences in proficiency, genre awareness, and feedback styles and then plan how to manage them in the future.
In many ways, this research extends the impact of genre analysis beyond writing collaboration at large. In addition to thinking of genre analysis as a scaffolding tool for texts, we might consider the role it plays in planning future relationships between collaborators. In deliberating project deliverables and feedback expectations, cowriters engage in productive conflict. When writers establish a set of explicit norms, cowriters create a plan for how texts will be written, reviewed, and revised, thereby minimizing surprises and unproductive conflict that might occur later.
Although this research initially began as a search for new strategies that applied to collaborations across EP differences, the findings point to the importance of planning regardless of team composition. Teamwork researchers have long argued that collaboration does not happen without intervention; it needs to be planned. But students often complain that planning takes too long and is a waste of precious time during a project. To reframe studentsâ perception of planning and increase their acceptance of genre analysis, this research provides valuable evidence of professionals using and benefiting from planning within real-world collaborations. By describing the experiences of the professional collaborators in this research, then, I hope to convince students that, regardless of team composition, the process of planning scaffolds productive experiences while accounting for and managing unproductive ones. And I hope that by teaching this planning process, writing instructors can help students anticipate and mitigate some of the anxieties they might feel about collaboration.
Suggestions for Classroom Implementation
As instructors, we might begin thinking about how these strategies could manifest themselves in the classroom and the ways that we can translate these practices for studentsâ use. To help teachers prepare students for collaborative writing situations, the following recommendations outline some possible approaches for using this research in the classroom:
Use Professionalsâ Experiences as Evidence for the Importance of Planning
One way that these strategies can be taught is by showing students quotations from my interviews with the professional collaborators. These professionals discussed the different challenges they encountered during workplace collaborations and explained how they used planning and negotiation strategies to facilitate productive cowriting and prevent unproductive conflicts. Their real-world experiences illustrate the types of situations that students can expect to encounter once they reach the workplace.
Use Team Charters to Facilitate Planning
Another way that these strategies can be taught is through direct application by way of a team charterâa contract that outlines the norms and expectations for a project and the team members. A team charter also serves as an opportunity for collaborators to identify and resolve any differences before the project begins (Wolfe, 2010). When used in the classroom, the team charter acts as a space for productive conflict and deliberation as students bring in different perspectives and agree on the best approaches. A team charter, then, provides a document around which planning can occur, specifically the type of planning that requires deliberating project goals and expectations, discussing feedback processes and priorities, and articulating approaches for resolving conflicts in a polite and productive way. The potential benefit of these strategies is their application to a wide variety of teams, including but not limited to teams made up of writers with linguistic, cultural, experiential, and disciplinary differences.
Limitations and Future Research
Although this research offers rich insight into the planning strategies used within collaborative writing, future research needs to investigate how and if professionals use these strategies in practice. The interview methods I used in this study offered rich interpretive data that stemmed from participantsâ reflections and memories of their experiences. But such an approach for gathering data falls short of illustrating the dialogic aspects of how participants negotiate texts with their cowriters in situ. Because of the reflective nature of interviews, this approach does not let us see how the strategies are enacted in the moment with other collaborators or how other collaborators react to the use of these strategies. To better understand the contexts in which these strategies are practiced and the implications of their use, more research needs to be conducted on the in situ practices of cowriting across EP differences.
More research is also needed on the classroom use of these strategies. Before we can argue for the effectiveness of these strategies within the classroom, we need to better understand how to best translate these workplace practices into the classroom. The transition from the workplace to the classroom is not seamless; the differences in stakes, goals, levels of expertise, and collaborative experience vary between professionals and students. Therefore, if students are to reap the benefits of these strategies and use them to engage in productive conflict, more research is needed on how to encourage studentsâ use of the strategies, on how students respond to and apply these strategies in their own collaborations, and on the extent to which these strategies manage the unproductive challenges that students typically experience.
Footnotes
Acknowledgments
I would like to thank all of the professionals who graciously shared their time and experiences. I also thank the reviewers who offered valuable feedback on this article as well as faculty, colleagues, and family who have offered their support and feedback on this project.
Declaration of Conflicting Interests
The author declared no potential conflicts of interest with respect to the research, authorship, and/or publication of this article.
Funding
The author disclosed receipt of the following financial support for the research, authorship, and/or publication of this article: This research was funded by the Association of Teachers of Technical Writing 2018 Graduate Research Award.
