Maximum Validated Progress per Unit of Time and Capital

Article 5 of 100 — The Product Side of Investment Performance

By Enrique Luis Sardi, Founder of SARDI and Co-Founder of SARDI PRO CAPITAL

Executive Summary

For product-centred portfolio companies, time is not merely a project-management variable.

Time influences:

Development expenditure
Competitive position
Revenue timing
Capital at risk
Market relevance
Organisational energy
The number of value-creation cycles available during the holding period

However, development velocity does not mean instructing teams to work faster, eliminate necessary validation or accept lower product quality.

SARDI PRO CAPITAL defines Development Velocity as:

Maximum validated progress per unit of time and capital.

The critical word is validated.

A team moving rapidly in the wrong strategic direction is not creating velocity. It is accelerating waste.

Genuine Development Velocity compresses the time needed to transform:

Capital into product assets
Knowledge into decisions
Opportunities into validated concepts
Concepts into industrialised products
Products into profitable revenue

It must accomplish this without increasing:

Strategic errors
Market risk
Technical or industrial debt
Rework
Product complexity
Organisational instability

Development Velocity is therefore not simply “faster development.”

It is a disciplined operating capability combining strategy, product intelligence, creativity, engineering, validation and decision-making.

SARDI PRO CAPITAL applies the FORMULA SARDI as a methodical and evidence-led system for achieving that capability.

Time Is an Investment Variable

A delayed product does more than create inconvenience.

It can postpone revenue, extend development expenditure, reduce the available market window and give competitors more time to establish customer relationships.

It can also leave capital trapped in unfinished development programmes that have not yet produced market evidence or economic returns.

For private equity investors, this creates a direct connection between development time and investment performance.

A shorter, well-controlled development cycle can:

Bring revenue forward
Bring cash flow forward
Reduce cumulative operating costs
Produce earlier market evidence
Accelerate the Value Creation Plan
Increase the number of product initiatives that can mature during the holding period
Strengthen the evidence available for the exit narrative

Research on new-product development generally associates development speed with improved project outcomes, but it does not support speed at any cost. One study of 197 managers found that faster speed to market was associated with better quality and lower costs in its sample. Other research warns that excessive compression can create diseconomies, while the economically appropriate launch timing depends on market size, margins, competition, product performance and the available market window.

The correct objective is therefore not minimum development time.

It is:

The shortest responsible path to validated economic value.

What Development Velocity Actually Measures

Development Velocity measures how efficiently an organisation reduces the uncertainties separating an opportunity from a commercially and industrially credible product.

Those uncertainties normally include:

Is the market opportunity real?
Which stakeholders determine the purchase?
What value must the product create?
What will customers pay for?
Can the product be technically realised?
Can it be manufactured at the required cost?
Can it achieve the required margin?
Can the company deliver it reliably?
Will the product remain competitive when launched?
Does the initiative support the investment thesis?

Development work creates value when it converts those uncertainties into evidence and executable decisions.

An attractive visual concept without technical feasibility is not sufficient progress.

A technically complete product without market relevance is not sufficient progress.

A validated concept without a viable COGS structure is not sufficient progress.

SARDI PRO CAPITAL therefore evaluates velocity across the complete product system rather than measuring engineering speed in isolation.

The Five Primary Advantages of Development Velocity

1. Cost Compression

Product development cost is not determined only by the hourly cost of designers, engineers and specialists.

It is also created by elapsed time.

Long development cycles can accumulate:

Repeated meetings
Project-management overhead
Context switching
Sequential handoffs
Reopening of previous decisions
Supplier waiting time
Management attention
Changing requirements
Duplicate analysis
Idle project periods
Rework caused by late discoveries

A concentrated development process can reduce these costs by shortening the period during which the project consumes organisational capacity.

This does not necessarily mean that every development day becomes cheaper.

Full-immersion phases may require greater daily intensity and more simultaneous participation.

The economic benefit arises because:

Specialists contribute at the moment their knowledge is needed.
Conflicts are identified earlier.
Decisions are not left waiting in organisational queues.
Workstreams advance concurrently.
Invalid directions are stopped before absorbing major investment.
The organisation maintains context instead of repeatedly rebuilding it.

