a. Embrace your unique blend of experience, skills, and strengths that you bring to the table. This will help you define your role in a team and outline your responsibilities more effectively.
b. Create a skills wish list and identify how collaborating with others can help you achieve your goals. For instance, participating in this project could lead to winning a patent, creating your own product, acquiring new skills, earning promotions, or connecting with interesting individuals who possess unique experiences.
c. Learn from everyone: recognize that the people around you are a valuable resource for learning.
d. Assume good intentions and find shared values even when opinions differ. Conflicts are inevitable in teamwork, but it’s important to remember that each team member is striving towards a shared goal in the best way possible, without undermining your expertise.
e. Let go of the need to have "all the answers". Listen and value other perspectives.

– SMART: Specific, Measurable, Attainable, Relevant, and Time-bound (with deadlines and mid-way checkpoints).

– Includes input from all team members. Listen to the team members: not all ideas can become goals, but make sure the team has provided opportunity for everyone to share their perspectives.

– Aligned with everyone in the team.

– Aligned with your stakeholders: supervisors, customers.

– Is written down in your document depository.

a. Define the necessary team roles and approximate responsibilities.
b. Distribute team roles among members.
c. Agree on final responsibilities.
d. Continuously review and adjust the objective and work steps as needed.

The role is not an official position in the company and does not come with a strict set of job responsibilities. The tasks and requirements of the role may change throughout the project as new tasks arise and requirements change. Additionally, employees may switch roles or take on multiple roles at once. For example, a software developer may also act as a Scrum Master, and a test engineer may be involved in customer research. When assigning roles, it is best to consider the personal initiative and qualities of team members, a clear understanding of the tasks involved, and selecting the most suitable candidates based on their knowledge and experience.

a. Define negotiation processes and establish binding rules for decision-making and reporting on implementation (format, frequency, countermeasures for non-compliance).
b. Agree on communication channels for online/offline group meetings.
c. Determine which questions will be settled through group or personal chat.
d. Regularly hold sync meetings to review progress and make necessary adjustments.

In conclusion, fostering true collaboration within a work team requires effort, intentionality, and a commitment to open communication and shared goals. By addressing the key challenges, setting clear goals, distributing roles and responsibilities effectively, and utilizing the right rules and tools, teams can create a collaborative environment that enhances productivity, creativity, and overall success.

Some cultures that are direct and explicit in their communication style may use indirect language when giving negative feedback, while others that are more subtle in their communication may be very straightforward when pointing out mistakes (Figure 1).

Negative feedback to a colleague is provided frankly, bluntly, honestly. Negative messages stand alone, not softened by positive ones. Absolutely descriptors are often used (totally inappropriate, completely unprofessional) when criticizing. Criticism may be given to an individual in front of a group.

Negative feedback to a colleague is provided softly, subtly, diplomatically. Positive messages are used to wrap negative ones. Qualifying descriptors are often used (sort of inappropriate, slightly unprofessional) when criticizing. Criticism is given in private.

The Evaluating dimension sheds light on how different cultures give negative feedback. For example, the Chinese manager learns never to criticize a colleague openly or in front of others, while the Dutch manager learns always to be honest and to give the message straight. Americans are trained to wrap positive messages around negative ones, while the French are trained to criticize passionately and provide positive feedback sparingly. It is crucial to be aware of these differences in order to adapt a feedback style accordingly.

One key aspect to consider is the use of upgraders and downgraders in language. Cultures that are more direct tend to intensify criticism with upgraders, such as absolutely, totally, or strongly: “This is absolutely inappropriate,” or “This is totally unprofessional.”

On the other hand, indirect cultures use downgraders to soften negativity, like kind of, sort of, a little, a bit, maybe, and slightly. Another form of downgrader is a deliberate understatement, where the speaker expresses a strong feeling in a way that tones down the emotion - for instance, saying “We are not quite there yet” instead of “This is nowhere close to complete,” or “This is just my opinion” instead of “Anyone who considers this issue will immediately agree.”

