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?
Working on Pinterest for Miro has made me care way too much about boring labels.
At first I wanted imported pins to land cleanly in Miro. Now I think the source labels matter more than I expected. Which board it came from, what got skipped, and why the layout changed.
It feels less clever, but probably more useful. If you build tools that move user content around, do you keep source details visible by default or only show them when something goes wrong?
After a review, I often see the comments get resolved but the reason disappears. A screenshot, color ref, or layout example stays in the file, but the actual yes/no decision is only in someone's memory.
In Figma team files, do you keep a small decision note near the references, or is that overkill once the review is done?
Yesterday a few comments made me rethink a small part of Pinterest for Miro. I was treating the post-import screen like a place to say done. Now I think it needs to say what changed, what failed, and what the app chose to skip.
The annoying part is that every extra line makes the importer feel heavier, but hiding it makes people trust it less.
If you are building import or sync flows, where do you put the messy details?
I used to think the cleanest client presentation was only the polished moodboard. Lately I keep wondering if a small not-picked section helps clients understand why the final direction won.
For interior projects, do you ever show the references that almost made it, or does that just reopen decisions you already made?
Building Pinterest for Miro has been making one thing obvious. People do not really trust an import because it says done. They trust it when they can see what came across, what failed, and what still needs cleanup.
I started wanting the Pinterest to Miro move to feel invisible. Now I think the better version is boring and explicit. Show the imported pins, missing images, duplicates, and anything that needs a manual decision.
For anyone building import or sync tools, do you keep the result screen tiny or do you give people a proper receipt?
After a while, adding more images does not make the direction clearer. It just gives people more things to compare.
Do you set a point where a moodboard becomes for choosing instead of collecting, or do you keep adding references until the answer feels obvious?
I thought the hard part would be moving saved pins into a Miro board.
The comments are pushing me toward a less flashy problem. What happens the next time someone imports the same source, and how clearly the app explains what it will leave alone before touching the board.
So today's work on Pinterest for Miro is mostly the screen before anything changes. Added, changed, no longer saved, and left alone need to read like normal product language, not a scary diff.
If you have built importers or sync tools, did you make people review every item or show a short summary first?
When a Figma file has reference screenshots next to the actual work, the screenshot can mean three different things.
One person added it for layout. Someone else sees color direction. A PM sees a competitor. By the time feedback starts, everyone is talking about the same image for different reasons.
Do you label references by what they show, why they were added, or the person who added them?
When you are presenting a visual direction, I am curious how much of the original reference pile you keep visible.
I can see the argument for showing the full moodboard because it explains the thinking. I can also see the opposite. Too many almost-right images can pull the conversation back into old options.
For client reviews, do you usually keep the whole reference board visible, or make a tighter version with only the images tied to a decision?
I am building Pinterest for Miro, and the thing I keep underestimating is not the first import.
The first import can be treated like a clean transfer. Pins come in, images land on the board, everyone is happy enough.
The second import is where the product starts to feel honest or confusing. A few pins were deleted. A few new ones were saved. Someone may have already reviewed the Miro board. If the app silently replaces things, people lose the reason behind the change. If it shows every change, the board starts feeling like a log file.
So I am starting to think the resync screen matters more than the import button. The tiny wording around skipped, removed, and newly added pins is doing more product work than I expected.
No link. Just a build note from a weirdly visual edge case.
I have been thinking about the point where a reference image stops helping a product or design review.
Early on, a screenshot or pin can be enough to say this is the mood. Later, the same image can turn into background noise unless someone labels the specific decision it is supposed to support.
I am starting to prefer fewer references in the review view, with a plain note next to each one. Color direction, interaction example, layout density, tone, or avoid this.
When you are reviewing visual direction with teammates, do you keep the original pile visible, or only the few references tied to decisions?
I am building Pinterest for Miro, and the more I test the import path, the less I think the hard part is pulling images across.
The awkward bit is what happens after the first clean import. People do not just move pins once. They come back after a client review, add a few new references, remove a few, then expect the Miro board to still make sense.
So I am treating the importer less like a transfer button and more like a repeatable handoff. It needs to make changed, skipped, and newly added references understandable without turning the board into a changelog.
No link. Mostly writing this down because visual tools make backend choices weirdly visible.
During early interior direction work, I keep wondering what happens after a client says no to an inspiration image.
If the image stays on the board with a note, it can stop everyone from circling back to the same idea. But it also keeps the no pile in front of the client, which can make the board feel heavier than it needs to.
If you remove it, the board looks cleaner, but the reason for the decision disappears.
Do you keep rejected references visible during the next review, or move them somewhere private?
I am building Pinterest for Miro, and one product detail keeps feeling less technical than I expected.
If someone imports a Pinterest board twice, what should happen to pins that are already in Miro? Skip them quietly, add duplicates, update the old ones, or keep a little note that says this pin was seen before?
The cleanest answer for engineering is not always the clearest answer for a person building a moodboard. They may want to know if a reference came back because it still matters, or if it is just the same pin being retried.
No link. I am mostly writing this down because retry behavior sounds invisible until the thing being moved is visual research.
During early visual direction work, I keep seeing teams split the references from the actual design file.
One person wants the Pinterest or screenshot references near the components so the reason for a choice is obvious. Someone else wants the Figma file clean and keeps references in a separate board or doc.
Both make sense. The messy part is review. By the time a teammate or client asks why something looks a certain way, the reference is usually somewhere else.
Where do you keep the references during critique, in the Figma file, a separate board, or only in notes?
I mean during the moodboard stage, before anything is final.
If a client says no to a material, color, or room reference, I am never sure whether it should stay on the board with a note, move to a rejected pile, or disappear completely.
Keeping it visible can stop the same idea coming back later. But it can also make the board feel cluttered and negative.
What do you usually do?
I am building Pinterest for Miro, and I keep finding that the import is the easy part to explain.
The harder bit is what happens after the pins land in Miro. Someone needs to know why a pin is there, what was rejected, what still needs review, and which images are just background inspiration.
I nearly treated all of that as cleanup. It is starting to feel like the actual product, even if it is less flashy than moving the pins over.
No link. Mostly writing this down because the boring follow-up work keeps changing what I build.
I like adding notes so the reason for each image does not disappear, but too many labels make the board feel like homework.
The worst version is when every reference has a paragraph and nobody looks at the images anymore.
When you share a moodboard, do you label the references up front, or leave the first pass mostly visual and explain it live?
I like adding notes so the reason for each image does not disappear, but too many labels make the board feel like homework.
The worst version is when every reference has a paragraph and nobody looks at the images anymore.
When you share a moodboard, do you label the references up front, or leave the first pass mostly visual and explain it live?