12
TRUST AS AN ARTIFACT OF KNOWLEDGE SHARING

12.1 THE IMPORTANCE OF TRUST

The importance of trust in knowledge sharing (KS) and its status as the lubricant of an organization’s operations are two good reasons to justify trust as a phenomenon of interest. Without trust, organizations would simply not be able to function. We can all easily imagine the chaos that would ensue if everyone in work suddenly decided that no one and no thing could be trusted. Fortunately, we are not only a highly collaborative species, an essential ingredient to human progress and development as Thomas Suddendorf notes, but we are also quite trusting.

Yet ironically and as has been seen time after time with other phenomena of interest, the definition of trust is a troubling concern. The scholar Jonathan Clifton is one of the few in the discourse world who has investigated “trust” in the workplace: pointing to the substantial body of conventional research on trust in organizational settings, much of which wrestles with the question of definition, he argues that it is futile to attempt to pin words onto what is essentially a human accomplishment in social interaction. According to this interpretation, trust takes its meaning from the context in which it is embedded or locally situated. Recall F. David Schoorman and colleagues’ model that locates trust in relationships as a measure of willingness to be vulnerable, defining trust as acceptable risk contingent on perception of ability, integrity, and benevolence. In this model, trust is consequently approached as an aspect of relationship and as a function of perception.

Further evidence of the phenomenon’s importance comes from a recently published empirical study of trust in organizational KS by Max Evans. As a starting point, Evans indicates the conditions necessary for effective KS as being a willingness to share, willingness to use, and perceived receipt of useful knowledge: KS, from this perspective, occupies highly complex social interactions and relationships. His study reports trust, shared language, and vision as the most important influencing factors in a willingness to share knowledge. Trust, he concludes, is particularly identified as a prerequisite for KS, which is fairly consistent with much of the rest of the knowledge management (KM) literature on the subject (see Chapter 3). From the discursive psychology (DP) perspective, “shared language and vision” can be readily mapped to shared understanding of context operating at the tacit level.

It is speculated that analysis of the data will show trust and related themes in action, providing the opportunity to explore how trust is made live in discourse, and with what effect, relevant to KS activities.

The data analyzed here comes from a recording of a meeting in which the activity of KS is understood as implicit. This is not a meeting in which one person deals out tasks and action: instead, it is regular event with team members coming together to share knowledge of actions and activities of mutual interest and concern. It is anticipated, then, that analysis of the data will display trust and its related themes in the interaction, providing the opportunity to explore how trust is made live in discourse and with what effect relevant to KS activities.

How do people “do trust”? If KS is concerned with producing accounts and descriptions, versions of affairs, with the aim of sharing this with others (“a willingness to share”), then it is a commonsense understanding to link trust to “factual accounting.” That is, people routinely serve up their accounts or reports as factual, authentic, and free of personal stake and interest, hence objective and trustworthy. For instance, Jonathan Clifton’s research shows how speakers invoke actions of “epistemic primacy” (the “I know more than you do” strategy: note that the word “superiority” is subsequently frequently used in place of “primacy” as the former is considered to more commonsensically indicative of the meaning applied here). This can be seen as a kind of action in which actors display the possession of access to unique and preferential knowledge. In scripting factual accounts, speakers orient to the trustworthiness both of account and of self, arguably contingent one to the other. In the terms of the research discussed earlier, in accepting and agreeing with versions produced by others (“a willingness to use and perceived usefulness of shared knowledge”), speakers index others’ trustworthiness—that is, a willingness to be vulnerable to others, as a measure of others’ ability, integrity, and benevolence. This consequently sets the directions of the present discussions, and, as the analysis shows, the business of factual accounting, epistemic superiority, and displays of access to privileged knowledge are routinely used. Moreover, these actions are seen as the foundation on which competing accounts are shown to be constructed.

Speakers Orient

The term “orient” or “orienting” is commonly used in discourse analysis to refer to that which speakers make relevant in their talk, whether consciously or unconsciously. Think of it like “notice” or “understand.” When I orient to something (object, subject, action, emotion, whatever), I am making this a live concern of my talk.

Speakers Index

Utterances are said to be “indexical” in that the meaning depends on the context of its use. For instance, a speaker might be said to be “indexing” to skepticism if the tone of their utterance emphasizes a downward movement suggesting a dismissing action. In the wider understanding, indexicality refers to speakers’ displays of their understanding of the meaning of other speakers’ utterances.

Turn-by-Turn Interaction

Typical conversation or meeting talk is structured according to “turns”: a turn is the conversational “slot” that each speaker fills with their utterance, with the turn structure implicitly understood by speakers according to the circumstances of the discourse interaction. In normal conversation, one speaker takes a turn, which is completed before the next speaker takes a turn. In meetings, speakers’ turns may be controlled by the meeting chairperson. The way that speakers construct and tacitly understand the turn structure of a discursive action is of particular interest to conversation analysts.

Relationally Situated

Something is relationally situated when its location (in time, context, spatial reference, etc.) works in relation with other features of talk.

We start with a brief discussion of the data and its context that forms the topic of analysis. This is followed by the analysis and discussion that shows trust to be a multidimensioned phenomenon, constructed in the turn-by-turn interaction of discourse, and as a relationally situated underpinning construct to KS. In this and all of the following analytic chapters, references are shown as embedded within the text to underline how the analysis and discussions are grounded in relevant research. The chapter concludes with some preliminary reflections. The findings are further discussed in Chapter 17, combined with those from subsequent analytic chapters.

12.2 DATA

The data under analysis comes from a Company B meeting recording. This is a regular team meeting, involving five participants, all male. Two are located in a meeting room in Company B’s London offices, with the others joining in via conference call. It is assumed that the virtual attendees cannot see the others, and vice versa, for the simple reason that there is no suggestion of such visual availability.

The context of the meeting is a weekly exchange of team activities, responsibilities, future actions, and issues arising. The subject is the development of data handling services (software application) for discrete units of a major public sector organization. There is a further meeting immediately following this one that some of these actors will also attend. It becomes clear that this second meeting has the business of decision-making and is the source of some tension. This largely emanates from “Steve” who mandates a speedy pace for the present meeting from the outset. There is also the almost continuous sound of fast, often furious, typing that can only emanate from the meeting room in London.

Patterned Sequential Organization

Episodes of discourse—whether ordinary conversation, meeting, or whatever—generally display a pattern of sequential organization—that is, the way that the speakers progress their turns one after the other, which establishes an implicitly understood set of speaker rules governing how, when, and what speakers should contribute. A simple example would be how a speaker’s question generally sets up an anticipation and expectation of another’s answer, so the structure and expected interaction is “question–answer.

