Feedback and Team Development — Business Communication & Negotiation

Introduction: Continuous Feedback Culture

Feedback is information about the outcomes of actions provided with the aim of improving future results. In the context of team management, feedback is one of the most powerful tools for employee development and increasing team effectiveness.

However, in most organizations, feedback works inefficiently. According to Gallup, only 26% of employees believe that the feedback they receive helps them perform better. The rest perceive it as a formality, criticism, or even a threat. This does not mean that feedback does not work; it means that most managers do not know how to give it properly.

Continuous feedback culture is an organizational environment where feedback is a norm, not an exception. In such a culture:

Feedback is given regularly (daily or weekly), not just once a year.
It is two-way—not just from manager to subordinate, but also vice versa, and among colleagues.
It is perceived as a gift and an opportunity for growth, not as punishment.
A safe environment allows people to speak honestly, without fear of consequences.

Feedback Models

SBI (Situation — Behavior — Impact)

SBI is one of the simplest and most effective feedback models, developed by the Center for Creative Leadership.

Situation: Describe the specific situation—when and where did the event you are discussing happen? This creates context and helps the person recall the moment.

Example: “At yesterday’s client presentation…”

Behavior: Describe the specific observable behavior—what the person did or said. Important: describe behavior, not evaluation. Not “you were unprofessional,” but “you interrupted the client three times during their question.”

Example: “…you responded to the client’s objection with concrete figures and cases from our portfolio…”

Impact: Describe the impact of this behavior—on you, the team, the outcome. This helps the person understand why their behavior matters.

Example: “…and this convinced the client—they agreed to a pilot project. Your preparation was a key factor.”

Full example of positive feedback using SBI: “During yesterday’s client presentation (S), you addressed the objection about cost with concrete ROI calculations and examples from similar projects (B). This dispelled the client’s doubts, and they agreed to the next step—a pilot project (I). Great job!”

Full example of constructive feedback using SBI: “At this morning’s standup (S), you reported the project delay only after the project manager asked (B). Because of this, we found out about the problem three days late and couldn’t reallocate resources in time (I). Can we discuss how to set up earlier communication?”

STAR (Situation — Task — Action — Result)

The STAR model is similar to SBI but more detailed and often used in performance reviews:

Situation: Description of the situation and context. Task: What task was the person assigned. Action: What specific actions were taken. Result: What result was achieved.

Feedforward

Feedforward (Marshall Goldsmith) is an alternative approach to feedback that focuses not on the past (what was done wrong), but on the future (what can be done better).

Principles of feedforward:

Instead of “Last time you did X wrong” → “Next time, try Y.”
Focus on development, not critique.
Reduces defensive reaction, because it doesn’t “attack” past behavior.
Can be used even between people who don’t know each other well.

Feedforward example: “For the next presentation, I suggest starting with a two-minute story about the client’s problem in their own words—this will immediately show that we understand their situation and build trust.”

1-on-1 Meetings

1-on-1 is a regular meeting between a manager and each team member. This is arguably the most important people management tool.

Structure of an Effective 1-on-1

Frequency: Weekly or every two weeks. For new employees, weekly is mandatory. Duration: 30–60 minutes. Owner of the agenda: The employee. It is their meeting, not yours.

Typical structure:

1. Check-in (5 min): How are things? How’s your mood? Is there anything important you want to discuss? This informal block shows that you care about the person, not just their work.

2. Priorities and Progress (10–15 min): What are you working on? What achievements this week? What’s planned for next week? Are there blockers I can help with?

3. Feedback (5–10 min): What I noticed—both positive and constructive. What would you like to discuss? Do you have feedback for me?

4. Development (5–10 min): Progress on the development plan. What skills do you want to develop? Do you need resources? Career goals.

5. Miscellaneous (5 min): Other topics the employee wants to discuss.

Mistakes in 1-on-1

Turning into a status update: 1-on-1 is not a report about completed work. Task statuses can be tracked in a tracker.
Canceling when “busy”: 1-on-1 is sacred time. If you regularly cancel—it signals to the employee that they are not a priority.
Only negative feedback: If the employee associates 1-on-1 with criticism, they’ll fear these meetings.
Manager monologue: Ideal ratio: manager speaks 30%, employee—70%.

Performance Review

Performance Review is a formal evaluation of an employee’s results over a certain period (usually half-yearly or yearly).

Modern Approaches to Performance Review

Traditional annual reviews are increasingly replaced by more flexible systems:

Continuous Performance Management: Regular feedback + quarterly check-ins instead of a single large annual review.

OKR-based review: Evaluation is tied to achieving OKRs (Objectives & Key Results). Transparent, measurable, focuses on results.

