LLOS.ai
Design › Image Management › Part 3 · Workflows & Production
🔵 Asset Management · Workflows & Production

Workflows & Production

By Pawan Nayar · LLOS.ai · ~30 min read · Engineering Design

Individual skills are notes; a workflow is the song. Twelve real jobs run end to end — each with its map, its timing, its checklist and its real failure cost — then the production system around them: folders, naming, versioning, backup, an AI pipeline, and the twenty myths that quietly ruin good work.

Capture
Edit
Review
Export
Archive
RAW_0421.dng
IMG_2093.jpg
DSC_8842.nef
hero_master.psd
edit_v2.psd
FINAL_final.psd
proof_01.jpg
client_review.pdf
hero_web.webp
hero_print.tif
thumb.jpg
2026_shoot.zip
backup.zip
Downloads_dump
Fifteen files. Five folders. Zero order. Sound familiar?
12 end-to-end workflowsProduction systems + DAMCalculators & myths

From Tasks to Pipelines

A professional deliverable is individual skills in the right order, with the right tool at each step, ending in a file that meets an exact spec. So each workflow below opens with a map (the whole pipeline in one line), its difficulty, time, software and output, then why companies care, where the time actually goes, the steps, a production checklist, the wrong vs right, a real failure and its cost, and what changes at scale.

Then the part nobody teaches: the system around the pixels — folders, naming, version control, backup, asset lifecycle and DAM — because at volume, image management is the real job.

Twelve Workflows

Grouped by difficulty. Open any one for its full pipeline.

Beginner
Workflow 03

Recipe Blog — Step Collage & Pinterest Pin

Difficulty ★★☆☆☆⏱ 40 min🖥 Canva📦 PNG
The map
Step photos→Crop→Numbered collage→Resize to Pin→Compress
Why companies care

Discovery — a keyword-rich, high-contrast Pin is free traffic that compounds for years.

Where the time goes
Layout
Hands on it
Blogger(self)
The steps
  1. Crop/straighten 6–8 step photos in a grid.
  2. Add consistent numbered circles.
  3. Duplicate → 1000×1500 Pinterest; bold, keyword-rich title.
  4. Compress (TinyPNG) before upload.
Production checklist
  • Clean sans-serif, not script?
  • 10% dark overlay behind white text?
  • Compressed before upload?
Get it wrong / get it right
✗ Thin script font on a busy photo
✓ Bold sans on a subtle dark overlay
What went wrongA Pin used a pale script font over the food photo; unreadable in the feed, it drove no saves.
Months of lost organic reach
What changes at scale

1 recipe → hundreds: a fixed Pin template turns each post into a 5-minute job.

Workflow 07

Blogging — Feature Image + Social Set

Difficulty ★★☆☆☆⏱ 30 min🖥 Canva📦 WebP / PNG
The map
Hero photo→Overlay + title→Master 1200×630→Resize set→Optimise
Why companies care

Page speed + reach — a light OG image that loads fast and re-crops cleanly to every platform.

Where the time goes
SetupDesignResize
Hands on it
WriterDesigner
The steps
  1. Place hero; subject clear of the text zone.
  2. Multiply overlay 10–20% for contrast.
  3. Master 1200×630 → duplicate to IG 1080² and Stories 1080×1920.
  4. Export WebP/JPG ~80; run through Squoosh.
Production checklist
  • Subject inside every safe-crop zone?
  • Text off the edges?
  • Optimised (WebP where supported)?
Get it wrong / get it right
✗ One giant image reused everywhere
✓ Per-platform crops from one master
What went wrongA single wide image was reused as the IG square; the headline was cropped off and the post flopped.
A campaign’s reach
What changes at scale

1 post → a content engine: a master + resize preset per platform, run on publish.

Workflow 10

Portfolio — Polished Headshot Set

Difficulty ★★☆☆☆⏱ 45 min🖥 Photoshop📦 JPG / TIFF
The map
RAW→Crop ratio→Retouch→Grade→Web + Print
Why companies care

First impression — a natural, confident headshot that reads as trustworthy at a glance.

Where the time goes
RetouchGrade
Hands on it
SubjectRetoucher
The steps
  1. Crop to ratio; straighten.
  2. Spot Healing at 200% zoom; keep skin texture.
  3. Curves S-curve + Color Balance for skin.
  4. Save for Web JPG 70–80; flatten TIFF for print.
Production checklist
  • Skin texture kept (no plastic)?
  • Web + print versions exported?
  • Master kept for re-crops?