While a substantial part of the meeting follows the patterned sequential organization of “topic announcement,” “participant report,” and “team leader evaluation,” its choreography is marked by regular disagreements—competing accounts of affairs. There are six extracts presented here, five of which orient variously to challenge and persuasion, rivalry centered on competence, attribution, and claims to superior knowledge, all of which are shown to have implications for trust. This, in itself, is not an unusual feature of everyday talk: as Robin Wooffitt, a sociologist at the UK’s University of York, explains in his book comparing conversation and discourse analysis (incidentally, essential reading for those interested), people routinely argue and disagree. He also makes the commonsense observation that disputes cannot be resolved by referring to the “facts of the matter” as it is precisely the facts that are usually in dispute. The first extract serves to set the scene, with participants orienting to their status in the context of the meeting, and a very particular imperative—the need for speed. Each extract is presented in the order in which it appears to illustrate the sequential unfolding of themes, challenges, and respective understanding of context that participants make live in their discourse in interaction.

12.3 CASTING THE CHARACTERS AND SETTING THE SCENE FOR ACTION

The meeting is initiated when the three remote actors dial in to the meeting using conference call technology. Extract 1 shows what happens.

Lines 1–9 script what would be colloquially known as the meeting “pecking order” while at the same time invoking the need for speed, setting direction, and the business at hand. Steve clearly orients to “doing leadership” in his rights to summon participants to the meeting confirmed with a roll call (Line 1) and in invoking his rights to be the first to formulate an assessment (“first turn assessment”; Clifton, 2012b: Line 4). The meeting callers are reflexively constructed as the “summoned,” therefore subject to command. Steve further works up his identity as leader through claiming rights to make decisions (Line 8) and to establish the pace of the meeting in his reformulation of Bob’s proposal (Line 7) with a sanction to “wheel us through the list.” This can be heard as a sense of time pressure with the need for speed, which Bob indexes with his “Alrighty …” (Line 9). Bob’s implied possession of the “list,” coupled with his claimed ability to suggest actions, casts him in a secondary role to Steve’s leader status.

Notice the 2 second delay in the three virtual attendees responding to Steve’s statement of who “we have” (Line 2): in a face-to-face meeting, such a delay would be understood to suggest troubles in interaction (Drew, 2003b), but as Steve does not orient to this understanding in his assessment (Line 4), it cannot here be analyzed as such. It could simply just be a case of the nature of “virtual meetings” being more tolerant of such delays.

First Turn Assessments

In his discursive study of leadership, published in 2012, Jonathan Clifton argues that when a speaker claims the first turn in an assessment sequence, that is a sequence designed to provide an assessment or evaluation of what another speaker has just said, for instance, this works on the level of a claim to overriding rights to set and manage the meaning of the discussion as a whole. This, he suggests, is a rhetorical hallmark of leadership.

Reflexively Constructed

When a rhetorical action by an actor has the function and consequence of scripting something or someone as its opposite. For instance, Abigail Locke and Derek Edward, in their fascinating analysis of former US President Clinton’s Grand Jury testimony, show how “(I)in portraying [Monica] Lewinksy as irrational, emotional and motivated by personal problems, Clinton reflexively defines himself , in contrast, as rational , behaving properly…” (2003 : 249).

Steve hesitates over what topic to start with—the extended “ummm,” brief pause, and carefully spoken “Right” invokes a display of searching (Potter, 1998a) among competing topics (Lines 4–6). Bob steps in with a tentatively spoken suggestion formulated as a question with a candidate answer (Potter and Edwards, 2012), orienting to Steve’s control of the “agenda” as leader. Steve’s stretched affirmative (“Ye:: ah”) indexes the candidate answer but scripts reluctance—going through the list would not have been his preferred course of action. Subsequent analysis shows how this actor frequently uses the stretched “ye:: ah” to signal difficulty, disagreement, or reluctance. Instead of producing an alternative course of action, he reformulates Bob’s suggestion, and the “list” becomes topicalized as the first business of the meeting, albeit one to be dispensed with at speed, with its imperative for participants to share knowledge.

Questions with Candidate Answers

When formulating a question, speakers will routinely include a possible answer embedded within the question. Thus, speakers offer a “candidate answer” to cospeakers on the expectation that this will be adopted and issued by the next speaker, in which turns-in-interaction have the effect of scripting consensus and collaboration.

The sense of speed invoked in this extract arguably has an interesting effect on subsequent transactions. In three of the following extracts (2, 3, and 4), the action of argument—competing accounts—is shown to be triggered at the point at which Bob, as the possessor of the list to be “wheeled through,” is attempting to effect topic closure and transition to a new topic. Also, Extract 3 contains a call for a “bigger discussion” on a particular topic. All of this suggests that the imperative for speed is not only creating a tension, but is also being resisted. The normative and appropriate place for topic discussion and comment would be between topic opener and closer. Thus, the action of initiating further discussion on a topic during or after the issuing for its closure indicates troubles, suggestive of dissatisfaction with time allocated to topic discussion, with its inference of a potential for decisions based on less than adequate discussion or debate. There is, in fact, only one instance of argumentative actions taking place within the appropriate topic discussion space, and that is initiated by Steve himself.

A final point to raise is the team’s mutual familiarity: roles are not explicitly established as they are already tacitly known. Thus, the mutual roles are cast and shown to be tacitly understood, the objective of the interaction is made live, and the team’s familiarity with one another made contingent.

12.4 WORKING UP TRUST THROUGH EPISTEMIC SUPERIORITY AND AUTHENTICITY

12.4.1 Emerging Challenge

The next extract comes less than three minutes into the meeting and displays the first evidence of emerging challenge in the form of competing accounts offered, respectively, by Steve and Ade. The latter, in his role as “commanded,” has a normatively understood imperative to couch his account in the actions of persuasion, trustworthiness, and so forth. Steve, on the other hand, as leader, has no such imperative: he has the rights to make decisions on behalf of team members without recourse to any form of warranting. Nonetheless, he is shown to accomplish many of the same actions in his account, making “team buy-in” to his version live and accountable. The difference between the two is that while Ade’s competing account reflexively conjures Steve’s as untrustworthy (in contrast to his own), Steve effectively wins the argument by simply reformulating the issue and removing it from the team’s control, which actions are made possible by his access to privileged knowledge. That is, he is able to resolve the disagreement without disputing Ade’s version of “the facts,” allowing the trajectory of the meeting to move on. Trust, then, comes to the fore. This is how the action plays out.

