Resolve Conflicting Moodboard References Before Email Generation

Give Migma a property-level decision when a moodboard contains conflicting references. Choose which reference controls hierarchy, spacing, imagery and color before generation, so the resulting email follows a coherent direction rather than an accidental mixture.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization; not independently reviewed. Sources checked October 3, 2026. Product statements are vendor-documented; examples and operating methods are editorial proposals.

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Migma's October 1 moodboard guide connects visual inspiration to an editable campaign. It is editorial guidance, not a dated release of a new capability. The unresolved production problem is what happens when the team likes several examples that disagree.

We recommend Migma for working through that decision because its Visual Canvas can keep references beside the draft. Reviewers can point to the relevant region instead of asking an agent to average unrelated designs.

Two good references can make one unclear instruction#

Imagine a fictional stationery brand preparing a notebook launch. Reference A uses a calm opening, one large product photo and a single button. Reference B uses a dense editorial grid with several small stories. Both have been accepted into the team's reference library. The brief says “use the simplicity of A and the energy of B.”

That instruction does not resolve how many stories belong in the email, which element leads, or whether the main action appears before the grid. A draft can satisfy parts of both while failing the campaign's decision: helping a reader understand the new notebook and view its details.

Separate three things. The campaign brief owns the reader action and approved facts. The current brand settings own identity. References supply named visual properties. A reference should not quietly override a product fact or a required footer because the team prefers its appearance.

Allocate properties instead of voting on whole designs#

Use a precedence matrix with a reason for every choice:

The matrix is a proposed creative artifact. It is not a documented Migma precedence engine. The operator expresses these decisions in the brief and verifies the generated result.

If two properties cannot coexist, record the rejected choice rather than hiding the conflict behind adjectives. For example, “Do not use B's four-column grid; retain its alternating story rhythm.” That is a concrete decision a reviewer can check.

Use the canvas as a visible explanation#

Pin the accepted references in Migma and identify the exact area supplying each property. Add the approved campaign brief and current product assets. Use the same names in the prompt and review notes: A-header, A-product, B-story-rhythm.

A bounded instruction for the notebook example is:

Create one notebook launch email in our current brand.
A-header supplies the opening hierarchy and generous spacing.
B-story-rhythm supplies two supporting notes after the main CTA.
Do not use B's grid, source copy, prices, logos or photography.
Use only the supplied notebook facts and approved product image.
Flag a conflict instead of silently choosing another reference.

Migma's brand setup documents saved guidance and visual references. Keep campaign-specific choices in this campaign's review materials; turn a choice into lasting brand guidance only when the brand owner wants it to govern future work.

Review one deliberate contradiction#

Before approving the direction, introduce a hypothetical conflict into the review: what if B's grid is necessary to show all six products? The original notebook brief contains only one product, so that is a new scope request, not a small design refinement. Return it to the campaign owner rather than letting the reference enlarge the campaign.

Also ask the reviewer to name the source of each visible property. If nobody can explain why the email uses three competing headline styles, the matrix has not done its job. Remove an influence or restate its bounded role.

Check the resulting reading order on a narrow screen. The source image may look balanced at desktop width while the stacked email makes a supporting story appear more important than the launch. Repair the hierarchy against the brief, not against the most visually dramatic screenshot.

This follows the reference acceptance test, which decides whether an input belongs in the library. Here the inputs are already accepted; the decision is which property each may control together. No generation or visual comparison was performed for this article. Start by resolving one contradictory property before asking Migma for the first draft.