Handling Tasks in Teams

Organizational behavior track — practices and decisions to balance deliveries, priorities, and relationships in tech teams. This guide brings together the most common scenarios that arise in the daily life of an engineer in agile and distributed teams.

🧭 The Nature of Teamwork

Working in tech teams goes beyond writing code or delivering tasks. It involves navigating ambiguities, negotiating priorities, handling feedback, and balancing your own load with the team’s health. The ability to manage these aspects defines a high-impact professional.

Common Challenges

Challenge	What it looks like	What it really is
Tight deadline	Speed problem	Expectation and scope problem
Priority change	Interruption in the flow	Opportunity for business realignment
Vague feedback	Personal criticism	Communication gap to be filled
Overload	Lack of time	Lack of clarity on what to prioritize
Conflict with peers	Relationship problem	Opportunity for expectation alignment

📦 Managing Deliveries and Deadlines

The foundation of trust in a team is predictability. Delivering what was promised, when it was promised, is the bare minimum. But what to do when the unexpected happens?

When You’re Running Late

Scenario: You realize you won’t deliver something on time. There’s 1 day or more left.

What to do:

Communicate as early as possible — the sooner, the more options the team has.
Be specific — how much is left, what is already done, what is the realistic new deadline.
Offer alternatives — a reduced version? An MVP? Help from someone?
Use the extra time to deliver with quality — there’s no point in delivering on time with fragile code.

✅ Ideal response: Communicate early, with transparency, and propose a solution.

❌ Response to avoid: Hiding the delay, hoping to make it, and warning at the last minute.

When You Finish Ahead of Schedule

Scenario: You finished all your deliverables for the week on Friday morning.

What to do:

Take the opportunity to learn — explore something the team is considering for the future.
Pay technical debt — refine something that has bothered you for a while.
Document — create a summary of the decisions you made in the project.
Help the team — see if anyone needs extra support.

✅ Ideal response: Use the extra time to add future value, not just to “kill time”.

❌ Response to avoid: Doing nothing, or starting a new task without alignment.

Handling Open-Scope Tasks

Scenario: You have 3 tasks with the same deadline. How do you start the week?

✅ Ideal response: Ask the lead or the team which one is the most critical for the business. Then, start with that one.

❌ Response to avoid: Starting with the easiest or the most interesting one without knowing what is a priority.

💬 Communication and Alignment

Most problems in teams are not technical — they are communication problems. Knowing what to say, when to say it, and how to say it makes the difference between a team that works and a team that just survives.

What to Do When You Receive Vague Feedback

Scenario: The client says “this looks weird” without giving more details.

✅ Ideal response: Politely ask which deliverable and which specific part is causing the perception. Guide the conversation to an objective diagnosis.

❌ Response to avoid: Guessing what the person means, or ignoring the feedback until it becomes a bigger problem.

How to Handle Feedback About Your Communication

Scenario: The lead says your communication “isn’t strong enough”.

✅ Ideal response: Accept that there is a gap (even if you disagree), ask what cadence and format they prefer, and commit to testing it for a week.

❌ Response to avoid: Getting defensive, justifying your current style, or promising to improve without knowing what to change.

How to Talk About Something That Will Cause Problems in the Future

Scenario: The client asks for a solution that you know will generate technical debt in 3 months.

✅ Ideal response: Send a message before starting, explaining the risk you see and proposing an alternative. Document your concern and your solution.

❌ Response to avoid: Building it the way it was requested without warning, or building it your way and explaining later.

⚖️ Negotiating Load and Priorities

Knowing how to say “yes” is important. Knowing how to say “no” is essential.

When the Client Asks for Something Out of Scope

Scenario: The client is asking for “quick favors” out of scope, and your main deliveries are starting to get delayed.

✅ Ideal response: Send a written summary of what was added out of scope and ask the client to prioritize: what stays and what can be paused.

❌ Response to avoid: Absorbing everything in silence and letting your main deliveries slip, or refusing the next favor without explaining the accumulated impact.

When the Team Asks for Help in an Area You Don’t Master

Scenario: Three weeks after joining, the team loses someone and asks you to cover an adjacent area for 2–3 weeks.

✅ Ideal response: Say you are open, but ask for a quick chat to understand the real scope and evaluate if a specialist wouldn’t be more suitable. Then, negotiate which of your deliveries can be paused.

❌ Response to avoid: Refusing immediately, accepting without questioning and overloading yourself, or accepting and letting your main deliveries drop.

When the Team Uses an Inefficient Process

Scenario: The deployment process is losing 30 minutes per release, but no one is complaining.

✅ Ideal response: Raise the problem in the next meeting, present a proposal, and offer to solve it if there is interest.

❌ Response to avoid: Solving it alone without alignment, or ignoring it because “it’s not your job”.

🧑‍🤝‍🧑 Relationships and Team Dynamics

A team’s success depends as much on technical ability as on the health of relationships.

How to Help a Low-Performing Peer

Scenario: A peer has been delivering subpar work for weeks.

✅ Ideal response: Send a direct and kind message, asking if everything is okay and sharing what you observed constructively.

❌ Response to avoid: Ignoring it, gossiping with other peers, or escalating to leadership without talking to the person first.

When You Think Your Work Is Correct, But the Reviewer Says It’s Wrong

Scenario: A senior on the client team comments “this is wrong, redo it” without giving context.

✅ Ideal response: Acknowledge the feedback, avoid assumptions, and propose a quick call to understand what needs to be adjusted.

❌ Response to avoid: Starting to redo it without understanding what is wrong, or responding with a defensive justification.

🛠️ Checklist for Leading Effectively

Item	What to do
Align expectations	Before starting, ask what the expected outcome is and what is most important
Communicate early	If something is going to be late, let them know beforehand — not on the delivery day
Document decisions	Record the “whys” so the team understands later
Ask for help structurally	Show what you’ve already tried, what your theory is, and ask for specific support
Be a partner, not an executor	Offer solutions, don’t just ask “what to do”
Take care of the team, not just the tasks	Healthy relationships sustain consistent deliveries

🧪 Practical Challenge

Choose one of the scenarios below and answer:

You have 3 tasks for the week. One is urgent for the client, another is technically challenging, the third is easy. Which one do you start on Monday? Why?
The client asks for a feature that you know will cause performance problems in production, but they insist it is a priority. How do you approach this?
A peer consistently delivers problematic code, and the team’s quality is dropping. You are not the team lead. What do you do first?