Get it wrong / get it right
✗ Over-smoothed, plastic skin
✓ Subtle dodge/burn, real texture
What went wrongA headshot was smoothed to plastic; it read as fake and cost the candidate credibility.
The opportunity itself
What changes at scale

1 headshot → a team of 200: a recorded action keeps everyone’s look consistent.

Intermediate
Workflow 01

Course Launch — Slide Cover + YouTube Thumbnail

Difficulty ★★★☆☆⏱ 15 min🖥 Photoshop · Canva📦 PNG / JPG
The map
Headshot→Cut out (PS)→Layout (Canva)→Resize→Slide + Thumbnail
Why companies care

Sell the course in a glance — a clean instructor and a title readable at thumbnail size drive click-through.

Where the time goes
PrepDesign
Hands on it
InstructorDesignerMarketing
The steps
  1. Cut out the headshot (Select and Mask), output a Layer Mask.
  2. Curves for skin; export PNG on transparency.
  3. Lay out 1920×1080 in Canva, title 60–100pt.
  4. Resize to 1280×720; bump the headline 15–20% for small screens.
Production checklist
  • Text legible at 25% zoom?
  • Headshot on its own masked layer?
  • Thumbnail under 200 KB?
Get it wrong / get it right
✗ Tiny title that vanishes at thumbnail size
✓ Bold title, high contrast, readable at 120px
What went wrongA course thumbnail set the title at 24pt; at YouTube’s render size it was illegible — click-through halved.
Half the launch traffic lost
What changes at scale

1 cover → 40 lesson thumbnails: build a Canva template with the title as the only variable.

Workflow 09

NGO Awareness Carousel (Instagram)

Difficulty ★★★☆☆⏱ 90 min🖥 Canva📦 PNG
The map
Message + CTA→Master slide→Charts + icons→Duplicate 10→Export set
Why companies care

Action — a story arc that carries a reader from hook to CTA and moves them to act.

Where the time goes
PlanDesign
Hands on it
CampaignerDesignerAudience
The steps
  1. Slide 1 as the hook (a big stat or question).
  2. One consistent icon style; import charts as SVG.
  3. Duplicate → change only the headline/stat; hold alignment.
  4. Final slide: CTA + hashtag + QR.
Production checklist
  • Under 30 words per slide?
  • Story order hook→problem→data→solution→CTA?
  • Exported as a PNG set?
Get it wrong / get it right
✗ Dense paragraphs on every slide
✓ One idea per slide, one CTA
What went wrongA carousel packed 80 words per slide; readers dropped by slide two and never reached the CTA.
A campaign’s conversions
What changes at scale

1 carousel → a weekly cadence: a master slide keeps a month of posts on-brand in minutes.

Workflow 11

Email Newsletter — Hero + Inline Images

Difficulty ★★★☆☆⏱ 45 min🖥 Photoshop · Canva📦 JPG / PNG
The map
Headline in image→Build @1200→Optimise <150KB→Inline icons→Test in clients
Why companies care

Deliverability + clicks — light, text-baked images that render everywhere email fonts don’t.

Where the time goes
DesignOptimiseTest
Hands on it
MarketerDesignerDeveloper
The steps
  1. Bake the headline into the hero (email blocks web fonts).
  2. Build at 1200px, export at 50% for retina.
  3. Save for Web JPG 60–70, keep <150 KB.
  4. Icons PNG-8/GIF ~64px; test in Gmail, Outlook, iOS.
Production checklist
  • Hero under 150 KB?
  • ALT text on every image?
  • Rendered in 3+ clients?
Get it wrong / get it right
✗ A 2 MB hero that never loads
✓ A 120 KB hero, text baked in
What went wrongA heavy hero was stripped by Outlook and slow on mobile; the CTA below it went unseen.
A send’s revenue
What changes at scale

1 newsletter → weekly: a template + export preset keeps every send light and on-brand.

Workflow 12

Fintech Dashboard → Landing Hero

Difficulty ★★★★☆⏱ 2 hrs🖥 Photoshop · Illustrator📦 WebP / PNG
The map
Screenshot→Scrub data→Callouts (AI)→Device mockup→Composite hero
Why companies care

Trust & conversion — a crisp, readable product shot that makes the app feel real and safe.

Where the time goes
CleanCalloutsMockup
Hands on it
PMDesignerWeb dev
The steps
  1. Clone-stamp out names/emails; crop to the key module.
  2. Vector callouts in AI → SVG/PNG.
  3. Drop the screenshot into a device mockup Smart Object.
  4. Gradients/shadows for depth; export WebP <500 KB.