This action involves three actors, Steve, Ade, and Bob. In Lines 43–45, Bob works to close down a list item with a two-part action: he serves up the classic topic boundary marker, “Ok” (Svennevig, 2012b ), combined with a projected future action (“… leave it on the list just to keep ↓chasing …”: Line 43). These collectively work up a topic closing component (Drew and Holt, 1988). But, rather than producing a new topic, Bob issues a topic extension with an assessment component (“but it’s good to know”: Line 44) combined with a knowledge component (“y’know”). The latter is typically used to project assumptions of shared knowledge and intersubjective agreement (Clifton, 2012a). Specifically, here, he is orienting to Ade’s account in the previous turn. This is the first occasion that Bob has offered an evaluative assessment, not formulated as a question directed to Steve. In interrupting Bob (Line 46), Steve effectively deletes any warrant that Bob might have to make evaluations, with the implication that only he has the entitlement to perform such actions. What happens next is a seesaw of competing assessment, with issues of trust being made live and under threat.

Topic Boundary Marker

These are devices that are particularly noticeable in agenda-driven meetings where a participant might use the term “okay” to display closure of one topic, leaving the field open for another to be initiated. Jan Svennevig of the University of Oslo, Norway, has published some interesting work that investigates this action in workplace meetings.

Contrast Devices/Markers

These are rhetorical devices—phrases or single words—which have the effect of marking a contrast between two or more different accounts or descriptions. So, for instance, “I could go to work on Monday but I would rather not.” According to analysis by Ann Widdicombe and her colleague, such devices are usually associated with and used in talk designed to persuade.

Preferred Turns

An account that starts with a weak agreement with the previous speaker, followed by an account that works at variance to this, thus constituting the speaker’s preferred state of affairs.

Footing

Someone is said to shift footing when they change from one stance, perspective, identity, or position to another. Examples include changing from talking about “I” to talking about “we.” For instance, Jackie Abell and her colleague explore how Princess Diana linguistically shifts position from that of her “royal role” to that of her role as a private individual, and with what consequences.

On the surface, the disagreement in Lines 46–57 is over nothing if Steve’s account that “…we’re gonna be getting out of …” (Line 56) is accepted, so why argue? To draw on Clifton’s (2012a ) analysis of trust in workplace interaction, this is about jockeying for position, through making claims to rights to knowledge. But these can only be considered as a form of “trust work” where recipients orient to the knowledge claims as such.

12.4.2 Competing Strategies for Conjuring Trust

There are two clear stages—and two different strategies—to the unfolding disagreement. In the first part, Steve receipts Bob’s assessment with a weak agreement and then replaces it with his own assessment (Line 46). Such turns are known as “preferred turns” (Edwards and Potter, 1992). The signal for an alternative version on the way is given by the repair (“I would” is replaced with “I do”), which is hearable as a contrast device. Such devices, usually taking the form of “but” or “that said,” for instance, mark the end of any concessionary material and the start of a competing assessment. According to Widdicombe and Wooffitt (1990), these devices are associated with persuasion talk: in this instance, it formulates the action of “I hear what you’re saying but ….” So while he does the business of accomplishing a correcting account of affairs to that proposed by Bob, he reduces the strength of the correction, thus invoking his sensitivity to the potential for sounding rude or unreasonably argumentative (Wooffitt, 2005).

Notice how Steve serves up his version of future events formulated first as what he would like to see and then deftly shifts footing (Abell and Stokoe, 2001) from first person to group collective (“… we don’t have much choice”: Line 47). This has the effect of projecting a mutually shared team status in respect of desktops: in other words, he scripts team consensus. Consensualism is shown to work up stake inoculation, against, for instance, criticism for having personal interest in one’s account, and in factualizing accounts (Edwards and Potter, 1992). Thus, it is not just a case of what Steve wants: he projects what he wants onto being what the team wants, and in this respect, they are collectively thwarted by external factors. This is “persuasion talk,” designed to elicit trust in Steve’s version of affairs on the part of hearers, and this is precisely what Ade orients to with his minimal agreement token (Edwards and Potter: Line 48). Perhaps indexing to the insufficiency of Ade’s assent, Steve plows on with his version (Line 49).

The second part to the unfolding disagreement talk occurs in Lines 50–58 and is initiated by Ade’s interruption that talks over Steve’s continued account of affairs as being inclusively imperative (“we do need to keep”: Line 49). Ade’s self-selected floor grab comes with a strong orientation to professional care and responsibility, in which he displays a different rhetorical strategy in constructing his version as trustworthy. He conjures the cognitive state of “being worried” but which is downgraded (“… a bit … the only part …”: Line 50), a practice that Jonathan Potter and his colleague (2003) describe as an activity of disclaiming responsibility. Thus, it is not Ade’s fault that he is worried, but rather the consequence of an external state of affairs. In Line 51, he invokes collaboration and consensus in scripting an inclusion pronoun (Abell and Stokoe, 2001) twice (“we go” and “we used”), which shifts the onus for worry onto the team as a whole: they should all be worried. This is followed by an explicit warrant for worry, framed as a conditional proposition (“if … then”: Chilton, 2004). In scripting himself as possessing knowledge about cause and effect, he serves a warrant for the authenticity of his claims (factual accounting), reflexively scripting Steve’s version as unacceptable–untrustworthy.

Conditional Propositions

These devices, typically structured as “If X, then Y,” are often used by politicians, according to professor of linguistics Paul Chilton, to make claims to possessing knowledge about cause and effect. Events thus described are displayed as having particular consequences. These can also be seen as a form of factual accounting, based on their conditional predictive attributes.

Empiricist Accounting

This type of accounting is particularly associated with talk that has the design of serving up facts. The term was arguably first used in sociology by Gilbert and Mulkay in their study of the discourse of scientists (e.g., 1984), although they refer to “empiricist repertoires.” Derek Edwards and his colleague argue that such accounts have the action of removing the speaker from responsibility for the facts, framing facts as independent from the speaker and as available “out there” as objective phenomena.

Ade completes his turn with an assessment (“not good”) in the form of an “unhedged” declarative assertion that works to frame accounts as uncontestably in stone (Clifton, 2012a ), which is linked to a projection of future action in what “we might as well” do. “Might” is interesting here because it would usually be associated with scripting a “hedge” or mitigation against criticism in its acknowledgement of the possibility of other candidate actions. However, here, it works up the commonsense nature of what might be done, conjuring a sense of tacitly known background knowledge (Clifton, 2006). Consequently, Ade’s description of affairs is displayed as emanating from concrete facts, with the future course of action cast as a reasonable one that the team would agree to, which reflexively further implicates Steve’s version as having untrustworthy status. Thus, Ade’s is designed to be an acceptable account, based on superior knowledge, orienting to status as trustworthy, and hard to challenge. There is also the suggestion of an invocation of risk—Ade clearly conjures Steve’s version as being risky (“not good”) and with the potential to lead to poor outcomes for the team. Thus, Ade can be said to have scripted himself as unwilling to be vulnerable (Schoorman, Mayer, and Davis, 2007).

12.4.3 Avoiding Direct Challenge by Reformulating the Problem

