LogoLogo
MethodsVisit our website
  • Overview
    • Getting started
    • Trends
    • Capacity
    • Allocation
    • Scenarios
    • Plans
    • Epics
    • Teams
  • Health Data
    • Cycle time
    • Flow efficiency
    • Intelligent forecast
    • Momentum
    • Resource contention
    • WIP limits
    • Dashboard
  • Additional Integrations
    • GitHub
    • GitLab (Cloud)
  • How to...
    • Add or remove users
    • Balance people's workloads
    • Change Jira project status configuration
  • OTHER RESOURCES
    • Data imported from source systems
    • Security
Powered by GitBook
On this page
  1. How to...

Balance people's workloads

Last updated 8 months ago

Socratic allows you to set a to help keep work flowing, and people from drowning.

WIP limits are a tried and true method for surfacing bottlenecks. While the concept originated with Kanban, it works regardless of your process. In Kanban, WIP limits are typically assigned to each work phase (e.g. To Do, Doing, Done). But the same idea can be applied to people.

Capping the amount of work in progress is sensible for a number of reasons. WIP makes finding bottlenecks easier—in this case, who may be overloaded—and it affirms the simple fact that trying to do too much at once leads to less actually getting done, and more team frustration.

See also our Methods post: .

Fighting the tax that drains software teams
personalized WIP limit
See at a glance people's workload, and take action to reduce overwork