The success of a 360-degree evaluation largely depends on how the relationship network is designed. A poorly constructed relationship map can lead to distorted results, dissatisfied employees, and an ineffective evaluation process.

This guide explains how to design evaluation relationships professionally so you gain a truly objective and comprehensive view of each employee’s performance.

Why the Relationship Network Is Critical

The essence of a 360-degree evaluation is collecting feedback from multiple perspectives. Relying only on direct working relationships is not enough. To get a complete picture, more distant—but still relevant—connections must also be included.

Core Principles

Minimum Requirements

Each evaluated employee should have at least five evaluators:

• At least one manager (direct or higher-level)
• Three to four colleagues (direct and indirect working relationships)
• Subordinates, if applicable

Types of Relationships

Direct working relationships include colleagues who work together daily, people involved in the same projects or workflows, and the direct manager.

Indirect but relevant relationships include colleagues who collaborate occasionally, cross-functional team members, and employees from other departments whose processes intersect.

Hierarchical relationships include direct subordinates, indirect subordinates (in leadership roles), and higher-level managers beyond the direct supervisor.

Step-by-Step: Setting Up Relationships

Step 1: Map the Organizational Structure

Start by identifying the formal hierarchy, then map informal working relationships. Review project teams and workgroup memberships to understand how people actually collaborate.

Step 2: Define the Minimum Relationship Network

For each evaluated employee, include:

• the direct manager
• two to three close colleagues they work with daily
• one to two more distant colleagues they interact with regularly
• all subordinates, if any
• optionally, a higher-level manager if they have visibility into the employee’s work

Step 3: Add Cross-Functional Relationships

Do not limit the evaluation to the employee’s own department.
If someone regularly collaborates with IT, Finance, or Marketing, include those colleagues they communicate with most often.

If the employee participates in cross-functional projects, project team members can provide highly valuable feedback.

For internal service roles such as HR or IT support, include a few internal “customers” as evaluators.

Step 4: Check Balance

Too many or too few evaluators can both cause problems.

The ideal range is five to twelve evaluators per person.
More than fifteen creates unnecessary administrative burden.
Fewer than five will not produce representative results.

Step 5: Involve Employees

A proven best practice is asking employees to nominate three to five colleagues they work with most closely. This often reveals important relationships that are not visible on the formal organizational chart.

The final relationship map should always be approved by HR or the system administrator, but employee input is highly valuable.

Common Mistakes and How to Avoid Them

Following only the formal hierarchy
Informal working relationships are often more influential than formal ones. Relying only on the organizational chart means losing valuable cross-functional and project-based feedback.
Solution: map informal networks and ask employees and managers directly.

Too narrow or too broad a network
Too few evaluators are not representative, while too many create excessive workload and frustration.
Solution: stay within the five to twelve evaluator range.

Only close colleagues provide feedback
This removes the broader organizational perspective.
Solution: include one or two colleagues who work with the employee occasionally but meaningfully.

Not enough managers included
Manager feedback is essential for understanding strategic alignment and long-term performance.
Solution: include at least one manager, ideally one or two.

Missing subordinate feedback for leaders
Leadership effectiveness is best judged by direct reports.
Solution: if subordinates exist, they must always be included.

Special Cases

New hires
Employees with less than three months at the company, or still in probation, should generally be excluded from performance evaluation until they have sufficient experience.

Remote or hybrid employees
Mapping cross-functional relationships becomes even more important. Include colleagues they interact with primarily online, and consider time zones and communication channels.

Practical Setup Tips

Start with managers, as they have the best overview of organizational relationships.
Document the rationale if someone has an unusual relationship map, such as project-based cross-functional work.
Prepare relationships at least one week before the evaluation starts, not on launch day.
Review the relationship map regularly, as organizational structures and collaborations change over time.

Administrator Checklist

Before launching an evaluation cycle, confirm for each employee:

• at least five evaluators are assigned
• at least one manager is included
• all subordinates are included if applicable
• at least one or two occasional but relevant collaborators are included
• the mix of managers, peers, and subordinates is balanced
• relationships are genuinely work-related, not only formal hierarchy
• the evaluator count is not excessive and not too low

Summary

A well-designed relationship map is the foundation of an effective 360-degree evaluation. An ideal network:

• includes at least five evaluators (ideally five to twelve)
• always includes managerial feedback
• covers both direct and indirect working relationships
• includes subordinates whenever applicable
• accounts for cross-functional collaboration
• remains balanced by role and perspective

Following these principles ensures an objective, reliable, and truly 360-degree view of employee performance, forming the basis of a fair and effective evaluation system.