According to authors Wood and Kroger (2000 ), prefacing an account with “Yeah, well,” as Steve does in Line 53, works as a weak token of agreement, which is a classic signal of forthcoming disagreement (Clifton, 2012a). However, Steve does not directly disagree with Ade’s account. Rather he discards it with empiricist accounting (Edwards and Potter, 1992), accomplishing a neat reformulation of the issue: the future predicted conversation is concretized temporally and will “prove” Steve’s reformulation of affairs. In other words, he retains the topic problem (Chilton, 2004) but reforms it in the light of his claims to privileged access to knowledge (Willig, 2003), thus avoiding a direct challenge to the authenticity of Ade’s account. Ade’s version is shown to be consigned to history, as irrelevant to the here, now, and future. Note how he also works to downgrade (Locke and Edwards, 2003) the problem (“…only an intermediate…”: Line 54).

Thus, Steve predicts a new set of affairs, which are beyond the decision-making powers of the team, which is carefully hedged as having conditional status (Wooffitt and Allistone, 2008). In this way, he works to downgrade the status of the problem raised by Ade and to diffuse the potential for further dispute.

A three-part turn sequence completes the interaction. Bob’s aligning report that there are “things we may not” (Line 55) is interesting in what it does. Firstly, it can be heard as orienting to knowledge (“things”) out there, which is beyond the reach of the team, but, secondly and crucially, it is argued here that Bob, in conjuring the team consensus, is orienting directly to the three virtual attendees. There is also a suggestion of lack of trust in external agents who know things and make decisions that impact on the team, which works reflexively to index Steve’s account as having trustworthy status. In Lines 56 and 57, in contrast to Bob’s account of lack of knowledge, Steve interrupts with a confirmation that he does have access to “things” out there actioned through his claim to knowledge served as news. That is, it is news to the other speakers, but not to him. The interactional accomplishment is trust: there are people out there who may not be trustworthy, but as Steve has access to knowledge of “things,” his account can be trusted, and Bob’s account in Line 55 can now be seen as an endorsement of Steve’s trustworthiness directed to the team. This can be unpacked a little more.

Warrant

People normatively use “warrants” and “warranting” to mark something as being satisfactorily explained, according to David Silverman. Simply, a warrant is an excuse or justification for some action. For instance, “I am not able to go to the meeting because I will be in New York”: not being able to go to the meeting is accountable (i.e., requiring an explanation), but comes with a warrant of being in New York, thus excusing the absence.

Steve’s turn in Line 56 is prefaced with the conjuring of a cognitive state (“I think …”), which, in contrast to his earlier stuttered “I-I-I think …” (Line 53) that marks his account as open to doubt, works here as an explicit opinion marker (Chilton, 2004 ). By linking Steve’s two utterances (Lines 53/54 and 56/57), the persuasion work becomes clearly evident as Steve conjures his version of affairs as being more and more authentic, and predictable, with the second part building on Bob’s admission of the existence of “things we may not know,” marking this as a version of affairs that only Steve can predict. The veracity of his opinion—and therefore its trustworthiness—can be seen in his confident emphasis on timescales (“fai::rly rapidly”: Line 57). His claim to privileged access to knowledge also works as a warrant in linking to his earlier stance over “getting off desktops” (Line 46). The risk is downgraded and that which Ade has conjured for group worry is effectively deleted but without challenging its authenticity. Steve, then, claims what Clifton (2012a) terms “epistemic primacy,” scripting self as trustworthy. Ade orients to this interpretation of affairs with his token of acceptance in Line 58. The entire interaction, then, is a delicate balance between offering competing accounts of affairs and sensitivity to others’ concerns displayed particularly by Steve, despite Ade’s initial inferred resistance to the trustworthy status of the latter’s account of affairs.

The following two extracts display disagreement taking a more confrontational and combative turn.

12.5 RISK AND COMPETENCE AS CONTINGENT FACTORS TO TRUST

12.5.1 Calling on Witnesses to Work Up Persuasion

Extract 3 comes some 5 minutes into the meeting. Just prior to this, Bob has raised a topic from his list, which is directed to Ade for comment. What follows next can only be described as a mutual questioning of ability by Steve and Damien, with implied risks to trust. Recall that Schoorman and colleagues (2007) posit “ability” as one of the three dimensions of trustworthiness, the calculation of which influences perception of acceptable risk in others. In the context of the following discussion, “ability” is understood to infer “competence” and “reputation.”

What is interesting about this particular extract is Steve’s formulation in Line 90, issued in a sarcastic tone of voice, and referencing the name of a competitor company. In his study of political interview discourse, sociologist Ian Hutchby (2011 ) shows how such “skeptical rejoinders” constitute nonneutral moves. Here, what the competitor company “uses” is precisely the software product that Damien calls into question (Lines 86–89). Steve’s response in Line 90 is not issued as a news item—that is, it is not designed to inform coparticipants of some new state of affairs. Rather, it can be heard as a strong rebuke. Does this signal a crumbling of trust between the two actors?

Skeptical Rejoinders

These are linguistic devices that invoke skepticism on the part of the speaker in response to a prior turn at talk and are usually terms that would otherwise have a nonskeptical connotation. The ways in which an utterance can be shown to be transformed into an action of skepticism include a downward movement of intonation, for instance, rendering the utterance as hearably dismissive. Thus, such devices are not neutral and can be linked to taking a position on some topic.

Reported Speech

Speech that is attributed to some other by the speaker is called “reported speech,” and this can be direct or indirect. Direct speech is where the reported words are framed as a direct quotation or citation. It is indirect if the reported words are offered as an approximation or summary or other representation of the actual words spoken. With direct reported speech clearly being the more powerful linguistic device, both are important, routinely used structures in talk. Their effect on both speaker and hearer is dependent on context, but an obvious function is to effect persuasion work or to bolster the factual nature of what is being reported.

Extreme Case Formulation

Originally studied by Anita Pomerantz, extreme case formulations such as “extremely,” “very,” “every,” “everyone,” and so on take an evaluation to its extreme. These devices have multiple functions and consequences. They can “up the ante” of a particular argument; they can be used to “normalize” something that might otherwise be considered to be unusual (e.g., a knife carrying youth explains that “everyone has one,” suggesting the carrying of knives is normative behavior). Jonathan Clifton notes that they can leave a speaker exposed to potential criticism in that all that is required to dilute what is being claimed is one exception, the idea that all swans are white until you find a black one!

The sequence initiates in accordance with the now established sequential organization: Bob issues a topic, which is commented on by the relevant actor, followed by an assessment scripted by Steve. Here, we see a variation. In this instance, Ade receipts the topic issue with his habitual “yeah” and then reports the issue status: no progress has been made, thus bouncing the topic straight back to Bob (Line 78). The latter’s slight hesitation in picking up his slot (“Okay”: Line 80), followed by the start of something more [unfortunately unintelligible], suggests surprise, but nonetheless signals topic closure. The expectation that is established here is that as the topic has not been looked at yet, there will be no need for an assessment by Steve, making a topic transition (Wooffitt, 2005) relevant. What happens next is contrary to this expectation.

