The easy mistake is to start with the org chart and ask what a role does. In small companies everyone wears multiple hats, so the role name tells you little. Look at the work instead.
Think of a restaurant kitchen. “Kitchen” is the broad function, and inside it sit prep, grill, pastry, dish, and expo. Those are areas of work, not job titles. One person might cover several stations on a small team, but the stations still exist.
How it shows up
A function is a stable area the business has to perform. A subfunction breaks it into a cleaner lane, and under it sit core activity records, the smaller named pieces that become SOPs, skills, or agent instructions. This matters for AI because agents are far easier to design around work than around vague roles. “Be my social media expert” is too blurry. “Turn long-form transcripts into three LinkedIn post drafts using this format” is something an agent can actually run.
Why you care
A subfunction lets you ask who owns this lane, what inputs it needs, what outputs it produces, and what decisions happen inside it. Once those are visible, delegation routing gets much cleaner. The point is to stop hiding work inside job titles, not to invent fancy labels. AI can’t help much with work you haven’t bothered to name.