Responsible Image Editing

Generating an image from scratch is one workflow. The other, often more common, is taking an image you already have and changing one specific thing about it. That's editing, and it's where AI tools save the most time in pre-sales: a solution-overview visual with the wrong background, an architecture diagram with a deprecated box still hanging around, a product screenshot with a stray annotation in the corner. But editing also concentrates the risk. The closer an edited image looks to a real screenshot or a real product view, the more carefully you need to handle what it says, what it implies, and how you put it in front of a customer.

Before you write any instruction, it helps to know what's on the menu, because the right vocabulary gets you a faster, cleaner result. Here's a table to help understand the different edit types AI can help with:

Most pre-sales edits are some combination of these. A "clean up this solution-overview visual" request is usually object removal plus a background change plus a light color match. Naming the edit type in your head first makes the instructions you write next much sharper, because each type has its own failure modes (warped hands in inpainting, ghosted edges in object removal, seams in outpainting) that you'll want to call out as things to avoid.

Free-form editing requests like "drop the cache box and update the background" are how good diagrams get ruined. The model has no idea what you consider untouchable, so it'll happily redraw a component label or shift a connector line in a way nobody approved. The fix is the Image Edit Brief, a four-part instruction:

• Preserve: what must remain exactly as-is.
• Change: the specific edit, described concretely.
• Avoid: artifacts, drift, or unintended modifications.
• Output: final format, dimensions, and where it's going.

Preserve is the part people skip. You have to explicitly name the components, the connector lines, the labels, the layout, anything you're not willing to lose. Change should be one or two surgical edits, not a wish list. Avoid catches the predictable failure modes: warped boxes, regenerated labels, mismatched styling between the old layout and the new one. Output ties the edit to its real use: a 16:9 demo slide has different demands than a print leave-behind.

Let's look at what a review conversation might look like:

• Ryan: What's the edit?
• Milo: Take the deprecated cache box out of the architecture diagram and freshen up the layout.
• Ryan: That'll come back with connectors and labels that look slightly different than the version we already validated. What are you preserving?
• Milo: Every remaining component, its label, its connector lines, the overall layout. Nothing else moves.
• Ryan: Good. And Avoid?
• Milo: No warped boxes, no relabeled services, no broken connector lines where the cache box used to be.

Notice Ryan's pressure: name what stays before you name what changes. That order is the whole brief.

A clean edit doesn't automatically mean a shippable asset. Before any AI-generated or AI-edited image leaves your hands for a customer, run it through five checks:

• Brand: does it match your company's visual system in a customer-facing asset, or does it read as generic stock?
• Audience: will the prospect, AE, or stakeholder seeing it interpret it the way you intend?
• Accessibility: does it need alt text, and is the contrast high enough where a slide title or callout overlays it?
• Accuracy: does the image imply something that isn't true, like a real customer's result, a live event, or a product capability, dashboard, or integration that doesn't exist?
• Disclosure: if the image is AI-generated or substantially AI-edited, do your team's norms or your audience's expectations call for labeling it as such, e.g. "illustrative, not actual product UI"?

The accuracy and disclosure checks are where most teams get burned. An AI image of "our platform in action" dropped into a solution brief reads as a real customer's live result, even if you never used the word "customer." A fabricated dashboard with an invented uptime card or a one-click integration the product doesn't offer becomes a story the moment a technical buyer asks whether that's real. The move when a risk surfaces is not always to scrap the asset: sometimes you revise the prompt, sometimes you change the caption or placement, sometimes you add a disclosure line, sometimes you walk away. The judgment call is yours, but it has to be a call, not a default.

The throughline of this unit: edits and AI images need a stated intent (the brief) and a stated standard (the five checks), or you'll ship something nobody actually approved. Before this becomes real, you'll get on a call with a product-marketing lead who wants to ship an AI image into a customer-facing asset tomorrow and isn't sure the risk is worth a delay. Your job in that conversation is to name the specific concerns, propose options, and land on a defensible call together: revise the prompt, change the usage plan, or kill the asset. Bring specifics. Vague risk talk loses to a publish deadline every time.

This unit explains how to professionally modify existing images using AI tools while maintaining brand standards and accuracy. You will learn to use the Image Edit Brief to give specific instructions on what to preserve and what to change, ensuring your demo-deck visuals and proposal images look natural. The lesson concludes with a checklist to evaluate your visuals for Brand, Audience, Accessibility, Accuracy, and Disclosure before they reach a customer.