## Use Previews to Iterate
Before releasing your API plan to invest significant design effort, get customer feedback, & iterate through multiple preview releases. This is especially important for V1 as it establishes the abstractions and patterns that developers will use to interact with your service.

[:ballot_box_with_check:](#previews-hypotheses) **YOU SHOULD**  write and test hypotheses about how your customers will use the API.

[:ballot_box_with_check:](#previews-at-least-two) **YOU SHOULD**  release and evaluate a minimum of 2 preview versions prior to the first GA release.

[:ballot_box_with_check:](#previews-key-scenarios) **YOU SHOULD**  identify key scenarios or design decisions in your API that you want to test with customers, and ask customers for feedback and to share relevant code samples.

[:ballot_box_with_check:](#previews-code-with) **YOU SHOULD**  consider doing a _code with_ exercise in which you actively develop with the customer, observing and learning from their API usage.

[:ballot_box_with_check:](#previews-share-results) **YOU SHOULD**  capture what you have learned during the preview stage and share these findings with your team and with the API Stewardship Board.