I know this is going to initially bother a lot of software engineers the wrong way but here me out: make a gantt chart and assign resources to each of the tasks. You can add "future hires" to see how much of a work load reduction you get.

Now depending on your work environment you can do one of two things:

- Work environment is still "healthy": Show your gantt chart to your boss as a justification for the resource count addition but highly stress that the dates are not accurate or even valid estimates. That is what a dedicated planning session is for.

- Work environment is not "healthy"/a bureaucracy: Come up with whatever justification you can that validates the number you came up with in a gantt chart (aka parallel construction) but don't show the gantt chart. They will take those numbers as gospel no matter what you say.

I second the Gantt chart approach. The way I modelled is in a spreadsheet, 1 cell = one week. Then on a top row write the number of engineers available. Discount 10%-20% for PTO (there's always someone in PTO).

In the 1st column write the projects and next a column with your estimates of man-weeks required. Here is where you should modulate the estimate depending on how business looks at these things: Do they know it's an estimate planning tool? Add the 30% overhead of your estimate: Shit always happens. Does business take your estimates as law? Add 50% padding.

Once you have that framework, get the milestones/end dates from business. These usually come as "having X feature in Q1", Y feature in Q3. So you have some leeway.

Start mapping how many engineer weeks would you need for each task for each week to finish in the milestone, ensuring you dont get to negative in the top (total engineers) row.

You also should consider the mythical man month: putting 10 engineers in a feature will most likely make it fail, not go super fast. Usually you want 3 or at most 4 ppl per project. This also depends on the size of the project.

With this data, you'll be able to show business that additional prioritizing needs to be done. On the flipside, they will question you your time estimates. You can use that to push to sit down and clarify/detail the project, maybe even split it in stages: the Gantt will allow you to model feature releases of a large project.

I used this framework successfully, and it served as a great communication tool between the CEO and myself (as head of Engineering).

Human Capital planning for SMB is being tackled by TONS of startups, but HC planning at the Enterprise level is much less competitive - however a point solution for HC planning will have tremendous difficulty breaking through to the mass market as the consumers of the end result (finance most often) have to cobble together the results from a solution that targets the single HC problem plus multiple other point solutions to actually generate the output desired (fully burdened headcount forecast matched to organizational objectives & a hiring/staffing plan along with other financial objectives driven off of headcount - such as software licenses, facilities space, etc.). Excel/Google sheets are superior here until an ERP is purchased by the organization in which case ALL point solutions become redundant and obsolete (leading to 100% churn for high growth/successful customers).

Our platform allows engineers/entrepreneurs to launch point solutions (meaning it solves one specific use case as compared to breadth of an ERP) to enterprise customers. If you're interested in chatting happy to discuss and help those trying to improve the lives of those trying to disrupt the forecasting & analysis world (regardless of whether it has anything to do with our company).

MS Excel Spreadsheets.

More than the tool, what matters is the discipline of all functions (i.e., departments) agreeing on the business processes such as annual budgeting, quarterly/monthly forecasting, feedback loops to account for recent trends and key program-wise/location-wise assumptions (eg. attrition, shrinkage, training yield, ramp-up/learning curve etc.,).

Then, you build up a bottom-up forecast with those key assumptions that translates to revenue and expenses to build a P&L forecast.

A spreadsheet offers the most flexibility. Again, more than the tool, it is the process and the discipline (includes agreeing on standards, lead-times etc.,).

This culture and practices also varies from organization to organization and in practice, in large organizations, you have the legacy of acquisitions that cause a diverse set of practices. While a common tool might help these organizations streamline and standardize the headcount planning process, the challenges are not technical but human and cultural.

As a corporate finance person that runs budgets for medium to large corporate, this is pretty spot on in those environments.

I’ve used various software to help, but it always comes back to spreadsheets. It’s usually too business specific and rapidly changing to try to use something off the self. Even when you build your perfect custom module in a software like Anaplan, Adaptive, Hyperion, etc. you’re at risk because the very algorithm of how you model labor can and does change and sometimes frequently even though you may think that’s something that should be rather set & forget it’s not. So the adhoc-ability of spreadsheets win.

The human processes are much more difficult to wrangle and change in a whim. If you’re growing fast, usually prioritization has to come into place and it’s like a horse race. Even some role that’s not even planned can suddenly pop up and get hired without budget. This happens a lot when the perfect candidate comes available and the company wasn’t originally going to hire but don’t want to miss the opportunity.

I’d love to be able to say, go build this B2B solution HN! But honestly, I have a hard time imagining anything would compete with the spreadsheet. It’s not like people haven’t already tried, it just doesn’t work well in practice for the end users.

Good point! But is this adhoc-ability something you want to support? I often think doing something adhoc never seems to benefit anybody, but happens all the time.

If you're creating any kind of support staff, where you can talk to a real human to get help, then the Erlang-C calculations work incredibly well to predict headcount and schedules.

Excel, but it's painful - as any change's through the year make it very hard to compare and contrast actual to budget (e.g. a simple rate change from a supplier vs adding someone to a team, moving different rate people between teams) and quite challenging to do different scenarios (e.g. impact of different inflation levels for different roles / countries). It is possible but requires a lot of discipline and excel expertise from everyone to make it work. I am exploring using a planning & budgeting tool (anaplan, pbcs).

Those tools will only slow you down, use Excel.

Also the pain you mentioned is exponential with those tools compared to in Excel. You’ll never have perfect budget unless you have a crystal ball and can anticipate everything that will change. Just explain the variance and move on. Forecasting is meant to somewhat solve this issue. Budget become quickly stale, the forecast is budget altered by a few big issues (usually things unknown during the budget). Also usually helpful to replace budget with actual as they become available

There are a few different tools and methods that can make headcount planning less painful. One method is to use a tool like Excel or Google Sheets to track headcount data over time. This can help you identify trends and make more accurate predictions. Another method is to create a headcount planning committee, which can help to gather input from different departments and make decisions based on collective data.

Why is it painful for you?

It's painful for me for a few reasons:

- Convincing and aligning with multiple people (my boss, HR, finance) that we need to hire X more people to hit whatever business goal or do some project. This results in a bunch of painful meetings and there's always one person that jumps in towards the end and re-questions if we need more people.

- Estimating the optimal number of people I actually need to deliver Y. I often underestimate which has rippling effects on putting more strain on the existing team and us always feeling behind.

- Working with too many spreadsheets! Needing to create multiple scenarios, data discrepancies which come from collaborators making their tweaks, etc... Wasted time reconciling what the latest or final proposal is.

Could you talk more about where you feel the pain? Do you use an org tree and how deep is it? Or do you have a couple pools of people who do similar things? Do you use 'cost centers' and do they fill needs at different levels of your org tree?

Spreadsheets work great because it's trivial to change the data structure, and because I can email/share them to the CFO. If I was to adopt a tool, it would have to at least export to spreadsheet.

Does your entire team read and write to the same spreadsheet?

We do monthly FTE forecasts and use a web tool called time2submit (www.time2submit.com).

How satisfied are you with this tool from 1-10?

We've only been using it since the beginning of the year but are really happy with it. Not sure what you expect but we sent around hundreds of Excel sheets every month for different purposes and now moved many of these processes to time2submit. If you don't need to gather information from other people, then I guess, it doesn't make sense to use that tool.

Do whatever the ERP tells me to do.

I’m sure people mean Google Sheets, not Excel, because it’s shareable. Some tips based on my experience: -Search for pre-built sheets to get an idea of how to build things out for your company -Build with ways to easily adjust headcount, salary, start dates -Factor overhead separately from salary -Version control/who’s allowed to edit is important -Know that it won’t go exactly to plan, so don’t worry -Tools like anaplan are just as hard to use as sheets, and cost a lot of money, avoid them for as long as possible

I definitely meant Excel, we use office365 - easily as shareable as Google sheets these days. Agree anaplan and friends also have downsides, but for me the complexity you end up in as you change things through the year and need to explain the impact of the change becomes too complex in Excel. We manage a team of about 220 people, when I had a team half the size it was more manageable.