CASE STUDY ORGANIZATIONAL SYSTEMS + PRODUCT DESIGN

Designing beyond the org chart

What happens when an organization is designed around accountability— not just employees?

I explored an organizational model that connects internal employees, external expertise, intelligent agents, and the work they collectively perform—while keeping human responsibility visible throughout the system.

01 THE ORGANIZATION
A
Organization Structure
B
Human Accountability
C
Work Execution + acceptance
D
Economics Cost + project health
GOVERNING PRINCIPLE

AI and external expertise can perform work. Accountability remains human.

ORGANIZATION ACCOUNTABILITY WORK ECONOMICS
02 RETHINKING THE ORGANIZATION

The organization is more than an org chart.

Traditional organizational models are good at showing where people sit. They are much less effective at showing how responsibility, external expertise, intelligent systems, work, and resources actually move through the organization.

A
Organization Business
B
Department Functional structure
C
Role Position
D
Employee Person

This structure tells us who reports to whom.

01
ANCHOR Human accountability
RESPONSIBLE
02
EXTERNAL CAPACITY Contractors
attached to work
03
EXTENDED CAPACITY AI agents
owned by human
04
EXECUTION Structured work
project → task
05
CONSEQUENCE Resources + economics
hours → cost

The question changes from “Where does this person sit?” to “How does this organization operate?”

01

Organizational structure still matters. But structure alone cannot explain work.

03 HUMAN ACCOUNTABILITY

Start with the human organization.

Before adding contractors, intelligent agents, or project economics, the system needs a stable foundation: the people who hold organizational responsibility.

Employees form the permanent internal hierarchy.

INTERNAL ORGANIZATION 8 EMPLOYEES
Illustration representing the Director of Engineering EMP-01
EXECUTIVE LEADERSHIP

Director of Engineering

Organizational authority

Illustration representing the Engineering Manager EMP-02
ENGINEERING

Engineering Manager

Technical leadership

Illustration representing the Project Manager EMP-05
PROJECT DELIVERY

Project Manager

Project accountability

Illustration representing the Operations and Resource Manager EMP-07
OPERATIONS

Resource Manager

Capacity + allocation

PROJECT + TECHNICAL DELIVERY INTERNAL CAPACITY
Illustration representing the Senior Project Engineer EMP-03
ENGINEERING

Senior Project Engineer

Illustration representing the Civil Engineer EMP-04
ENGINEERING

Civil Engineer

Illustration representing the CAD and Design Specialist EMP-06
DESIGN

CAD / Design Specialist

Illustration representing the Field and Survey Engineer EMP-08
FIELD

Field / Survey Engineer

04 EXPANDING THE WORKFORCE

Expertise can enter without entering the hierarchy.

Organizations often need specialized expertise or additional capacity without creating a permanent internal role. Contractors extend the workforce through the work itself.

Contractors connect to projects and work while an internal employee retains organizational accountability.

WORKFORCE MODEL INTERNAL + EXTERNAL CAPACITY
Internal
External
01
INTERNAL ORGANIZATION Permanent human structure
Illustration representing the Project Manager EMP-05
INTERNAL OWNER

Project Manager

Holds internal accountability for the contracted work relationship.

PROJECT WORK ACTIVE
West Oakland
Drainage Improvement
PROJECT
DELIVERABLE
WORK PACKAGE
TASK
ORGANIZATIONAL BOUNDARY
WORK RELATIONSHIP ←
02
EXTERNAL CAPACITY Specialized expertise
Illustration representing a Contract Hydraulic Engineer CON-01
CONTRACTOR

Hydraulic Engineer

Hydraulic analysis

Illustration representing a Contract CAD Specialist CON-02
CONTRACTOR

CAD Specialist

Drawing production

Illustration representing a Contract Survey Specialist CON-03
CONTRACTOR

Survey Specialist

Field survey support

Illustration representing a Contract Environmental Engineer CON-04
CONTRACTOR

Environmental Engineer

Environmental review

RELATIONSHIP LOGIC
INTERNAL Employee
ACCOUNTABLE FOR →
EXECUTION Work
← ASSIGNED TO
EXTERNAL Contractor
05 EXTENDING HUMAN CAPACITY

AI belongs to a person—not the hierarchy.

Intelligent agents can expand operational capacity, but they need a clear place in the organization. I treated each agent as an extension of a specific employee rather than as an independent organizational actor.

Every active AI agent remains directly connected to one accountable human employee.

OWNERSHIP MODEL Human → Agent → Work
Human employee AI agent
EMP-02 ACCOUNTABLE HUMAN
Illustration representing the Engineering Manager
ENGINEERING

Engineering Manager

