All insights
    Max Västhav

    We save the image brief before we generate the image

    AI image generation has gone from experimental to a daily tool. But there's a catch: most people save the image — not the process.

    aicontent-opsbuild-in-publicimages

    AI image generation has gone from experimental to a daily tool. But there's a catch: most people save the image — not the process.

    That makes it hard to reproduce, evaluate, and improve.

    The problem: the image exists, the brief is gone

    You generate an image in Midjourney, Higgsfield, or DALL-E. It looks good, you download and publish. A week later you want a variation. Which prompt did you use? Which style? Which negative instructions?

    The information might exist in a chat history at the provider. Often it's nowhere.

    Our solution: log the brief as metadata

    In VasthavM's content workflow, we save the image brief as structured data before the image is generated.

    Every image has a manifest with:

    • content_id — which article or post the image belongs to
    • image_prompt — the exact prompt
    • negative_prompt — what the image should not contain
    • style/model — which model and style was used
    • status — generated, approved, published, archived
    • usage — where the image is used (LinkedIn, blog, OG)
    • performance — impressions, clicks, engagement if applicable

    Why it matters

    1. Reproducibility

    If an image performs well, we want to make more in the same style. With a saved brief, we can.

    2. Evaluation

    We can compare high-engagement images with their briefs. Patterns emerge: short prompts, dark backgrounds, and text-free images perform better on LinkedIn in our data.

    3. Traceability

    When the AI Act requires transparency about AI-generated content, we already have the log. We know which image is AI-created, which prompt was used, and who approved it.

    4. Team efficiency

    If someone else needs to create an image in the same visual profile, they can start from existing briefs instead of starting from scratch.

    What our workflow looks like

    1. Content ID is created in the bank
    2. Image brief is written (prompt + negative + style guide)
    3. Image is generated via Higgsfield
    4. QA: does the image match the brief?
    5. Manifest is updated with status + drive link
    6. Image is uploaded to Visual Bank
    7. Image is connected to publication
    

    We store everything in a spreadsheet (Mira Content Bank) with an Assets tab. No complicated tools needed.

    It's not about perfection

    We don't log briefs to be bureaucratic. We do it because AI-generated material needs the same traceability as all other content work.

    It's a small detail that makes AI content more measurable, more reproducible, and more accountable.

    If you work with AI images regularly — start logging the brief before you generate the image. Your future self will thank you.

    Cookies. Privacy