What is Team Radar?

Team Radar is a lightweight pulse survey tool that measures team health across six critical dimensions. Unlike heavy annual surveys, Team Radar provides quick, actionable snapshots of how your team is feeling and performing—enabling you to spot trends, address concerns early, and celebrate wins.

Why Team Radar Matters

  • Early Warning System: Catch morale or alignment issues before they become serious problems
  • Data-Driven Leadership: Make decisions based on quantified team sentiment, not guesswork
  • Psychological Safety: Anonymous mode encourages honest feedback without fear
  • Trend Analysis: Compare results over time to measure impact of changes
  • Engagement: Shows your team their voice matters and you're listening
lightbulb

Tip: Team Radar works best when run regularly (monthly or bi-weekly) to establish a baseline and track changes over time.

Getting Started

Step 1: Create a Team Radar Campaign

  1. Navigate to Team Health > Team Radar
  2. Click "New Team Radar"
  3. Give your radar a descriptive name (e.g., "Q1 2028 Engineering Team Radar")
  4. Select your template (see Template Options below)
  5. Set an optional due date for responses
  6. Decide on anonymity mode:
    • Anonymous: Responses are fully anonymous (minimum 3 responses required to view results)
    • Standard: Manager can see individual responses (minimum 5 responses to view aggregated data)
  7. Click "Create & Send" to launch the campaign

Step 2: Team Members Respond

Each team member receives an email notification with a link to submit their radar. The survey takes approximately 2-3 minutes to complete.

Respondents rate six dimensions on a scale of 1-3:

  • 1 - Disagree: Below expectations, needs improvement
  • 2 - Agree: Meeting expectations, generally positive
  • 3 - Strongly Agree: Exceeding expectations, excellent
warning

Privacy Threshold: Results won't display until the minimum response threshold is met (3 for anonymous, 5 for standard) to protect individual privacy.

Step 3: Review Results

  1. Once the minimum threshold is met, managers can view results
  2. Results include:
    • Radar Chart: Visual representation of all six dimensions
    • Trend Analysis: Delta comparison with previous radar (if available)
    • AI-Generated Insights: Automated analysis of significant changes (≥15% shift)
    • Response Distribution: Breakdown of how many people chose each score
  3. Export data for further analysis or presentations

Step 4: Close the Radar

When the survey period ends:

  1. Click "Close Radar" on the campaign card
  2. System marks the radar as Completed with a timestamp
  3. Managers receive a summary email with key insights
  4. Results are archived and serve as comparison baseline for future radars

Template Options

Team Radar offers six specialized templates, each tailored to different team contexts with contextualized dimension labels:

1. Standard Template

radar Standard

Best for: General-purpose teams across any department

Dimensions:

  • Velocity: How quickly the team delivers value
  • Fun: Team morale and enjoyment at work
  • Alignment: Clarity on goals and priorities
  • Process: Efficiency of workflows and systems
  • Role: Clarity of responsibilities and expectations
  • Communication: Information flow and collaboration quality

2. Engineering Template

code Engineering

Best for: Software engineering, DevOps, and technical teams

Dimensions:

  • Delivery speed: Sprint velocity and deployment frequency
  • Team morale: Satisfaction with technical challenges and culture
  • Technical alignment: Agreement on architecture and tech decisions
  • Development process: CI/CD, code review, and release efficiency
  • Role clarity: Understanding of technical responsibilities
  • Team communication: Standup, PR feedback, and documentation quality

3. Sales Template

trending_up Sales

Best for: Sales, business development, and revenue teams

Dimensions:

  • Sales velocity: Pipeline movement and deal closure speed
  • Team energy: Motivation and enthusiasm levels
  • Goal alignment: Clarity on quotas and targets
  • Sales process: Efficiency of CRM, handoffs, and methodology
  • Territory clarity: Understanding of accounts and ownership
  • Team collaboration: Knowledge sharing and cross-selling support

4. Support Template

support_agent Support

Best for: Customer support, success, and service teams

Dimensions:

  • Response efficiency: Ticket resolution speed and SLA adherence
  • Team well-being: Emotional health and burnout prevention
  • Priority alignment: Understanding of customer needs vs internal goals
  • Support workflow: Ticketing systems, escalation paths, knowledge base
  • Role expectations: Clarity on tier levels and responsibilities
  • Cross-team communication: Collaboration with product, sales, and engineering

5. Remote Team Template

home Remote

Best for: Distributed, hybrid, or fully remote teams

Dimensions:

  • Async productivity: Effectiveness of asynchronous work
  • Remote culture: Sense of belonging despite physical distance
  • Distributed alignment: Shared understanding across time zones
  • Remote workflows: Tools, documentation, and async communication
  • Autonomy: Clarity on remote work expectations and flexibility
  • Virtual communication: Video calls, Slack, and written communication quality

6. Leadership Template

groups Leadership

Best for: Leadership teams, executive groups, and management committees

