Logo Color Correction — Bluepoint

Overview

During the 2025-11-06 team standup, Andrzej and Melissa identified and resolved a perceived color mismatch between Bluepoint's logo variants. The client (Wade) had flagged that different logo files appeared to use different shades of blue. Investigation revealed the root cause was a browser preview rendering issue rather than an actual export error — the underlying vector files used consistent brand-book colors throughout.

Rather than correcting a technical error, the resolution was a deliberate visual alignment: updating the flat "solid blue" logo to use the more vibrant blue from the gradient version, and renaming files to make variant types explicit.

Problem

The client perceived a noticeable color difference between logo variants when viewing exported files (JPEGs/PNGs) in a browser. Specifically:

The "solid blue" logo appeared as a duller, darker blue
The "gradient" logo appeared as a richer, more vibrant blue
The client expected all blue logo variants to match the brighter, more vibrant tone

Root Cause

The discrepancy was not an export error. When opened in Illustrator, all files used the same brand-book color values. The visual difference was caused by:

Browser preview rendering — Chrome displays SVG/vector previews with color shifts that don't reflect the true exported output
Inherent color difference between gradient and flat variants — The gradient logo uses a brighter blue at its highlight point; the flat "solid blue" used a distinct, darker brand-book color that was technically correct but visually inconsistent with client expectations
Uncalibrated client display — The client's monitor likely exaggerated the perceived difference

Complicating Factor

The Bluepoint brand guideline documents the gradient logo in use (e.g., in the 15-year anniversary logo) but does not specify the gradient color stops. This left ambiguity about which blue should be considered the "primary" blue.

Resolution

To align with the client's visual expectations and prevent future confusion, the following changes were agreed upon:

File Updates (Andrzej)

Update solid blue logo — Replace the existing flat "solid blue" color with the brighter, more vibrant blue used in the gradient version's highlight
Rename gradient files — Add the word gradient to all gradient logo filenames so variant type is immediately clear (e.g., bluepoint-logo-blue-gradient.png)
Apply consistently — Make the same updates to both the Bluepoint and Bluepoint ATM logo families, ensuring all variants are consistent across both brands
Move finals to design assets — Once complete, ensure all corrected files are placed in the design assets folder, which is the source of truth and the folder the client will be given access to

Brand Guideline Note

The gradient blue should be formally added to the Bluepoint brand guideline, as it is already in active use across logo files and the website. This was not done as part of this task but was flagged as a follow-up.

Key Decisions

Decision	Rationale
Update solid blue to match gradient's vibrant blue	Client's visual expectation takes precedence; "customer is always right"
Do not change website CSS colors	Website colors are approved and client-preferred; changing them would require broader scope
Rename gradient files to include "gradient"	Prevents future confusion for team and client when selecting logo variants
Apply changes to both Bluepoint and Bluepoint ATM logos	Consistency across the full brand family
`design assets` folder is source of truth	Prevents accidental use of in-progress files from the `projects` working folder

Action Items

[ ] Andrzej — Update solid blue logo files to use the brighter gradient blue
[ ] Andrzej — Rename all gradient logo files to include "gradient" in the filename
[ ] Andrzej — Apply updates consistently to Bluepoint ATM logo variants
[ ] Andrzej — Move all finalized logo assets to the design assets folder
[ ] Melissa — Communicate the color update to the client, framing it as an alignment to their visual preference and noting the gradient will be added to the brand guideline

Context & Notes

The color mismatch discussion arose directly after the standup proper; Andrzej flagged it and Melissa joined to review files live via screen share
Melissa noted the meeting with Wade the previous day had been difficult — he was frustrated about several Bluepoint deliverables, making it important to resolve this cleanly and quickly
Mark noted the client shouldn't technically need vector files, but the client is reviewing JPEGs/PNGs, which is where the preview issue manifests
The brand guideline was originally created by a former team member (Rob); the gradient was used in practice but never formally documented

^[1]
^[3]
^[2]