Owns technical responsibility and reviews agent-assisted engineering work.

HUMAN ACCOUNTABILITY
OWNS
A1
AI AGENT Design Review Agent

Checks drawing packages against defined criteria.

A2
AI AGENT Specification Agent

Supports technical research and specification lookup.

A3
AI AGENT QA Support Agent

Flags inconsistencies for human review.

EMP-05 ACCOUNTABLE HUMAN
Illustration representing the Project Manager
PROJECT DELIVERY

Project Manager

Owns project coordination and approves agent-supported planning outputs.

HUMAN ACCOUNTABILITY
OWNS
B1
AI AGENT Schedule Agent

Supports sequencing, milestones, and schedule checks.

B2
AI AGENT Project Brief Agent

Synthesizes project activity into structured summaries.

B3
AI AGENT Risk Review Agent

Surfaces potential project issues for evaluation.

RELATIONSHIP RULE ACCOUNTABILITY MUST TERMINATE IN A HUMAN
VALID
H EMPLOYEE
OWNS →
A AGENT
→ WORK

Human ownership remains explicit.

NOT ALLOWED
A AGENT
OWNS →
A AGENT
→ WORK

Accountability cannot terminate in another agent.

FROM CAPACITY TO EXECUTION WORK SYSTEM
ACCOUNTABLE Employee
EXTENDS CAPACITY AI Agent
EXECUTION Work
DECISION Human Review
06 THE ORGANIZATION BECOMES OPERATIONAL

Structure becomes useful when it connects to work.

The organizational hierarchy and the work structure are different systems. The model becomes operational when the people accountable for the organization connect to the projects, deliverables, and tasks being executed.

Employees bridge organizational responsibility and project execution.

OPERATIONAL ORGANIZATION MAP Two connected systems
HUMAN ACCOUNTABILITY PRESERVED
A
ORGANIZATION GRAPH

Where responsibility lives.

ORGANIZATION CivicWorks Engineering
DEPARTMENT Engineering + Delivery
ROLE Project Management
Illustration representing the Project Manager
EMP-05 ACCOUNTABLE HUMAN

Project Manager

Holds organizational and project responsibility.

AI
EMPLOYEE-OWNED AGENT Project Brief Agent
INTERNAL

The employee remains inside the permanent organizational hierarchy. The agent does not.

THE BRIDGE
EMPLOYEE connects responsibility to execution →
ACCOUNTABILITY WORK
B
WORK GRAPH

Where execution happens.

CLIENT City Infrastructure Program
COMMISSIONS
PROJECT ACTIVE
West Oakland Drainage Improvement
CONTAINS
DELIVERABLE Drainage Design Package
CONTAINS
WORK PACKAGE Hydraulic + Site Design
CONTAINS
TASK IN PROGRESS

Update drainage plan

WORK OBJECT ACCEPTANCE REQUIRED
CONTRIBUTOR LAYER Different relationships. Shared work.

A task can connect internal employees, external expertise, and employee-owned agents without treating them as the same kind of organizational actor.

01 EMPLOYEE
Illustration representing the Senior Project Engineer
INTERNAL CAPACITY

Senior Project Engineer

Assigned to project work through the internal organization.

ASSIGNED TO WORK →
02 CONTRACTOR
Illustration representing the Contract Hydraulic Engineer
EXTERNAL CAPACITY

Contract Hydraulic Engineer

Connected through project work rather than the employee hierarchy.

ASSIGNED TO WORK →
03 AI AGENT
AI
EXTENDED CAPACITY

Design Review Agent

Assists work under direct ownership of a human employee.

ASSISTS WORK →
SHARED WORK OBJECT Update drainage plan
EXECUTION → REVIEW → ACCEPTANCE
THE OPERATIONAL CHAIN
01 Organization
→
02 Human Accountability
→
03 Capacity
→
04 Work
→
NEXT Outcome
07 FROM STRUCTURE TO EXECUTION

The organization exists to deliver something real.

Organizational structure becomes meaningful when it is connected to an outcome. To test the model, I placed it inside a civil engineering project where internal teams, external specialists, and intelligent agents contribute to the same body of work.

The project gives organizational relationships a shared operational context.

PROJECT 01 West Oakland
Drainage Improvement
CONTEXT Civil Infrastructure
STATE Active
MODEL Multi-source capacity
Illustration of an urban infrastructure construction project
01
PHYSICAL SYSTEM Site
02
ENGINEERED SYSTEM Design
03
ORGANIZATIONAL SYSTEM Delivery
PHYSICAL PROJECT CONTEXT

A real project requires more than organizational structure. It requires coordinated expertise, decisions, work, review, and delivery.

