Roles vs. skills
Roles describe what someone does (Designer, Developer). Skills describe what they're capable of. Use roles for broad planning, skills for precise matching.
Make confident planning decisions based on real data, not guesswork, by setting up the right foundations from the start, from roles and availability to rates and skills.
Read time
10 minutes
Goal
Set up your site
Primary Tool
Teamwork.com
The quality of every resource decision you make, from who works on what to whether a project is profitable, depends entirely on the data you put in at the start.
Roles describe what someone does (Designer, Developer). Skills describe what they're capable of. Use roles for broad planning, skills for precise matching.
Available hours minus time off, unavailable blocks, and calendar meetings equals real availability. All three inputs are needed for capacity data that reflects reality.
Set up roles before adding any allocations.
Use unavailable time to proactively capture training, recurring standups, and admin, not just vacation.
Assign utilization targets early so you have a performance baseline from day one.
Connect Calendar for the most accurate real-world availability view.
Keep roles, skills, and availability updated as your team and work evolve.
Skipping working hours setup. This single gap makes every capacity number wrong.
Using skills as job titles. Keep roles for titles and skills for specific capabilities.
Leaving permissions unconfigured. The wrong people editing resource plans causes planning chaos.
Adding rates as an afterthought. It's harder to backfill financial data than to start with it.