This guide explains how to use the Members analytics view in Productized Services:

• /wp-admin/admin.php?page=psfw-analytics&tab=members

It helps you make better staffing and reassignment decisions using member-level workload signals.

What This View Is For #

The Members view is designed for capacity and ownership analysis.

Use it to:

• compare workload distribution across team members
• identify imbalance between active and closed work
• spot over-allocation risk before deadlines slip
• support fairer assignment and handoff planning

Core Features and Benefits #

1) Member Workload Cards by Work Type #

Feature:

• workload cards break down member data across key dimensions, including:
  • projects workload
  • projects closed
  • tasks workload
  • tasks closed

Benefit:

• separates current load from completion history so decisions are based on both pressure and output

2) Time Scope Controls #

Feature:

• date range scoping for workload analysis windows

Benefit:

• helps distinguish temporary spikes from sustained capacity issues

3) Team-Wide vs Member-Level Perspective #

Feature:

• compare full-team distribution and member-specific workload context

Benefit:

• prevents both overreaction to single cases and blind spots in team-level planning

4) Assignment Decision Support #

Feature:

• view highlights where current ownership is concentrated

Benefit:

• supports faster, safer reassignment decisions during daily operations

5) Completion Context for Fair Balancing #

Feature:

• includes closed/completed-oriented workload views alongside active work views

Benefit:

• reduces unfair balancing decisions that ignore historical throughput

How and When to Use Members Analytics #

Use It Daily When #

• assigning new high-priority work
• handling urgent escalations
• validating whether a member can safely take more tasks/projects

Use It Weekly When #

• reviewing team capacity trends
• adjusting ownership strategy
• planning staffing changes and handoff standards

Use It During Bottlenecks When #

• one member repeatedly becomes a delivery choke point
• work completion slows without obvious task-level cause
• reassignment decisions need objective workload evidence

Step-by-Step: Running a Capacity Review #

Step 1: Open Members Analytics #

Go to:

• /wp-admin/admin.php?page=psfw-analytics&tab=members

Start with your default range for a baseline read.

Step 2: Review Active Load Signals First #

Focus on active workload dimensions:

• project-related current load
• task-related current load

Identify members carrying disproportionately high active responsibility.

Step 3: Cross-Check With Closed Work Signals #

Then review closed/completed dimensions:

• projects closed
• tasks closed

This prevents misclassifying productive members as overloaded without context.

Step 4: Apply Date Scope for Fair Comparison #

Set a consistent date window before comparing members.

Avoid comparing one member’s short-range snapshot to another member’s long-range pattern.

Step 5: Make Assignment Decisions #

Use combined active + closed context to decide:

• who can absorb urgent tasks
• who needs workload relief
• where ownership should be redistributed

Step 6: Recheck After Rebalancing #

After reassignment changes, re-open Members analytics with the same scope.

Confirm whether distribution is improving.

Practical Decision Patterns #

Pattern A: Overload Prevention #

• signal: one member has consistently high active load vs peers
• action: redirect incoming assignments and shift non-critical items

Pattern B: Throughput-Aware Balancing #

• signal: high active load but also strong closed output
• action: rebalance cautiously, preserving productive flow while reducing risk spikes

Pattern C: Hidden Capacity Recovery #

• signal: member has lower active load and stable close rates
• action: route suitable incoming work to improve team-level balance

Best Practices #

• use Members analytics before daily assignment planning
• evaluate active and closed signals together
• keep date scope consistent during comparisons
• document major rebalancing decisions with rationale
• review impact of assignment changes within 1–2 cycles

Common Mistakes to Avoid #

• balancing only from active load without completion context
• reassigning too aggressively from a single snapshot
• ignoring date scope differences when comparing members
• making staffing decisions based on intuition alone

Summary #

Members Analytics is your capacity-balancing dashboard.

Used consistently, it improves assignment fairness, reduces overload risk, and helps your team sustain predictable delivery performance.