Tracking Team Performance
Scenario: You manage a team and need to understand their productivity, identify bottlenecks, and make data-driven staffing decisions. You also need to report team performance to leadership.
The Problem
Without visibility:
- Guesswork: You think you know who's busiest, but you're just remembering who complained last
- Reactive management: You find out there's a problem when a customer complains, not before
- Unfair evaluation: Performance reviews are based on impressions, not data
- Silent bottlenecks: Queues build up without anyone noticing until it's a crisis
- No trend data: You don't know if resolution time is getting better or worse
- Leadership blind: When your boss asks "how's the team doing?", you improvise instead of showing data
How Avikto Solves It
Building Your Dashboard
You create a Team Performance Dashboard showing real-time metrics:
KPI Cards (The Pulse)
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Cases Created │ │ Cases Resolved │ │ Avg Resolution │ │ SLA Compliance │
│ 87 today │ │ 64 today │ │ 18.4 hours │ │ 94.2% on time │
│ ⬆ (from 72 last) │ │ ⬆ (from 59 last) │ │ ⬇ (from 22.1) │ │ ⬆ (from 91.1%) │
└──────────────────┘ └──────────────────┘ └──────────────────┘ └──────────────────┘
These cards show health at a glance and trend direction (up/down).
Queue Status Chart
A bar chart shows cases in each queue:
Queue Depth (What's Waiting)
─────────────────────────────
Intake: ████████ 23 cases
Triage: ██████ 18 cases
Review: ████████████ 35 cases (⚠️ HIGH)
Authorization: ███ 9 cases
Resolved: █████████████ 40 cases
You see at a glance: "Review queue is backed up. We need more reviewers or faster review time."
Resolution Time Trend
A line chart shows how long cases take over time:
Average Resolution Time (Days)
──────────────────────────────
╱
╱ ╲
╱ ╲ Target: 1.5 days
─ ╲
Week 1: 1.9 → Week 2: 1.8 → Week 3: 1.7 → Week 4: 1.6 (improving!)
You can see whether the team is getting faster or slower.
Team Member Workload
A table shows individual performance:
| Team Member | Cases Assigned | Cases Resolved | Avg Resolution | SLA Met |
|---|---|---|---|---|
| Alice | 8 | 12 | 1.2 hours | 100% |
| Bob | 10 | 8 | 2.8 hours | 87% |
| Carol | 6 | 9 | 1.4 hours | 100% |
| David | 12 | 7 | 3.1 hours | 82% |
This shows who's productive, who's struggling, and who might need help.
Drilling Down
When you see a problem (like the Review queue backed up), you can drill down:
- Click the "Review" queue bar
- See all 35 cases in Review with their age
- Identify the 5 cases that have been waiting > 2 days
- See who's assigned to Review and if they're overloaded
- Reassign or escalate as needed
Creating Custom Reports
Beyond dashboards, you build scheduled reports for different audiences:
Weekly Team Report (for your team)
Every Monday at 9 AM, the team gets a report showing:
- Cases created and resolved last week
- Average resolution time
- SLA compliance percentage
- Cases that escalated
- Top issue categories
Goal: The team sees how they're doing and any areas needing attention.
Monthly Management Report (for your boss)
Every 1st of the month, leadership gets a report showing:
- Trend: Are we getting faster or slower?
- Trend: Are SLA breaches increasing or decreasing?
- Capacity: Do we have enough people?
- Cost per case resolved (if you track cost data)
- Recommendations for staffing changes
Quarterly Stakeholder Report (for customers)
Every quarter, you send customers a report on their cases:
- Cases opened and closed
- Average resolution time
- SLA compliance
- Trend analysis
Spotting Problems Early
Your dashboard alerts you to:
- Overdue cases: Cases past their due date show in red
- Blocked cases: Cases that haven't moved in 3+ days
- Queue overflow: When Review hits 40+ cases, a warning appears
- Missed SLAs: SLA compliance drops below your target (94%)
- Slow resolution: Resolution time trends above your target (1.5 days)
Because you see these early, you can act before customers complain.
Using Data for Decisions
Example 1: Hiring Decision
Your dashboard shows:
- Cases created per week: 400
- Cases resolved per week: 350
- Backlog growing by 50 cases per week
- Average resolution time: 2.3 days (target: 1.5 days)
- Team size: 8 people
You model: "If we hire 2 more people, backlog shrinks. At current rate of 43 cases per person per week, 10 people could handle 430 cases, clearing the backlog."
You propose hiring to your boss with data, not a gut feeling.
Example 2: Process Improvement
Your dashboard shows:
- Authorization queue has average age of 4.2 days
- All other queues average 0.8 days
- Authorization is your bottleneck
You investigate and find: "Authorization requires sign-off from the CFO, who reviews emails once a day."
Solution: Create a workflow that batches authorizations and sends them to the CFO at 9 AM and 2 PM instead of one-by-one. Result: Average Authorization time drops from 4.2 days to 1.1 days.
Data shows the problem; data validates the fix.
Example 3: Team Coaching
Your team member David has:
- 3.1 hour average resolution time (vs. 1.5 hour team average)
- 82% SLA compliance (vs. 94% team average)
- 12 cases assigned but only 7 resolved last week
Rather than assume David is lazy, you:
- Check if his cases are harder (they're the same distribution as everyone else's)
- Check if he's new (nope, been here 6 months)
- Schedule a 1:1 and ask: "I notice your resolution time is higher. What's blocking you?"
David says: "I'm not sure about the authorization rules. I keep second-guessing myself."
You: Pair him with Alice (top performer) for a week. After, David's time drops to 1.8 hours and SLA jumps to 96%.
Data identified the person needing help; conversation identified the root cause; coaching fixed it.
The Result
You now:
- ✅ Know team health in real time (no more guesses)
- ✅ Spot problems before customers complain
- ✅ Make staffing decisions based on data
- ✅ Coach team members with evidence, not impressions
- ✅ Report to leadership with dashboards and trends
- ✅ Identify bottlenecks and fix them
- ✅ Track whether improvements actually work
Key Features in Action
| Feature | How it helps |
|---|---|
| Dashboards | Real-time view of team metrics and trends |
| KPI Cards | Quick pulse of health and direction (up/down) |
| Charts | Visualize trends over time (getting faster or slower?) |
| Reports | Scheduled, email-delivered insights for stakeholders |
| Drill-down | Click a problem to see the cases causing it |
| Case History | See what happened with each case (how long in each queue) |
| Notifications | Alerts when queues back up or SLAs are at risk |
| Contacts/CRM | See customer history (is this customer always problematic?) |
Next: Learn how to create and customize dashboards for your specific needs.