ONE PROJECT / THREE CONNECTED SYSTEMS

The same project can be viewed through three different layers. Each answers a different operational question.

01
ORGANIZATION

Who is responsible?

Internal roles establish authority, ownership, and accountability for delivery.

DIRECTOR
PROJECT ENGINEERING
02
CAPACITY

Who or what can contribute?

Employees, contractors, and employee-owned agents provide different forms of project capacity.

H C AI
03
WORK

What must be delivered?

Projects become deliverables, work packages, and tasks that can be assigned and evaluated.

PROJECT DELIVERABLE TASK
THE WORK BECOMES VISIBLE

Organizational capacity becomes engineered work.

Inside the project, abstract relationships become specific assignments: analyze conditions, develop drawings, coordinate technical decisions, update plans, and prepare work for review.

01 Project need
02 Structured work
03 Technical output
TECH-01 ENGINEERING PLAN
Civil engineering site plan
OUTPUT Design documentation
STATE Prepared for review
Technical work is an output of the system—but an output is not yet an accepted outcome.
PROJECT CONTRIBUTION Different capacity converges on the same work.
H
EMPLOYEE Engineering
C
CONTRACTOR Specialist input
AI
EMPLOYEE-OWNED AGENT Assistance
WORK OBJECT Drainage Design Package EXECUTED
08 EXECUTION IS NOT ACCEPTANCE

Completed work still needs a decision.

A task can be executed by an employee, contractor, or intelligent agent without automatically becoming accepted project work. Execution records what was produced. Acceptance records a human decision about whether that work is ready to move forward.

Execution can be distributed. Acceptance remains an explicit point of accountability.

THE DISTINCTION
01
EXECUTION

The work was performed.

An assigned actor produced the requested output. The system can record who or what contributed, when it occurred, and what was produced.

EXECUTED
≠
02
ACCEPTANCE

The work can move forward.

An accountable human reviewed the output and made a decision: accept it, return it for revision, or prevent it from progressing.

HUMAN DECISION
REVIEW MAKES THE DIFFERENCE

The first output does not have to be the final output.

Technical work often moves through review and revision before it becomes accepted project work. Instead of treating this as failure, the system preserves the review cycle as part of the work history.

SYSTEM RULE Work can be complete as an execution event while remaining incomplete as an accepted outcome.
TECH-03 TECHNICAL REVIEW
REVISION REQUIRED
Civil engineering drainage plan with technical review markup
REVIEW Human evaluation
REVISION Changes required
OUTPUT STATE Executed
REVIEW STATE Revision required
ACCEPTANCE STATE Pending
The redline is not separate from the work. It is evidence of the decision process between execution and acceptance.
WORK STATE
Acceptance is a transition, not an assumption.

The system makes the review cycle visible instead of collapsing production and approval into a single “complete” state.

01 EXECUTED

Output produced.

SUBMIT →
02 HUMAN REVIEW

Output evaluated.

DECISION
03A REVISION REQUIRED

Return to active work.

03B ACCEPTED

Count toward accepted work.

REVISION LOOP Revision Required → In Progress → Executed → Human Review
WHO CAN EXECUTE? Different actors can produce work. The accountability model does not change.
H
EMPLOYEE Executes work
→ REVIEW
C
CONTRACTOR Executes work
→ REVIEW
AI
AI AGENT Executes / assists
→ HUMAN REVIEW
HUMAN ACCOUNTABILITY

The system records the decision. It does not make accountability disappear.

Acceptance does not claim that work is objectively perfect. It records that an authorized human reviewed the available output and made the decision to move it forward.

OUTPUT Produced
→
HUMAN Reviews
→
DECISION Accepted
09 WORK HAS A COST

Every outcome consumes something.

Once work is structured and accepted, the system can connect execution to the resources required to produce it. Hours, contracted capacity, and project costs become part of the same operational picture.

Progress tells us what was accomplished. Resource consumption tells us what it took.

01
WORK

Task

A defined unit of project execution.

Update drainage plan
CONSUMES →
02
RESOURCE

Hours

Labor or contracted capacity used by the work.

Actual consumption
INCURS →
03
ECONOMICS

Cost

The economic consequence of consumed resources.

Actual project cost
PROJECT ECONOMICS

The project now has two stories.

One describes how much work has moved forward. The other describes the resources consumed to get there. They influence one another, but they are not the same measure.

01 / WORK Progress
40%

Accepted work

How much of the approved project scope has reached an accepted state.

WORK SIGNAL ACCEPTED / BASELINE
02 / RESOURCES Consumption
52%

Budget consumed

How much of the approved project budget has been consumed by work performed so far.