Overriding Bob’s attempt to mobilize a topic transition, Steve marks Ade’s response as insufficient by stalling topic closure. His utterance across Lines 81–82 effectively performs power-persuasion: first, he displays rights to prevent topic closure, and then he works to upgrade the task’s importance, which he does using a direct reported speech device. In reporting what the client says (“… every time I talk to a [client] they do go …”: Line 81), he neatly works up a warrant for maintaining the topic and ramping up its potency. It is “direct” in so much as it conjures a quotation of what others have said. Such devices serve to strengthen claims, rendering them more credible as fact (Wood and Kroger, 2000). Note how also, in using what others have said to issue a warrant for his version of affairs, Steve effectively disposes of any personal stake or interest in the version (Wetherell, 2001).

What this also suggests is that Steve acknowledges the need to persuade others on this point, with this persuasion talk directed to Ade. Note that he makes no reference to the task itself, instead invoking the negative consequences of the task not being done. This can be seen as a direct admonishment to Ade: it is his lack of attention to the topic that risks negative consequences, but there is no hint of questioning Ade’s competence, only his priorities. Also note the extreme case formulation prefacing the reported speech (“every time;” Line 80), used here as an instrument to upgrade the “ante” (Schegloff, 1997). This formulation powerfully and persuasively works up the routine and predictable nature of what “clients” will say: this does not just happen once or twice, but each time he engages with clients. It is so routine and part of the course, then, that this is cast as “common knowledge” (Edwards and Potter, 1992). The stakes associated with the task that Ade has reportedly not “looked at” are thus heightened, and risk is made live, to which Bob aligns agreement (Line 83). The nature of the task, at this point, is not the topic of dispute. Things then take a surprising turn.

12.5.2 Two Competing Versions of the Same Witness Accounts

Despite not being the agent of the task under discussion, Damien self-selects with a turn designed to shift risk from “not doing the task” to the task itself. He directly challenges Steve’s account and its warrant by rescripting what clients say as inconsequential: it is the very “routineness” (“always say”: Line 84) of what clients say that renders it not worth listening to. This is a classic example of variability inherent in talk: in essence, both Steve and Damien use a similar account of what clients say, emphasizing the routine frequency. But Steve’s account upgrades the importance of what clients say, while Damien’s does precisely the opposite. As Robin Wooffitt succinctly notes, “(T)the possibility of variation in and between versions of events is built into the fabric of everyday life” (2005 : 16). Consequently, an appeal to the facts will not resolve the issue. The contrast marker (“but”) signals the preferred nature of what is about to follow (Edwards and Potter, 1992). Steve’s talk-under (“I know”: Line 85) orients to what is about to now emerge as being a known-about account. Damien does not concede his turn to Steve’s interruption, but continues to press his version of affairs, summoning a broader picture with a call for a “bigger discussion” (Line 86/87).

12.5.3 Issuing Challenges to Competency and Undermining Trust

This call works on two levels: First, it indexes back to his account of what clients “always say” framing this as irrelevant, and beside the point, thus deleting any risk associated with what they say, reflexively working up criticism of Steve’s use of such evidence. Second, the call for a bigger discussion, formulated as a decision-making event (“whether to use [] or not”: Line 87), implies that the decision has already been discussed, but not thoroughly enough with the suggestion that its decision outcome is flawed. Risk is thus made live along a new trajectory. Collectively, Damien’s account serves as a competency challenge, which effectively undermines the previous speaker’s competence to comment on a given issue (Hutchby, 2011 ).

Declarative Assertion

When a speaker asserts a particular version of affairs as fact, which is not hedged in any way with, for instance, a qualifier such as “I think” or “it’s possible that,” then this version is said to be constructed as a representation of concrete reality. In asserting such an actual state of affairs, the speaker is said to be making self accountable for being right. It thus works on the level of an appeal to trust.

The decision-making process is further called into question through the issuing of a declarative assertion (Clifton, 2012a) in Line 88/89. In his study of trust actions in workplace interactions, Clifton shows how such assertions work up states of affairs as concrete reality, thus formulating the speaker as accountable for being right. The action of holding oneself publicly as accountable is a marker for trustworthiness. In this instance, Damien scripts a prediction of minimal benefits to be gained if Steve’s course of action is adopted. Thus, Damien’s account works as a display of superior knowledge as authentic, which is nonetheless accountable. It is accountable in the sense that future events could prove him to be right—or wrong. Such claims are inherently risky, so in making a concrete prediction about “the first month’s returns,” Damien rhetorically and reflexively scripts himself as knowledgeable and competent expert, with integrity (in nonetheless reporting such a negative projected future action). Consequently, his display of possessing superior knowledge, of ability to predict, and of accountability, integrity, and authenticity all work interrelationally as a display of “doing trust.” In other words, he constructs his version of affairs as hard if not impossible to dispute. But this is precisely what Steve does.

Orienting to the implicit competency challenge (Hutchby, 2011), Steve’s rejoinder is immediate—a tapering off and lowering of voice tone—issuing a discard by scripting the evidence of what another company (later identified as a competitor) does. It can also be heard as a call to common knowledge of facts out there (Edwards and Potter, 1992): this is what everyone knows. This arguably conjures a question over Damien’s ability and knowledge, with its implication that Damien’s account is biased in favor of his own interests. Thus, he reverses the competency challenge, scripting Damien’s account as not to be trusted, and that others know more, with all of associated consequences for reputation. Trust becomes undermined, and Damien makes no further contribution at this point. The impact of Line 90 can be seen in the two second delay and repair in Line 92, in which Bob attempts to “line under” the debate with a tentative formulation of a question on future projected action, issuing this with a candidate answer (Hepburn and Wiggins, 2005). He clearly makes live a context of discomfort, initiating a turn transition.

In this exchange, ability and reputation are shown as tacitly managed, as accountable and contingent to trust, authenticity, and trustworthiness. Actions are recipient designed (Potter and Edwards, 2012) to invoke warrants (e.g., claims to superior knowledge) for the trustworthiness of accounts. In this way, trust can be seen as implicit to KS, as well as working corelationally with ability and reputation.

It is claimed that Extract 3 shows trust breaking down; however, this is not the end of the matter.

12.6 TRUST BREAKDOWN CONNECTS WITH Knowledge Sharing BREACHES

12.6.1 Factual Accounting as a Warrant for Trust

Extract 4 comes a few lines later, following the selection of Manoj to “look into” the task (the subject of Extract 3) and the latter’s acceptance of the work.

