What Horizon Is For
Horizon is the leadership view for understanding where operational pressure is building across a workspace. Use it to see pod health, strategist load, unresolved fire pressure, and the areas that need escalation before they become client-facing problems.
- Review workspace, pod, or solo-strategist health from one place.
- Find overloaded members before Fire work becomes invisible.
- Drill from agency view into pods, members, and managed brands.
- Use top alerts to decide where leadership attention should go first.
- Spot data-quality gaps that may make load or assignment reporting incomplete.
Recommended Workflow
- 1Start with the current scope description to confirm whether you are viewing the whole workspace, one pod, or your own strategist view.
- 2Check the health score and zone before looking at individual cards.
- 3Read Top Alert when it appears; it summarizes the highest-priority risk in the current view.
- 4Use the metric cards to compare brand count, fire count, unresolved work, and revenue direction.
- 5Open a pod when a team health card is red or amber.
- 6Open a member when that strategist has heavy fire load, unresolved 48h work, or a low health score.
- 7Review managed brands and data-quality gaps before escalating or reassigning work.
Health Score And Zones
Health score
A directional rollup of brand pressure, fire load, unresolved work, and revenue context in the current scope.
Green
The scope is stable enough for normal monitoring. Still review unresolved work if the count is not zero.
Amber
The scope deserves close watch. Look for the specific pod, member, or brand creating pressure before it turns into Fire overload.
Red
Leadership attention is needed. Review the alert, drill into the affected member or pod, and decide whether to escalate, reassign, or unblock.
Best habit
Views And Drilldowns
Workspace view
Shows cross-pod health, total brand pressure, solo strategists, and the highest-priority leadership alert.
Pod view
Shows one team's member load, pod-level metrics, average resolve time, and revenue context.
Member view
Shows one strategist's brand ownership, Fire and Watch counts, health score, and the brands creating pressure.
Breadcrumbs
Use breadcrumbs and Back to Horizon or Back to pod to move between scopes without losing context.
Alerts And Pressure Signals
Top Alert
The strongest risk detected for the current view. It may point to a red pod, red member, fire overload, or stalled resolution.
Fires
The number of brands in Fire status. A high count means immediate response work may be overloading the team.
Unresolved 48h
Brands that have stayed unresolved long enough to deserve escalation. Treat this as a leadership queue.
Average resolve time
How long issues tend to remain open in the current scope. Use it to spot coaching, process, or staffing problems.
Revenue Context
Weekly revenue
The current weekly revenue rollup for the selected scope. Use it as context for prioritization, not as the only health signal.
Revenue delta
The weekly comparison against the prior baseline when available. Positive revenue does not cancel unresolved operational risk.
Brand revenue
Member brand cards show actual and expected revenue to help explain whether a brand's pressure is commercial, operational, or both.
Health plus revenue
The strongest leadership read comes from combining health score, Fire load, unresolved time, and revenue movement.
Data Quality
Missing strategist assignment
A brand is not assigned to a strategist, so pod and member load may be incomplete until ownership is fixed.
Pod mismatch
A brand, strategist, or assignment may not line up with the expected pod structure. Confirm the workspace setup before acting.
Leadership-owned brand
A brand may still be assigned to a leadership user. Reassign it if day-to-day ownership should belong to an account manager.
Missing insight log
Operations context may be incomplete. Open Operations before making a strong judgment from Horizon alone.
What To Do Next
- Red workspace: open the top alert, then drill into the affected pod or member.
- Red pod: inspect member cards and look for concentrated Fire or unresolved 48h work.
- Red member: review managed brands, Why Red, and any stalled brand cards before escalating.
- Assignment gaps: fix brand ownership or pod setup before relying on load metrics.
- Operational issue found: open Operations for the brand-level response workflow.
- Strategic planning needed: use Horizon to choose the team priority, then use Revive, Trajectory, or Composer for execution planning.
Common Questions
Why do I only see one pod or myself?
Horizon respects workspace role and scope. Some users see the whole workspace, pod managers see their pod, and solo strategists may see only their owned brands.
Why is a team missing?
Horizon needs active pods, brand ownership, and member assignments. Check workspace setup and data-quality notes.
Should I reassign work from Horizon alone?
No. Use Horizon to find the pressure, then inspect Operations and team context before changing ownership or priorities.
Why can revenue look good while health is red?
Revenue and operational risk are different signals. A team can be generating revenue while unresolved issues or Fire load are still too high.