Autonomous Projects

How autonomous can
a company become?

Most companies are built around continuous human execution.

People coordinate processes, transfer information, make operational decisions, communicate between departments and ensure that work continues.

Technology has traditionally helped people perform these activities more efficiently.

Valend investigates a different question:

What happens when the organization itself is designed to require progressively less continuous human intervention?

The objective is not to remove humans from companies.

The objective is to understand where human involvement creates unique value and where organizational dependency on continuous human execution can be reduced.

Human responsibility, ownership, strategic direction and oversight may remain important even as operational dependency decreases.

re:one serves as a practical environment in which Valend can study this transition.

Metric

Human Dependency Ratio — HDR

The Human Dependency Ratio is an experimental Valend metric designed to measure how dependent an organization is on continuous human involvement.

100% Human Dependent
0% Human Dependent

Execution Dependency

How much operational work currently requires direct human execution?

Decision Dependency

How many operational decisions require a person before the organization can continue?

Coordination Dependency

How dependent are workflows, departments and information flows on humans coordinating them?

A Human Dependency Ratio of 100% describes an organization that cannot meaningfully operate without continuous human execution and coordination.

A lower Human Dependency Ratio indicates that larger parts of the organization can continue operating without continuous human intervention.

A Human Dependency Ratio of 0% is a theoretical reference point and should not be presented as necessarily desirable or achievable.

The purpose of the metric is to make organizational autonomy measurable and comparable over time.

Research Philosophy

Understand, not maximize

Valend does not assume that every organizational function should become autonomous.

Each function is studied individually.

For every area of the company, Valend asks:

01

What does this function actually do?

02

Why does it currently require humans?

03

Which dependencies exist between this function and the rest of the organization?

04

Which parts could theoretically operate with less continuous human intervention?

05

Where should human responsibility remain?

06

What new risks appear as dependency decreases?

The objective is to understand the organizational limits of autonomy rather than simply maximize automation.

Principle

Built for Autonomy. Validated by the Market.

Valend follows a clear principle:

Autonomy has no value if the product does not create real value for customers.

Every autonomous project therefore follows the principles of the Lean Startup methodology.

Valend does not begin by trying to maximize automation.

We begin with a real market problem.

A product is built, tested with real users and improved based on actual market feedback.

Only systems that demonstrate real customer value should continue to develop toward greater autonomy.

The Continuous Cycle

Build
Measure
Learn
Improve
Increase Autonomy

This means that technological autonomy and market validation develop together.

Market Before Autonomy

Market Validation Before Autonomy

An autonomous company cannot be successful simply because its technology is autonomous.

It must still solve a real problem.

It must attract users.

It must create measurable value.

And ultimately it must be able to sustain itself economically.

For this reason, every Valend project is continuously tested against the market.

Research Questions

?

Does the product solve a relevant problem?

?

Do customers actually use it?

?

Do customers return?

?

Are customers willing to pay?

?

Can the product deliver its value reliably?

?

Can the organization deliver this value with decreasing human dependency?

Autonomy is therefore not treated as the first objective. Customer value comes first. Autonomy is developed around a product that proves that it deserves to exist.

Product Design

Every Product is Designed Around HDR

Every Valend product is designed with the Human Dependency Ratio in mind from the beginning.

Traditional products are usually designed around features, processes and human roles.

Valend adds another design dimension:

How much continuous human dependency does this product and organization require?

For every new product, Valend therefore studies:

Execution dependency

Decision dependency

Coordination dependency

Human oversight requirements

Operational exceptions

Market dependency

The objective is not simply to automate individual tasks. The objective is to design the complete product and organization in a way that allows the Human Dependency Ratio to decrease over time.

Development Principle

The Valend Development Principle

Every project should follow four stages.

1

Problem

Identify a real market problem. Do not begin with automation technology. Begin with a customer need.

2

Product

Build the simplest product capable of solving that problem. Use Lean Startup principles to test assumptions quickly.

3

Market Validation

Expose the product to real customers. Measure usage, retention, feedback, willingness to pay and actual value creation. If the market does not validate the product, the project must adapt, pivot or stop.

4

Autonomy

Once the product demonstrates real value, progressively reduce unnecessary human dependency. Measure this development through the Human Dependency Ratio.

The cycle then continues

Market Feedback → Product Improvement → Organizational Improvement → Lower HDR

Competition

Autonomy Must Compete

Valend does not create autonomous systems only inside controlled experiments.

Ultimately, autonomous systems must operate in the same environment as traditional companies and products.

They must compete for:

CustomersRevenueQualitySpeedReliabilityCapitalResources

If an autonomous system requires permanent protection from real market conditions, it has not yet demonstrated organizational autonomy. For Valend, the market therefore becomes part of the experiment. An autonomous system must prove that it can create value in the real world.

Core Principle

Every Valend product must prove two things

1

It creates real market value.

2

It can progressively reduce its Human Dependency Ratio without destroying that value.

Neither result is sufficient on its own.

A highly autonomous product without customers has failed.

A successful product that cannot reduce its human dependency may still be a good company, but it has not yet achieved the research objective of Valend.

Market Value × Organizational Autonomy

Valend therefore studies the relationship between market value and organizational autonomy. The objective is to increase both.

Research System

Organization as a Research System

The diagram below shows the structure of a traditional company. Click on an area to explore its Valend research program.

Select an organizational area to see its research program.

Shape the research project

If you want to dive deeper into Valend's research on autonomous organizations or discuss a specific project, talk to us.

Request a conversation

Connect with Valend

Become part of the Valend idea forge and advance your applied AI venture.

We use cookies

We use cookies to ensure the basic functions of the website (technically necessary) and to analyse usage anonymously (only with your consent). Privacy Policy