The European Space Agency uses concurrent engineering to replace sequential specialist handoffs with multidisciplinary, real-time collaboration. ESA reports that this approach allows design changes and system-level consequences to be evaluated collectively as they emerge; ESA materials also document substantial reductions in conceptual-design duration in its own specialised environment.

SARDI PRO CAPITAL does not assume that ESA’s exact performance figures transfer automatically to industrial companies.

The transferable principle is stronger:

Waiting, handoffs, fragmented information and late conflict detection are development costs.

2. Time-to-Market Leadership

A shorter validated development cycle can allow a portfolio company to reach the market before competitors.

This can create:

Earlier revenue
A longer effective selling window
Earlier customer feedback
Earlier reference installations
Stronger distributor commitment
Faster installed-base creation
Greater opportunity to define customer expectations
More time to improve the product before competitors respond

Being first is not automatically valuable.

An early but weak product can educate the market for a better competitor.

Time-to-market leadership becomes valuable when the product reaches the market with sufficient:

Relevance
Reliability
Differentiation
Manufacturability
Margin potential
Commercial readiness

Development Velocity therefore seeks validated market leadership, not premature launch.

3. Innovation Anticipation

Companies often identify major product shifts only after competitors have made them visible.

By that stage:

Customer expectations may already be changing.
Competitors may control key accounts.
Suppliers may be aligned with another architecture.
Market standards may be forming.
The follower may be forced into reactive development.

Development Velocity improves the company’s ability to investigate future product opportunities before they become obvious.

This requires more than fast engineering.

It requires faster cycles of:

Observation
Product intelligence
Strategic interpretation
Hypothesis development
Conceptualisation
Validation
Investment decision

A company capable of moving through this cycle rapidly can identify potential product drivers earlier and decide whether to:

Lead
Follow deliberately
Partner
Acquire capability
Reject the opportunity

Innovation anticipation does not mean predicting the future with certainty.

It means reducing the time between detecting a relevant signal and making an evidence-based strategic commitment.

4. Organisational Agility

Many product-development delays are not technical.

They result from:

Unclear ownership
Competing priorities
Long approval chains
Part-time participation
Functional silos
Missing information
Risk avoidance
Excessive committee escalation
Decisions deferred until the next monthly meeting

Development Velocity creates organisational agility by establishing:

A clearly defined product mission
Explicit decision rights
A small cross-functional core team
Direct access to relevant executives
Shared evidence
Short decision cycles
Protected working time
Fewer organisational handoffs

Agility does not mean absence of control.

It means that governance is designed to produce timely, informed decisions rather than procedural waiting.

5. Momentum Creation

Product programmes influence the psychology and behaviour of the organisation.

A programme that produces no visible progress for months can create:

Internal scepticism
Declining management attention
Employee fatigue
Supplier disengagement
Loss of customer interest
Competition for resources
Pressure to reduce investment

A programme that produces a sequence of validated outcomes can create momentum.

Examples include:

A validated customer problem
An approved product strategy
A costed concept
A functional prototype
A confirmed manufacturing route
A customer validation
A pilot order
A market-ready product

Each result makes the next commitment easier to justify.

Momentum can attract:

Management support
Internal talent
Specialist partners
Supplier participation
Customer involvement
Commercial attention
Additional capital

Momentum should not be confused with theatre.

Frequent presentations, prototypes or announcements do not constitute progress unless they reduce material uncertainty or move the product toward economic reality.

The Wider Economic Advantages

The five primary advantages create several additional effects relevant to private equity.

Earlier Revenue and Cash Flow

Reducing the period between investment and commercial availability can bring forward the revenue curve.

The value depends on:

Adoption
Product margin
Market size
Production capacity
Commercial execution

Speed alone does not guarantee revenue, but delay makes earlier revenue impossible.

Lower Capital at Risk

At any point in development, capital is exposed to unresolved market, technical and industrial assumptions.

Fast validation allows weak initiatives to be stopped earlier.

This can reduce:

Sunk development cost
Tooling committed to invalid concepts
Inventory linked to premature designs
Engineering resources locked into low-value programmes
Management commitment to politically protected projects

The objective is not to make every initiative succeed.

It is to make success or failure visible before disproportionate capital has been consumed.

Faster Market Learning

The market provides information that internal discussion cannot completely reproduce.