Of course, downgraders are commonly used in all societies, but some cultures rely on them more heavily than others. The British, for example, are known for their skillful use of downgraders, which can sometimes leave others confused by their communication style.

The Anglo-Dutch Translation Guide, featured in Figure 2, has been shared online without attribution in multiple iterations. It amusingly demonstrates how the British employ downgraders and the resulting perplexity this can cause for individuals from a different cultural background (specifically, the Dutch).

We can identify distinct quadrants that represent different cultural characteristics in giving negative feedback. From high-context and direct to low-context and indirect feedback styles, each quadrant requires unique strategies for effective communication with individuals from diverse cultural backgrounds.

In quadrant A, characterized by low-context and direct negative feedback, individuals value honesty and transparency in communication. Feedback is given in a straightforward manner, without the need for subtle hints or indirect messages. It is important to accept criticism positively and not take offense, as it is intended as a sign of respect for one's professionalism. However, it is advised not to try to mimic this direct style of communication if it is not natural to your own cultural background, as it may lead to misunderstandings and unintended offense.

Quadrant B represents cultures that are high-context yet direct in their negative feedback. These cultures may communicate between the lines but are sharp and direct when it comes to criticism. It is important to pay attention to the nuances of communication in these cultures to understand the underlying messages being convey.

In quadrant C, low-context and indirect negative feedback is common, individuals may find this style of feedback confusing and insincere. But representatives of this style, for example Americans, tend to balance negative feedback with positive comments, which can be perceived as exaggerated and patronizing by some European cultures. To effectively communicate with individuals from cultures that value explicit communication styles, it is important to be clear and direct in both positive and negative feedback, while also being mindful of cultural differences and showing appreciation for other perspectives.

Lastly, quadrant D cultures prefer high-context and indirect negative feedback, where criticism is delivered subtly and privately. It is important to avoid giving negative feedback in front of others, as this can lead to embarrassment or humiliation. Understanding the hierarchical structures and cultural norms of these cultures is crucial in navigating feedback interactions effectively.

Politeness can be perceived differently depending on the individual. Providing feedback, especially if it is negative, can be a delicate matter. It becomes even more challenging if the recipient feels that they have been addressed impolitely. A successful manager must be able to adjust their behaviour, show humility, gauge the situation before giving feedback, assume good intentions from others, and work on building strong relationships.By being aware of these differences and adapting communication styles accordingly, leaders can effectively motivate employees and enhance team performance.

- differing requirements on time
- varied approaches to achieving goals
- status or role discrepancies

Name: It's when one admits they've been hurt or acknowledges the experience as traumatic.
Blame: it's when the injured party believes someone else is responsible for their injure or that they are the cause of the deprivation.
Claim: the injured party communicates this finding to the guilty party. If the guilty party takes no action in response to their claims, it escalates into a dispute.

For example, let's say Sarah forgets to inform her colleague Mike about an important meeting. Mike feels excluded and accuses Sarah of not adhering to the team's communication protocol. This accusation marks the beginning of the name-blame-claim loop.

Relationship Conflict: This type of conflict arises from clashes between personalities. It's often characterized by negative interpersonal behaviors like snide remarks, avoidance, or direct arguments. While dealing with relationship conflicts can be emotionally taxing, managing them effectively can lead to positive outcomes.

Task Conflict: Task conflicts stem from disagreements regarding goals or objectives within an organization. These conflicts often involve various organizational functions, each with its own priorities and charters. However, addressing task conflicts can spark productive discussions on resource management and organizational strategies, offering valuable insights.

Process Conflict: Process conflicts emerge from disagreements over the methods used to achieve a goal. Unlike task conflicts, which focus on goals themselves, process conflicts revolve around decision-making processes. Resolving process conflicts can lead to the discovery of more efficient ways to accomplish objectives.

Status Conflict: Status conflicts revolve around disagreements over personal responsibilities within a team or organization. These conflicts commonly arise when determining leadership roles or assigning credit for accomplishments. Successfully resolving status conflicts can bring clarity to team dynamics, enabling more effective collaboration and task completion.