360-degree feedback: Feedback is collected not only from the manager but also from colleagues, subordinates, clients. Provides a fuller and more objective picture.

Calibration sessions: Managers at the same level jointly discuss the ratings of their employees to ensure fairness and consistent standards.

Difficult Conversations

One of a manager’s hardest tasks is conducting difficult conversations: about termination, underperformance, conflicts. Avoiding these conversations leads to worsening situations.

Conversation about Underperformance

Preparation:

Gather specific facts and examples (dates, metrics, incidents).
Identify the root cause: the employee cannot (lacks skills) or does not want (lacks motivation)?
Prepare an improvement plan (Performance Improvement Plan—PIP).

Structure of the conversation:

Clearly and directly state the issue: “I want to discuss your work over the past month. I’ve noticed results are below expectations.”
Provide specific examples (SBI): “The last three reports contained data errors noticed by the client.”
Listen to the employee’s perspective: there may be reasons you are unaware of (personal problems, lack of resources, unclear requirements).
Jointly develop an improvement plan with specific goals, deadlines, and support.
Set a date for the next check-in.

Conversation about Termination

Be direct and brief: “I have decided to part ways.” Don’t prolong the preamble.
Explain the reasons succinctly and factually.
Show empathy, but be firm: the decision is final.
Explain next steps (compensation, timeline, handover).
Don’t discuss the decision—it has already been made.

Conflict Management

Don’t ignore conflict—it will not resolve itself.
Listen to both parties separately, then together.
Focus on interests, not positions.
Help find a mutually beneficial solution.
Record agreements and monitor implementation.

Coaching vs Mentoring vs Managing

Three roles a manager can play in an employee’s development:

Coaching

Approach: Helping a person find the solution themselves through questions, not advice. When to use: When the employee can find the answer themselves but needs a structure for thinking. Key tools: Open questions (GROW model: Goal — Reality — Options — Will). Example: Instead of “You need to do X” → “What result do you want to achieve? What options do you see? Which seems most promising?”

Mentoring

Approach: Passing on experience and knowledge from a more experienced person. When to use: When the employee needs experience they don’t yet have—career growth, navigating the organization, developing in a new area. Key tools: Stories from personal experience, advice, introductions, role modeling. Example: “When I was in your position, I encountered a similar situation. Here’s what worked for me…”

Managing

Approach: Setting tasks, monitoring results, providing resources. When to use: For routine management of work, prioritization, coordination. Key tools: Goal setting, delegation, feedback, performance review. Example: “For this project, the priorities are as follows… The deadline… Let’s define milestones.”

An effective manager switches between the three roles depending on the situation and employee needs. Typical mistake: only using managing, ignoring coaching and mentoring.

Team Development Stages (Tuckman Model)

Bruce Tuckman (1965) described four stages any team goes through:

Forming

The team has just assembled. People get acquainted, act politely, avoid conflict, rely on the leader.

Characteristics: Politeness, caution, uncertainty, dependence on the manager, low productivity. Leader’s role: Directive style (S1). Clear goals, rules, expectations. Help with introductions and relationship building.

Storming

Conflicts begin—over roles, influence, work approaches. People show their personalities, disagreements and frustration arise.

Characteristics: Conflicts, competition, disappointment, resistance, low (or declining) productivity. Leader’s role: Coaching style (S2). Help resolve conflicts, establish norms, explain “why” and “what for”. Normalize conflicts: “This is a normal stage; we’ll get through it.”

Important: many teams “get stuck” at this stage or fall apart. The leader’s task is to lead the team through storming, not suppress conflicts (suppressed conflicts return).

Norming

The team develops common norms, values, and working rules. People begin to understand and accept each other, learning to collaborate.

Characteristics: Cohesion, trust, collaboration, established processes, rising productivity. Leader’s role: Supporting style (S3). Facilitation, support, encouragement of initiative. Transfer responsibility to the team.

Performing

The team operates as a unified mechanism. High autonomy, mutual trust, focus on results. Conflicts are resolved constructively, without leader involvement.

Characteristics: High productivity, autonomy, interdependence, proactivity, satisfaction. Leader’s role: Delegating style (S4). Minimal intervention, strategic direction, shielding the team from external disruptions, ensuring resources.

Not all teams reach the Performing stage. It requires time, effort, and skilled leadership.

Psychological Safety (Amy Edmondson)

Psychological safety is the belief of each team member that they won’t be punished or humiliated for:

Asking a “stupid” question
Admitting a mistake
Proposing an unconventional idea
Expressing disagreement with the majority or manager’s opinion
Asking for help

The Project Aristotle study (Google) showed that psychological safety is the number one factor determining team effectiveness—more important than skills, experience, or resources.