Earlier concept testing, prototypes, simulations, customer trials and pilot deployments can reveal:

Unanticipated use conditions
Buying objections
Missing stakeholders
Price sensitivity
Installation problems
Operational advantages
Product-service opportunities

Development Velocity brings the learning event forward.

More Strategic Optionality

A fast and disciplined development capability allows an organisation to explore several alternatives before committing to one architecture.

It can also preserve the option to:

Change direction
Reposition
Simplify
Stop
Partner
Reuse a platform
Enter an adjacent market

Slow development frequently reduces optionality because the organisation becomes economically and emotionally committed to its first direction.

Reduced Obsolescence Risk

The longer a product remains in development, the greater the possibility that:

Customer needs change
Technology advances
Competitors launch
Regulation changes
Component availability shifts
Cost assumptions become outdated

Development Velocity reduces the distance between the evidence used to define the product and the market conditions present at launch.

Earlier Value-Creation Evidence

Private equity boards need evidence that the investment thesis is becoming operationally real.

A fast sequence of validated product milestones can provide earlier visibility into:

Margin opportunities
Market relevance
Development feasibility
Customer demand
New growth engines
Organisational capability

This allows the sponsor to update capital allocation and risk assessments earlier.

More Value-Creation Cycles During Ownership

A long development cycle may allow only one substantial product transformation during the holding period.

A faster capability can permit several cycles:

Initial product correction
Margin redesign
New platform development
Market-specific variants
Adjacent growth products
Exit pipeline preparation

The advantage is not simply more launches.

It is more opportunities to convert product intelligence into enterprise value before exit.

Faster Post-Acquisition Alignment

The first months following acquisition often contain:

Competing interpretations of the investment thesis
Unresolved legacy initiatives
Management uncertainty
Unclear product priorities
New reporting expectations

A concentrated Product Value Creation process can rapidly establish:

The product baseline
Priority initiatives
Decision rights
Economic targets
Development sequence
Required resources

This gives management and the investor a shared operating agenda.

Stronger Exit Readiness

A future buyer can place greater confidence in a company that can demonstrate:

A credible product pipeline
Shorter development cycles
Repeatable development capabilities
Validated new growth products
A coherent product platform
Evidence of product-market fit
Reduced product risk

Development Velocity can therefore contribute not only to current earnings but to the credibility of future growth.

What Development Velocity Is Not

Development Velocity is not:

Removing every development phase
Launching incomplete products
Reducing customer research
Avoiding engineering validation
Ignoring manufacturing
Forcing permanent overtime
Making decisions without evidence
Accepting technical debt silently
Moving quickly to create an appearance of progress

Research on accelerated development identifies both benefits and potential time-compression diseconomies. Product-development performance and timing must be considered together rather than treating minimum time as an independent objective.

The correct principle is:

Compress waiting, fragmentation, ambiguity and rework—not essential thinking, evidence or validation.

The FORMULA SARDI Approach

SARDI PRO CAPITAL applies FORMULA SARDI as a structured operating approach to product strategy, creativity and development.

SARDI publicly describes the SARDI FORMULA as the product of multidisciplinary capabilities and a problem-solving approach developed across industrial machinery, manufacturing equipment and market-driven products.

FORMULA SARDI should not be described as laboratory science.

Its scientific character lies in its discipline:

Observation before conclusion
Evidence before commitment
Hypotheses made explicit
Alternatives compared
Assumptions tested
Results measured
Decisions revised when evidence changes

In the SARDI PRO CAPITAL context, FORMULA SARDI connects eight activities.

1. Define the Economic Objective

Every programme begins with a relevant investment objective:

Margin
Growth
Market access
Product-market fit
Development speed
Pricing power
Risk reduction
Enterprise value

The product brief follows the economic objective—not the reverse.

2. Map the Complete Product System

SARDI PRO CAPITAL examines:

Customers
Users
Buyers
Specifiers
Operators
Service teams
Suppliers
Production
Commercial teams
Regulation
Competitive alternatives

This avoids developing a product around the assumptions of only one internal function.

3. Extract Product Intelligence

Product intelligence converts observations, market evidence, technical knowledge and stakeholder behaviour into decision-relevant information.

The objective is to identify:

What matters
What does not matter
What remains uncertain
Where value is being lost
Where differentiation may exist
Which assumptions require validation