1. Accommodating
lose/win situation
Embracing a " I lose, you win" scenario where one party yields to accommodate the needs of the other. The accommodation strategy is employed when:

2. Avoiding
lose/lose scenario
This conflict management style involves simply disengaging from the conflict, resulting in a "lose-lose" outcome. In this case, you would continually avoid the person or the issue. This approach is most suitable:

3. Compromising
win/lose – win/lose situation
This conflict management style gives you the opportunity to seek a middle-ground solution where both parties concede and gain, resulting in a "win-lose, win-lose" situation. This conflict management style gives you the opportunity to find a middle-ground solution for everyone involved. Compromise is most effective:

4. Collaborating
win/win situation
This scenario offers mutual benefits, but it demands significant effort and cooperation to navigate through disagreements effectively. It hinges on trust and dedication from all parties to resolve issues at their core. Each party must be open to understanding and empathizing with the perspectives of others. Collaboration is best suited when:

5. Competing:
win/lose scenario
Insisting on one's own argument until it prevails, leading to a "win-lose" outcome.
This strategy is most suitable in the following circumstances:

1. Avoid Generalizations:
Instead of making sweeping statements that generalize someone's behavior, focus on specific instances and facts.

• For example, rather than saying "You always miss deadlines" , provide feedback based on specific instances, such as "This task wasn't completed by the deadline."

2. Address Issues, Not Individuals:
When addressing work-related problems, it's crucial to focus on the issue at hand rather than attacking the person. Offer constructive feedback and frame requests in a way that encourages collaboration and improvement.

• For instance, rather than questioning someone's competence, address specific gaps in their work and offer support in rectifying them.

3. Stay Focused on the Present:
Avoid bringing up past grievances or experiences unrelated to the current issue. Stay focused on addressing the immediate concern and finding a solution that benefits everyone involved.

• For example, instead of bringing up past issues like, 'Last time I had to do all the work, so now I'm going to watch how you make things work, when you have no access to data and no time!' (this focuses on past problems), it's better to ask, 'How do we share the workload for this project evenly and fairly?' (focusing on task distribution for this project only).

4. Focus on Solutions, Not Blame:
When faced with ethical violations or conflicts, prioritize finding solutions rather than assigning blame. Instead of accusing someone of misconduct, focus on addressing the issue at hand and collaboratively working towards a resolution.

• Attack: Ivan never gets any work done in the group, he just uses the results’ of other people’s work.
• Response: Can you explain specifically what you propose?

VS. I do not think it’s appropriate to discuss other people’s bahaviour in a team. We can discuss task distribution when we have a list of tasks at hand. At the moment we are discussing X, let’s get back to that.

Assess the Situation:
Understand the perspectives of both parties, identify the type of conflict, clarify the goals for resolution, and avoid generalizations.

Get Ready for the Conversation:
Approach conflict resolution with a calm mindset, clearly define expectations, consider the other party's viewpoint, plan the message thoughtfully, and choose an appropriate time and place for discussion. Conflict conversations should take place in a comfortable environment in which individuals feel able to speak freely, express emotions, and come to a mutually agreeable resolution.

Have a Productive Conversation:
Seek understanding through asking many questions, establish common ground to diffuse emotions, label the type of conflict for alignment, ask for advice from the other party to generate goodwill, acknowledge emotions without getting overly emotional, set ground rules for civil discourse, and focus on future solutions to avoid dwelling on issues from the past that cannot be changed.

Get to a Resolution and Make a Plan:
Propose creative options that meet everyone's needs, collaborate on brainstorming possibilities and seeking input from everyone involved, consider contributions from all parties, ask pertinent questions to facilitate resolution, evaluate options to choose the best solution, document agreements for clarity.

