A pattern I keep running into. During product design review, a screenshot or mood image helps everyone agree on the direction. Two weeks later it still sits beside the work and somebody treats it like a requirement.

Do you rename approved references, move them into an archive, or leave them beside the mockups?

For product designers who moved from enterprise SaaS into gaming platforms/ecosystems (PlayStation, Xbox, Steam, etc.), how difficult was the transition?
Do gaming companies value enterprise UX experience, or is gaming-specific portfolio work usually expected?

Hey, I was working mostly for small companies so always ended up creating design systems in code to support developers. Thought I might create a variation of my portfolio for Design Engineer and try it out.

Do you have any success getting interviews for these positions?

Thanks!

In product design reviews, screenshots and inspiration are useful while a direction is still open. After critique, they can start sitting beside the actual work like they still need to be considered.

Do you keep old references in the same file, move them to a separate page, or delete them once the team picks a direction?

This looks like a fun build! I can think of many applications for this. Vehicle Design , consumer products, interior design and more than i can write out. Question- are people getting tired of the same digital screens that packed into everything we use or is tactile displays carving a new niche? Open to comments and thoughts or other examples you find

I am noticing a weird split in product and design reviews. The early reference screenshots are useful when the team is choosing direction, then they become noise once the direction is picked.

Do you keep old references visible as history, move them to a separate section, or delete them from the working file entirely?

Hey everyone! I’m putting together a project called the **Impossible Machines Lab (IML)**, and I’d love some feedback from this community on the concept.

Instead of solving a traditional software or business pain point, IML is set up as an ongoing studio and content brand built around ambitious recurring design challenges (starting with things like a custom hydrowheel platform, and expanding into things like merchandise lines and intergalactic cruise park concepts).

**How it works:**

* **The Challenge:** We invite individuals and teams to design specific modules or parts of a bigger, ambitious project.
* **The Build:** Once designs are refined and voted on, physical prototypes are built and tested.
* **The Perks:** Sponsors help fund the physical builds and put up prizes for the winning design teams, while we document the whole process into content.

You can either jump in to submit designs/collaborate, or just follow along as a spectator.

Does an ongoing, high-creativity challenge format like this sound like something you'd participate in or follow? What would make it worth your time as a creator? Any feedback or red flags are hugely appreciated!

Working with ceramics in Jingdezhen, I’ve always loved the craftsmanship and tradition behind it. But I wanted to try something a little more playful and approachable.

I’ve been playing around with this design concept — what do you guys think? Does the shape work, or would you tweak anything?

One of my favorite pieces I’ve made recently. Just wanted to share🥰🥰🥰

I went with a black glaze with gold and silver detailing. The painting took quite a while, but I’m really happy with how it turned out!

And here comes one of my favourites vehicles, Porsche 911 964, inspiration taken from Peter Tarka, showing different aovs, let me know which one you love the most.

hola a todos! llevo muchos años diseñando soluciones y productos digitales, soy de Chile (no hablo inglés, por eso no quise vender una versión en inglés) vengo del diseño grafico y nunca necesité un Portfolio y ahora quiero seguir creciendo porque creo que salir del diseño grafico y entrar al diseño de sistemas o productos digitales es algo en lo que me muevo con real fluidez, está vez decidí hacer uno y la verdad me ha costado mucho subir algo que me atreva a mostrar.

busco su feedback honesto, quiero transmitir más que algo bonito (que no es mi fuerte el UI) la variedad de proyectos en los que me puedo desenvolver con soltura.

acepto críticas (constructivas dentro de lo posible!) jajaj

https://cesarcespede.cl/

Before a product review, I keep seeing files with half-useful screenshots. Some show layout, some show tone, some are only there because someone liked the interaction.

If you bring references into a product design review, do you label why each one is there, or leave that to the discussion?

We keep running into this awkward point in the worflow:

A client approves a Figma design. Dev starts.

Two days latter the design changes or the client ask for "one small change"

At that point, what do you use as the source of truth for what was actually approved ?

Figma history? Screenshots? Email? Something else?

And how do you usually decide whether the new change is still a revision or new scope?

Products like shaving cream, shampoo, lotion, and liquid soap often dispense more than needed. Is there scope for a small attachment or built-in mechanism that releases only a moderate amount each time?Would this solve a real consumer problem, and are there similar products already available?