4. Formulate Product Hypotheses

A product direction is treated as a hypothesis.

For example:

Reducing setup complexity will increase customer adoption and reduce service cost.

A modular architecture will lower COGS and accelerate market-specific variants.

A redesigned premium offer will increase price realisation.

Each hypothesis identifies what must be true for the initiative to create value.

5. Develop Alternatives Concurrently

FORMULA SARDI avoids committing prematurely to one solution.

Market, design, engineering, cost and manufacturing perspectives are considered together.

This is consistent with the logic of concurrent engineering, where relevant disciplines work on a shared and evolving design rather than exchanging completed work sequentially. ESA describes this approach as a systematic, multidisciplinary environment in which perspectives are considered in parallel and changes are assessed collectively.

6. Validate the Critical Assumptions

Not every element requires the same level of proof at the same time.

SARDI PRO CAPITAL prioritises the assumptions capable of invalidating the programme:

Customer relevance
Technical feasibility
Cost feasibility
Product safety
Manufacturing feasibility
Regulatory viability
Commercial logic

Validation effort is directed toward the highest-risk unknowns first.

7. Make Explicit Decisions

Each major decision records:

Available evidence
Assumptions
Alternatives considered
Expected effect
Responsible owner
Conditions requiring revision

This creates speed without losing organisational memory.

8. Convert Validation Into Industrial Reality

Velocity is incomplete until the validated product becomes:

Manufacturable
Supplyable
Commercially supportable
Serviceable
Economically credible
Available to customers

FORMULA SARDI therefore connects product strategy and creativity with engineering, industrialisation and market readiness.

Full-Immersion Development

SARDI PRO CAPITAL uses full immersion during phases where concentration and cross-functional interaction can materially reduce elapsed time.

Full immersion means that a selected team works with protected attention on one clearly defined product mission for a concentrated period.

The team may include:

SARDI PRO CAPITAL product specialists
Portfolio company management
Engineering
Manufacturing
Commercial leadership
Finance
Supply-chain representatives
Selected customers or suppliers

The Advantages of Full Immersion

Context Is Preserved

Team members do not need to reconstruct the project’s logic at every meeting.

The problem, evidence and current decisions remain cognitively active.

Handoffs Are Reduced

Questions that would normally travel between departments can be answered directly.

Work Becomes Concurrent

Design, cost, engineering, market and manufacturing implications can be evaluated together.

Contradictions Surface Earlier

A commercial ambition that creates an industrial impossibility becomes visible before months of work are committed.

Shared Understanding Improves

Different disciplines hear the same evidence and understand why decisions are being made.

Creative Depth Increases

Protected concentration gives teams sufficient time to move beyond the most obvious solutions.

Decisions Become Executable

The necessary decision-makers and specialists are available while the issue remains current.

ESA’s concurrent-design experience offers a strong example of the underlying mechanism: specialists work in real time on a shared model so that changes, dependencies and constraints can be identified immediately rather than discovered after sequential handoffs.

Full Immersion Is Not Permanent Intensity

Full immersion is most useful during:

Product-strategy definition
Concept development
Architecture decisions
Critical validation
Recovery of delayed programmes
First-100-day planning
Design-to-value programmes

It should not become a permanent state.

Continuous full immersion can create:

Fatigue
Reduced reflection
Narrow attention
Weak documentation
Burnout
Exclusion of important external perspectives

The correct model alternates concentrated collaboration with individual analysis, external validation and recovery time.

The Daily Steering Committee

During accelerated phases, SARDI PRO CAPITAL can establish a daily steering committee.

This is not a daily board meeting.

It is a short, decision-focused governance mechanism.

A typical committee may include:

The programme sponsor
A portfolio company executive
The accountable product owner
The SARDI PRO CAPITAL programme lead
A rotating specialist when required

Its Purpose

The daily steering committee exists to decide:

What is blocked?
What evidence has changed?
Which trade-off requires authority?
Which resource is missing?
Which assumption has been invalidated?
Which scope or priority must change?
What must be decided before the next working cycle?

Project governance literature identifies the sponsor and steering committee as central governance roles and emphasises that governance must establish clear and consistent decision rules. PMI also notes that project work involves continual decisions concerning priorities, resources, approaches and timelines.

