I've seen this happen more times than I'd like… a team spends weeks working through a rebrand or website restructure. Early thinking turns into moodboards, and the moodboards turn into concepts that become real pages. The VP of Marketing knows the CEO will need to see it, but not just yet. The intention is usually good, and most VPs do this for understandable reasons:
- "Let's make it stronger first."
- "Let's get one more round done."
- "Let's make sure we can defend it."
Because nobody wants to waste the leader's time with unfinished work, nor create confusion before there's something concrete to react to. In fact, this isn't a process problem. It's a visibility issue driven by how the VP manages their own exposure.
Then, when the CEO finally sees it, the conversation moves backwards: suddenly, questions that should have surfaced weeks ago finally appear. Next, assumptions get challenged, direction changes, and work gets reworked. At that point, the issue isn't whether leadership saw the work: it's what they saw, and when.
The Three Root Causes:
1. Career risk
The first reason isn't a flaw in the VP. It's simply a human, rational response to how marketing leadership is usually evaluated: the VP is judged on results, not process, because nobody gets credit for showing rough thinking.
So exposing unfinished work can feel risky, especially in front of a CEO, investors, or a board. Early iterations are messy by definition, since the thinking is still forming, and the direction isn't fully proven yet. Therefore, waiting feels safer.
The problem is that every week of waiting increases the cost of disagreement. If leadership pushes back on a positioning direction after two days, that's manageable. However, if the same disagreement appears after six weeks of design and development work, everything slows down. The work doesn't just pause. It restarts… and that's expensive.
2. No strategic frame to anchor the work
The second issue is more structural. Many rebrands start before leadership has fully aligned on positioning. It's usually obvious that change is needed, but what's less obvious? It's what the company is actually becoming.
I've sat in conversations where leadership agreed on the need for a new website but couldn't agree on who the company was trying to serve. Others agreed they needed a rebrand, but had completely different views of where the business was heading. When that happens, every early iteration becomes subjective, because there's nothing to evaluate it against:
- No strategic frame
- No agreed positioning
- No shared narrative
Without that foundation, design gets forced to carry the argument. So, the VP ultimately presents visual solutions, and that's where things get uncomfortable. The conversation becomes about colors, layouts, and preferences, instead of about the direction behind them.
The difficult part? The VP usually feels this pressure before anyone else does. They're trying to move execution forward while leadership is still negotiating what the company stands for.
3. Misreading what the CEO actually wants
The third reason is surprisingly common. Many VPs wrongly assume the CEO wants polish, whereas most growth-stage CEOs want clarity. They are pattern-thinkers and are trying to understand the direction, why a decision is being made, and how it supports growth.
The design itself is rarely the main concern… the direction is. But because the VP assumes leadership wants finished work, they delay sharing until execution is already well underway. By then, the CEO is reacting to outputs instead of helping shape the thinking behind them.
I've seen situations where leadership would have aligned quickly if they had been involved earlier at the strategic level. Instead, they were shown work that invites a different type of feedback. Now they find themselves debating the solution instead of discussing the problem. And the visibility gap gets unavoidably self-inflicted… because the VP has been solving for a version of the CEO that often doesn't exist.
Two Complementary Solutions Needed to Fix the Visibility Gap:
1. Replace iteration reviews with strategic checkpoints
The answer is not to show more rough work, but to change what gets shown. So instead of reviewing design iterations, leadership reviews decisions in progress, such as positioning options, market interpretation, and narrative direction.
In practice? Leaders get brought in at the strategic layer, not the execution one; the conversation moves upstream. As a rule, each checkpoint should answer three questions:
- Why are we making this decision?
- What problem does it solve?
- How does it support business goals?
Visual execution becomes evidence of a direction that has already been agreed upon, and not the mechanism used to discover the direction. Actually, this dynamic prevents late-stage resistance because leadership has been part of the thinking from the start. As a result, VPs are replacing the wrong meetings with the right ones and stop defending their creative choices, while leadership starts evaluating strategic decisions.
2. Define decision ownership before the work starts
The complementary solution is even simpler. I've worked with teams where fifteen people were giving feedback, so nothing moved. Eventually, we reduced the decision group to three people. The process became dramatically faster almost immediately, because the structure was established before any design work began.
The real solution is to define decision rights upfront, in writing:
- Who contributes perspective
- Who challenges direction
- Who approves positioning
- Who approves execution
When these roles are unclear, the VP ends up managing exposure. When they're clear, the VP can focus on moving the work forward. They know which conversations require leadership and which don't. The right people see the right decisions at the right time. Nobody is guessing.
Key takeaway
Visibility is often treated as a transparency issue, but it isn't. It's a structural problem. When positioning is clear, decision ownership is defined, and leadership is involved at the strategic level, there is very little reason to hide anything.
The VP doesn't need to protect unfinished work because the conversations are happening where they should happen: early… before execution becomes expensive, before assumptions become designs, and before disagreement turns into rework.
If you are preparing for a rebrand and unsure whether your foundation is ready, I work with leadership teams to set a clear path forward. The build is handled by Onward Agency, a focused team across design, development, and motion. Ensuring the original intent is preserved from decision to delivery. Because that's how delivery risk is reduced, stakeholder pressure is managed, and rebrands move forward with confidence.