How to Create Psychological Safety

1. Response to mistakes: When an employee makes a mistake, your reaction sets the level of safety in the team. If you respond with criticism and punishment—people will begin to hide mistakes. If you respond with curiosity (“What can we learn from this mistake?”)—people will be open.

2. Modeling vulnerability: Admit your own mistakes first. “I messed up prioritization in the last sprint. Here’s what I plan to change.”

3. Invitation to participate: Actively seek opinions, especially from quiet team members. “Maria, what do you think? Dmitry, what risks do you see?”

4. Gratitude for honesty: When someone voices an unpopular opinion or points out a problem—thank them: “Thanks for raising this issue. It’s important.”

5. No-blame culture: Focus on solving the problem and learning, not on finding someone to blame. Blameless postmortems after incidents.

Team Health Check

Team Health Check is a regular assessment of the team’s “health” across various parameters. A popular model is Spotify Team Health Check, which evaluates the team in categories:

Mission: Do we understand why we exist and what value we create?
Speed: Do we deliver results quickly?
Quality: Are we proud of the quality of our work?
Fun: Do we enjoy working together?
Learning: Are we constantly learning and improving?
Support: Do we get the support we need from leadership and other teams?
Teamwork: Do we interact effectively with each other?
Pawns/Players: Do we control our work (players) or are controlled (pawns)?

Each parameter is evaluated on a traffic light principle: green (everything is great), yellow (there are manageable problems), red (serious issue). Results are discussed by the team, and action items are developed for red and yellow zones.

Retrospectives

Retrospective is a structured meeting for the team to analyze the past period (sprint, project, quarter) with the goal of continuous improvement.

“Mad, Sad, Glad” Format

Mad: What annoys us and hinders our work?
Sad: What makes us sad, what didn’t work?
Glad: What makes us happy, what worked well?

“Start, Stop, Continue” Format

Start: What should we start doing?
Stop: What should we stop doing?
Continue: What should we keep doing?

Principles of an Effective Retrospective

Regularity: Hold retrospectives regularly (every 2–4 weeks), not just after failures.
Safety: The retrospective is a no-blame zone. Everything said is aimed at improvement, not finding scapegoats.
Concrete action items: Each retrospective must conclude with concrete actions with responsible people and deadlines. Not more than 2–3 action items—otherwise, nothing will get done.
Follow-up: At the next retrospective, check whether the previous action items were completed. Otherwise, retrospectives turn into “talks about nothing.”
Facilitation: Use a facilitator (on rotation) who manages the process, keeps time, and involves all participants.

Practical Assignments

Assignment 1

Question: You are the manager of a seven-person team. One of your best developers, Andrey, has started making coding mistakes over the last two months, missing deadlines and appearing withdrawn at meetings. His colleagues are complaining that they have to redo his work. Previously, Andrey was one of the best in the team for two years. Prepare: (1) a scenario of a 1-on-1 conversation with Andrey using the SBI model and a coaching approach; (2) action plan options depending on the reasons identified.

Solution:

Preparation for 1-on-1:

Gather specific facts: what mistakes, which deadlines were missed, when did the decline begin.
Don’t make assumptions about reasons—the conversation’s purpose is to find them out.
Mindset: care and support, not criticism. Andrey is a valuable team member with a two-year excellent track record.

Conversation scenario:

Beginning (establishing a safe atmosphere): “Andrey, hi! How are you? How’s everything in general? I wanted to talk to you—not as a boss, but as someone who cares. We have a good working relationship, and I value you in the team.”

Feedback using SBI: “I’ve noticed something over the past two months and want to talk openly with you. Last week at code review (S), three critical errors were found in the authorization module that you would’ve definitely caught yourself before (B). This caused Maria to spend half a day fixing them, and we delayed release by two days (I).

Also, over the last month, two deadlines were missed—the client report and API integration. This puts pressure on the whole team.

I want to emphasize: for two years you’ve been one of the best on the team, and I know you’re capable of excellent work. So I’m concerned—has something changed?”

Coaching block (listening): Let Andrey speak out. Possible causes:

Personal problems (family, health)
Burnout
Job dissatisfaction (boredom, no growth)
Conflict with a colleague
Problems with new technologies/tasks

Use open questions:

“Tell me, how have you been feeling at work lately?”
“What has changed over these months?”
“What would help you return to that peak state?”
“Is there something I, as manager, can change?”

Action plan options:

If the cause is burnout:

Offer a vacation (1–2 weeks) for recovery.
Temporarily reduce workload—reassign some tasks.
Review task allocation: maybe Andrey does too much routine work.
Discuss work-life balance: any overtime?
Offer a new interesting project after recovery.