To all intents and purposes, the topic has been closed, a resource assigned to the task, with agreement that it should be carried out. Bob actions a topic boundary marker (Svennevig, 2012b ), “Kay good” (Line 101), with the rapid typing suggesting that the decision just made is being concretized in the form of meeting notes. It can be speculated that this concretizing action is what drives Damien to reopen it in what is essentially a breach of the meeting’s procedural norms, something that it is assumed that only Steve, as Leader, is warranted to do. The claims to witness evidence constructed by Steve in Extract 3 have not persuaded Damien to change his opinion.

It is suggested here that Damien orients to his breach of meeting norms with a metaphorical “hand in the air” suggested by his opening particle “Uh” (Line 103), working up a claim to a turn. Note how his opening utterance contains markedly heavy exhalations of breath and a repair: “… it’s gonna … that’s gonna ….” This invokes frustration—the proverbial “banging of the head against a brick wall.” His concerns have moved from issues around what the client can expect (Extract 3, Lines 87–89) to those around a team member who has just been tasked with “a lot of work.” This is tonally emphasized, making it hearable as derived from expert knowledge. His orienting to a concern for others is designed to inoculate against potential criticism of having personal stake and interest (Edwards and Potter, 2005). His claim is thus serving up facts that are out there for any reasonable person to see.

He further embellishes the factual nature of his account with quantification: “two weeks’ work” (Line 105). The actor treats this piece of “fact” as accountable (Silverman, 2007), wrapping it in a two-part warrant. The scripting of “y’know,” prior to the quantification “fact,” typically works to project shared knowledge and intersubjective agreement (Clifton, 2012a); the team already jointly know this to be the case—thus, shared consensus and corroboration are invoked (Edwards and Potter, 1992). The second part of the warrant lies in the appeal to a self-evident level of common sense (Thompson, 2004) concerning what the task will specifically require (“… there’s basically at least one rule for every single field”: Lines 105/106), formulating this as obvious to everyone (but perhaps not Steve) and therefore undeniable. Notice also the absence of any references to cognitive states (e.g., I think) that might conjure a doubt marker or epistemic downgrade (Clifton). This absence increases the strength of the account as a warrant for an objective and therefore authentic state of affairs.

Doubt Marker and Epistemic Downgrades

Use of phrases such as “I think” and “I’m not sure” can serve to conjure doubt over whatever claim or account is being constructed, thus orienting to uncertainty. Likewise, “I think” and similar phrases can also perform the action of downgrading or diluting the knowledge that the speaker claims to possess. However, “I think” can also signify an expression of opinion as the personal possession of the speaker. How such phrases are understood depends on the context in which they are performed.

Quantification Rhetoric

This refers to utterances in which numerical and nonnumerical descriptor (e.g., “small,” “large”) phrases are used to construct accounts as factual and as designed to argue. The way in which such phrases are deployed is also significant in effect: for instance, half a million “sounds” more than 500,000 because the former refers to “millions,” while the latter invokes “thousands.

Damien’s turn works up Steve as being unreasonable, perhaps not even being in possession of the most basic facts (e.g., the rule for every field). It also orients to pressures of time, with the heavy emphasis on “a lot of work” quantified as being “two weeks,” with the risk that this implies in rendering valuable resources unavailable for other, perhaps more important work. In their study of quantification rhetoric in a media environment, Potter and his coworkers (1991 ) argue that such accounts are not simply accounts of some “robust reality” but are specifically designed to argue. The upshot is a second attempt by Damien to serve up a version of Steve’s “task” as being inappropriate and risky. However, it now transpires that Damien has entirely misunderstood the nature of the task.

12.6.2 A Breach in Knowledge Sharing Comes to the Fore

Steve is quick to discard Damien’s version of affairs (Line 109) for the second time. The stuttering repetition of “tha-that’s” coming at the start of his turn suggests a measure of surprise. Damien’s description of the task is not what Steve is asking to be done, thus working up a classic form of counter argument. However, Steve does more than simply correct Damien’s understanding of what is being asked for. He orients to the implicit “accusation” contained in Damien’s turn. Not only does Steve rebut the charges, but he also deflects the conjured “unreasonableness” back at Damien. The task is downgraded to “simple,” with a rhetorical boundary parked around its scope (Line 110). The requirement for a report on feasibility and scale of the now future projected task (the action that Damien has been concerned with), contrasted with “not to actually ↑do it” (Line 113), scripts Damien’s version of affairs, in which Manoj is understood to be tasked with doing the “actual” job, as being wholly irregular and something that Steve would never sanction. Steve, in this fashion, successfully retakes the moral high ground, arguably eroded as a result of his “quip” in Line 90, while simultaneously dismantling the position scripted by Damien. Damien’s position—his ability and reputation—is thus undermined. What Steve displays is a constructed context of lack of trust.

The upshot of the interactions in Extracts 3 and 4 is a significant climb-down by Damien (Line 114) and arguably a breakdown in trust. The gap of silence indicated in Line 115, with its audible sounds of papers rustling, suggests discomfort among team members.

There is one question that remains unanswered: how is it that Damien misunderstood the task that Steve (and Bob) refers to at the outset of the discussion? While it cannot be known or even speculated what is going on in the minds of speakers, what can be speculated is that the breakdown in trust between Steve and Damien, inaugurated in Extract 3, clouds the issues for the speakers and the business of sharing knowledge. Damien formulates the task of migration from one software database to another as (i) a lot of tedious work, (ii) not likely to give more than minimal benefits in return, and (iii) as a topic that needs a much broader discussion, with its suggestion of insufficient and even poorly informed discussion to date. That, by any standards, is an entrenched position. Steve, on the other hand, orients to what the clients want, what the competitor company does (and knows), and to himself as competent manager who would not require a task to be actually done before it is understood fully in terms of scope and feasibility. They are almost—but not quite—arguing about different things. Note how Steve does not orient to Damien’s concerns: he effectively discards them. A breakdown in trust has, it is conjectured, resulted directly in a break in communication, as Argyris (2009) predicts will happen when communications deteriorate, and hence a breach in KS.

12.7 KNOWLEDGE, TRUST, AND BLAME

12.7.1 Issuing the Call to Account

The following two short extracts appear in a further disagreement interaction between the same two actors—Steve and Damien—occurring around 20 minutes into the meeting. These extracts are different from the rest because, in this case, the disagreement is not issued at or during topic closure but is located in its normative and expected position in the discourse structure. Steve is coming to the end of a short descriptive report of another meeting at which he presented the team’s software product for review, receiving a good reception. This leads him into a relatively lengthy and technical description of navigation through the software application, which ends with Line 200, and the formulation of a problem.

