What Are the Functions of HR, and Which Should a Small Employer Build First?
November 6, 2026
HR is ten connected areas, not one job. What each area does, why they work as a system, and the order I would build them at 10, 25, 50 and 100 employees…
By McKinley Malbrough III, J.D., MS-HRM
Published October 30, 2026. Last updated November 11, 2026.

Cover photo: #WOCinTech Chat on Flickr, CC BY 2.0. About the photos
Short answer
Every organizational structure moves decisions to a different place, so each creates a different HR job. Functional structures need clear levels and handoffs, flat ones need explicit decision rights, divisional ones need consistent pay and policy across units, matrix ones need a named owner for each employee’s review, and team-based ones need a way to grow people without promotions. A RACI chart makes the ownership visible.
Every organizational structure moves decisions to a different place, so each creates a different HR job. Functional structures need clear levels and handoffs. Flat ones need explicit decision rights. Divisional ones need consistent pay and policy across units. Matrix ones need a named owner for each employee’s review. Team-based ones need a way to grow people without promotions. A RACI chart makes the ownership visible.
I am Mac Malbrough. I hold a J.D. and an MS-HRM, I am not an attorney, and I help small employers organize work and ownership. The company examples below are hypotheticals I made up to show how each shape behaves. They are not client stories.
Most small companies do not choose a structure. They accumulate one. The founder hires a salesperson, then an operations person, then a bookkeeper, and a shape emerges. It works until the company reaches a size where the old habits break: two people think they approve the same expense, nobody owns onboarding, or an employee has three bosses and no review.
Those are HR problems that start as structure problems. Pay decisions need a person who owns the budget. Reviews need a person who has seen the work. Policy needs a person who can enforce it. Structure answers who those people are. If you do not decide it, the answer comes from whoever is loudest, and that choice tends to create the inconsistency employees notice.
In a functional structure, people are grouped by what they do: sales, operations, finance, service. A hypothetical 40-person distributor is a typical example. Each function has a head, and work flows from one function to the next.

The HR consequences are mostly about levels and handoffs. You need job levels within each function so that pay and promotion are comparable. You need an agreed way to handle work that crosses functions, such as an order that sales promises and operations delivers. And you need to watch for silos: when each function builds its own hiring and onboarding habits, new hires get a different experience depending on the door they came through. A shared onboarding plan solves most of this.
A flat structure has few or no layers between the owner and the people doing the work. A hypothetical 15-person design studio may have one lead and everyone else reporting to the lead. It is fast and personal.
The HR risk is that decision rights are unwritten. Who approves a raise? Who can say no to a client request? Who handles a complaint about the lead? With no layers, an employee who has a problem with the person at the top has nowhere to go, so a flat company needs an outside route: a second contact, a written complaint procedure and a named person who is not the lead. Growth is the other risk. Flat structures give people few promotion steps, so you need another way to recognize growth, such as expanding responsibility and pay within a level.
A divisional structure groups people by product, customer or location. A hypothetical 80-person company with a restaurant group and a catering arm is an example, each with its own manager and team.

The HR consequence is consistency. When each unit runs itself, pay, scheduling and discipline drift apart. Two people with the same job in different units get different treatment, and that is hard to defend. The fix is a small set of company-wide rules, such as a shared pay range for each job title and a common process for discipline, with room for local differences that have a stated reason. In California, multi-location employers should also check local ordinances, which differ by city. My article on Bay Area local employment ordinances shows how much they can vary.
In a matrix, people report to more than one leader, typically a functional manager and a project or product lead. A hypothetical 60-person agency with project leads who borrow staff from a pool is an example.
The HR consequence is accountability. If an employee has two managers, who writes the review, who approves time off and who handles a performance concern? The answer must be explicit. The usual solution is a “home” manager who owns the employee’s review, pay and development and collects input from the project leads. Without that, reviews become a patchwork and the person with the least information ends up making the decision. A matrix also raises workload conflicts, so ask each manager to agree on priorities before assigning work, not after.
A team-based structure organizes work into small, cross-skilled teams with considerable autonomy. A hypothetical 50-person software company with five product teams is an example.
Here the HR challenge is growth and fairness. Teams have fewer managers, so promotion cannot depend on moving up a ladder. Define levels by scope and skill, and base pay on the level, not on the team. Watch for uneven workloads between teams, and use common tools for goals and feedback so that people on different teams are judged on comparable evidence. Team members also need a place to raise concerns about a teammate that does not go through the team itself.
RACI stands for Responsible, Accountable, Consulted and Informed. For each task or decision, you name one person who is accountable, the people who do the work, the people who must be consulted and those who only need to know. The rule that makes it work is one accountable person per decision. If two people share accountability, nobody has it.
Start with the decisions that HR touches most: approving a hire, setting pay, approving time off, issuing discipline, closing a complaint, running a review. Draw the grid for your current structure and look for rows with no accountable person or two. Those are your gaps. The RACI matrix kit has the templates, and my article on HR templates for RACI, skills gaps and development plans shows how they fit together.
When the structure changes through growth, repeat the exercise. Pair it with a headcount plan so you know where new roles land. The Headcount and Hiring Forecast helps you see when a team will outgrow its manager, and the Succession Planner for Critical Roles highlights the roles where one person holds the knowledge.
Some structural changes, such as moving an employee to a different manager or reducing hours or duties, can affect pay, schedules or legal obligations. Talk with an employment attorney before a reorganization that reduces anyone’s pay or role, or that involves layoffs.
Most small companies drift from flat to functional somewhere between 15 and 30 people, and from functional to divisional or matrix later. Treat each move as a project with an announcement, not as a quiet change in who reports to whom. Before you announce it, decide the new reporting lines, the job titles, any pay changes and the first decisions the new managers will own. Then tell each affected person individually, in this order: their own manager, the person themselves and then the team. People accept change more easily when they hear it from the person they work for and when they can see what stays the same.
If your structure has few layers, offer growth sideways instead, as described in building a career lattice without promotions.
Draw your current structure on one page, including who reports to whom and any dotted lines. Then list five decisions that HR touches and write the name of the accountable person next to each. If you cannot name one, you have found your first fix. Share the page with your managers and ask whether it matches what they believe.
Use the RACI matrix kit to document the decisions, and if you want help redesigning ownership as you grow, book a free consult through my HR services for small businesses. My book The Small Employer HR Field Guide covers the structures and the first policies each one needs.
Related reading: six HR models small employers can use.
McKinley holds a J.D. but is not a licensed attorney. Articles here are general information, not legal advice. For your specific situation, talk with an employment attorney.
Data current as of November 2026. Sources are linked where each figure appears.
Share this article
This article is general information, not legal advice. Laws change and every situation is different; for advice on yours, talk with an employment attorney.
Related questions
November 6, 2026
HR is ten connected areas, not one job. What each area does, why they work as a system, and the order I would build them at 10, 25, 50 and 100 employees…
November 7, 2026
Textbook HR models are useful when you know which problem each one solves. Six well-known frameworks in plain English, who developed each, a small-employer example, a quick chooser by problem, and what…
November 6, 2026
A RACI matrix kit, a skills gap workbook, a development plan kit and a training needs workbook, built for 10 to 150 person organizations. What problem each one solves, how it works…