Map job families before comparing talent demand

Workforce data loses meaning when titles hide different jobs. One department might use analyst for a person who prepares reports, while another uses analyst for a person who resolves customer cases. A coordinator title might cover scheduling in one group and technical setup in another. Counts by title then mix unrelated work. Before comparing demand, vacancies, internal movement, or hiring difficulty, build job families around work people perform. The purpose is a shared view of comparable roles, not a new naming system for every employee.

Begin with a modest scope. Choose one function, a small group of related titles, or a hiring question already under discussion. A map covering an entire organization in one meeting invites guesses. A map covering six titles from two departments gives leaders enough detail to test categories. Ask for current role profiles, recent job descriptions, sample work, and names of managers close to daily work. Titles matter as references, yet duties provide evidence for grouping. Keep the source beside every observation, so later review does not depend on someone’s memory.

Use a small set of prompts in each conversation. Ask which recurring work fills most of a week, which tools support work, which decisions the person makes or supports, and how much independence the role carries. Ask what a new hire learns during early weeks. Ask where work passes to another team. These prompts show distinctions hidden behind similar titles. They also show overlap between titles which look unrelated on an organization chart. Answers should describe work, not personality or assumed skill level.

Fictional situation: Renee, a talent solutions consultant, meets an operations group at fictional Lakeside Health Services. Their vacancy report separates patient access coordinators from intake specialists. Renee asks Hal, a manager, “Which work separates these groups during a normal shift?” Hal says both groups register patients and update records. Coordinators also address authorization questions before a visit, while intake specialists follow a defined registration sequence. Renee records those duties and sends two proposed families to the access director for review. She does not select family names alone.

The first proposed family is registration support. Common duties include greeting, identity collection, record updates, and standard intake steps. The second is authorization support. Common duties include researching incomplete authorization details, coordinating with internal teams, and resolving exceptions within an assigned process. Those labels are working labels, not final descriptions. The access director says some intake specialists perform authorization work during busy periods. Renee marks shared coverage as an open question instead of forcing a clean division unsupported by daily practice.

Similar titles deserve comparison, yet matching words do not prove similar work. Place every title beside duties, tools, decision scope, required knowledge, and escalation route. Look for meaningful differences. A role using one system might still serve a different purpose. A coordinator who assigns work across a team has a different decision scope from a coordinator who enters completed work. A role resolving exceptions needs a different evidence trail from a role following a standard checklist. Your map should show differences plainly enough for a manager to challenge them.

Different titles sometimes belong in one family. One department might call a role scheduling assistant, another might call similar work workforce coordinator. When recurring duties, tools, and decision level align, place both titles under a shared provisional family. Keep local titles visible beside the family name. Leaders often need local terms for reports, payroll systems, or manager conversations. A job family map adds a comparison layer. Daily language stays visible, which keeps the map useful during a conversation with a local manager.

Validation keeps the map honest. Send each owner a short request with the proposed family, included titles, common duties, and unanswered questions. Ask owners to mark incorrect groupings and add examples from current work. Do not ask for approval of a polished final document when evidence is thin. Renee writes, “I grouped intake specialist and registration associate under registration support because both roles complete standard intake steps. Which recurring duties make this grouping inaccurate?” The reply adds evidence and identifies where further review is needed.

Handle mixed roles directly. Some people spend half a week on one family and the rest on another. Do not assign those people to whichever category produces a cleaner count. Record the mixed role, the work split when known, and the source for the estimate. When the split changes across sites, show site context. A map displaying uncertainty helps leaders ask better questions later. A map hiding uncertainty leads to arguments over numbers without a shared definition beneath them. Honest uncertainty has more value than false precision.

After validation, use families to frame a narrow demand question. Instead of asking why analyst vacancies are high, ask where vacancies sit across reporting analysis, case resolution, or workflow coordination. Instead of comparing title counts across departments, compare roles with similar duties and independence. The map does not prove why demand differs. Leaders receive a better unit for gathering evidence. A manager then reviews pay bands, work location, training time, scheduling, or approval timing with appropriate owners, based on a definition everyone has reviewed.

Keep the map provisional when work changes. A new tool, revised workflow, or merged team sometimes alters duties without changing titles. Put a review date on the document and name a person who reports major changes. Do not schedule constant reclassification. Use ordinary operating moments: an annual workforce review, a new role design, a recurring vacancy discussion, or a system change. The map supports decisions when close to current work. An old map with no owner becomes a source of stale comparisons.

Before review, ask each manager for one recent example per title. A short work sample exposes vague wording faster than a title comparison. Renee records the example source and date beside the proposed family. When two managers describe different work under one title, she keeps both descriptions visible until a later conversation resolves the difference.

Practice with fictional Northline Services. Northline has two departments and six titles: scheduling assistant, workforce coordinator, reporting analyst, service analyst, intake specialist, and authorization coordinator. Ask each fictional manager for recurring duties, tools, decision scope, and escalation route. Group only roles supported by similar evidence. Leave one title ungrouped when notes conflict. Send fictional manager Priya this message: “I placed scheduling assistant and workforce coordinator in scheduling support. Which weekly duties should I check before keeping them together?” Add Priya’s reply beside both titles, then compare vacancy counts only after her response changes or confirms the group.