Production checklist
  • All sensitive data scrubbed?
  • Callout text legible on mobile?
  • Hero under 500 KB?
Get it wrong / get it right
✗ Blurry screenshot, tiny callouts
✓ Crisp module, large legible labels
What went wrongA dashboard hero shipped with a real customer’s name visible; it had to be pulled and re-shot.
A privacy incident
What changes at scale

1 hero → 28 localised pages: keep callouts as editable vector text for fast translation.

Advanced
Workflow 02

Financial Report → Social Infographic

Difficulty ★★★★☆⏱ 2 hrs🖥 Illustrator · Photoshop📦 PNG / JPG
The map
KPIs→Vector charts (AI)→Backdrop (PS)→Compose→Export @2x
Why companies care

Investor trust — clean, accurate charts read as credible; sloppy ones read as risk.

Where the time goes
DataChartsCompose
Hands on it
AnalystDesignerComms
The steps
  1. Rebuild bar/line charts as vector (Align panel for spacing).
  2. Blur + lower-contrast the backdrop photo (PS).
  3. Compose in AI; one headline + one insight subhead (<15 words).
  4. Export for Screens: PNG @2x for IG/LinkedIn, JPG for X.
Production checklist
  • Top 3–5 KPIs only?
  • Numbers legible on a 5″ phone?
  • Platform-suffixed filenames?
Get it wrong / get it right
✗ Twelve stats crammed edge to edge
✓ Three stats, one clear key insight
What went wrongAn infographic shipped 12 KPIs at 9pt; on mobile it was an unreadable wall — engagement near zero.
A quarter’s comms wasted
What changes at scale

1 report → a quarterly series: lock a master template so only the numbers change.

Workflow 05

Mobile App UI — Icon & Illustration Pack

Difficulty ★★★★☆⏱ 90 min🖥 Illustrator📦 SVG / PNG
The map
Draw @24px→Pixel-align→Duplicate sizes→Export for Screens→1x/2x/3x pack
Why companies care

Engineering handoff — a clean, consistent asset pack that drops into the build with zero rework.

Where the time goes
DrawAlign
Hands on it
DesigneriOS/Android dev
The steps
  1. Draw on a 24×24 artboard, Pixel Preview on.
  2. Align to the pixel grid (round positions).
  3. Name artboards icon_home_24, _48…; use Symbols so edits propagate.
  4. Export for Screens → PNG + SVG at 1x/2x/3x.
Production checklist
  • Whole-pixel positions (no blur)?
  • Consistent naming convention?
  • SVG + raster fallbacks exported?
Get it wrong / get it right
✗ Fractional-pixel icons that blur
✓ Pixel-snapped, crisp at every size
What went wrongIcons drawn off the pixel grid shipped soft on every device; the whole set was redrawn.
A sprint of rework
What changes at scale

1 icon → 400 localised stores: automate export; never hand-crop per locale.

Workflow 06

Wedding — Batch Edit & Album Proofs

Difficulty ★★★★★⏱ 8 hrs🖥 Lightroom · Photoshop📦 JPG / TIFF
The map
RAW→Cull→Global grade→Hero retouch→Batch export→Proofs
Why companies care

Fast, consistent delivery — a coherent set delivered quickly, with easy revisions.

Where the time goes
EditReview
Hands on it
PhotographerRetoucherCouple
The steps
  1. Import RAW, build Smart Previews; cull in Survey view.
  2. Set WB/exposure on one, sync to similar shots.
  3. Hero retouch in PS (returns a layered TIFF).
  4. Batch action: vignette+sharpen; export JPG q85 sRGB 3000px; Contact Sheet II → PDF.
Production checklist
  • WB grouped by lighting scene?
  • Skin texture kept (low-radius sharpen)?
  • Master RAW + edits archived?
Get it wrong / get it right
✗ Each photo colour-corrected by eye
✓ One grade synced across the scene
What went wrongColours were corrected shot-by-shot; the album jumped warm-to-cool page to page and was re-graded.
A full re-edit, unpaid
What changes at scale

1 wedding → 4,500 RAW: presets + sync + batch actions turn 8 hours into ~1.

Expert
Workflow 04

AI Art → Gallery Print Poster

Difficulty ★★★★★⏱ 3 hrs🖥 Photoshop📦 TIFF / PDF/X
The map
AI art→Upscale→16-bit→CMYK proof→Print TIFF
Why companies care