The Advantages

A well-designed daily steering committee can:

Reduce decision latency
Prevent unresolved issues from blocking several teams
Maintain alignment with the investment thesis
Make trade-offs visible
Control scope
Accelerate resource allocation
Detect material deviation early
Preserve executive attention
Create accountability

The Required Discipline

The meeting should normally be brief and cover decisions rather than general status.

Each issue should arrive with:

The decision required
Relevant evidence
Available alternatives
Recommended option
Consequences of delay
Named decision owner

A daily steering committee becomes counterproductive when it:

Includes too many participants
Reopens settled decisions without new evidence
Micromanages specialists
Becomes a reporting ritual
Lacks authority to decide
Generates new work without removing priorities

The value comes from daily decision capacity, not daily meeting frequency.

Daily Decisions

Development speed is frequently determined by decision speed.

A team cannot advance when it is waiting for:

Market selection
Cost targets
Feature priorities
Architecture approval
Supplier choice
Prototype funding
Regulatory interpretation
Product-positioning decisions

Daily decisions do not mean making every decision impulsively.

They mean creating a system in which material decisions are addressed at the speed required by the project.

Four Principles

1. Separate Reversible and Irreversible Decisions

Reversible decisions can often be made rapidly and tested.

Irreversible or capital-intensive decisions require greater evidence and authority.

2. Decide at the Lowest Competent Level

Escalation should occur only when the decision exceeds the team’s mandate, capital threshold or risk authority.

3. Record Assumptions

A decision should preserve the assumptions that justified it.

This allows the organisation to revise the decision when those assumptions change.

4. Place a Deadline on Deferral

“Not yet” can be a valid decision.

It must include:

The missing evidence
The responsible person
The next decision date
The cost of waiting

An unresolved issue without a decision date is not governance.

It is delay.

PMI describes iterative programme management as a sequence of smaller ongoing decisions aligned with a shared strategic vision. This supports the principle that governance can be both disciplined and continuous rather than dependent only on infrequent stage reviews.

Measuring Development Velocity

Development Velocity should not be measured by counting tasks completed.

SARDI PRO CAPITAL recommends a scorecard connecting progress, evidence, time and capital.

Core Metrics

Time to Validated Product Strategy

Time from programme initiation to an approved strategy supported by market, technical and economic evidence.

Time to Validated Concept

Time required to produce a concept that meets defined customer, technical, industrial and financial criteria.

Time to Critical-Risk Resolution

Time required to resolve the assumptions most capable of invalidating the initiative.

Decision Latency

Elapsed time between identifying a decision requirement and receiving an executable decision.

Development Cost to Validation

Capital consumed before the initiative achieves a defined evidence threshold.

Rework Ratio

Percentage of development effort required to correct work caused by avoidable late discovery or unclear decisions.

Time to Industrial Feasibility

Time required to establish a credible manufacturing, supply and COGS path.

Time to Market

Time between the agreed programme start and validated commercial availability.

Time to First Revenue

Time between investment approval and the first economically meaningful customer revenue.

Validated Progress per Unit of Capital

The amount of strategically relevant uncertainty resolved for the capital deployed.

A Development Velocity Board View

A PE board does not need a detailed engineering dashboard.

It needs visibility into whether development capital is being converted into investment value.

A concise board view can include:

Current validated stage
Capital deployed
Capital remaining
Critical assumptions resolved
Critical assumptions unresolved
Decision latency
Time-to-market forecast
Expected product economics
Product-market-fit evidence
COGS confidence
Industrialisation confidence
Key risks
Value-creation impact
Required sponsor decisions

This allows the board to distinguish between:

Fast and validated progress
Fast but unstable progress
Slow but deliberate progress
Slow progress caused by organisational friction
Activity without meaningful progress

The Development Velocity Paradox

The fastest organisations do not necessarily rush.

They often appear fast because they invest earlier in:

Clear objectives
Appropriate expertise
Shared information
Early validation
Cross-functional integration
Explicit decisions
Manufacturing considerations
Customer evidence

They prevent late surprises rather than recovering from them.

This produces the central paradox:

The disciplined organisation can move faster because it spends less time correcting avoidable errors.

FORMULA SARDI supports this logic by integrating strategic, creative, technical and economic thinking from the beginning rather than allowing each discipline to work in isolation.