Steve is referring to layers within the navigational system of the team’s software application, one of which is claimed to be missing (Line 200). The topic is issued as an assessment formulated as a question through a raised voice tone at the end. Although he uses the inclusive pronoun “we,” typically having the effect of projecting or presupposing agreement in meeting contexts (Clifton, 2006 ), it is hypothesized that here, the pronoun serves to separate “we” as a group that includes Steve, the members of the previously reported review panel, and possibly the other three meeting participants, from Damien himself. It can thus be heard as “we have a problem, and it’s your responsibility”—as a blame action, but with the raised tone at the end, making it hearable as a question.

What is the effect of serving an assessment in the form of a question? A question is one part of an adjacency pair, with an answer forming the other. The two are discriminately related in that the first defines an appropriate response in the second (Silverman, 2007). Thus, Steve’s turn makes an answer from Damien conditionally relevant (Wooffitt, 2005). He is publicly calling him to account.

Adjacency Pair

This term is drawn from the terminology of conversation analysis, and it refers to two conversational items that naturally and inevitably belong together. Greetings, for instance, are examples where if one speaker issues a greeting, it is incumbent on the other to respond similarly. Questions and answers are another example: if a person asks a question of another, the expected response is an answer to the question, not, for instance, a further question. Thus, these are “ordered pairs” such that the first part sets a requirement for a particular second part to be delivered, so it is made “conditionally relevant.” If a required second part is not forthcoming, it is generally treated by the first part speaker as a non-normative absence.

Intensifier

An intensifier is a word or phrase that works in the same way as an “extreme case formulation” in its effect of upgrading a given feature of the topic under discussion. So, for example, one speaker might say that a recently watched film is pretty good, and the subsequent speaker might describe the same film as well worth watching. This description is not an extreme case formulation because it is, evidently enough, not extreme, but it intensifies the previous description.

The rhetorical pattern displayed in Lines 200 to 206 is a repeat of “yes it is” contrasted with “no it’s not”: Ian Hutchby (2011 ) refers to such devices as “polar contrastives,” typically used in argumentative discourse. Damien bluntly denies Steve’s account of the software (“nothing is missing”: Line 202), formulating this denial as accountable by wrapping it with a warrant (e.g., “… only way … couldn’t be worked …”: Lines 202–203). This is stake management work in the sense of scripting one account while simultaneously undermining another (Edwards and Potter, 2005) and in fact undermining any potential alternative in the formulation of “only way.” In displaying his knowledge of what is not missing, he orients to self as technical expert, reflexively constructing Steve as inexpert and even irrational in his suggestion that “something is missing.” He bolsters his account in Line 206 by scripting an upshot (“… it’s there it just doesn’t show”), with “just” working to downgrade the issue (Abell and Stokoe, 2001). This is delivered in response to Steve’s stretched receipt token (Line 205)—which can be heard as a skeptical rejoinder (Hutchby)—in the attempt to formulate an acceptable end to topic in its dealing with Steve’s initial question over “something missing.” Instead of closing the topic, Steve ups the ante in the form of an intensifier (Schegloff, 1997), upgrading the issue to “a problem,” with “that’s” working as a metaphorical pointing of the finger. Blame is thus made live and attributed.

In the final part of Extract 5, there is a short delay before Damien responds, which makes his initial acceptance of the label “problem” hearable as an admission, and thus Damien orients to the blame work done by his colleague. Note, however, how Damien’s construct of “it’s a problem” contrasts with Steve’s version (“that’s a problem”), which can be seen as initializing a strategy of depersonalizing the problem. The “but” in Line 208 signals the start of a disclaimer (Potter and Wetherell, 1987), an acknowledgement that attribution has been made live and must be deflected.

12.7.2 Managing Blame

He first deselects himself as the subject of blame (“there’s nothing that could be done”) and then offers a contradictory set of affairs that explicitly sets the trajectory of attribution back in Steve’s direction (“… unless you wanna …”: Line 209). The warranting work for this redirected attribution is formulated in the implicit understanding that Steve, in his leader role, is responsible for project budget, with the rights to spend money on a novel solution (“(hire) someone for the software”: Line 209). There is a solution available out there, but it requires money to be spent, and Steve owns the responsibility for this, with the reflexive implication that it is Steve’s fault for not spending appropriate sums of money. His absolution work is completed in his subsequent proffering of his solution as the only one reasonably available, with the implicit understanding that his account of affairs can be trusted as an accurate description of reality: he has done as best as he can.

12.7.3 Question over Competence or Simply not Sharing Knowledge?

What is interesting about this interchange, with all its connotations of blame and attribution, is that Damien is not only aware of the “problem,” but has already taken steps to resolve it in the only available way. However, until now, that is a state of affairs unknown to Steve. Knowledge of the “problem” has only come to communal light as a consequence of the competing accounts. This is unusual given the attention to detail that, elsewhere, Steve in his role of leader is shown to display. This understanding of events becomes explicit in Extract 6.

In the intervening lines, Steve and Damien continue to discuss the problem and its implications for the software. Just prior to this, Damien has repeated his assessment that “it’s a problem” but one about which nothing can be done. (It is also worth noting that, throughout all of these exchanges, the rhetoric is largely spoken in reasonable tones—the tones of voice one would expect in a professional business meeting.)

Steve’s turn in Lines 220 and 221 can be seen as orienting to a lack of trust in the account given by Damien (“nothing to be done”). Not only does Steve persist in the existence of potential other solutions out there, with the implication that either Damien does not know of them or has not considered them, but he now introduces another character in his “suggestion” that Damien “have a conversation” with David. This conjures “David” as more competent and implicitly more trustworthy than Damien, scripting a competency challenge (Hutchby, 2011). This, in contrast to his earlier issuing of the problem in Line 200, is not formulated as a question. The nonquestion status can be seen in Damien’s response with its noncommittal utterance: that is, as it is not a question, an answer is not conditionally relevant. Steve scripts such a projected future event as having the ability to realize devious solutions (“way to trick it”: Line 219), with the implication that these will come from David. Damien is reflexively scripted as either lacking in such knowledge and imagination or, possibly, holding it back. This latter understanding stems from Steve’s subsequent turn (Lines 224–227).

With no articulated response from Damien, with instead his nonlinguistic utterance suggesting disdain at the proposal of “tricking,” Steve continues to conjure knowledge of solutions “out there” with his repeat of “y’know” projecting intersubjective agreement (Clifton, 2012a) shared with Damien. That is, Steve scripts Damien as being privy to knowledge that he has not shared, which may hold an acceptable solution to the problem (“something”). So the work done here is persuasion, with Steve’s own claims to knowledge mitigated by “I don’t know.” This phrase is shown to be a way that people handle or downplay stake or interest in reports and descriptions (Edwards and Potter, 2005). This formulation works in sharp contrast to the project knowledge that Steve scripts Damien as having, but not sharing. The issue of trust is again made live, with attribution work setting its trajectory.