Physical product quality — a gallery print that holds up under a light and a loupe.

Where the time goes
UpscaleRetouchProof
Hands on it
ArtistRetoucherPrint lab
The steps
  1. Image Size → Preserve Details 2.0 → 7200×10800.
  2. 16 Bits/Channel; add 0.5–1% noise to fight banding.
  3. Proof Setup to the printer’s CMYK; Selective Color for gamut-safe hues.
  4. Save TIFF (LZW) with the profile, or PDF/X-1a.
Production checklist
  • Enough pixels at 300 PPI for 24×36?
  • 16-bit to avoid banding?
  • Soft-proofed to the lab’s profile?
Get it wrong / get it right
✗ Neon RGB sent straight to the press
✓ CMYK soft-proofed, gamut-safe
What went wrongAn RGB poster printed with the neon flattened to mud; the full run was rejected.
$6,000 reprint
What changes at scale

1 poster → an edition: save the proof + profile as a reusable print preset.

Workflow 08

Academic Paper — Multi-Figure Plate

Difficulty ★★★★★⏱ 3 hrs🖥 Illustrator · Photoshop📦 TIFF / PDF
The map
Plots + photos→Vectorise charts→CMYK photos→Assemble plate→Export to spec
Why companies care

Acceptance — a plate that meets the journal’s exact spec so it is not bounced at submission.

Where the time goes
ChartsPhotosAssemble
Hands on it
ResearcherDesignerJournal
The steps
  1. Vectorise charts (8–9pt, consistent strokes).
  2. Photos → CMYK/Grayscale, Levels, 300 PPI at print size.
  3. Assemble on an 8.5×11 artboard; label A, B, C with Smart Guides.
  4. Export PDF (fonts embedded) or TIFF (LZW) to the journal spec.
Production checklist
  • CMYK/Grayscale per spec (no RGB)?
  • Fonts embedded or outlined?
  • 300 PPI at final size?
Get it wrong / get it right
✗ RGB figures with un-embedded fonts
✓ CMYK, fonts embedded, to spec
What went wrongA plate submitted in RGB with live fonts was auto-rejected at upload, delaying the paper a cycle.
A review cycle lost
What changes at scale

1 figure → a paper of plates: an editable AI master makes reviewer changes minutes, not hours.

Every Workflow at a Glance

Time, difficulty, output and the scaling move — the whole set in one table.

WorkflowTimeDifficultyOutputScales by
Course Launch15 min★★★☆☆PNG / JPG1 cover → 40 lesson thumbnails
Financial Report → Social Infographic2 hrs★★★★☆PNG / JPG1 report → a quarterly series
Recipe Blog40 min★★☆☆☆PNG1 recipe → hundreds
AI Art → Gallery Print Poster3 hrs★★★★★TIFF / PDF/X1 poster → an edition
Mobile App UI90 min★★★★☆SVG / PNG1 icon → 400 localised stores
Wedding8 hrs★★★★★JPG / TIFF1 wedding → 4,500 RAW
Blogging30 min★★☆☆☆WebP / PNG1 post → a content engine
Academic Paper3 hrs★★★★★TIFF / PDF1 figure → a paper of plates
NGO Awareness Carousel (Instagram)90 min★★★☆☆PNG1 carousel → a weekly cadence
Portfolio45 min★★☆☆☆JPG / TIFF1 headshot → a team of 200
Email Newsletter45 min★★★☆☆JPG / PNG1 newsletter → weekly
Fintech Dashboard → Landing Hero2 hrs★★★★☆WebP / PNG1 hero → 28 localised pages

The Part Nobody Teaches

Image management is the system around the pixels: where files live, how they are named, versioned, backed up and found.

Folder structure
ClientProject/
├─ 01_RAW/          camera originals - never edited
├─ 02_Working/      layered PSD / AI masters
├─ 03_Exports/
│   ├─ Web/         webp, jpg
│   ├─ Print/       tif, pdf/x
│   └─ Social/      per-platform
└─ 04_Archive/      zipped, dated, backed up
Naming conventions
✗ hero_final.psd · hero_final_FINAL.psd · hero_v3_new_USE_THIS.psd
✓ hero_master.psd · hero_web.webp · hero_print.tif · hero_instagram.jpg · hero_2026-07-15_approved.psd

A name should say what, where it goes, and which version — never “final_final”.

