monday’s workaround isn’t good enough 
Users have used monday’s flexibility to create various workarounds for defining project-level resource planning. 
However, these solutions have major downsides: 

ImpactMajority of resource mgmt use cases require resource planning on the project level
Not all resource managment use cases call for project-level resource planning. Some would require a more granular task-level planning (where the tasks of the project are known before-hand), or even combine both project-level and task-level planning.

So how would we know which use case to focus on first?
To answer this question, we conducted two surveys that revealed the division of the different use cases amongst potential (opps) and existing clients. There was a clear winner:

User journeys We got two different personas to account for  
The Resource Planner would be used by two main personas, with different jobs-to-be-done:

1. Project manager - Define resource types needed for the project, and effort needed for each resource type. 

2. Resource manager - Review projects with resource types that require assignment, and assign to relevant resources that have capacity.