Unfortunately, Damien’s turn at talk in Lines 228–232 is all but unintelligible, but there is enough of a gist to gather that, again, Damien is scripting “only one solution,” and this has already been considered (and possibly implemented). The final turn in this extract (Lines 233/234) marks a radical change in rhetorical trajectory. Once again, Steve uses a rise in tone at the end of the utterance, which, here, does not script a question but rather an appeal for consensus. He issues a subjective assessment of the software that is being used to create the team’s software product as problematic and prospectively unlikable. This not only displays his claims to rights to make such an evaluation, actions that are linked to, for instance, persuasion and blaming (Wiggins and Potter, 2003), but also constructs his evaluation as not being voluntarily made, but rather as a consequence of the “offending” software application—and presumably, its creators.

Thus, Steve’s “game-changing” evaluation of affairs erases blame from Damien and from himself and works to reestablish trust through orienting to consensus. The upshot is an evaluation of a state of affairs that is shared by everyone, so it must be true (Edwards and Potter, 1992), and as something that they will all just have to live with. In shifting blame to the software, Steve effectively changes rhetorical strategy. Damien’s subsequent turn (not included here) orients to this in offering a more detailed account of the problem and what he has done to resolve it, which raises the question of why he did not do so earlier in this exchange. The exchange concludes with Steve accepting things as they are, but leaving options open.

12.8 PRELIMINARY REFLECTIONS

The starting point of the present analysis has been the speculation that KS is contingent to trust and that this, as a phenomenon invoked by speakers in interaction, can be shown to work corelationally with the other KS themes of identity, risk, and context. We further speculated that trust will be shown to have an influencing effect on KS activities in discursive action and that trust as a KS theme can be shown to be tacitly accomplished by speakers as psychological phenomena. These speculations are explored in the context of an organizational meeting. One meeting was selected for analysis over examples from multiple meetings to ensure that developing relationships could be brought to the fore. Consequently, the six extracts are included in the order in which they appear in the meeting transcript.

What the analysis shows is that KS practices are inextricably bound to matters of trust, as made contingent and live by the meeting participants themselves. Trust is shown to be a dynamic, constantly changing pattern of rhetorical action: it is invoked by one speaker then dismantled by another and then reestablished. Displays of trust also vary from context to context: for instance, in his interaction with both Ade and Damien, Steve deals with matters of interrelational trust in different ways. What is also clearly seen is how trust works corelationally with risk as a live concern for speakers: for instance, in Extract 2, Ade conjures Steve’s proposed plan of action as risky invoking its untrustworthiness, displaying tacit knowledge of background facts as a warrant. Steve mediates this state of affairs by simply discarding the issue which he is able to do because he has access to privileged knowledge (epistemic superiority) which Ade does not, and which is superior to Ade’s. Ade displays acknowledgment of his colleague’s superior knowledge through his acceptance of Steve’s version. Risk is thus managed as a contingency to trust.

We have also seen how trust works corelationally with identity—particularly visible in the collaboratively conjured contexts of reputation, competence, and authenticity, for instance. In the last extract, for example, Steve is shown to negotiate his understanding of Damien as either incompetent or obstructive with his sharing of knowledge. It is almost as though he is testing first one theory and then another in order to reach a view of Damien as one or the other. Of course, both options come with a problem that must be managed, and the blame that has been conjured and made live must be attributed somewhere. Moreover, we can also argue that risk can also be shown to be corelational with identity, as well as trust. In the latter example, Steve can be understood to be carefully working to mediate the risk of a breakdown in trust and attribution left unresolved, which he does skillfully by relocating both attribution and distrust onto the software at the root of their conversation.

On a point of general observation, knowledge displays, as a function of doing trust, are linked to persuasion rhetoric, authenticity, factual accounting and attribution, as well as risk. Trustworthiness of self and account are shown to be mutually contingent: it is difficult to have one without the other.

On the question of trust as an influencing factor in KS, it has been shown how in the moment-by-moment turns of discourse, trust erosion is implicated in KS problems, with consequences for mutual displays of competence and reputation. Breakdowns in trust are speculated to lead to a clouding of issues. It was noted earlier how trust can work relationally with attribution (in this case, of blame), linking this to risk: analysis shows that the explicit removal of blame leads to a reestablishment of trust, which in turn reengages KS actions as voluntary. We see similar outcomes in the analysis of another meeting (Chapter 16; extract 2) in which two speakers volunteer additional and important accounts when the meeting lead exonerates them from any criticism or blame.

Extract 6 particularly displays speakers’ tacit understanding of the importance of trust to the business of sharing knowledge and the goal of solving problems. In working to resolve the trust breach-attribution problem, Steve and the other participating speakers index to their tacit sense of the meeting’s purpose and what will and will not facilitate and mediate its business of KS. A further display of tacit knowing can be seen in Extract 1 in which speakers invoke both mutual familiarity and the sense of mutual status and rights. Thus, and in effect, the meeting’s norms are made live and displayed as collaboratively shared. Some of the subsequent actions, however, are shown to be deviant to these norms in, for instance, Damien’s introduction of argumentative alternative claims after a topic closing action has been initiated, and contrary to the meetings norms in respect of Steve’s status as the only speaker with rights to breach these rules (Extract 3).

What is missing from the analysis, though, is an explicit example of Schoorman and his colleagues’ model of trust being contingent on perception of another’s ability, integrity, and benevolence. Understood as the human characteristic of being well-meaning or kind, benevolence, as a discursive construct of speakers themselves, does not appear to feature in the present discourse, which is otherwise shown to display concerns with trust, reputation, and so forth. It is possible that a further and deeper analysis might hint at its presence, but, alternatively, it might simply be the case that benevolence is not a constructed action here because the action of constructing and displaying trust and trustworthiness in organizational settings is not contingent to perception of another’s kindness, for instance.

The next chapter continues to develop these lines of exploration by focusing particularly on the phenomenon of risk.

FURTHER READING

  1. Clifton, J. (2012). ‘Doing’ trust in workplace interaction. In Mada, S. and Saftoiu, R. (Eds). Professional Communications across Languages and Cultures. Amsterdam: John Benjamins Publishing Company.
  2. Evans, M. (2013). Is trust the most important human factor influencing knowledge sharing in organizations? Journal of Information & Knowledge Management, 12 (4): 1350038 (17 pages).
  3. Schoorman, F., Mayer, R. and Davis, J. (2007). An integrative model of organizational trust: past, present, and future. Academy of Management Review, 32 (20): 344–354.
  4. Wooffitt, R. (2005). Conversation analysis and discourse analysis: a comparative and critical introduction. London: Sage.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.188.238.31