Separate test work from production
Organize development, preview, staging and production work explicitly. Review the variables and connected services for each environment rather than assuming they share data.
MolternProduct managers
For your team
Make the next experiment usable.
Give prototypes a shareable deployment and keep test work separate from the production environment.
Flight paths artwork / 07
An experiment becomes more useful when people can return to the same working URL. Agree on the audience and data boundary, deploy the smallest version, and give a technical owner responsibility for configuration, costs and the next release.
Put it into practice
Start with one useful team workflow
Choose a specific problem and the people who need the result. Involve a technical owner for configuration and access, then validate the workflow with its users.
Review capacity before you scale
Check the workspace plan, workload limits, CPU, memory and storage requirements. Review usage and applicable guardrails before adding or resizing resources.
Detailed instructions are maintained in the product documentation.
Questions before you start
Does a preview copy production data?
Do not assume it does. Configure appropriate test services and verify which data and variables the preview can access.
Can a non-developer start a project?
A business team can define the need and explore services. Involve an authorized technical owner for deployment and sensitive configuration.
Are program benefits or resource limits automatic?
Plans and eligibility differ. Use the pricing and billing pages for current terms; program benefits require individual confirmation.
Keep exploring
All pages ↗
Start with one useful workload.
Bring your code or choose a service, then give the result a clear operating home.
Start building ↗