# Teamwork at Work — Stand-ups, Code Review Etiquette, Feedback and Working with Your Manager

Source: https://skills101.in/learn/professional-skills/teamwork-code-review-feedback — Skills101 free tutorial (Professional Skills). Updated 2026-11-21.

In college, most work is individual: your exam, your marks, your assignment. At work, almost nothing ships without other people — designers, testers, other developers, product managers and your manager. Engineers who are pleasant and dependable to work with get better projects, more help and faster promotions. This lesson covers the everyday habits that make you that person.

## 1. Daily stand-ups

Many teams meet for 10–15 minutes each morning (a **stand-up**). Each person usually answers three questions:

1. What did I finish yesterday?
2. What will I do today?
3. Is anything **blocking** me?

A good update is short and specific:

> "Yesterday I finished the login timeout fix; it's in review. Today I'll start the password-reset email. I'm blocked on the email API key — Neha, could you help after this?"

Avoid long technical discussions in the stand-up. Say "Let's discuss after the call" and continue — it respects everyone's time.

## 2. Code reviews: giving comments

In most teams, every change is reviewed by another developer through a **pull request** (PR). Reviews catch bugs and spread knowledge — but badly written comments hurt people and slow the team.

![Unhelpful versus helpful review comments: "This is wrong" versus "This fails when the list is empty: add a check?"; "Bad name" versus "Could total be cartTotal? It's used in 3 places"; "Why did you do this?" versus "Curious why a loop here; would a map be simpler?"](https://skills101.in/learn-img/professional-skills/review-comments.svg)

Good review comments:

- **Comment on the code, not the person**: "This function…" not "You always…".
- **Explain why**: point to the bug, the risk or the rule.
- **Suggest, don't command**: "Could we…?", "What do you think about…?"
- **Mark small things as small**: "Nit: extra blank line." So the author knows what really matters.
- **Praise good work** too: "Nice, this test covers the edge case well."

## 3. Code reviews: receiving comments

Your code will get many comments, especially early on. That is normal and is one of the fastest ways to learn.

- Remember: **the review is about the code, not about you.**
- Thank the reviewer and **reply to every comment** — fix it, or explain politely why you chose differently.
- If you don't understand a comment, ask: "Could you show an example of what you mean?"
- Keep PRs **small** (a few hundred lines at most where possible). Small PRs get faster, better reviews.
- Write a clear PR description: what changed, why, and how you tested it.

## 4. Giving and receiving feedback

Outside code, you'll give and receive feedback on behaviour and work. A simple, respectful format for giving it is **SBI**:

- **Situation:** "In yesterday's client demo…"
- **Behaviour:** "…you explained the payment flow very clearly, but skipped the error case they asked about."
- **Impact:** "…so the client asked again by email, and it delayed their approval."

It describes facts, not personality ("you are careless"). When receiving feedback:

- **Listen fully** without defending yourself immediately.
- Ask for an example if it's unclear.
- Say thank you, decide what you'll change, and later show that you changed it.

Ask for feedback yourself, regularly: "Is there one thing I could do better in my PRs?" People who ask improve faster — and managers notice.

## 5. Working with your manager

Your manager decides much of your work and your growth. Make their job easy:

- **Understand expectations:** what does "done" mean for this task? By when? What's the priority?
- **Give updates before they ask**, especially about risks: "This may slip by a day because the API changed."
- **Bring options, not only problems:** "The library doesn't support X. We can write a small wrapper (2 days) or switch libraries (4 days). I suggest the wrapper."
- Use **one-on-one meetings** to discuss your growth, ask for feedback and raise concerns.
- Keep a short list of what you've done each week — it helps in reviews and appraisals.

## 6. Disagreements

Disagreeing is healthy; how you do it matters.

- **Disagree about ideas, with reasons and data**, not with emotion: "I think caching here could show stale prices; here's the case I'm worried about."
- Listen to understand the other view — they may know something you don't.
- If you can't agree, **escalate the decision politely**, not the conflict: "Let's ask the tech lead which risk matters more."
- Once a decision is made, **commit to it** even if it wasn't your choice ("disagree and commit").

## 7. Owning mistakes

Everyone breaks something eventually — a failed deployment, a bug in production, a missed deadline. What builds trust is how you respond:

1. **Tell people quickly** — hiding a problem makes it much worse.
2. **Help fix it** first; discuss causes after.
3. **Explain what happened and what you'll change** so it doesn't repeat.

Many good teams run "blameless" reviews after incidents: they focus on fixing the process, not punishing a person. Being honest early is always respected.

## Common mistakes

- Long, rambling stand-up updates — or hiding blockers.
- Harsh or vague review comments ("This is bad").
- Treating review comments as personal attacks, or ignoring them.
- Huge PRs that nobody can review properly.
- Surprising your manager with bad news at the deadline.
- Hiding mistakes.

## Quick recap

- Stand-up: **yesterday, today, blockers** — short and specific.
- Review comments: about the **code**, explain **why**, **suggest**, mark nits, praise good work.
- Receive reviews and feedback **calmly**, reply to everything and keep PRs small.
- Feedback format **SBI**: Situation, Behaviour, Impact.
- Update your manager early, bring **options**, disagree with **reasons** — and **own mistakes** quickly.


Practice quiz and free certificate: https://skills101.in/learn/professional-skills/teamwork-code-review-feedback