Repair the Relationship:
Reflect on progress made, adopt a solution-focused approach rather than dwelling on the past and what may or may not have gone wrong in the process, seek opportunities for positive interactions, reconnect through insightful questions, apologize if necessary without expecting reciprocity, emphasize commonalities, spend time fostering appreciation, involve others in repairing relationships, and provide constructive feedback for improvement.

Let's imagine a scenario where two colleagues, Alex and Taylor, are experiencing a conflict over the division of responsibilities for an upcoming project.

1. Assess the Situation:
Alex feels overwhelmed with their workload and believes Taylor is not pulling their weight. Taylor, on the other hand, feels they are contributing equally but perceives Alex as being controlling. The conflict seems to stem from a misunderstanding of each other's perspectives and expectations regarding their roles in the project.

2. Get Ready for the Conversation:
Both Alex and Taylor agree to meet during lunch in a neutral setting away from their desks. They come prepared with notes outlining their concerns and goals for the discussion. They commit to listening to each other's viewpoints without interruption and agree to approach the conversation with an open mind and a willingness to find a resolution.

3. Have a Productive Conversation:
During the conversation, Alex and Taylor ask probing questions to better understand each other's perspectives. They realize that their conflict arises from differing expectations about their roles and responsibilities. They acknowledge each other's emotions and express empathy towards one another's concerns. They establish ground rules for respectful communication, such as speaking calmly and refraining from personal attacks.

4. Get to a Resolution and Make a Plan:
After brainstorming various solutions, Alex and Taylor agree to reassess their project timeline and divide tasks more evenly based on their strengths and availability. They also decide to schedule regular check-ins to monitor progress and address any emerging issues promptly. They document their agreements in writing to ensure clarity and accountability.

5. Repair the Relationship:
Alex and Taylor reflect on their conversation and the progress they've made in resolving their conflict. They recognize the importance of maintaining a positive working relationship and commit to rebuilding trust and mutual respect. They apologize for any misunderstandings and express gratitude for each other's contributions. They agree to continue fostering open communication and providing constructive feedback to support each other's growth and development.

Initially developed at Intel by Andy Grove and popularized by John Doerr in Google, the OKR approach has spread globally, becoming a cornerstone of success for dynamic and innovative companies, such as Amazon, LinkedIn, and Netflix.

The process starts with defining clear objectives - well-defined tasks or goals and identifying one or more key results - specific metrics used to track the achievement of the objective. The essence of OKR is to outline how to achieve goals through specific, measurable actions. Key results can be quantified on a scale of 0-100% or in any numeric unit (e.g., dollars, percentages, units, etc.). Objectives should also be supported by initiatives - plans and activities that help achieve the objectives and advance key results.

Alignment can be vertical or horizontal:

Vertical Alignment ensures the integration of OKRs across different organizational levels so that individual employee goals align with team objectives, and team goals align with company objectives.

Vertical alignment occurs in two forms:

• W-shaped “Top-down”: Company-level OKRs are initially set, then cascaded to team levels. Teams align their OKRs with corporate objectives, after which all objectives are reviewed and adjusted if necessary, and work begins.
• M-shaped “Bottom-up”: OKRs are initially set at the team level and then reviewed at the corporate level to align with its objectives. Corporate OKRs are then established and cascaded back to the team level for final alignment before work commences.

Horizontal Alignment ensures the coordination of OKRs across different teams and/or departments within the company to synchronize efforts and avoid conflicts of interest.

OKR Cadence refers to the period during which goals and key results are established, tracked, and evaluated to synchronize efforts within a team or company.

OKRs can be annual or quarterly. Typically, OKRs follow a three-month cycle—each quarter. Progress is reviewed weekly, allowing for a concentrated focus on achieving objectives.

Criteria for OKR Setting

Objective Criteria:

• Clear, ambitious, and motivating
• Unambiguous and easy to understand
• Limit to 3-5 objectives per unit (department, team)

Key Result Criteria:

• Action-based Key Results measure the completion of tasks, stages, or project outcomes. Typically start with verbs like: launch, create, develop, deliver, compile, define, release, test, prepare, plan.
• Value-based Key Results measure outcomes of successful actions quantitatively. Typically start with verbs like: achieve (value)/ increase (range).
• Limit to 5 Key Results per objective.