ECONOMIC SIGNAL ACTUAL / BUDGET
≠
DO NOT COLLAPSE THESE SIGNALS

40% complete does not mean 40% of the budget should be gone.

Projects rarely consume resources in a perfectly linear relationship with completion. Early investigation, mobilization, specialist work, procurement, or other front-loaded activity can legitimately change the cost curve.

RESOURCE SOURCES

Cost can enter the project through different relationships.

The system preserves those differences rather than treating every contributor as interchangeable labor.

H
EMPLOYEE

Internal capacity

Employee time can be allocated across projects while organizational responsibility remains connected to the employee's permanent role.

TIME → WORK → COST
C
CONTRACTOR

External capacity

Contracted expertise can carry an authorized rate, available hours, actual hours, and resulting project cost.

RATE × HOURS → WORK → COST
AI
AI AGENT

Extended capacity

Agent activity remains connected to its human owner and the authorized work it supports rather than being treated as independent organizational labor.

ACTIVITY → WORK → RESOURCE USE
PROJECT BASELINE

Cost only means something in relation to a plan.

Rather than judging project performance from a single burn ratio, actual activity can be compared with the approved budget and the project's expected cost pattern.

BETTER QUESTION Are we consuming resources differently than we expected at this point in the project?
PROJECT West Oakland Drainage Improvement
ECONOMIC BASELINE
CLIENT VALUE $180K
PROJECT BUDGET $145K
TARGET MARGIN $35K
RESOURCE CONSUMPTION PROJECT TIME →
CURRENT
Planned baseline
Actual consumption
INTERPRETATION

A difference between planned and actual consumption becomes something to investigate—not an automatic judgment about project or workforce performance.

THE ECONOMIC MODEL Work creates evidence. Economics adds consequence.
01 Accepted Work
+
02 Actual Cost
+
03 Time
+
04 Baseline
→
NEXT Project Outlook
10 UNDERSTANDING PROJECT HEALTH

Project health is not one number.

Once structure, work, acceptance, resources, and cost are connected, the system can provide a more meaningful view of project health. But no single metric tells the whole story.

Health emerges from multiple signals interpreted together—not from a universal score.

PROJECT

West Oakland
Drainage Improvement

STATE Active
BASELINE Current approved plan
VIEW Operational outlook
PROJECT HEALTH MODEL

Five signals.
One project.

Each dimension answers a different question. Together they create a more useful operational picture.

01 PROGRESS
40% accepted

What has moved forward?

Accepted work compared with the current approved project scope.

ACCEPTED WORK
02 ECONOMICS
52% budget consumed

What is the work costing?

Actual and committed project costs compared with the approved economic baseline.

COST + FORECAST
03 SCHEDULE
44% time elapsed

Where are we in time?

Time elapsed, milestone status, and schedule variance against the approved plan.

TIME + MILESTONES
04 READINESS
1 critical dependency
TECHNICAL APPROVAL Pending

Can the project move forward?

Dependencies, approvals, blocked work, and other conditions that affect delivery readiness.

DEPENDENCIES + APPROVALS
05 CAPACITY
Coverage available
ENGINEERING
CAD
SURVEY

Do we have what the work requires?

Required capability compared with available and allocated project capacity.

CAPABILITY + ALLOCATION
INTERPRETING THE SIGNALS

The value comes from relationships between signals.

Individual metrics become more meaningful when they can be interpreted against the rest of the project.

PROGRESS 40%
OBSERVATION

Accepted work is moving forward.

TIME ELAPSED 44%
OBSERVATION

Progress and elapsed time are relatively close.

BUDGET CONSUMED 52%
INVESTIGATE

Consumption is ahead of both progress and elapsed time.

?
THIS IS A QUESTION, NOT A VERDICT

Is higher consumption expected at this stage of the project?

The difference becomes a signal to investigate against the approved baseline, committed costs, remaining work, and expected cost curve. The interface surfaces the condition; it does not invent the explanation.

PROGRESS ≠ READINESS

A project can be nearly complete and still unable to move forward.

Percentage complete describes accepted scope. It does not tell us whether a critical approval, dependency, or unresolved responsibility is preventing delivery.

ACCEPTED WORK 96.8%
→
!
DELIVERY BLOCKED Critical approval pending READINESS ≠ COMPLETION
FROM STATUS TO OUTLOOK

Health should help us look forward.

Historical metrics explain what has happened. Project decisions also require an estimate of what remains.

01 / ACTUAL What has happened?
Accepted work
Actual cost
Time elapsed
→
02 / REMAINING What is left?
Remaining scope
Required capacity
Open dependencies
→
03 / FORECAST Where are we heading?
Forecast cost
Schedule outlook
Projected margin

