Design errors often only become apparent after printing. This is the process to detect them beforehand.
Most brand identity errors do not appear when viewing files on screen. They only become evident when the logo is scaled down on a flyer, stretched on a sign, or when the actual background washes out the colors. Testing the identity in real-world environments is a mandatory step before handing over files for production, not an optional one. Investing a few days in early testing helps save on the entire cost of reprinting and the waiting time that arises later.
Most brand identity errors do not appear when viewing files on screen. They only become evident when the logo is scaled down on a flyer, stretched on an outdoor sign, or when the actual background washes out the colors. This is why the testing process in real-world environments, before handing over files to the printer, is not an optional step.
The screen emits light from within. Printed materials reflect light from the outside. These are two completely different perception mechanisms, and the human brain processes them in different ways. A logo that looks sharp and balanced on a 27-inch screen can lose all its fine details when scaled down to actual size on an A5 flyer. A deep navy color on screen can turn into a solid black block when printed offset on highly absorbent paper.
The issue is not just about color. The viewing distance completely changes the reading conditions. A sign designed to look good from 30cm on screen can become a jumble of letters when viewed from 5 meters by a pedestrian. A good testing process must accurately simulate the distance, lighting, and materials of the actual deployment environment.
Not every identity system needs to be tested in all environments. However, there are four groups of environments that most Vietnamese brands implement, and each group has conditions that expose errors in different ways.
Identity testing is a structured process with clear criteria for each environmental condition.
Step 1. Create a prioritized list of applications for deployment. Before testing anything, you need to know where this identity will first and most frequently appear in the first six months after delivery. Focus your testing rigorously on those touchpoints, rather than spreading it thin.
Step 2. Prepare test files in the correct production format. Do not test using the original design file. Export the file in the format required by the printer, usually PDF/X-1a or PDF/X-4 for printing, PNG or SVG for digital. Correct color space, CMYK for print, RGB/sRGB for digital. Correct resolution.
Step 3. Test print and apply the actual mock-up. Print flyers and business cards at actual size. Apply the mock-up of the sign to a real wall, taking photos under different natural lighting conditions (morning, afternoon, evening with lights). Do not use a Photoshop mock-up to completely replace this step.
Step 4. Testing against criteria, not feelings. How many levels of scaling down can the logo still be readable? Does the contrast between the text and background meet the minimum ratio according to WCAG standards? Does the printed color match the specified Pantone or CMYK values? These are technical questions that can be measured, not aesthetic ones.
Step 5. Record results and adjust the original file. Any adjustments arising from testing must be updated in the original file and noted in the brand guidelines. Do not just correct the output file. This loop ensures that the next print does not repeat past errors.
A brand is the gut feeling customers have about a product, service, or company. That feeling is formed from every touchpoint, not just from the design file.
Marty Neumeier, The Brand Gap
Not every business owner can recognize these errors until the publications have been delivered. Below are the most frequently occurring errors in practice.
In many design projects, the real-world testing step is overlooked for two common reasons. The first is time pressure: when the printing deadline has been set before the design project is completed, there is no time left for testing. The second is that no one clearly states this step from the beginning in the project scope, so both parties tacitly overlook it.
The result is a process that jumps straight from "approving the file on screen" to "sending the file for printing." The gap between these two steps is where money is lost later on, not always a lot, but never less than the cost of proper testing from the start.
A good process places the testing step as a named phase, with a timeline and clear acceptance criteria right from the project planning stage. This is an integral part of the delivery process, not just an extra task when time allows.
Lindgaard et al., "Attention web designers: You have 50 milliseconds to make a good first impression", Behaviour & Information Technology, 2006. Marty Neumeier, The Brand Gap. Byron Sharp, How Brands Grow. Jenifer Tidwell, Designing Interfaces. Research on printing context and identity application from real-world processes at Sinh Vũ Studio.
The screen displays RGB colors with light coming from behind, while printed materials reflect ambient light. The same color can look completely different when printed on couche paper, aluminum sheets, or tarpaulin. Additionally, the actual size and viewing distance in real-world environments create perceptual conditions that differ significantly from viewing files on a 24-inch screen.
Depending on the scale of the identity system, the real-world testing phase typically takes between two to five working days, including test printing, photographing the actual mock-up, and adjusting the files. This cost is much lower than the cost of reprinting the entire publication when errors are discovered post-production. This step is included in the project scope from the beginning, not an additional expense.
The most common issue is logos losing detail when scaled down below 20mm and colors shifting when printed on textured backgrounds. Additionally, there is text losing contrast when placed on real-world images, and the proportions of signs appearing unbalanced when viewed from a pedestrian's distance. These errors do not appear on the PDF file viewed on a computer.