What SARDI PRO CAPITAL Contributes

SARDI PRO CAPITAL acts as the product operating layer between the investment thesis and product reality.

SARDI PRO CAPITAL contributes:

Product intelligence
Product strategy
Stakeholder understanding
Structured creativity
Design-to-value
Product architecture
Development coordination
Validation
Investor-grade reporting
Hands-on execution

SARDI PRO CAPITAL does not seek speed as an isolated achievement.

SARDI PRO CAPITAL seeks to increase:

Validated product value created per unit of time and invested capital.

The purpose is not to make the organisation permanently faster at everything.

The purpose is to make it faster at the decisions and activities that determine product-led enterprise value.

Key Takeaways

Development time is an investment variable.
Development Velocity means maximum validated progress per unit of time and capital.
Speed without validation can accelerate waste.
Cost compression results from reducing waiting, handoffs, fragmentation and avoidable rework.
Time-to-market leadership requires sufficient relevance, quality, manufacturability and margin.
Innovation anticipation shortens the distance between emerging signals and evidence-based investment.
Organisational agility depends on decision rights and governance, not absence of control.
Momentum is created through visible, validated progress.
Full immersion preserves context and enables concurrent cross-functional work.
Daily steering committees should decide, not merely review status.
Daily decisions require evidence, authority and traceability.
FORMULA SARDI integrates product strategy, creativity, validation and industrial execution.
The objective is the shortest responsible path from opportunity to profitable market reality.

Frequently Asked Questions

What is Development Velocity?

Development Velocity is the ability to convert capital, knowledge and opportunities into validated, economically credible products within the shortest responsible time.

Is Development Velocity the same as time-to-market?

No. Time-to-market is one outcome. Development Velocity also measures validation, decision speed, capital efficiency, risk reduction and industrial readiness.

Can faster product development reduce cost?

It can reduce accumulated coordination, management, waiting and rework costs when acceleration comes from integration and earlier validation. Speed created by skipping essential work can instead increase total cost.

Does acceleration reduce product quality?

Not necessarily. Research has found contexts in which development speed is associated with better quality and lower cost, but excessive compression can create trade-offs and diseconomies. The outcome depends on how acceleration is achieved.

What is full-immersion development?

Full immersion is a temporary operating mode in which a protected, multidisciplinary team works intensively on one defined product mission with direct access to evidence and decision-makers.

Why use a daily steering committee?

A daily steering committee can remove blockers, make time-sensitive trade-offs and prevent unresolved decisions from stopping development during intensive programme phases.

Does daily decision-making mean deciding without sufficient evidence?

No. It means that evidence requirements, decision rights and deadlines are defined so that necessary decisions do not remain unresolved unnecessarily.

What is FORMULA SARDI?

FORMULA SARDI is SARDI’s multidisciplinary and problem-solving approach to product strategy and development. SARDI PRO CAPITAL applies its evidence-led logic to product-centred private equity value creation.

How should a PE board measure Development Velocity?

The board should monitor validated milestones, decision latency, capital used, critical risks resolved, rework, time-to-market, industrial confidence and expected economic contribution.

About Enrique Luis Sardi

Enrique Luis Sardi is an entrepreneur, strategic designer and founder of SARDI.

His work focuses on industrial product strategy, stakeholder-centred development, Product Intelligence and the creation of innovative physical products for B2B companies.

Through SARDI and FORMULA SARDI, Enrique Luis Sardi has developed a multidisciplinary approach connecting market relevance, strategic creativity, product development and economic value.

About SARDI PRO CAPITAL

Founded by entrepreneurs Enrique Luis Sardi and Adrian Soto, SARDI PRO CAPITAL is a specialised spin-off of SARDI.

SARDI PRO CAPITAL is the Product Operating Partner for private equity firms and product-centred portfolio companies.

SARDI PRO CAPITAL applies Product Intelligence, FORMULA SARDI and hands-on execution to compress the responsible path between product opportunity, validation, industrialisation and profitable revenue.

SARDI PRO CAPITAL — The Product Side of Investment Performance.

DEVELOPMENT VELOCITY: HOW PRODUCT-CENTRED PORTFOLIO COMPANIES TURN TIME INTO ENTERPRISE VALUE