THE VR SCHOOL
  • Schools & Districts
    • License the academy
    • Free program for your students
    • Request a demo
  • Catalog
    • AI & Data
    • Cybersecurity & Web
    • Programming
    • Health Science
    • All Guilds
    • All courses
  • Families
  • Accreditation
  • Log In
  • Request a demo
  • Home
  • Courses

RLP Graphic Design A — Design Thinking and Principles

Curriculum

  • 4 Sections
  • 20 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Unit 1: Graphic Design as Visual Communication
    5
    • 1.1
      What Graphic Design Does: Audience, Message and Medium
      50 mins
    • 1.2
      The Visual Elements: Line, Shape, Value, Texture and Space
      100 mins
    • 1.3
      Reading Design Across Eras, Cultures and Industries
      100 mins
    • 1.4
      Designing a Flyer: From Brief to Print-Ready File
      100 mins
    • 1.5
      Portfolio Project: Graphic Design in the World
      150 mins
  • Unit 2: Design Thinking: Problems, Audiences and Briefs
    5
    • 2.1
      Design Thinking and the Client Brief
      50 mins
    • 2.2
      Ideation Under Constraints: Mind Maps and Thumbnails
      100 mins
    • 2.3
      Empathy, Audience Research and the Mood Board Critique
      100 mins
    • 2.4
      Prototyping and Testing Two Approaches
      100 mins
    • 2.5
      Portfolio Project: Design Problem Case File and Pitch
      150 mins
  • Unit 3: Tools, Media and the Iterative Workflow
    5
    • 3.1
      Choosing the Right Tool: Raster, Vector and Layout
      50 mins
    • 3.2
      One Design, Two Media: Hand and Digital
      50 mins
    • 3.3
      Rights Lab: Copyright, Licenses and Fair Use for Designers
      100 mins
    • 3.4
      Iteration in Practice: Drafts, Versions and Feedback
      100 mins
    • 3.5
      Portfolio Project: Iteration Portfolio from First Draft to Final
      150 mins
  • Unit 4: Principles of Design
    5
    • 4.1
      Principles That Direct the Eye: Hierarchy, Contrast and Emphasis
      50 mins
    • 4.2
      Same Content, Four Layouts: Balance, Alignment and Proximity
      100 mins
    • 4.3
      Rhythm, Movement, Unity and Gestalt in Critique
      100 mins
    • 4.4
      Proportion, Scale and Visual Metaphor Across Cultures
      100 mins
    • 4.5
      Portfolio Project: Principles Poster and Semester Portfolio Review
      50 mins

Iteration in Practice: Drafts, Versions and Feedback

Unit 3  ·  Production Workshop  ·  Lesson 14 of 20

Iteration in Practice: Drafts, Versions and Feedback

GADP.DES.6RLP-GDA
Hands revise three increasingly polished poster layouts connected in a feedback loop.
By the end of this lesson I can…

move a design through rough, comp and final stages, manage versions and backups professionally, and use feedback to make and document purposeful revisions.

Instruction

Design is a loop, not a line. No professional gets it right the first time. The design process cycles: make a version, get feedback, evaluate, revise, and go around again until the design meets its criteria or the deadline arrives. The record for this course calls this trial, evaluation and refinement. Mistakes are information.

The stages of a design. Studios commonly name the stages. Thumbnails are tiny concept sketches (Unit 2). Roughs are larger, full-size sketches or quick digital layouts that test composition and hierarchy with real headline text. Comps (comprehensive layouts) look close to finished, with chosen type, colors and images, and are what a client approves. The final is the corrected, production-ready file. Each stage answers different questions, so each needs different feedback: at the rough stage ask “Is the idea clear?”, not “Is that the right shade of green?”

Getting useful feedback. Ask specific questions tied to your criteria: “What do you notice first?” “What is this asking you to do?” “Where did your eye get stuck?” Separate feedback on goals (“I cannot find the date”) from feedback on taste (“I don’t like purple”). Goal feedback is almost always worth acting on. Taste feedback matters when it comes from the audience or the client, and less when it comes from someone outside the audience. You do not have to take every suggestion, but you should record every one and decide on purpose.

Worked example. A student’s rough poster gets three comments: (a) “I read the logo before the event name”; (b) “The photo is great”; (c) “I’d use blue.” Comment (a) points to a hierarchy problem, so the student reduces the logo and enlarges the event name. Comment (b) says keep the photo. Comment (c) is taste from someone outside the audience, so the student notes it and tests it only if time allows. The change log records all three and what was done.

Versions and file names. Never work on your only copy, and never name a file final_FINAL_2.svg. Use a consistent pattern: client_project_v01.svg, v02, v03. Save a new version before any major change (File > Save As) so you can always go back. Keep a short change log: date, version, what changed, why.

Back up. A widely used rule is 3-2-1: keep three copies of important work, on two different kinds of storage, with one copy somewhere else (such as a parent-approved cloud folder). Lost work is the most common, and most avoidable, disaster in a design course.

