One Horizon|Docs

Private BetaStart GuideConceptsTerminologyQuick Tour
OverviewUnderstanding MetricsTeam InsightsIndividual Insights
HomeWaitlistBlog
Terms of UsePrivacy Policy

© 2025 One Horizon. All rights reserved



Team Insights

Team Insights provide a comprehensive view of your team's productivity, collaboration patterns, and overall health. These metrics help you understand how your team is performing and identify opportunities for improvement.

Work Type Distribution

Overview Chart

The work type distribution provides a visual breakdown of where your team's effort is focused:

  • Frontend: User interface and client-side development
  • Backend: Server-side logic and API development
  • Infrastructure: DevOps, deployments, and system administration
  • Documentation: Technical writing and knowledge sharing
  • New Features: Product enhancements and new functionality
  • Bug Fixes: Defect resolution and issue remediation
  • Refactoring: Code improvement without functional changes

Key Metrics

  • Feature vs. Maintenance Ratio: Balance between new development and technical debt
  • Frontend vs. Backend Balance: Full-stack development distribution
  • Infrastructure Investment: Time spent on system improvements and DevOps

Contribution Breakdowns

Interactive stacked bar charts show each team member's percentage contribution to different work types, helping identify:

  • Specialization Patterns: Who focuses on what types of work
  • Load Distribution: Whether work is evenly distributed or concentrated
  • Skill Utilization: How team expertise aligns with project needs

Language Distribution & Contributions

Programming Language Usage

Track which technologies your team actively uses, ranked by lines of code changed:

  • Primary Languages: Main technologies driving development
  • Supporting Languages: Secondary technologies and tools
  • Language Trends: Growth or decline in specific technology usage
  • Other Category: Languages with less than 1% usage grouped together

Team Member Language Contributions

Stacked bar charts reveal:

  • Language Ownership: Which team members drive specific technologies
  • Polyglot Developers: Contributors working across multiple languages
  • Knowledge Distribution: Whether language expertise is concentrated or spread

Insights for Planning

  • Resource Planning: Understanding skill requirements and capacity
  • Technical Debt: Identifying legacy technologies needing migration
  • Skill Development: Areas where team members are expanding expertise

Work Topic Distribution

Project and Functional Areas

Visual breakdown showing how effort is distributed across:

  • Major Projects: Key initiatives and feature development
  • Functional Areas: API, UI, database, security, etc.
  • Cross-cutting Concerns: Shared services, tooling, infrastructure
  • Maintenance Areas: Legacy system support and technical debt

Topic Contribution Analysis

Team member contribution charts show:

  • Project Ownership: Who leads different initiatives
  • Cross-functional Work: Contributors spanning multiple areas
  • Expertise Mapping: Subject matter experts for different domains

Focus Indicators

  • Topic Concentration: Whether team is focused on key priorities
  • Knowledge Silos: Areas with single points of failure
  • Collaborative Projects: Initiatives with broad team involvement

Activity Calendar

Daily Completion Heatmap

GitHub-style activity calendar showing task completion patterns:

  • Peak Activity Days: Periods of highest development velocity
  • Work Patterns: Weekly and seasonal rhythms
  • Consistency Indicators: Steady vs. sporadic delivery patterns
  • Team Synchronization: How aligned team work patterns are

Color-Coded Intensity

  • No Activity: Light gray for days without completed tasks
  • Low Activity: Light blue for 1-2 completed tasks
  • Medium Activity: Medium blue for 3-5 completed tasks
  • High Activity: Dark blue for 6+ completed tasks
  • Very High Activity: Darkest blue for 30+ task points

Pattern Analysis

  • Sprint Rhythms: How activity aligns with development cycles
  • Burndown Patterns: Task completion distribution throughout periods
  • Work-Life Balance: Activity outside normal business hours

Team Member Overview

Contributor Profiles

Interactive team member cards displaying:

  • Profile Information: Name, avatar, and contact details
  • Contribution Summary: Recent activity and focus areas
  • Individual Links: Direct access to personal insights
  • Team Integration: Role within current projects

Navigation Features

  • Clickable Profiles: Direct links to individual insights pages
  • Team Context: How individual work fits into team goals
  • Contribution Tracking: Quick access to member-specific metrics

Overall Team Metrics

Task Completion Summary

High-level productivity indicators:

  • Tasks Completed: Total number of day-scope tasks in the selected period
  • Weighted Score: Complexity-adjusted measure of work completed
  • Average Complexity: Typical difficulty level of team's work

Understanding Weighted Scores