Version control
Master
↓
Client review
↓
Approved
↓
Production
↓
Archive
Backup (one SSD failure = years lost)
Laptop
↓
Cloud
↓
External SSD
↓
Cold archive
Asset lifecycle
Capture
↓
Edit
↓
Review
↓
Export
↓
Publish
↓
Archive
↓
Reuse
Legal / rights
Licensed
↓
Released
↓
Attribution
↓
Commercial use
↓
Archive
Digital Asset Management (DAM)

At volume, files need a library, not a folder: metadata, tags, collections, ratings, keywords, search and archive. A DAM is how a team of hundreds finds the one approved logo in seconds instead of emailing “does anyone have the final?”

Decision Trees

Memorable because they end in a single answer.

Which format?
Need transparency? → PNG
↓
Need it tiny? → WebP
↓
Need to scale (icon/logo)? → SVG
↓
Need animation? → GIF / WebP
↓
Otherwise a photo? → JPG/WebP
Which colour space?
For screen? → sRGB
↓
For print? → CMYK / Pantone
↓
Brand-critical? → embed the ICC profile
Where does the blur come from?
Original soft? → re-shoot / re-source
↓
Export soft? → fix resample/format
↓
CDN re-compressing? → tune delivery
↓
CSS scaling past pixels? → ship a 2×

Automation, QA & Handoff

Professionals automate the repeat, check before they ship, and hand off cleanly.

Automation toolkit
Photoshop ActionsLightroom presetsIllustrator actionsBridge batchCanva Brand KitBatch renameImageMagickTinyPNGSquooshCDN auto-format
Pre-export QA checklist
  • Resolution correct for the output?
  • Colour space right (sRGB/CMYK)?
  • ICC profile embedded?
  • Metadata set / stripped as needed?
  • Compression sensible (no banding)?
  • Alt text / accessibility done?
  • Named by convention?
Software handoff
Photoshop→Illustrator→Figma→Developer→Website

Workflow Calculators

Answer the questions that stall every export.

Print size at 300 PPI
= 10.0 in wide
Bandwidth at scale
= 4.8 TB / month
Compression savings
≈ 300 KB · saves 85%

The Modern AI Workflow

The pipeline every designer now needs — generation is a step, not the finish line.

Prompt→Generate→Upscale→Retouch→Background→Typography→Export

The craft has moved downstream: prompting is cheap, but upscaling cleanly, retouching the tells, matching colour, setting real type and exporting to spec is where a designer still earns the result.

What Changes at Scale

Every workflow above is written for one asset. Enterprises think in hundreds of thousands.

1 image → 5,000 product photos1 thumbnail → 2M YouTube1 icon → 40 app stores1 dashboard → 28 languages1 wedding → 4,500 RAW
Enterprise image pipelines
Netflix thumbnailsAmazon catalogGoogle Play assetsApple App StoreE-commerce product pipelineNewsroom image deskMagazine productionMuseum archiveMedical imagingSatellite imagery
Production dashboard
42Assets
39Approved
2Missing
1Blocked
Which one are you?
The perfectionistedits one hero for three hours
The exporterforty tabs of Save-As
The hoardernever deletes a RAW
The renamerhero_FINAL_FINAL_v9
The folder fanaticsubfolders inside subfolders
The automatorrecords everything as an action

The Myth-Busting Encyclopedia

Not myth-vs-reality flashcards — each one gives you the belief, the truth, why it sticks, a test you can run, and the rule.

Always save JPGs at 100% quality.
What everyone says

Always save JPGs at 100% quality.

The reality

JPG is always lossy; even 100 re-compresses. Keep masters as PSD/TIFF; web quality 70–85 is usually smaller with no visible loss.

Why people believe it

100 ‘feels’ safest, so people never question it.

Test it yourself

Export the same image at 100 and 80 and flip between them — you won’t see the difference.

The rule

Quality 80 (or WebP); keep a lossless master.

More megapixels means a better photo.
What everyone says

More megapixels means a better photo.

The reality

Sensor size and lens quality matter far more; a large sensor with fewer megapixels beats a tiny high-count phone sensor.

Why people believe it

Bigger numbers feel like more quality.

Test it yourself

Compare a full-frame 24MP shot with a 108MP phone in low light.

The rule

Judge the sensor and lens, not the megapixel count.

A bigger file size means higher quality.
What everyone says

A bigger file size means higher quality.

The reality

A noisy, poorly-compressed image can be huge; a clean, well-compressed one is small and looks better.

Why people believe it

We equate weight with value.

Test it yourself

Optimise an image and compare it, at 100%, to the bloated original.

The rule

Size is a cost, not a quality signal.

