An idea platform on AI, work, and organizations

The Two Project

AI changes tasks. Workflows need owners.

Exploring how work evolves in the age of AI.

Work does not change all at once. It changes through the workflows organizations choose to redesign.

AI improves tasks. Organizations run on workflows. Transformation happens when those workflows are redesigned with clear ownership.

Most AI strategies operate at the wrong level.

Leaders often speak at the organization level while teams experiment at the task level. What is missing is the workflow that connects the two.

Without workflow redesign, task gains stay local. With it, they can compound into organizational change.

Task, Workflow, Organization.

T-W-O explains AI transformation across three layers: tasks, workflows, and the organizations that own them.

Diagram showing the Task, Workflow, and Organization layers of the T-W-O framework.
The T-W-O framework connects task-level capability choices to workflow redesign and organizational structure.

Organization

Roles, incentives, accountability, and governance determine whether workflow redesign can stick.

Workflow

Workflows are the missing middle where task-level gains either compound or stall.

Task

Tasks are the atomic units of work. Each one raises a simple question: human, AI, or external provider?

Why AI transformation stalls, and how it moves.

The evaluator age

Knowledge work shifts from pure production toward evaluation, steering, and refinement.

The validation tax

Automation adds hidden overhead when output must still be checked, corrected, and coordinated.

Incremental transformation

Organizations change more effectively one workflow at a time than through wholesale reinvention.

Automation can add work before it removes work.

Many AI deployments underperform because they add a hidden second layer of effort: verification.

Without workflow redesign, that burden can exceed the gains from automation.

Diagram illustrating the validation tax created when AI output requires extra checking.
Validation becomes a structural cost when AI is inserted into tasks without redesigning the surrounding workflow.

The Owner

A Business Novel about Work in the AI Era

A novel about a familiar mistake: treating AI as a technology initiative when the real challenge is ownership and workflow change.

Explore the Book

Transformation becomes real when a workflow is actually redesigned.

The framework becomes useful when applied to concrete operating systems such as software delivery, support, and document-heavy review.

Workflow redesign example showing a software development process restructured around AI capabilities and human checkpoints.
An example of redesign: moving from a traditional delivery flow to a capability-based workflow with explicit human checkpoints.

Software development

Feature delivery can be reorganized around AI capability blocks, review checkpoints, and clearer release ownership.

Customer support

Escalation paths, quality assurance, and resolution ownership all change when AI handles more of the first pass.

Document-intensive workflows

Legal review, compliance, and analysis become clearer when machine processing is paired with explicit human judgment.

Three lines of work, developed with seriousness.

Book

The Owner is the narrative expression of the framework.

Framework

Essays and position work on the missing middle, capability reallocation, and AI transformation.

Talks

Talks on workflows, validation burden, and redesigning work incrementally.