Dimensions:

  • Strategic execution: Progress on organizational goals
  • Leadership cohesion: Trust and collaboration among leaders
  • Strategic alignment: Agreement on vision and priorities
  • Decision-making process: Speed and quality of executive decisions
  • Leadership accountability: Ownership of outcomes and follow-through
  • Cross-functional collaboration: Information sharing and department coordination

Interpreting Results

Understanding Scores

Average Score Interpretation Action
2.5 - 3.0 Excellent Celebrate wins, document what's working, share best practices
2.0 - 2.4 Good Maintain momentum, identify small improvements
1.5 - 1.9 Needs Improvement Schedule 1:1s, gather qualitative feedback, create action plan
0.0 - 1.4 Critical Concern Immediate intervention required, team meeting, escalate to leadership

Reading AI-Generated Insights

When a dimension changes by ≥15% compared to the previous radar, the system generates contextual insights:

trending_up

Velocity improved by 18%

Great progress! Consider: What changed? New processes? Better tools? Document these wins and share with other teams.

trending_down

Communication dropped by 22%

Needs attention! Consider: Are meetings effective? Is information siloed? Schedule a team retro to identify blockers.

Trend Analysis

The delta comparison shows both absolute change (+0.5) and percentage change (+25%) for each dimension:

  • Positive delta: Dimension improved since last radar
  • Negative delta: Dimension declined since last radar
  • No delta: First radar or no significant change

Best Practices

Frequency & Timing

  • Monthly cadence: Ideal for most teams—enough time for trends to develop without losing momentum
  • Bi-weekly cadence: For fast-moving teams or during major transitions
  • Quarterly cadence: Minimum frequency to maintain meaningful trend data
  • Consistent timing: Run radars on the same day (e.g., first Monday of each month)

Maximizing Participation

  • Set clear deadlines (typically 3-7 days from launch)
  • Send reminder emails midway through the survey period
  • Block 5 minutes in team meetings for everyone to complete it together
  • Explain how results will be used (transparency drives engagement)
  • Share previous insights and actions taken to prove you're listening

Acting on Results

  1. Within 48 hours: Review results and identify top 1-2 concerns
  2. Within 1 week: Share high-level results with the team (celebrate wins, acknowledge concerns)
  3. Within 2 weeks: Hold a team discussion or retro to gather qualitative context
  4. Within 1 month: Implement at least one concrete change and communicate it
  5. Next radar: Reference previous issues and show progress
warning

Warning: Running radars without acting on results is worse than not running them at all. It signals that leadership doesn't care about feedback.

Communication Guidelines

  • Don't: Blame individuals or hunt for "who said what" (even in standard mode)
  • Don't: Dismiss low scores as "just complaining" or "people being negative"
  • Don't: Only focus on problems—celebrate improvements too
  • Do: Present results objectively with context
  • Do: Ask for input on solutions (don't assume you know the fix)
  • Do: Follow up and close the feedback loop

Privacy & Anonymity

Anonymous Mode

  • Response tracking: System records that someone responded, but not their specific answers
  • Minimum threshold: 3 responses required before results display
  • No individual data: Only aggregated scores visible
  • Best for: Teams with trust issues, new teams, or sensitive topics

Standard Mode

  • Response tracking: Manager can see individual scores
  • Minimum threshold: 5 responses required for aggregate view
  • Individual visibility: Useful for targeted 1:1 follow-ups
  • Best for: High-trust teams, smaller teams, or when follow-up conversations are needed

Data Security

  • Responses stored in encrypted database
  • Access limited to team managers and account admins
  • Audit trail tracks who closed each radar campaign
  • Data retention follows company data retention policy

Frequently Asked Questions

Can I customize the dimensions?

Not currently. The six dimensions are based on research and best practices. However, you can choose from six templates that contextualize labels for different team types.

What if my team is too small to meet the minimum threshold?

For teams with fewer than 3 people, consider:

  • Using Team Radar at the department level instead
  • Running in standard (non-anonymous) mode with full transparency
  • Using 1:1s for feedback instead of surveys

How do I handle consistently low scores?

  1. Don't panic: Low scores are data, not personal failures
  2. Seek context: Hold team discussion to understand root causes
  3. Prioritize: Don't try to fix everything at once
  4. Co-create solutions: Involve team in designing improvements
  5. Track progress: Use subsequent radars to measure impact
  6. Escalate if needed: Some issues require organizational support

Can I compare results across teams?

Yes! Account admins can view the Executive Dashboard which shows:

  • Average scores across all teams
  • Team-by-team comparison
  • Organization-wide trends
  • Outlier detection (teams significantly above/below average)

What happens to old radars?

Completed radars are archived and remain accessible for historical comparison. They serve as baseline data for trend analysis in future radars.

Can I edit a radar after it's been sent?

No. Once a radar is launched, settings are locked to preserve data integrity. If you need to make changes, close the current radar and create a new one.

Who receives notifications?

  • On creation: All team members receive an email invitation
  • Reminders: Non-responders receive reminder emails (if enabled)
  • On completion: Manager receives summary email with insights
  • Activity feed: Team members see radar events in their activity stream
help_outline

Still have questions? Contact support at [email protected] or visit our Help Center.

Next Steps