300 DPI is what makes a print sharp.
What everyone says

300 DPI is what makes a print sharp.

The reality

DPI only re-tags density; sharpness comes from enough pixels for the physical size.

Why people believe it

The ‘300’ number is repeated everywhere without the pixel context.

Test it yourself

Set an 800px image to 300 DPI and print it — still soft.

The rule

Think pixels-for-a-size, then set 300 PPI.

CMYK has more colours than RGB.
What everyone says

CMYK has more colours than RGB.

The reality

The opposite — RGB (emitted light) reaches far more colours than CMYK (ink).

Why people believe it

Print feels ‘more real’ than a screen.

Test it yourself

Soft-proof a neon RGB green to CMYK and watch it flatten.

The rule

Design in RGB, convert and proof for print.

Vibrance and Saturation are the same.
What everyone says

Vibrance and Saturation are the same.

The reality

Saturation boosts every colour equally (wrecking skin); Vibrance protects saturated areas and skin.

Why people believe it

They sit next to each other and both ‘add colour’.

Test it yourself

Push each to +50 on a portrait and compare the skin.

The rule

Reach for Vibrance on anything with people.

Experiment — guess the quality

Four exports of the same photo. Click the one you think is the uncompressed original.

Industry Says

AdobePreserve the source; edit non-destructively, always.
GoogleLighter images rank higher — optimise for Core Web Vitals.
AppleExact pixels (PNG) or infinite scale (vector) — nothing soft between.
NetflixOptimise for recognition at thumbnail size.
AmazonTune every image for conversion, not artistry.
MetaOptimise for feed speed above all.

The Vocabulary

The language of production and asset management.

Workflow

Definition
The ordered sequence from raw input to finished, delivered asset.
Why it matters
Naming it turns a scramble into a repeatable, teachable process.

DAM

Definition
Digital Asset Management — a searchable library of media with metadata, tags and versions.
Why it matters
It is how teams find the one approved file in seconds, not emails.

Version control

Definition
Keeping master, review, approved, production and archive as distinct, never-overwritten states.
Why it matters
It is why a rollback is a click, not a rebuild.

Batch processing

Definition
Applying one recorded action across many files at once.
Why it matters
It turns an eight-hour export into a coffee break.

Contact sheet

Definition
A single grid of thumbnails for review and selection.
Why it matters
It is how a client picks from 300 shots without 300 emails.

Soft-proof

Definition
Simulating on screen how colours will look on a specific output device.
Why it matters
It catches the RGB-to-CMYK shift before the press does.

Retina / DPR

Definition
Device pixel ratio — how many physical pixels map to one CSS pixel (1×/2×/3×).
Why it matters
It is why a crisp web image needs a 2× asset.

Pipeline

Definition
The full path an asset travels across people and tools, capture to publish.
Why it matters
Image management is designing that path, not just editing a file.

Common Questions

The workflow and asset-management questions designers actually ask.

What is a design workflow, really?

An ordered path from raw input to delivered asset — what to gather, which tool at each step, how to export, and where it goes. Naming and repeating it is what separates production from improvisation.

How should I name and organise image files?

Name by what it is, where it goes, and which version (hero_web.webp, hero_2026-07-15_approved.psd) — never “final_final”. Keep RAW, working masters, exports and archive in separate folders, and never overwrite a master.

How do professionals back up creative work?

In layers: laptop, cloud, external SSD, and a cold archive. One SSD failure can destroy years, so the master always lives in at least two places, one of them off the working machine.

How does a workflow change at scale?

One asset becomes thousands, so the manual steps must become automated: templates, presets, batch actions and a system that generates every size from one master. You stop hand-crafting and start operating a pipeline.

Where does AI fit into an image workflow?

As one step, not the finish line: prompt, generate, then upscale, retouch, remove backgrounds, set real type and export to spec. The craft has moved downstream to integrating and finishing the generated image.

What should I check before every export?

Resolution for the output, colour space (sRGB/CMYK), embedded profile, metadata, sensible compression, accessibility/alt text, and correct naming — a quick QA pass that catches the expensive mistakes.

Test Your Production Sense

Ten questions in seven formats, each with layered hints. Served from the bank, never hardcoded.

Loading the question bank…
Question 1 of 10
Multiple choice

Which Is the Right Call?

Five rounds. Two options each — the professional choice, and why.

Round 1 of 5Score 0
Copyright © Pawan Nayar · LLOS.ai · 2026 — Original pedagogy, voice, and design — all rights reserved. Image Management · Workflows & Production.