# Common failure modes * Adopting CVA in principle while leaving the legacy operating model in place * Creating slices that are too broad in scope * Creating slices that fail to engage your full organizational ecosystem * Using deterministic measures of success to gauge performance * Targeting outputs over outcomes {% hint style="success" %} ***Pragmatic Insight:*** *CVA is ultimately about product creation as your primary business capability. Budget and schedule are legacy governance modes that destroy this capability. Using these measures, your teams will either: a) Re-implement your last system with vague promises of achieving the higher-order customer experience goals “next year”, or they will b) aggressively copy the best-in-class work of the last three years. In both cases, you don’t have a customer experience model that works in complex environments (see* [*Part I*](/the-better-way/01-the-big-picture/part-one-introduction.md)*), or that creates customer-obsessed teams that instead produce the work that others will copy in the future.* {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://tbw.rangle.io/the-better-way/02-the-better-way/principle-one-focus-on-customer-value-and-adaptability/common-failure-modes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.