ITmode

How to support each other at work without distractions

Three ways to arrange support when it is hard to start a task, work through it, or see progress.

Updated 6 min read

Several profile cards connected in a dark community interface

Suppose you planned to investigate a bug this morning. You open the task, reread the comments, and check the chat. Then you answer an email and look at another project. Half an hour has passed, and you have not tried reproducing the error. Telling a colleague “I cannot get started” feels awkward: it is still your task.

You could write: “I am about to look into this error. Want to work for half an hour together, each on our own task?” Your colleague does not need to know your code or watch your screen. They can agree, suggest another time, or decline.

Support takes different forms. Today you want advice; tomorrow you want to share what finally worked. Decide whether you need help starting, solving a problem, or noticing progress. That makes it easier to explain what you need.

Start together, even on different tasks

Try arranging half an hour with someone you know at a time that suits you both. Sit at nearby desks or agree by message. If you use a call, discuss whether you need cameras and microphones; reading code while constantly talking can be difficult.

Before starting, each person names their task. You might reproduce an error using test data while your partner writes an email, reviews design feedback, or reads documentation. Each works independently, then shares a brief recap.

One slot, two different tasks
  1. Start together

    Each person names their task.

  2. Work for half an hour

    You
    Reproduce a bug
    Your partner
    Write an email

    There is no need to check on each other during the block.

  3. Finish with a recap

    What happened, and where will you continue?

This is an example arrangement. Choose the duration yourselves; screen sharing and explaining the entire task are optional.

After the first attempt, discuss whether you started, what you did, and whether conversation got in the way. If one person wanted quiet reading while the other kept asking questions, save those questions for afterwards next time.

Say what help you need

Sometimes you get started but then become stuck. If you reproduced an error without finding its cause, discuss what you checked and where you stopped.

“Help me with this bug” leaves the time commitment unclear. Does it mean checking an error message or setting aside half a day? Name the time, context, and request:

Example request

“Have ten minutes after lunch? I checked authentication and the response format, but the request still fails. I want to show what I ruled out and discuss the next check.”

Time
Ten minutes
Context
What you already checked
Request
Choose the next step

Example message · Hypothetical situation

Your colleague can decide whether to help now, suggest another time, or point you to someone who knows the code. If you do not know how long it will take, say you can start with ten minutes and decide afterwards.

Sometimes you want to talk rather than receive advice. Say so: “Can I talk for five minutes? I do not need a solution yet.” When someone asks you for support, ask whether they want to work through the problem or just talk.

Discuss what changed in the task

After half an hour, your colleague has finished their email while your bug remains. That can feel like wasted time. But you may have found when the error occurs and ruled out two causes. You now know more about where to look.

Be specific: “It is not fixed. It happens only on the repeated request; next I will check where state is stored.” A message leaves a record to return to. If you spent the block switching tabs, acknowledge that too and discuss what got in the way.

Start with three questions: what worked, where did you stop, and what comes next? Share with one person if you prefer; a public feed or ranking is optional. Minutes describe time spent, while a note describes what changed.

A three-line recap
StageNote
DoneReproduced the error on the repeated request.
StoppedHave not found the cause yet.
NextCheck where state is stored.

Hypothetical example

The task could also be a hypothesis, prototype, or client conversation. Keep what helps you continue or explain the help you need.

Leave each other room for quiet

If you keep checking messages, waiting for praise, or feeling embarrassed about your results, change the arrangement. Perhaps you meant to work quietly but now receive “How is it going?” every five minutes. Save questions for the end, share results when convenient, or take a break from the arrangement.

Agree beforehand on when to message, how much time you have, and how to cancel. “I cannot make it today” can be enough. Working together does not oblige either person to help with every task or reply immediately.

Avoid competing over hours. Your tasks, workloads, and available time differ. Twenty minutes for one person and two hours for another say little about the work’s value. Ask whether you did what you intended and whether help is needed.

Begin with one message: “Working on your tasks tomorrow? Let us start together and briefly share what happened afterwards.” Then discuss whether it suited both of you. If not, change the arrangement or leave it.

Research sources

  1. Cues of working together fuel intrinsic motivation — Priyanka B. Carr and Gregory M. Walton, Journal of Experimental Social Psychology, 2014. DOI.
  2. Does Monitoring Goal Progress Promote Goal Attainment? — Harkin and colleagues, Psychological Bulletin, 2016. DOI.