If the cause is boredom/no growth:

Discuss career goals: where does he want to grow?
Suggest a tech lead or mentor role for newcomers.
Give opportunity to explore a new technology and do an internal presentation.
Jointly create a six-month development plan.
Suggest participation in conferences/training.

If the cause is personal problems:

Show empathy and support.
Suggest flexible schedule or remote work.
If appropriate—offer help (EAP—Employee Assistance Program, if available).
Temporarily lower expectations and workload.
Agree on regular check-ins for monitoring.

If the cause is conflict with a colleague:

Listen to both sides.
Arrange mediation.
Review task/project allocation if needed.
Set clear collaboration rules.

Conversation conclusion: “Andrey, thanks for sharing. I want you to know: we’re a team, and I’m here to help. Let’s define concrete steps we can take right now and meet in a week to check on things. You’re a valuable team member, and we’ll find a solution together.”

Assignment 2

Question: Your six-person team is stuck at the Storming stage (per Tuckman’s model). Symptoms: two employees (Alexey and Olga) constantly conflict over architectural approaches; the rest avoid expressing opinions at meetings; decisions are made slowly due to lack of consensus; one employee (Dmitry) is considering leaving. Develop a plan to move the team from Storming to Norming, including concrete actions over the next 4 weeks.

Solution:

Diagnosis: The team is at Storming—conflict over influence and approaches. It’s a normal but painful stage. Key issues: open conflict Alexey–Olga, silence from others (suppressed opinions → lower engagement), lack of decision norms, risk of losing Dmitry.

Week 1: Stabilization and Individual Work

Days 1–2: Individual 1-on-1s with everyone:

With Alexey and Olga: listen to each position without judgment. Understand the root cause (technical disagreements? personal dislike? status struggle?). Convey: “Conflict of ideas is normal and helpful. Personality conflict is destructive. We need to turn the first into the second.”
With Dmitry: “I know the atmosphere is tough now. Tell me, what’s bothering you? What needs to change for you to be comfortable staying? I value you in the team and want you to stay.”
With others: “I’ve noticed you speak up less at meetings. What’s holding you back? Your opinion is important to the team.”

Day 3: Team “Rules of the Game” session (2 hours):

Goal: jointly develop norms and working rules for the team.
Format: facilitated discussion.
Topics for discussion:
1. How do we make decisions? (Consensus? Voting? Leader’s call after discussion?) → Agree on a process.
2. How do we debate disagreements? (Rules: criticize ideas, not people; listen to the end; argue with data)
3. How do we give feedback? (Using SBI model, timely, constructive)
4. What is unacceptable? (Personal attacks, sabotage, silent dissent)
All norms are documented in writing and posted in a visible place (online—pinned message).

Week 2: Resolving Alexey–Olga Conflict

Hold a mediated Alexey–Olga meeting (1.5 hours):

Rules: each speaks in turn, no interruptions, focus on interests, not positions.
Each describes their position and explains why they think it’s right.
Together, determine: what is common in their approaches? Where are actual points of disagreement?
For each disagreement—find a compromise or run an experiment (try both approaches on small tasks and compare results).
Agree on a constructive format for future debates.

Meanwhile: create a “safe space” for others:

At team meetings, use “round robin”—each speaks in turn.
Send agenda before meetings and ask for written opinions.
Anonymous survey: “What change would make you happiest in the team?”

Week 3: Building Trust

Team exercise “Personal Maps” (1 hour): each shares: where they’re from, hobbies, motivation, annoyances. Goal: see each other as people, not just coworkers.

Joint mini-project (2–3 days): assign the team a task requiring close cooperation from all. Purposefully mix Alexey and Olga in one subgroup with specific roles. Goal: show they can work productively together.

Retrospective (1 hour): “Start, Stop, Continue”—what’s changed in 3 weeks? What’s working? What needs more improvement? Mark progress, even small.

Week 4: Consolidation and Transition to Norming

Repeat check-in 1-on-1s with all—how has the atmosphere changed? What else is needed?
Formalize the decision-making process for architecture: introduce ADR (Architecture Decision Records)—each decision is documented with arguments “for” and “against”. This depersonalizes discussions.
Introduce rotation of meeting facilitator—each takes turns leading meetings. This distributes “power” and involves everyone.
Plan a team retreat (offline if possible)—informal time together accelerates trust building.
Agree on regular retrospectives (every two weeks) as a mechanism for continuous improvement.

Success metrics (after 4 weeks):

Dmitry decides to stay.
Alexey and Olga discuss disagreements constructively without personal attacks.
All team members speak up at meetings.
Decisions are made within the agreed process without delays.
The team starts forming common norms and “rituals” (signs of transition to Norming).