Program design
Define the objective, the output, and what gets measured. The publication boundary is agreed up front.
- Category
- Scoping
- Includes
- Customer-approved program brief
- Good to know
- A design is not an outcome.
AuraOne / Customers / Reference engagements
AuraOne will publish customer quotes, names, and measured outcomes only after the customer approves the exact language and the result has supporting evidence.
Until then, review representative program designs as designs, not as customer proof. Reference conversations are arranged during program scoping only where a customer has approved them.
At a glance
How reference engagements work
A testimonial is earned after a customer accepts the work and approves publication. Every AuraOne program produces structured records that teams use to verify quality, provenance, and operational fit.
Define the objective, the output, and what gets measured. The publication boundary is agreed up front.
Retain the delivery record, the customer's acceptance, and the known limitations.
Publish only the quote, the result, and the scope the customer explicitly approves.