1. Define the visitor’s decision
The example audience is designers choosing a lamp for an office. They need to compare dimensions and finishes, identify a model and request its technical sheet. The catalogue presents products rather than selling them online.
The intended journey is product list, product page, exploration and enquiry. Describe where visitors arrive and how they continue. Someone following a link directly to a product should recognise the item, the business and the contact option without visiting the home page first.
2. State what each choice changes
Each product page supports rotation, zoom within agreed limits and a command to reset the view. Visitors can select one of two finishes. The selected name and the visual preview must agree.
A visible finish does not establish stock availability. In this example it does not change price, power or dimensions. A configurator combining components would need separate commercial rules. List permitted combinations before adding more controls.
- Comparison: readable dimensions and characteristics for each model.
- Selection: product code and finish included in the summary.
- Enquiry: information required by the team responding.
- Exclusions: orders, payments, live availability and automatic prices.
3. Prepare an asset record for each product
For each lamp, record its code, verified dimensions, description, photographs, available 3D file and approved finishes. Assign ownership of missing information. Identify who prepares each item, who checks it and when it will be available.
Request a file assessment before estimating the whole catalogue. Conversion, simplification and material preparation should be visible scope items. Confirm usage rights too. The screen presentation in this example does not replace physical samples or technical documentation.
4. Describe the page without its scene
If the model does not load, keep an image, dimensions, written finish information and the enquiry action available. If selecting a finish is unavailable, the summary should say so rather than silently assign a choice.
Agree which phones and browsers will be tested. MDN explains that WebGL capabilities and limits differ between devices. A successful run on the developer’s computer is not enough to establish catalogue support for the intended audience.
5. Turn the brief into observable checks
Complete one representative product page before repeating the work. The person approving it should run these checks with the reference product information available.
| Check | Expected result |
|---|---|
| Select a finish | Preview, label and summary show the same selection. |
| Switch products | The enquiry uses the newly selected product code. |
| Reset the view | The product returns to the agreed starting position. |
| Open without 3D | Essential information and contact remain available. |
| Submit an enquiry | The received message contains the product and any finish chosen. |
6. Confirm the scope before requesting a quote
Compare proposals using the same sample product and catalogue list. Mark unresolved decisions explicitly: a file or interaction may need a small assessment before the full work can be confirmed. Keep proposed later additions separate so they do not quietly alter the first version.
- How many products and finishes must be available at launch?
- Which assets are ready, and which need to be produced?
- Which actions and information are essential to an enquiry?
- Who approves product information and its representation?
- Which checks define an acceptable first version?
Explore an example
Ospivia’s homepage is an internal project with a 3D scene. It is a visual reference, not the synthetic lamp catalogue described here.
Explore 3D development ↗Prepare your project brief
A reusable text template: objectives, users, features, materials and acceptance checks. Download it without registration and edit it with your team.
Download the project brief (.txt) ↓Technical references
Published by Ospivia Studio, prepared with AI assistance and checked against the linked technical sources. Examples are illustrative and are not customer results.