When the Brief
Is Wrong.
A financial broker needs their profile banner updated with award badges. The platform wants SVG. The design uses photography. Nobody catches the incompatibility until delivery.
This is the story of a two-day technical loop that should have been a ten-minute conversation. It happens constantly in creative operations. Here's what went wrong, how the team recovered, and the lesson that applies to every spec-driven delivery.
Asset
Broker Profile Banner
Platform req.
SVG, max 700KB
Design constraint
Photographic background
Resolution
PNG, under 400KB
The Root Problem
The spec was written for logos.
The asset was photographic artwork.
The platform's SVG requirement is entirely reasonable for its intended use case: logos, icon sets, simple brand marks. These are mathematically defined shapes with no pixel data. An SVG of a logo is fully scalable because there are no pixels to blur.
The broker profile banner was different. It used a dark photographic background with a gold lighting effect and three award badge graphics. Photography is inherently raster. It's pixel data. You can place a photograph inside an SVG file, but it doesn't become vector. It's a photograph sitting inside an SVG container.
The spec wasn't wrong. It was incomplete. It said "SVG" without specifying what that meant for a mixed-media asset. And that ambiguity cost two days.
What the platform meant
A fully vectorised SVG: mathematically defined shapes, paths, and fills. No raster data. Infinite scalability. Typical for logos, icons, and simple brand marks.
What the design contained
An SVG container with embedded raster photography. The file is technically an SVG. But the photographic background is still pixel data. It blurs when zoomed. It's heavy. It cannot be compressed below the limit.
The Thread
How it actually played out
Two days. Ten messages. One avoidable loop.
See the conversation as it unfolded in real time
The Creative Ops Lesson
What this ticket teaches us
SVG does not mean fully vectorised
An SVG file can and frequently does contain raster elements. A JPEG embedded in an SVG is still a JPEG. The format is a container, not a guarantee of vector content. Platform specs written for logos do not automatically apply to photographic banner artwork.
Interrogate specs at brief stage, not delivery stage
The question that needed asking on day one: what kind of SVG? Fully vector? Or SVG container acceptable? Is photography in the design? What are the actual rendering requirements? One hour of spec interrogation up front prevents two days of rework.
Test the ceiling early
When a file size limit is flagged, the right move is to immediately test the stripped-down version. The team confirmed that even a plain vector background still exceeded 700KB. That data point ended the circular conversation and unlocked the correct path.
Pushing back is part of the job
Recommending PNG over SVG and explaining why is a professional call, not a failure. Creative ops teams that can make that recommendation clearly and confidently protect delivery timelines and client relationships better than those who keep trying to satisfy an incompatible spec.
"The team did the right things. They compressed. They optimised. They tested alternatives. They escalated when they hit the ceiling. The issue wasn't execution. It was a misaligned requirement that needed to be surfaced and challenged, not endlessly worked around."
Artisan Systems, Creative Ops Analysis
Test Your Instincts
How would you handle it?
Three decisions. Real scenarios. No wrong answers to learn from.
Project Summary
Case study with a client of Artisan Systems.
Related
Spec confusion at brief stage is a fixable problem.
The Creative Ops Audit identifies where your team's intake and briefing process is most vulnerable to exactly this type of delay.