u/Plastic_Catch1252

I am curious how people handle this in real teams.

At the start of a project, reference boards are supposed to be messy. Screenshots, Pinterest saves, old UI examples, brand bits, color ideas, competitors, random details that only matter for one corner of the work.

That mess is useful while exploring, but it gets harder when the team needs to decide what actually belongs in the system. People react to old directions, or a reference gets kept because the vibe is right even though nobody wrote down what part of it matters.

Do you keep the big research board and annotate it, or do you make a smaller decision board once patterns and rules start forming?

I'm curious how other architecture students handle this.

Early in a project I save way too many references: plans, facades, material photos, diagrams, random Pinterest stuff, projects that only have one detail I like.

It helps at first, but by the time I need to explain the idea, the board is kind of a mess. Half the images are not really part of the direction anymore. They were just stepping stones.

Do you keep one big reference board and label everything, or do you make a smaller board just for crit so people do not get distracted by old ideas?

Curious how brand folks handle this.

At the start of a project I like messy reference boards: old campaigns, type samples, product screenshots, colors, random Pinterest saves, competitors, whatever gets the direction moving.

The problem is later. Once a direction starts to harden, the board still has a lot of stuff that was useful at the time but is not really part of the final logic. If a client or teammate opens it, they can read an early maybe as if it is still part of the direction.

Do you keep one messy internal board and make a cleaner client-facing version, or do you keep everything in one place and label the references more carefully?

Curious how people here handle references once a project moves past the early moodboard/styleframe phase.

Early on, a board can be messy: animation references, transitions, color, type, pacing, bits from ads or title sequences.

Later it gets awkward. The board has too much stuff on it, and half the references only helped shape an early direction. If a client or teammate looks at it later, they can read old maybes as if they are still part of the direction.

Do you keep one big board and mark what is approved, or split it into a cleaner client/team board once the direction is set? Also curious where you keep the notes on why each reference is there.

I am curious how other game teams handle visual references after the early exploration phase.

At the start, I like having a messy board. Environments, UI screenshots, lighting, character ideas, random texture references, whatever helps the direction form.

The problem is later. Half of that board is no longer relevant, but it still sits there and people keep reading old maybes as if they are part of the current direction.

Do you keep one big reference board and mark what is approved, or do you make a smaller board once the direction is tighter? Also, who owns that cleanup on your team? Art lead, designer, producer, whoever saved the references in the first place?

I am curious how other people handle the messy middle between research and presentation.

Collecting references is easy. Then the board turns into logos, packaging, colors, type, campaigns, screenshots, and a few things that only made sense during early exploration.

Before a client sees the direction, do you usually rebuild a tighter board in Figma, Miro, or a deck? Or do you keep the raw reference board and talk through it live?

A raw board can make sense to the person doing the research, but feel too noisy for a client. Wondering what process people here use.

I am trying to figure out the cleanup step after a Pinterest board gets too big.

For small projects, a board is easy to read. Once it gets past 80 or 100 pins, I start losing track of what is still useful, what was just early exploration, and what should actually move into a client or team review.

If you use Pinterest for moodboards, interiors, brand references, product ideas, or anything collaborative, how do you usually clean it up?

Do you make a final picks section, split the board into smaller boards, or move the shortlist into something like Miro or Figma before anyone else sees it?

I keep running into the same workflow problem on design projects.

Pinterest is fast for collecting references early, but once the board gets big it stops being useful for review. By the time there are 100 to 200 pins, nobody can tell what is signal, what is leftover exploration, and what is actually meant to guide the work.

Then I move it into Miro or Figma so the team can talk on top of it, but that just exposes the real issue: the painful part is not importing the references, it is turning the pile into a board that people can react to without getting lost.

If you work this way, what is your actual cleanup step?

Do you prune first and only move the shortlist? Do you keep one messy source board and one review board? Do you annotate the references before stakeholder review?

I am asking because I started building a tiny tool around this workflow and realized the import step might be the easy part.

Newer agency problem I keep seeing.

Clients are pretty good at sending taste signals. Pinterest boards, screenshots, competitor pages, random examples from old campaigns. At the start that mess is useful.

The trouble is when it gets passed straight to the person doing the work. Then the designer or editor has to guess what is a real direction, what is just a loose preference, and what the client forgot to explain.

Do you keep one cleaned up board or brief between the client and the team, or do you let the production person see the raw pile and sort it out?

I am curious how people handle this before the board turns into a dump.

When I save references for a project, the first board is usually messy on purpose. Good pins, maybe pins, duplicates, old ideas I forgot to delete.

The problem is later. If I want to share the board with someone or use it to make decisions, the full board is too noisy.

Do you make a second cleaner board, or keep pruning the original until it makes sense again? I have tried sections and a tiny final picks area, but I am not sure if that is the least annoying way.

I have been thinking about the awkward step between saving references and showing a direction to a client.

The raw Pinterest board is usually too much. Duplicates, old saves, nice images that do not really fit, and a few pins that only make sense to the person who saved them.

The pass that seems to work best for me is this.

Pick the 10 to 15 strongest references. Remove anything that only shows personal taste, not the project direction. Group the pins by decision, like color, layout, texture, tone, or audience. Add one short note for why each group matters. Keep the rejected pins somewhere else so the review does not turn into a second search.

