Concept

Useful visibility helps people understand your work and reach you when they need to.

Issue

Being seen, being available and producing a useful result are different things.

Solutions

Work out what others need to know, then plan a truthful progress update.

Say you’re checking the evidence for a recommendation. Your shared document hasn’t changed because you’re still reading. You wonder whether to add something just so other people can see you at work.

Before you add an edit, ask two questions and keep them apart. Does someone need something from you now? Or are you trying to make the work look busier than it is?

The first question is about a dependency: something a person needs from you. The second is about how your work looks to others. You can say honestly what you’re doing and still get on with the work that leads to a result people can use.

This module is for people whose work means reading, reasoning or rough drafts. It assumes you can choose truthful words about your progress, and that you’re allowed some space for work that isn’t done. If your job says when you must be reachable or when work is due, that still comes first.

What you’ll get from this module

In this module

By the end of this module, you’ll have a clearer way to explain your progress. You’ll also be able to judge when rough work can stay in a place you’re allowed to use for notes. We’ll link research on status indicators, messaging at work, monitoring cues, privacy in a factory and cashiers at work. You’ll look at a case from your own daily life. Then you’ll write a truthful update and a handoff plan, or find what you need to clear up first.

What does being visible actually change?

Survey research: people manage how their status looks.

Online status indicators show whether someone is online now or was a short time ago. A 2020 study by Camille Cobb and colleagues analyzed survey answers from 200 smartphone users. It also set tasks about spotting and controlling these signals. The people surveyed said they used the signals to manage how they looked to others.

That gives the worry in the opening a basis you may know from your own life. A sign that you are online can turn into a thing you try to manage for an audience. You think about how others will read what you do, as well as what you want to do.

Why it matters: These were reports from smartphone users in general. They don’t show how much reading, thinking or drafting at work is lost when people can be seen through digital tools. Managing how you look to others is not the same as losing time you could have spent on useful work.

Read the study of online status indicators.

Workplace field research: presence can help people coordinate.

Being visible also has a good use. A 2000 study by Bonnie A. Nardi, Steve Whittaker and Erin Bradner looked at instant messaging among 20 people across two companies and an independent contractor.

Interviews, some observation and a limited set of message logs showed how presence lists helped people find contacts. Short opening messages helped them agree whether to talk, and when.

To find someone online was one step. To know they could talk was a second step, linked to the first but not the same. The signal helped people start to coordinate. The exchange made clear what could happen next. That is a reason to keep helpful contact details in place when you make room for rough work.

Why it matters: This was a small qualitative study of early messaging at work. The people in it were free to delay replies. That doesn’t override the reply times your own job sets.

Read the field study of workplace messaging.

Lab experiment: cues about what is judged can change priorities.

A separate question is what people think they will be judged on. Jeffrey M. Stanton and Amanda L. Julian studied monitoring cues: messages about which parts of a person’s work were being watched. Students got these messages during a 35-minute task on a computer, in which they corrected addresses.

Their 2002 study is described here from an uncorrected proof that an author uploaded. It reports 134 students recruited and 124 analyzed once some were left out. Group sessions were given messages at random. A message said that quality was watched, that quantity was, that both were, or it named neither one. All of the students believed they were being watched.

The cues changed how important the students thought quality and quantity were. Some quantity results changed too. But corrections per examined record showed no statistically significant effect on quality.

Why it matters: What the students were told about the watching made a difference, even though all of them believed they were being watched. The experiment did not show that monitoring harmed quality. For your own case, the question to ask is what the signal really asks you to deliver.

Read the monitoring-cue experiment.

Factory field experiment: a boundary around the process can matter.

A 2012 study by Ethan S. Bernstein looked at privacy at a factory in China. In a five-month experiment in 2009, two physical production lines were picked at random to get curtains.

Each line ran two shifts, which gave four line-shifts behind curtains. The comparison group had 28 line-shifts with no curtains. Production and quality were still recorded. Defect-free output per hour rose on the curtained lines, and those lines kept a lead over the lines with no curtains.

Observations and interviews suggested that privacy helped people try things out and share ideas within their teams. People outside could see less. People inside the curtain could still work as a team. Managers could still track what the teams made, though they saw less of how the teams worked.

