.png)
The quest to express work in mathematical terms is a transformative effort at the intersection of organizational science and practical management. For most of business history, jobs were defined by their titles, not their contents. A “Financial Analyst” and a “Senior Associate” might be doing substantially different work — or nearly identical work — with no formal framework to tell them apart. That ambiguity made workforce planning intuitive at best and political at worst.
Translating work into a mathematical framework changes this. It enables objective measurement and comparison of jobs and tasks, eliminating ambiguity about what constitutes productive work. It supports the automation and optimization of workflows by providing a precise language for what machines can and cannot do. And it gives managers a design tool — not just a descriptive one — for reimagining roles as AI capabilities expand.
This article builds the formal framework in three layers: first, a set-based model of the job as a collection of tasks; second, a partition model that separates automatable from human-required tasks; and third, a continuous degree-of-automation model that captures the reality of human-in-the-loop work. Each layer adds precision and practical utility. The final section translates the math into organizational implications that any manager can act on.
“Automating work is not the same as eliminating it. The mathematical models in this article show why: automation changes which tasks are executed by machines versus humans, but the job — the structured system of tasks — remains. Understanding the composition of that system is the foundation of every intelligent workforce decision.”
Part I: The Job as a Structured System of Tasks
We begin with the most fundamental question: what is a job, mathematically? The answer is not a role, a title, or a headcount entry. A job is a structured collection of tasks, each with attributes, dependencies, and constraints. The following six definitions build this model progressively from minimal to complete.
1. Basic Set-Based Definition
The simplest and most foundational model: a job is a finite set of tasks. This captures what the job entails, without yet specifying how tasks relate to one another or what attributes they possess.
Definition. Let a job be defined as a finite set of tasks:
IMPLICATION. Job titles lose explanatory power the moment you define the job mathematically. Two analysts with the same title, performing different tasks, are in different jobs. This has direct consequences for compensation equity, automation planning, and performance measurement.
ORGANIZATIONAL CONSEQUENCE. Workforce design shifts from headcount planning (how many people?) to task allocation planning (which tasks need to be performed, by whom or what, and how often?). This is the foundational shift that AI makes necessary.
2. Job as an Aggregation Function
A set tells us what a job contains, but not how those tasks combine into a coherent unit of work. The aggregation function F captures the logic of combination — sequencing, coordination, execution flow, and interdependence among tasks.
Definition. If we want the job to be an aggregation of tasks, not just a list:
For a simple additive workload (tasks are independent and sequential), F reduces to a sum:
IMPLICATION. Process redesign is the act of changing F, not just changing which tasks are in the set T. Many automation initiatives fail because they replace individual tasks (changing T) without redesigning the aggregation logic (changing F). A workflow designed around human sequential processing may yield no value when individual tasks are automated, yet F remains unchanged.
ORGANIZATIONAL CONSEQUENCE. AI-driven workflow redesign requires changing both T (the task composition) and F (the sequencing and coordination logic). The highest ROI transformations address both simultaneously — removing tasks that exist only because of human coordination overhead and collapsing sequential steps that AI can execute in parallel.
3. Tasks with Attributes
A task is not just an activity — it is a measurable unit with quantifiable properties. Adding attributes to the task model transforms it from a conceptual tool into an analytical one. Three attributes are sufficient to describe most tasks for automation planning and workforce design purposes.
Definition. Let each task be a vector of three core attributes:
The job as a whole can then be described as an aggregate of its task attributes:
IMPLICATION. This model makes it explicit that total cognitive demand (σ) accumulates only in human tasks — and it is this accumulated judgment load that defines what is irreplaceable about a given job. As automation absorbs low-σ tasks, the remaining human work becomes cognitively denser and more valuable per unit of time.
ORGANIZATIONAL CONSEQUENCE. Managers can now audit their teams' task portfolios by σ level. Tasks where σᵢ is low and δᵢ is high are the highest-priority automation candidates. Tasks where σᵢ is high are where human development investment should concentrate. This is the analytical foundation for the workforce redesign.
4. Job as a Weighted Task Function
Not all tasks contribute equally to a job's output or value. A client call that drives $1M in revenue and an email that updates a calendar both appear as tasks in the set model, but they are not equivalent. The weighted task model assigns importance weights to each task, enabling more precise analysis of where value is created and where automation has the most leverage.
Definition. If tasks contribute unequally to the job's output, define:
IMPLICATION. Weight and automation-eligibility are independent dimensions. A task can be high-weight and automatable (e.g., financial report generation), low-weight and automatable (e.g., scheduling), high-weight and human-required (e.g., a critical negotiation), or low-weight and human-required (e.g., a brief peer check). The highest-value automation targets are tasks that are both high-weight and automatable — they deliver cost savings without sacrificing the work that creates the most value.
STRATEGIC CONSEQUENCE. AI investment prioritization should be driven by the product of wᵢ and automation-eligibility, not by headcount impact. A firm that automates ten low-weight tasks may see less economic impact than one that automates one high-weight task at the center of its delivery model.
5. Job with Dependencies and Cycles
Most jobs do not consist of independent tasks. In practice, tasks have dependencies (task B cannot begin until task A is complete), parallelism (tasks C and D can run simultaneously), and cycles (task E repeats after task F feeds back into it). A directed cyclic graph formally captures this structure.
Definition. Define the job as a directed cyclic graph (DCG), where nodes are tasks and edges are dependencies:
A practical example: BIP Capital's Quarterly Performance Reporting cycle is a DCG. Every quarter, the team: (A) evaluates portfolio company financial performance, then (B) runs valuation models, then (C) calculates investor returns, then (D) publishes performance reports. The DCG is A → B → C → D → A, cycling every quarter indefinitely.
IMPLICATION. Understanding a job's dependency structure is essential for automation planning, as automation opportunities are constrained by these dependencies. A task in the critical path of a DCG that blocks three downstream tasks is a higher-priority automation target than an isolated task — because speeding it up accelerates the entire downstream chain, not just itself.
ORGANIZATIONAL CONSEQUENCE. Process mapping at the DCG level — not just listing tasks, but documenting their dependencies and cycles — is a prerequisite for intelligent automation sequencing. Organizations that map their DCGs before deploying AI consistently identify higher-value automation targets than those that automate task by task without structural context.
6. General Abstract Definition
The five models above can be unified into a single general definition that is flexible enough to accommodate any job structure: simple or complex, linear or cyclic, uniform or weighted. This is the most complete representation and the one on which the automation analysis in Part II is built.
Definition. Let the most general job model be defined as:
IMPLICATION. Every job in every organization can be described by some instance of this model. The value of having the general form is that it provides a shared language across operators, technologists, executives, regulators, and investors — enabling precise conversations about what a job entails, where automation applies, and which constraints must be preserved.
ORGANIZATIONAL CONSEQUENCE. The general model serves as the foundation for AI ROI modeling, workforce redesign, and governance frameworks. Any organization that can describe its key jobs in this form has the analytical foundation to make automation decisions rigorously rather than intuitively.
Continue reading the full article on Mark Buffington's Blog, Stacked Edge.