Curious how other people do this. Do you show clients the raw board first, or only the cleaned up version?

I am trying to get better at the handoff between visual research and team review.

The collecting part is loose. Pinterest boards, screenshots, competitor flows, packaging, app screenshots, old brand examples, random notes from research. That mess can be useful for the designer, but it is not always useful for a PM or client.

Do you keep one big reference board and guide people through it, or do you pull a smaller set into a cleaner review board first?

I am starting to think the rough board and the review board should be separate. The rough one is for finding the direction. The cleaner one is for making a decision. Curious how product designers handle that without turning it into a second design project.

Curious how other agency people handle this.

For brand or creative work, the early reference pile usually starts messy. Pinterest boards, screenshots, old client assets, competitor links, random packaging photos.

That is fine while the team is still exploring. The harder part is when it needs to become something a client or PM can react to without getting lost.

Do you keep the messy source board and walk people through it, or do you rebuild a smaller review board before feedback? I am mostly asking about the handoff between inspiration collecting and client review, not the actual design feedback tool.

I am curious how people handle this in real projects.

Early references usually live all over the place for me: Pinterest boards, screenshots, links from a client, maybe a few older comps. That mess is fine while I am exploring.

Once the work needs feedback, I usually end up making a cleaner board in Figma or FigJam with only the references that matter. Otherwise people react to the noise instead of the direction.

Do you keep a big source board around and point people to it, or do you rebuild a smaller review board before sharing with non-designers? I am trying to tell if the cleanup step is just my habit or something other teams also do.

I keep running into this on brand direction work.

The messy collection phase is easy enough. Pinterest boards, screenshots, old packaging, competitor sites, whatever gets the direction moving.

The part I am curious about is the handoff after that. When it becomes a client or team conversation, do you keep pointing people back to the original Pinterest board, or do you rebuild a tighter working board somewhere else?

I usually end up making a smaller board with only the references that matter, because the original board gets too noisy. But that also means copying things over and losing some of the context from where they came from.

How are you handling that? One source board, or a cleaned-up review board?

Product: a small Miro app that turns a Pinterest board into a Miro moodboard. The use case is for people who collect references in Pinterest, then need to discuss or organize them in Miro.

Market: I think the real users are designers, brand teams, researchers, planners, and maybe agencies. I do not know if that is a real market or just a workflow itch inside a small group of people.

Competition: mostly manual copy/paste, screenshots, leaving the Pinterest board open in another tab, or rebuilding the board inside Miro by hand. The risk is that this should just be a tiny native Miro feature, not a standalone thing.

Stage: built and listed in the Miro Marketplace. Not raising money. I am trying to figure out if the narrow pain is worth pushing harder, or if I am overvaluing a task that only annoys me.

Customer conversion: find people already complaining about reference cleanup, moodboards, Pinterest boards, Miro boards, or moving visual research between tools. If they already describe the problem in their own words, then show the app. If they do not, I probably should not try to create the pain for them.

Why me: I built it because I kept seeing this handoff in planning and visual work. No special founder story. Just close enough to the workflow to notice the boring manual step.

Roast the weak parts. Is this a real workflow problem, or just a convenience? Does "Pinterest to Miro moodboards" sound clear, or does it sound too tiny to care about?

I made a small Miro app for a workflow I kept seeing in visual planning work.

People collect references in Pinterest because it is fast. Then when the project gets serious, the actual conversation moves into Miro. That leaves this boring middle step where someone copies pins over, cleans up screenshots, and rebuilds the board.

The app takes a Pinterest board URL and lays the pins out on a Miro board. Pretty small idea, but that is kind of the point.

I am trying to tell if this sounds like a useful little tool or just a "neat once" thing. If you use Pinterest, Miro, Figma, or FigJam for moodboards, would you expect this to exist?

I am working on a small Miro app that does one job: it turns a Pinterest board into a Miro moodboard.

At first I thought the hard question was whether the idea was too narrow. I am starting to think the better question is whether it sits inside a real workflow or just saves a few minutes once in a while.

The workflow version is pretty clear: someone collects references in Pinterest, the team discusses them in Miro, and the annoying handoff between the two tools happens every project.

The feature version is weaker: someone imports a board once, says neat, and never thinks about it again.

I am trying to figure out which side this belongs on before I make the copy bigger than the product. For people building micro SaaS, how do you tell when a tiny tool is actually part of a workflow and not just a nice-to-have shortcut?

I keep running into this with moodboards and visual planning.

Pinterest is where the references pile up. Miro is where the team actually sorts and talks through them. The annoying part is the middle step, copying pins over, cleaning up the board, then trying to remember which references mattered.

I am curious how other Miro users handle this today.

Do you rebuild the board manually, paste screenshots in chunks, use some browser workaround, or avoid Pinterest once the work moves into Miro?

I kept running into this on design and planning work.

Pinterest is where references get saved. Miro is where people actually talk through the board. In between, someone ends up copying pins over by hand or pasting screenshots until the Miro board is usable.

So I built a small Miro app that takes a Pinterest board URL and lays the pins out in Miro as a moodboard. No big platform idea. Just that one handoff.

I am trying to sanity check whether this reads as a useful little app or too narrow to bother with.

If you use Pinterest, Miro, Figma, or similar tools for visual planning, would you expect an app like this to exist, or would you just keep doing the manual copy/paste thing?