In the analysis below, we explore 1) working as whole persons, 2) creating partnerships, 3) unclear decision making processes and last 4) informal power dynamics.
Working as whole human beings and EL demands
Unsurprisingly, interview participants describe how they manage their emotions in relation to experiences on Flowdock. One of the key characteristics that stands out relates to how Flowdock becomes an extension of informal social interactions both between staff and between staff and customers. Jonathan, a programmer, describes that Flowdock has a chat function, allowing them to share material of both professional content and leisure content online 24-7 in a way that engages him professionally, as well as privately:
Yes, and many of us have it on our mobile phones too, so if you are away from the computer, you can constantly have a look anyway. But it is also very social, and we also have this language where you can share things you find on the web, whether it's for fun or professionally, or just something interesting. There is also a flow that is only about American politics for those with that hobby.
To Jonathan Flowdock is a tool that creates social cohesion as the ongoing digital conversation about both professional and private content give rises to a sense of digital proxity. Having Flowdock on mobile phones enables him to be constantly connected (“constantly have a look”). To him, being on Flowdock and contributing to the ongoing conversation in the organization is pleasurable as it enables a sense of digital proximity – he feels part of the team and connected to the company and as well as to his collegues. Flowdock is practiced in a way so that professional and social content is mixed, and in that sense the technology opens up a space where staff come to work as whole persons as it is also stated in the agile manifesto and in accordance with the agile normative goal. Jonathan explicitly values this practice, even though he uses his spare time (without being paid for it) which contributes to the erosion of boundaries between work and private life; a theme that traverses the material. Informed by Hochschild (1983) and the theoretical framework that excels at identifying exploitative dynamics in which emotions are commodified, we highlight the increased demands on EL that staff members have to meet while navigating work/life balances.
Creating partnerships and EL demands
Flowdock provides a space for informal and collaborative interaction between staff and partners/customers. Staff has to relate to partners in a more informal way, more as whole persons in accordance with the agile ideology. Each partner has their own channel and here Jonathan explains what that entails:
It is a slightly more informal way of communicating. So it is of great importance, also because there is something cultural about the way of communicating, where - with some customers - you can have a ‘language’ that is only found there. If the customer understands it and you have a common understanding of the language there, it's like having a really fun meeting with the customer, where you can make all sorts of insane jokes together and you are on the same wavelength. You can have that feeling there too. It's like in the old days when SMS language was ‘a thing’. (…) You use some different elements with emojis, funny comments and jokes and animated GIFs. (…) It's much more interactive [on Flowdock] and much more real-time than emails are. Emails tend to get too formal because you sit down and write and reflect on your words and you write ‘Sincerely’, etc. It just has a much more formal tone.
He emphasises how Flowdock affords another kind of social contact with clients as it is more interactive, real-time and stripped of the formalities and politeness characteristic of emails. Jonathan identifies timing and and responding quickly as a key. The activities on Flowdock enable, encourage or afford using a playful and informal language filled with insider references and entertaining memes supporting a bodily experience of trust, partnership and being ‘on the same wavelength’. For Jonathan doing this relational work and engaging in these informal interactions provides him with a sense of joy and is directly linked to his job satisfaction.
Exploring the EL from the perspective of the technology and social practices related to it allow us to understand how the rhythm and framing of chat messages (rather than longer emails, for instance) in Flowdock presents a script (Akrich, 1992; Latour, 1996) that encourages a more informal communication compared to emails. Based on Jonathan’s account we come to understand that Flowdock affords informal behaviour among users, who are encouraged to relate to each other more like private persons instead of maintaining a professional distance, again pushing boundaries between private and professional spheres. The informal social rules on Flowdock makes it possible to share information in a flat, transparent and democratic way. This allows for more intimate communication, which is crucial when establishing partnerships in the agile organization, and trust, which is necessary for making quick decisions and relying more on competent craftsmanship than standardised procedures and systems. Flowdock communication places new EL demands; both internally in the agile organization as Flowdock activity enables a sense of digital proximity in relation to the company and collegues, as well as externally, as informal flowdock activity is part of the EL implicated in constituting a partnership rather than interacting with customers. Having to interact informally as a whole person and with a sense of humour is not just icing on the cake, but rather a central task to live up to the demands in the company creating a sense of digital proximity both internally and externally. Feeling the ‘right’ feelings and evoking the ‘right’ emotional feelings in partners is not epipheral, but rather key to create a partnership that is built on collaboration and trust.
Unclear decision making and EL demands
In alignment with the agile manifesto, there is an opposition against systems and procedures, leaving decision making processes relatively unclear. This opposition works as a normative ideal creating certain social rules making some emotional reactions more legitimate than others. According to Sophie in conversation with Benjamin below, it becomes extra challenging to decipher whether a decision is being made on Flowdock compared to analogue encounters. Communicating digitally entails that the conversation is stripped of non-verbal cues, and that sometimes results in what she terms ‘bad tone’:
Sophie, Team Leader, Consultant: I think it has replaced a lot of dialogue. We don't talk so much in a forum where we have an agenda, a decision to be made. The culture is like this – we don’t know when we are in the process of making a decision on a flow. (…) I think a lot is lost when you can't see facial expressions. Much communication is lost in that. There is often a bad tone in there.
Benjamin, Junior Programmer: Everything is visible to everyone and it's a flat hierarchy. There are also some other issues; the tone and that things can be misunderstood over text.
The lack of clarity is increasingly a problem in virtual communication, as interaction here is stripped from clues that might help decode the level of importance. Sophie describes how aspects of communication are lost without facial expressions and they both recognize a problem with the “tone”. Due to problems interpreting verbal expressions without facial cues, people are more likely to perceive a neutral or direct quote as hostile or angry (Friedman & Currall, 2003). Words, emojis, etc. therefore have to compensate for the lack of the comforting eye contact or warm smile we use to convey the right messages. These digital conditions shape demands on EL, as staff has to manage a sense of unclarity and perhaps frustration, and also interpret and respond to emotional cues without a wellknown source of knowledge.
The seemingly flat hierarchy seems to result in high levels of insecurity among staff. Simon says: ‘It takes very little before everything blows up in the air, right?’ and he elaborates: ‘We have so much history, so much strength in that… very flexible, agile processes, etc… so every time somebody tries to put things into boxes, there is a lot of resistance.’ The volatile milieu is also described by Simon, who notes that ‘emotions run high because [the staff] constantly change between talking generally and in relation to what we are going to do concretely. There is a nervousness.’ The EL is affected by a general atmosphere that runs in the organization and shape what is needed in terms of emotion management, both in terms of suppressing nervousness but also in terms of evoking calmness. The impact of this volatile milieu is also experienced by Monica:
I think I have been a lot more frustrated than I have ever been in other jobs. Despite the fact that I feel that we are doing a lot of things right, and I really think it is a good company in many ways, I just think there is something in the culture, or whatever the hell it is… I can see it in my colleagues, something is happening here (…) It is a culture with a lot of feeling, I mean, people have a lot of feelings about their work somehow. That is what I experience as relatively new here. There is this resistance towards power, but if there is no agenda, then what is a meeting? It is simply a battleground for attitudes and if nobody knows what we are doing right now, then you easily misunderstand one another.
It seems there is a heightened risk of misunderstanding when you mix agile organising, flat structure, emotional investment. This mix has implications for the demands on EL in a digital context. In alignment with Hochschild’s rich descriptions of the importance of EL, it seems hard for Sophie to put her finger on what is going on, but she spends a lot of energy registrering emotions and dealing with them.
Related to constant connectivity and the unstructured information on Flowdock, managing large amounts of data has been related to experiences of stress (or techno-stress) (Atanasoff & Venable, 2017). During a focus group interview with employees, three colleagues discuss what they term the ‘overflow’ on Flowdock meaning being overwhelmed by data they have to keep track of:
Nicolas, Team Leader, Programmer: (....) They [the staff, ed.] don't know where to look. There is an overflow [our italics]. In Flowdock, we have, maybe, 73 flows. ‘Where did you hear about that? ’. You miss something if you are not everywhere. It creates fragmentation. I have a workflow where I check everything continuously to determine if I should keep up.
Sophie: For me, it means I often spend half an hour or an hour of internal time that you can't bill. Everything can be relevant and everything can be irrelevant. That's the downside to it. Also from an organizational perspective, economics.
Benjamin, Programmer: There are many things that start out as irrelevant but which then become important through the talk. I can definitely recognise that.
Continuously keeping track of conversations is necessary as ‘you miss something if you are not everywhere.’ Nicolas quotes a common question posed by staff: ‘where did you hear that?’ The question indicates a sense of insecurity and a fear of missing out, echoing the volatile milieu noted above. Benjamin notes that it is impossible to distinguish between relevant and irrelevant flows as these are always emerging in new and unpredictable ways. In that sense, every new piece of information shared on Flowdock calls upon rapid, real-time responses as this is the nature of communicating informally on Flowdock. It is necessary to keep track of how relevance evolves and is produced in the ongoing virtual conversation. As irrelevant and relevant information is weaved together and navigating that is key to doing the job and hence also the ability to manage these feelings of being overwhelmed, frustrated or even fearful. Alvesson (2004) similarly points out that knowledge workers are self-managing and this often involves a sense of ambiguity. Part of EL for staff involves managing an ambiguity as they continually ask themselves; What do I risk if I am not everywhere, all the time? Staff has to do deal with a constant doubt about whether to be connected at all times (with the risk of being overwhelmed) in order to be part of the organization and contributing as well as experiencing the positive aspects of digital proximity enabled here.
For some staff members (especially those with limited resources), the manifold invitations become overwhelming. Notably, only one (Preben) among the 23 employees has decided to be inactive on Flowdock. The fact that they have a collegue who signed out underlines the intricate and subtle power dynamics at play. Jonathan says: ‘so it is not something that is dictated from above that you have to join’ supporting Jonathan’s experience of it being voluntarily. Participating on flowdock is not mandatory, however, not being there has consequences and it seems clear that contributing on Flowdock is a central forum for creating digital proximity which seem to be considered as appropriate. Preben (Team Leader, Senior Programmer) describes: ‘I'm not exercising my opportunity for influence. That way, I isolate myself as an employee. It is a waste of time and ineffective. It has a consequence for me, but also for the organization.’ Preben decribes being isolated, supporting our claim that activities on Flowdock builds a sense digital proximity among staff. He is unable to take part in decision making processes and while he is aware of the individual problems of this he also points to the the organizational problem.
Informal power dynamics and emotional demands
The use of Flowdock is described as a technological enactment and support of the organization’s flat hierarchy. Anybody can voice their take on a subject on equal terms with colleagues and management. In general, the interviews and focus group interviews everybody talked about a democratic ideal facilitating self-managing and engaged workers and a high level of autonomy, but also that participation was not equally distributed. Partners in the company stood out as having a particular and more potent voice. Seniority and specialised knowledge were pinpointed as crucial currencies in negotiating authority. It is commonly known that flat organizations with a less formal hierarchy experience an increase in informal hierarchies (Diefenbach & Sillince, 2011) and that these hierarchies are less transparent and function on the basis of status and other legitimising norms. Flowdock provides a forum for staff to bring up new ideas on supposedly equal terms. However, during the interviews it becomes clear that the informal power operates through classical stratification lines, such as seniority and possibly also gender, as Julie describes:
It is impossible to avoid that when somebody with a lot less seniority brings up an idea, then that… brutal feedback comes. Perhaps it was a bad idea. But anyhow, now he is gonna think that it was a bad idea, because [the boss] said so. Not necessarily because it was a bad idea.
Part of being an autonomous and innovative employee means taking initiatives. The purpose is to test ideas in the professional community in a rapid and agile fashion, but as described it is impossible to isolate the professional content. While each voice in principle has equal access, the weight of the different voices is very different. Similarly, Sophie describes:
My sense is that [one of the partners] tries to be a little bit present everywhere which is a little inappropriate, because it’s not very motivating to get a comment from the CEO who has not really had the time to properly understand the work you have been doing.
Getting quick feedback on Flowdock is sensitive according to Sophie, and the voice of the CEO naturally carries a lot of weight. In addition, when he is present everywhere, all the time, we suggest that plays a role in negotiating what is conveived of as an appropriate level of engagement. This gives rise to ambivalence for Sophie: on the one hand, she wants to be creative and innovative, but doing so comes with a risk, as she notes: ‘it becomes sensitive. I think it becomes too much for me to do it.’ The idea is that staff presents new ideas on Flowdock in a democratic fashion and that the conversation is strictly professional, however, the lived experience indicates increased EL demands. In the absence of structured procedure in terms of reciving feedback, we identify here a risk of interpreting rejections as personal, requiring EL to manage the emotional side to the informal power dynamics. When agile organizing seek to enable innovation and initiative, it might be important to take into accound the emotional atmosphere and the EL involved in the concrete analogue and digital practices.
The subtle dynamics and unwritten rules that guide behaviour become extremely important in relation to dealing with conflict on Flowdock. While real-time responses are possible, we identify issues of timing as important as this comes to show in relation to a specific event in the organization.
Overall, the conflict concerned a disagreement about how to define the organization in terms of ideology. Three staff members participated in a conference abroad and here they met some representatives of another company who were interested in alternative ways of organising and who sougt out consultanty on the matter. Being flattered and intrigued, the attending staff members worked out a draft describing the company in holicratic terms. Doing so sparked an enormous conflict on Flowdock, described by some as an “explosion”:
Hey, why does it say holacracy? Why sociocracy? What's this about? What the hell has that got to do with our web page? You know it's going crazy. The people who respond do not know what the text has to be used for. So it just explodes (…). There are other people who react and you just think “what the hell”.
John describes that Simon P. was at a meeting, so he had not seen what had happened: He accessed the flow later and thinks: ‘What the fuck!’’ John P. notes that they are ‘shouting’. From an EL perspective, the choice of words are interesting as they share the common denominator of being almost tactile. Through specific wordings and the use of exclamation marks, it is possible to convey not only factual information but indeed also emotionally charged information. In sharp opposition to creating digital proximity, such wording and digital behavior results in fragmentation and conflict. The incident uncovers how EL is linked to the rhythm of the communication. Due to the conversation taking place on Flowdock, they communicate out of tune with one another. All staff members are simultaneously part of other rhythms, such as participating in analogue interactions, while the event unfolds without them knowing. The virtual and the analogue realities intertwine and co-constitute each other in complex ways. One colleague passing the other in the hallway results in him being pulled into the flow. The timing and fragmentation of the event plays an important role in its emergence.
Leaving the communication forum unmanaged invites a whole range of explosive affective reactions and hence demands for managing emotions in the company.