Managing time and responsibility. Iteration can go on forever, so set a limit. Plan backward from the deadline: final due Friday means comp approved by Wednesday and rough feedback by Monday. When you work for a client, deliver each version on the date you promised, or tell the client early that you cannot.

Knowing when to stop. A design is done when it meets the criteria, not when it is perfect. Last-minute changes that are not tied to the criteria often add risk, such as new typos or broken layouts, rather than value.

📖 Read for this lesson

The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.

  • Iteration Workshop Sheet: A Worked Rough, Sorted Feedback, a Change Log and File NamesSLS original worked example; constructed poster and feedback · about 2 min

    A described rough, five feedback comments sorted into goal and taste with decisions, a filled-in change log, stage and file-naming rules and a backup plan.

Vocabulary in context

  • iteration — Repeating a cycle of making, testing, evaluating and revising to improve a design.
  • rough — A full-size early layout that tests composition and hierarchy.
  • comp — A comprehensive layout close to the finished design, used for client approval.
  • version control — Saving numbered versions of a file so earlier states can be recovered and changes tracked.
  • change log — A dated record of what changed in each version and why.

Formative check

Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.

+50 XP

Which feedback should you almost always act on?

It names a problem with the design’s goal (the hierarchy), not a matter of taste.
+50 XP

Which file name follows a professional version pattern?

Client, project and a zero-padded version number keep files sortable and traceable.
Flashcard

Thumbnail

Tap to reveal
Answer

Tiny concept sketch: is there an idea?

Flashcard

Rough

Tap to reveal
Answer

Full-size layout: is the composition and hierarchy clear?

Flashcard

Comp

Tap to reveal
Answer

Near-final: does the client approve the look?

Flashcard

Final

Tap to reveal
Answer

Corrected, production-ready file

Flashcard

3-2-1 backup

Tap to reveal
Answer

Three copies, two kinds of storage, one elsewhere

Copy two entries from your change log. For each, give the feedback you received, the change you made, and why that change serves your criteria.

0 words
Quick self-check

How confident are you that you can manage versions and backups and revise a design purposefully from feedback?

Not yetVery confident

Missouri CTE — Graphic Arts/Desktop Publishing (034353) objectives addressed: GADP.DES.6, GADP.WRS.7, GADP.FND.7, GADP.FND.6, GADP.FND.4, WHST.9-10.5

Instructional focus: Professional iterative production workflow

Reading

Iteration Workshop Sheet: A Worked Rough, Sorted Feedback, a Change Log and File Names

SLS original worked example; constructed poster and feedback · SLS original

Why this reading. The workshop asks you to make version 2 of your design, keep a change log and record feedback. This sheet supplies a worked case, the food bank poster from the Unit 2 readings, so you can see what a rough, a comp and a change log look like. SLS original; the poster and the feedback are constructed.

Version 1 (rough), described

File: valleyharvest_poster_v01.svg, letter size, black and white. The logo, 2.5 in. wide, sits at top left; the headline “Build Saturday” is 36 pt below it; a crate drawing fills the middle; the day and time are 12 pt at the bottom; the scan code is 0.75 in. square in the bottom right corner.

Feedback received, sorted

CommentGoal or taste?Decision
“I read the logo before the event name.”Goal (hierarchy)Act: logo reduced to 1.25 in.; headline to 54 pt
“I could not find the time.”Goal (findability)Act: day and time moved under the headline, 24 pt
“The crate drawing is great.”Goal (keep)Keep unchanged
“I would use blue.”Taste, from outside the audience, and the job prints black and whiteNote it; do not act
“The code is tiny.”Goal (function)Act: code enlarged from 0.75 to 1.25 in.

Change log

DateVersionWhat changedWhy (feedback)
Oct. 2v02Logo 2.5 to 1.25 in.; headline 36 to 54 ptLogo read before headline; the headline is now 54 ÷ 36 = 1.5 times its old size
Oct. 2v02Day and time to 24 pt beneath the headlineTwo testers could not find the time
Oct. 3v03Scan code 0.75 to 1.25 in.Code hard to scan from 3 feet

Stages and file names

Thumbnail (concept) → rough (full-size layout with real headline) → comp (chosen type, colors, images; what a client approves) → final (corrected, production-ready). Ask at the rough “Is the idea clear?” and at the comp “Is this what you want?” Name files valleyharvest_poster_v01.svg, _v02, _v03; do not overwrite. Before any big change, Save As.

Backup and time

3-2-1: three copies, on two kinds of storage, one somewhere else (for example the school cloud drive). Plan backward: final due Friday, comp approved Wednesday, rough feedback Monday. Stop when the criteria are met.

Up NextComplete & Continue →

Leave a Reply Cancel reply

Rights Lab: Copyright, Licenses and Fair Use for Designers
Prev
Portfolio Project: Iteration Portfolio from First Draft to Final
Next

© 2026 The VR School | Career content by Wiley | Powered by Sejal Learning Systems.

Join free · Accreditation · Privacy Policy · Terms of Service

Modal title

Main Content