Design Pattern · September 2026

From applications to work

Businesses do not need CRM software; they need work performed. Decompose the outcome into roles, tasks, workflow, and capabilities, and the application stops being the organizing unit.

Under the pillar Zero Neo

What is actually needed

Nobody needs a CRM. What is needed is: identify a prospect, remember what is known about them, communicate, schedule follow-up, track commitments, prepare material, record interactions, recognize signals, and decide what happens next.

A healthcare organization does not need patient relationship management software either. It needs to receive an inquiry, identify the patient, understand intent, schedule care, collect information, communicate instructions, coordinate staff, follow up, observe completion, escalate exceptions, and measure outcomes.

Once the work is written out this way, the question of whether a dedicated application is required becomes answerable rather than assumed.

Applications, capabilities, work, outcomesA software category is decomposed into the capabilities it provides, those capabilities are mapped to the work being performed, and the work is judged by the outcome it produces.Categorywhat the market sellsCapabilitieswhat it actually providesWorkwhat has to get doneOutcomewhat the business needed
The application is not the unit. The work is.

The work decomposition model

The model runs from the outcome downward, and then back up through evidence. Every layer is written down, because a layer nobody can state is a layer nobody can automate or govern.

Business outcome

What the organization needed to be true at the end.

Roles

Who is accountable, who performs, who approves, who is informed.

Tasks

The discrete pieces of work, named the way staff name them.

Workflow

Order, timing, branches, and what happens when nobody responds.

Required capabilities

Forms, records, messaging, storage, scheduling, reporting, approvals.

Existing platform services

Which owned service supplies each capability.

Execution

Human, conventional automation, or AI for each step.

Observable evidence

What each step leaves behind that proves it happened.

Outcome

Compared against the metric the business already reports.

Why the unit matters

When the application is the organizing unit, the work is fitted to whatever the vendor imagined, and the gap between the two is absorbed by staff doing things off-system.

When the work is the organizing unit, the tooling is fitted to the work, and off-system behavior becomes a visible signal that something is wrong rather than an invisible tax.