📔
Aude Product Documentation
  • Welcome to Aude
    • Why Continuous Performance Management?
  • Goals
    • Introduction
    • Personal Development Goals
    • Performance Categories
      • Microsoft's Growth Mindset Principles
      • Google's Ten things we know to be true
      • Amazon's Leadership Principles
      • Engineering Excellence
    • Defining Effective Goals and Criteria
  • Managing Aude
    • User Management
      • Managing Users
      • User Roles
    • Team Management
      • Creating and Managing Teams
    • Managing Data Sources
      • Data Sources & Integration Setup
      • Issue Tracking
        • Jira
      • Source Control
        • Github
      • Knowledge Management
        • Confluence
      • Messaging
        • Slack
          • Managing the Aude for Slack App
  • Onboarding
    • Building Better Engineering Teams Together
    • Getting Started with Aude
      • Connecting Your Engineering Tools
      • Connecting GitHub
      • Connecting Slack
      • Connecting Jira and Confluence
      • Define Your Leadership Principles
      • Invite Users
      • Setting Up Your Teams
      • Calibrating Your Performance Insights
      • Connecting GitLab (Installation Guide)
  • Information Security
    • Aude Data Retention Policy
    • Aude Service Level Agreement
    • Aude Data Portability Policy
    • Aude Data Protection Policy
Powered by GitBook
On this page
  • Organize Your Collaboration Groups
  • Team Structure
  • Common Team Configurations
  • Key Concepts
  • Best Practices
  1. Onboarding
  2. Getting Started with Aude

Setting Up Your Teams

Organize Your Collaboration Groups

Teams in Aude represent the actual working groups in your organization—the people who collaborate daily, regardless of reporting structure. While your org chart shows who reports to whom, teams show who works together.

Team Structure

Each team consists of:

  • Team Name

  • Team Leader(s)

  • Team Members

  • Team Description

Common Team Configurations

  • Project Teams (e.g., "Checkout Service Team")

  • Product Teams (e.g., "Mobile App Team")

  • Feature Teams (e.g., "Search Experience")

  • Platform Teams (e.g., "Infrastructure")

Key Concepts

  • Users can belong to multiple teams

  • Teams can have multiple leaders

  • Team membership is independent of reporting relationships

  • Performance insights are shared with team leaders

  • Teams can be time-bound (for project teams) or permanent

Best Practices

  • Mirror your actual working structure, not just the org chart

  • Create teams that align with how work gets done

  • Keep teams small enough to maintain strong collaboration (typically 5-12 members)

  • Consider cross-functional team members who regularly contribute.

PreviousInvite UsersNextCalibrating Your Performance Insights

Last updated 7 months ago