Complexity weighting provides fair assessment:

  • Low Complexity Tasks: Weight of 1.0 (bug fixes, simple features)
  • High Complexity Tasks: Weight of 3.0 (architectural changes, complex features)
  • Unknown Complexity: Weight of 1.5 (tasks without explicit complexity)

Time Period Flexibility

  • Predefined Periods: Week, month, quarter, half-year, year
  • Custom Date Ranges: Specific analysis windows
  • Rolling Periods: Dynamic windows that update automatically

Team Health Indicators

Work-Life Balance Score (0-1, higher is better)

Measures sustainable work patterns:

  • Calculation: Based on tasks completed outside normal business hours
  • Healthy Range: 0.7-1.0 indicates good work-life balance
  • Warning Signs: Scores below 0.5 suggest potential burnout risk

Collaboration Index (0-1, higher indicates more collaboration)

Reflects team complexity of work:

  • High-Complexity Focus: Teams tackling challenging, collaborative problems
  • Balanced Workload: Mix of complex and routine tasks
  • Skill Development: Opportunities for growth and learning

Velocity Trend Health

Short-term velocity comparison:

  • Positive Values: Team acceleration (recent > earlier periods)
  • Negative Values: Potential slowdown requiring investigation
  • Near Zero: Consistent, sustainable delivery pace

Knowledge Risk Assessment

Risk Identification

Table showing areas with concentrated expertise:

  • High Risk Areas: Single points of failure (risk score = 1.0)
  • Medium Risk Areas: Limited expertise (risk score = 0.5)
  • Low Risk Areas: Distributed knowledge (risk score < 0.5)
  • Primary Contributors: Key people for knowledge transfer

Mitigation Strategies

  • Cross-training: Expanding expertise across team members
  • Documentation: Capturing tribal knowledge
  • Pair Programming: Spreading domain expertise

Using Team Insights Effectively

For Team Leads

  • Daily/Weekly Reviews: Monitor work distribution and activity patterns
  • Sprint Planning: Use historical data for capacity planning
  • Health Monitoring: Track work-life balance and collaboration indicators

For Engineering Managers

  • Resource Allocation: Ensure priorities align with team capacity
  • Process Improvement: Identify bottlenecks through activity patterns
  • Team Development: Use language and topic distribution for growth planning

For Product Teams

  • Feature Planning: Balance new development with maintenance work
  • Release Coordination: Understand team capacity and expertise
  • Technical Strategy: Language trends inform technology decisions

Chart Interactions

Interactive Features

  • Clickable Legends: Show/hide team members in contribution charts
  • Hover Tooltips: Detailed information on data points
  • Responsive Design: Charts adapt to different screen sizes
  • Color Coding: Consistent team member colors across all visualizations

Data Export

  • Trend Analysis: Historical data for planning and reporting
  • Cross-functional Sharing: Metrics for stakeholder communications
  • Progress Tracking: Period-over-period comparisons

Best Practices

Interpretation Guidelines

  • Focus on Trends: Look at patterns over time, not daily fluctuations
  • Consider Context: Factor in project phases, team changes, external events
  • Balanced Metrics: Use multiple indicators together for complete picture
  • Action-Oriented: Use insights to drive concrete improvements

Common Patterns

  • High Velocity + Balanced Distribution: Healthy, productive team
  • Concentrated Expertise: Opportunities for knowledge sharing
  • Consistent Activity: Sustainable delivery patterns
  • Cross-functional Contributions: Strong collaboration and flexibility

Next Steps

Want to understand individual team member contributions?

Explore Individual Insights →

Ready to dive deeper into the calculations behind these metrics?

Understanding How Metrics Work →

Remember: These metrics are meant to inform decisions, not replace human judgment. Use them as conversation starters and tools for continuous improvement.


Related Articles

Individual Insights

Understanding personal productivity, skills development, and contribution patterns.

March 28, 2025

Team Insights

Definition of each metric, how it is measured, how it is actionable.

March 28, 2025

Understanding Metrics

Technical deep-dive into how insights are calculated and what the numbers really mean.

March 28, 2025

Best Practices

General best practices for running effective meetings.

March 28, 2025
  • Work Type Distribution
  • Language Distribution & Contributions
  • Work Topic Distribution
  • Activity Calendar
  • Team Member Overview
  • Overall Team Metrics
  • Team Health Indicators
  • Knowledge Risk Assessment
  • Using Team Insights Effectively
  • Chart Interactions
  • Best Practices
  • Next Steps
  • Back to top