The software development framework for the agentic era.

From velocity to value - making software delivery transparent.

SUPPORTED BY LEADERS FROM

The Framework Guiding Principles Who's Behind It

Reframing What We Measure

Software delivery has long celebrated speed; DORA metrics, deployment frequency, and change lead time.

But speed without direction isn’t progress.

PRISM is an acronym for:
1. Product Requirements
2. Implementation
3. System Design
4. Measurable Impact

It shifts the focus from velocity to value.

It’s a framework and alliance that helps teams measure what truly matters: alignment, craft, and measurable impact across the software development lifecycle.

Guiding Principles

Principles that guide the framework and our belief in how product teams should focus on value creation.

PRISM
Guiding Principle

No. 1

Requirements
as Hypothesis

Requirements must be framed as impact hypotheses tied to a measurable North Star Metric (NSM).

Clear, testable, and traceable requirements form the backbone of the SDLC.

PRISM
Guiding Principle

No. 2

Design as a
Force Multiplier

Design should be validated early through prototypes and wireframes. Includes but is not limited to with engineering, product, and users.

Investment in design testing earlier in the lifecycle reduces cost and risk.

PRISM
Guiding Principle

No. 3

Engineering as
Craft & Enablement

Engineering excellence includes modularity, maintainability, performance, and security.

Tools and agencies should be evaluated on how they enable higher-quality engineering outcomes, not just speed.

PRISM
Guiding Principle

No. 4

Impact as the
North Star

The North Star Metric expresses delivered value to the customer and business.

Leading indicators (performance, quality, throughput) and trailing indicators (revenue, cost savings) roll up to the NSM.

PRISM
Guiding Principle

No. 5

Traceability
& Transparency

End-to-end visibility is essential: requirement -> design -> implementation -> outcome.

Traceability highlights early lifecycle investment and prevents costly rework later.

PRISM
Guiding Principle

No. 6

Async by Default,
Sync for Alignment

Default to asyncronous workflows for discovery, design reviews, planning/status, and decisions.

Use living docs, RFCs/ADRs, demos, and decision logs with clear SLAs.

Slide 1

Slide 2

Slide 3

Slide 4

Slide 5

Slide 6

Who's Behind It

A collective of product, design, and engineering minds who know there’s a better way to measure value creation beyond engineering velocity. This is about going from definition to delivery and creating real-world value and impact.