A forecast is an informed projection based on the current baseline and remaining work—not a guarantee.

SYSTEM VIEW WHAT THE MODEL CAN NOW CONNECT
01 Organization
→
02 Accountability
→
03 Work
→
04 Acceptance
→
05 Resources
→
06 Economics
→
07 Project
Intelligence
—
DESIGN DECISION

No magic health score.

Reducing progress, cost, schedule, readiness, and capacity to a single number would make the interface simpler—but the underlying decision less transparent. I chose to preserve the signals so people can understand what is driving the project's condition.

PROGRESS ECONOMICS SCHEDULE READINESS CAPACITY

11 Architecture → Interface

The interface needed to catch up with the idea.

The original interface represented the organization. The redesign needed to represent how the organization actually operates—across accountability, work, resources, intelligent systems, and evidence.

The interaction shift

The architecture stopped being something to explain. It became something the user could navigate.

01 Organization
02 Responsibility
03 Work
04 Evidence
05 Decision
01 / Navigate

From org chart to operational organization.

Selecting a person no longer reveals only a title and reporting line. It reveals an operational footprint—projects, accountability, owned agents, external relationships, and current work.

Operational Organization Explorer showing employee hierarchy and operational context.
Operational Organization Explorer

Organizational structure becomes an entry point into responsibility rather than the end of the experience.

Design consequence

Once the system could connect people to work, the interface could begin answering why.

02 / Inspect

Metrics became inspectable intelligence.

A project signal should not ask the user to trust a number. The interface exposes the source, calculation, context, and interpretation behind the value.

Project overview with rationale and evidence drawer explaining an operational metric.
Rationale / Evidence

Surface the condition. Expose the evidence. Leave consequential interpretation to the human.

03 / Execute

Organizational relationships became navigable work.

Project → Deliverable → Work Package → Task creates the execution structure, while employee, contractor, and AI relationships remain visible without pretending they are equivalent.

Project work hierarchy showing project, deliverable, work package, task, employee, contractor, and AI agent.
Structured Work

Accountability, assignment, contribution, and AI ownership remain distinct relationships.

04 / Trace

Activity became evidence.

The operational history preserves more than an activity feed. It records who or what acted, the related work, the state transition, and the human accountability surrounding that event.

AI activity does not become human acceptance. Execution, review, authority, and acceptance remain separately inspectable events.
Operational audit trail with event evidence showing AI activity, human ownership, related work, and state change.
Operational Audit Trail

What happened → who or what acted → under whose authority → what changed.

Product principle

The interface does not hide complexity by collapsing it. It makes the relationships behind a decision inspectable.

01 Organization
02 Accountability
03 Work
04 Evidence
05 Decision
Working model

Explore the interaction model.

The prototype explores how organizational structure, project work, evidence, resources, and human accountability can operate as one connected experience.

Explore prototype ↗

The result

Reflection →

12 Reflection

What the model revealed.

The exploration began with organizational structure. Following the relationships through work, AI, external expertise, acceptance, and economics revealed a more fundamental design problem: how responsibility survives complexity.

Primary insight

Designing for AI did not remove the need for human accountability. It made the need to model accountability more precisely impossible to ignore.

01

Membership and participation are different.

Employees belong to the organizational structure. Contractors participate through work. AI agents extend the capacity of a specific employee. Treating all three as equivalent resources would erase relationships the organization needs to understand.

02

Doing work and accepting work are different.

Execution can be distributed across employees, contractors, and intelligent agents. Acceptance is a separate decision with its own authority, evidence, and history. Activity is not the same thing as trusted progress.

03

Progress and consumption are different.

A completion percentage becomes meaningful only when considered alongside cost, elapsed time, remaining capacity, dependencies, and the approved baseline. The system should surface those relationships without turning them into an automatic judgment.

04

Complexity can live beneath a simple interface.

The underlying architecture can remain rich without appearing on screen all at once. Progressive disclosure allows the interface to reveal the relationship needed for the decision at hand while preserving the deeper system underneath.

What survived the complexity

After expanding the model and stress-testing its edge cases, the core architecture became simpler—not because the underlying system was simple, but because its organizing principle was clear.

01

Organization

02

Human Accountability

03

Work

04

Evidence

05

Decision

Time + Authorization
preserve the context around every relationship.

The larger question

How can an organization expand who—or what—can perform work without losing sight of who remains responsible for it?

The constant

Human accountability
remained the constant.

What began as an exploration of an HR management interface became a systems-design investigation into how people, intelligent agents, external expertise, work, evidence, and economics can remain connected without removing human judgment.