Why it matters: This was a small physical experiment with only two treated production lines. It gives a reason to think about allowed space for rough work. It leaves open what private digital drafting does.

Read the factory privacy study.

What does being seen change?

Supermarket field research: being visible can support productive effort.

Less visibility is not always better. A 2009 study by Alexandre Mas and Enrico Moretti used transaction records from 394 cashiers in six supermarkets, two years per store.

Higher productivity among coworkers went along with higher scanning productivity for the worker being studied. The researchers also looked at who could see whom. A worker’s scanning productivity was linked to how productive the coworkers who could see that worker were. This pattern supported an explanation based on pressure from coworkers.

This was field evidence that used shift changes and statistical controls. It was not an experiment that set at random who was watched. Its outcome was scanning productivity, not the quality of a complex recommendation.

Why it matters: The cashier finding is a helpful counterweight to the factory result. Tasks and set-ups differ, and so does the way being visible can help. The choice you make in practice needs to take account of the work and of the people who depend on it.

Read the study of cashier peer effects.

What should she say, and what can stay rough?

What this means for you

Be visible in ways that tell people about the task, the results they can use and what they really need from you. Give rough work room only within the set-ups you’re allowed to use. The research gives reasons to look hard at those choices. It doesn’t set a general amount of thinking lost to digital visibility.

Separate being available from making progress

Start by working out who needs something from you, what they need and when. A colleague who is trying to reach you needs to know when they can. Someone waiting for your recommendation needs the result, a draft they can use or an honest account of what is still not settled.

Keep both needs in view. A true message about when you can be reached can’t stand in for a promised draft. A good draft can’t stand in for a reply you must give while someone is relying on you.

Use a channel you already have to describe the work and the next handoff that will help. In the made-up opening, you could explain that you’re checking evidence and will share the recommendation at the agreed handoff. Include the usual urgent route only if it is truly open to use.

In live service, safety-sensitive work, tasks tightly tied to other people’s and jobs with set reply times, stay as visible and reachable as the work requires. If you don’t know what someone needs, clear that up before you change how you work.

Check whether the unfinished draft is already someone else’s input

A scratch space is a private place for rough work. It fits here only when you’re allowed to use it and nobody needs the live draft. Both conditions matter. Being allowed doesn’t tell you, on its own, whether someone else is waiting for something inside it.

Say your recommendation is due at an agreed handoff and nobody needs the rough notes before then. You can use an allowed scratch space to work on them, then share a version people can use.

Now change one fact: a colleague needs to know what you’re not yet sure about so they can go on with their own work. Keeping it to yourself until the handoff would hold back something they need. Share what you’re unsure about when it starts to matter, even if the recommendation isn’t done.

If you’re required to work live with others, keep doing the reading and reasoning within that set-up. Say truthfully what stage you’re at. Don’t promise a steady stream of edits. If it’s unclear what is allowed or who depends on what, keep the required set-up and ask what can change.

Make the next handoff useful

Name what the other person will be able to use: a decision, a draft, a point you have checked or a real blocker. This ties the update to the task, not to how much activity is on show.

Prefer a handoff that is already planned. Updates added just to show effort can turn into one more task to keep up. The aim is to make the work easy to follow. It isn’t to add a new stream of status reports.

At the handoff, share what you really have. If the evidence still leaves a question open, say what the question is and what it stops you from deciding. Don’t present something you’re unsure of as finished work.

Never fake activity, misstate how reachable you are or quietly hold back a draft someone needs. Where your job truly requires or rewards quick replies that others can see, keep giving truthful signals that help. A new way to describe progress can’t change what your workplace requires or rewards.

Which piece of work is on your mind?

How about your daily life?

Where do you need time to read, reason or write a rough draft while someone else needs to know what is going on?

You might be checking a recommendation, working through a hard part of a report or getting material ready for a shared project. Choose a case where you have a say over your wording or over an allowed space to prepare.

Write down cases you’d like to handle more clearly. One that fits is enough.

A situation in my daily lifeWhat someone else needs to know or receive
________________________________________
________________________________________

Which one would help you most to explore now?

