Which of the following is a valid step in the FOCUS Dataset workflow?

• A. Build a specification detailing and metrics
• B. Ignore community input
• C. Build vendor invoices without standardization
• D. Create a proprietary pricing model

Answer: (A)

The main idea here is establishing a clear, shared blueprint for what will be captured and how it will be measured. Building a specification that details the metrics provides the foundation for the entire workflow: it defines the data model, what each metric means, how data will be collected, and what quality criteria must be met. With this specification, everyone uses the same definitions, enabling consistent data gathering, validation, and analysis across teams and providers. Without it, later steps become ambiguous and data can be interpreted in conflicting ways, making it hard to compare results or trust the dataset.

Why this is the best choice: it creates the standardized framework that drives reliability and interoperability. When you have a formal specification of metrics, you can design data collection processes, quality checks, and reporting around a common baseline, which is essential for meaningful FinOps insights.

Why the other options don’t fit: ignoring community input undermines collaboration and transparency, which are crucial for a dataset that many stakeholders rely on; building vendor invoices without standardization introduces inconsistency and breaks comparability; creating a proprietary pricing model reduces transparency and hinders broad reuse of the dataset.