A useful 3D model is built for its intended use. A hero render, real-time game asset, product visualisation, and 3D-printable object have different requirements. Decide the target platform, scale, level of detail, and output format before modelling. ## Gather references and block the shape Collect multiple views and dimensions where available. Start with simple primitives and check proportions from several angles. Keep the silhouette readable before adding small details. ## Refine geometry Use clean topology where deformation or subdivision is needed. Apply bevels and supporting loops deliberately, and remove hidden geometry that adds complexity without improving the result. For real-time use, plan polygon count and level of detail around the target device. ## Materials and lighting Choose physically plausible material values and use appropriate roughness rather than making every surface glossy. Set a clear key light, fill light, and rim or environment light as needed. Test reflections and shadows at the final camera angle. ## Export and inspect Apply transforms where required, check scale and orientation, name objects and materials, and pack or document external textures. Export the format requested by the target application, such as GLB/GLTF for many web viewers. Re-import the exported file to verify materials, texture paths, animation, and axis orientation.
Practical implementation checklist
- Define the audience and the main action this page should support.
- Review navigation on desktop and mobile, then remove links that do not help visitors.
- Test important links, forms, phone numbers, and email addresses before publishing.
- Ask someone unfamiliar with the project to complete the main task and note where they hesitate.
Measure whether the change helped
Record a baseline before changing the page. Track relevant outcomes such as qualified enquiries, completed bookings, task completion, or support questions. Rankings and conversions can vary, so use meaningful periods and real user feedback.
Design around the user’s next decision
For each screen, identify what a person needs to understand and what action they should take next. Give that action a clear visual priority, use familiar labels, and place supporting information nearby. A decorative element should never make the main task harder to discover or complete.
Create spacing and type rules that remain consistent across the page. Related elements should feel grouped, while separate sections need enough breathing room to be scanned independently. Avoid squeezing text into narrow cards or relying on tiny type to fit an overloaded layout.
Test real content and awkward cases
Do not evaluate a design only with short sample labels and ideal images. Test long headings, missing images, validation messages, large numbers, empty results, and content that changes length. Check keyboard focus, contrast, zoom, touch targets, and narrow screens as part of the same review.
Ask someone unfamiliar with the interface to complete the main task without coaching. Observe where they hesitate or make mistakes. Their behaviour is often more useful than asking only whether the page looks attractive.
Improve the design in measured steps
Prioritise issues that block a task, hide important information, or cause repeated confusion. Fix those before spending time on small visual details. Change one meaningful area at a time where possible, then repeat the same task to see whether the experience improved.
Document reusable components and design decisions so new pages stay consistent. Consistency does not mean every section must look identical; it means controls behave predictably and visual differences communicate a real difference in purpose.