My chosen situation: ____________________

You can change your choice. Carry it into the exercise below. Choosing it doesn’t yet show that drafting in private is right for it.

Plan a truthful progress update

Start with your chosen situation. If you came straight here, choose a task of reading, reasoning or rough drafting where you have a say over truthful updates or an allowed space to prepare.

In live service, safety-sensitive work, tasks tightly tied to other people’s and jobs with set reply times, stay as visible and reachable as the work requires. Never fake activity, misstate how reachable you are or quietly hold back a draft someone needs.

  1. Identify the dependency. Write who needs what from you and when. Include any reply times you must meet and the real route for urgent contact. If a duty is unclear, name what you need to clear up before you change the set-up.
    Person, needed input, timing and reachability: ____________________
  2. Name the work and next useful handoff. Describe what you’re working toward and what you can honestly hand over at a handoff that is already planned. That might be a decision, a draft, a checked point or an issue that is still open.
    Current work and next handoff: ____________________
  3. Choose where unfinished work can develop. Use a private scratch space only if you’re allowed to and nobody needs the live draft. If not, keep the required shared set-up and say what stage you’re at. Share what you’re not yet sure about when someone needs it to carry on.
    Permitted arrangement, or question to clarify: ____________________
  4. Write the update and follow through. Use a channel you already have to explain the task and the next handoff, and keep what you say about when you can be reached truthful. Do the groundwork the task needs. Then share the result people can use, or the real blocker, at the handoff.
    My truthful update: ____________________
    What I will share, or what remains unresolved: ____________________

Ask Jing

Become a Jingius.

Plan your progress update

Loading interactive tool…

Your next step

You’ve finished the plan when it names the needed input, how you can be reached, the allowed way of working and the handoff that will help. If it’s unclear who depends on you or what is allowed, the result to bring is that exact question. It is not an assumption that you can withdraw.

A note on the evidence

The studies look at outcomes that differ: how people say they present themselves, coordination, what people see as the priority, and production on particular tasks. The factory and cashier findings are about physical workplaces. Neither predicts the effect of private digital drafting.

The account of the monitoring study uses an uncorrected proof uploaded by an author. Its quality result was not statistically significant. That doesn’t show that every kind of monitoring has the same effect.

How we prepared this module

This module links survey research, qualitative research at work, a lab experiment and two studies of physical workplaces. The made-up drafting case makes the choices about who depends on you concrete. The written exercise helps you prepare a truthful account of one task and its handoff.

Sources

  • Camille Cobb, Lucy Simko, Tadayoshi Kohno, and Alexis Hiniker. (April 2020). User Experiences with Online Status Indicators. Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems, ACM, pp. 1–12. Author-hosted CHI paper; “METHOD: Participants,” PDF p. 3; “Efforts to Control OSIs,” PDF pp. 7–8; “OSIs: Leaving Users App Dependent,” PDF p. 9.
  • Bonnie A. Nardi, Steve Whittaker, and Erin Bradner. (December 2000). Interaction and Outeraction: Instant Messaging in Action. Proceedings of CSCW ’00, ACM, 79–88. Author-hosted proceedings PDF; “RESEARCH QUESTIONS AND METHODS,” p. 80; “Availability” and “Preambles,” pp. 83–84.
  • Jeffrey M. Stanton and Amanda L. Julian. (January 2002). The impact of electronic monitoring on quality and quantity of performance. Computers in Human Behavior, 18(1), 85–101. Author-uploaded uncorrected proof, version 7; §§4.1–4.3, proof pp. 6–7; §5.3, p. 10; §5.5, pp. 11–12.
  • Ethan S. Bernstein. (June 2012). The Transparency Paradox: A Role for Privacy in Organizational Learning and Operational Control. Administrative Science Quarterly, 57(2), 181–216. Author manuscript; “STUDY 2: FIELD EXPERIMENT,” manuscript pp. 20–23; learning mechanism, pp. 28–34; design limits, p. 42.
  • Alexandre Mas and Enrico Moretti. (March 2009). Peers at Work. American Economic Review, 99(1), 112–145. Author-hosted journal PDF; §IV.A, pp. 121–123; §V, pp. 133–137.