Doerr’s Formula for setting OKRs is:
"We will achieve [Objective] measured by [Key Results]."

Improve the Efficiency of Training New Support Engineers:

1. Reduce the training period for interns to two months.
2. Decrease financial costs of training by 30%.
3. Achieve a trainee satisfaction score of 4.5 out of 5.
4. Maintain customer satisfaction at a level of 4.8 out of 5.

Working with OKRs makes the organization more transparent, flexible, and adaptable to changes. Consequently, employees with these qualities are more engaged in achieving organizational goals. It becomes easier to cascade objectives from overall company goals to departmental, team, and personal goals, eliminate barriers, provide feedback, and motivate the team to achieve their objectives.

The OKR Events Cycle is made up of Cadences – these are periods where goals and key results are set, tracked, and evaluated to keep everyone in sync within a team or company. There are three types of cadences: annual – for setting and executing the overall strategy, quarterly – for working on OKRs that help achieve parts of the strategy, and weekly – for checking in on the current progress of OKRs.

Start by establishing an annual cadence for strategy execution. Set long-term strategic directions and overall objectives for the year. Ensure these objectives are ambitious and inspiring, focusing on the organizational level, and that your company possesses all the necessary competencies and resources. Follow these steps:

• Define the Company's Mission and Vision: Understand clearly where the company is heading and what tasks must be accomplished.
• Formulate Annual Objectives: Outline the main strategic priorities that will guide the company's activities throughout the year.
• Establish Key Results: Set specific, measurable indicators to assess the success of achieving annual objectives, for example, through the use of the Balanced Scorecard approach.

At the start of each quarter, establish specific OKRs that will help achieve the annual strategic objectives. Follow these instructions:

• Drafting OKRs: OKRs should be defined at different levels within the company—both corporate and team levels. Each team sets its own goals and key results that need to be achieved within the quarter. Make sure these goals are ambitious but achievable, and that the key results are measurable.
• Alignment OKRs: Align objectives and key results at each level with the company's strategic directions. Ensure alignment so that every department and team works in a unified direction and achieves coordinated goals (the alignment process is explained in greater detail in Article

Conduct weekly or bi-weekly meetings to keep teams aligned and responsive to any changes. Focus these meetings on achieving key results by doing the following:

• Review Tasks and Progress: Discuss the current status of your OKRs, analyze progress, and set priorities for the next week. Keep everyone informed about the team's progress, achievements, and upcoming tasks.
• Identify Obstacles: Identify potential problems and obstacles that could hinder progress. Develop plans to overcome these challenges.
• Request assistance: If the implementation of your initiatives requires support from other teams or employees, you may present this need during the meeting.

During these check-ins, use dashboards to provide a visual overview of key metrics and progress, helping everyone see how close they are to achieving their goals. Utilize backlogs to track pending tasks and prioritize future work, ensuring alignment with objectives.

Finish the OKR cycle with a retrospective at the end of each quarter to enhance the quality of the process of working on OKRs.

• Analyze Achieved Results: Assess whether objectives and key results were met. Review which strategies and approaches were most successful and which were not.
• Identify Problems and Improvements: Discuss the obstacles encountered during the OKR cycle, and develop plans to address them in the future. Pay attention to the effectiveness of teamwork, the atmosphere and relationships within the team, the approaches used, and the quality of communication both within the team and with external stakeholders.

By following these steps, you can effectively organize and manage the OKR events cycle, ensuring that your team stays aligned and focused on achieving its objectives.

Now that we have successfully dealt with the organization of the OKR process, it's essential to define and assign key roles within the team. This helps clearly distribute responsibilities and maintain regular communication among participants.

By following these steps, OKRs become more than just a management system; they become part of the corporate culture, driving ambitious goal achievement, maintaining high employee engagement, and ensuring flexibility in changing conditions.