Unlock a clear path forward when the assets you inherit are doing more harm than good.
January 25, 2026 · Gev Marotz · 3 min read
When you inherit bad work, the risk isn’t the work itself. The risk is letting it slide and having your name become the new owner of it.
Key takeaways
Inherited assets feel “good enough” because they’re already in motion.
Keeping them buys short term comfort and long term doubt in your judgment.
The move is: respect what exists, reset the standard, redirect to the real issue.
Give options, not an ultimatum.
If you only fix the surface, you inherit the blame when it fails again.
The bad asset problem
There’s a moment that comes up in fractional work again and again.
You inherit something that doesn’t quite work.
A logo. A forecast. A codebase. A process.
It’s already in use. People are attached to it. And it would be easier to just keep going.
That choice usually feels harmless.
It isn’t.
Using inherited work that doesn’t meet the bar keeps things comfortable in the short term.
Over time, it erodes trust in your judgment.
A logo, but not really about a logo
This could have been anything. It just happened to be a logo.
On a recent project, the founders were attached to a logo that wasn’t good enough for the role it was playing.
They liked it.
They’d already put it into decks and email signatures.
The issue wasn’t taste.
It just wasn’t ready.
“We think this is our brand,” they said.
I paused and said:
“I’m not comfortable putting my name on this yet.”
That sentence shows up in different forms across every role.
It’s the moment you choose between keeping the peace and owning the standard.
The move: give paths, not a fight
Instead of shutting it down, I laid out three paths.
Refine Clean up what’s there. Fix the fundamentals. Make it consistent.
Hybrid Keep small elements, but introduce stronger structure around them.
Start fresh Build something new from strategy, not aesthetics.
The logo was just the surface.
The real question was how to handle inherited work without sidestepping responsibility.
A simple framework: Respect → Reset → Redirect
This is what’s worked for me.
1) Respect
There’s always a reason something exists.
Acknowledge that without pretending it’s good enough.
“I see what you were going for. Here’s where it starts to break down.”
2) Reset
At some point, the standard has to be named.
“I can’t put my name on this in its current form.”
Not as a threat.
As a boundary.
3) Redirect
Weak outputs are usually symptoms.
The logo wasn’t the real problem.
The problem was unclear fundamentals.
In finance, this shows up as a forecast no one trusts. In engineering, it’s compounding technical debt. In design, it’s a template dressed up as a brand. In ops, it’s a process that depends on heroics.
Different artifacts. Same risk.
Building on sand.
If you fix the surface but leave the foundation broken, when it fails later they won’t blame the old work.
They’ll blame you.
Copy you can steal
If you need a calm way to say it without escalating:
“I see why you chose this. Here’s where it breaks once we put it under load.”
“I’m happy to refine it, but I don’t want to ship it as is.”
“We can keep it for now, but we should be honest about the risks.”
“If we want this to hold up, we need to fix the fundamentals first.”
Where we landed
After sitting with it, the founders said:
“We don’t actually know our brand well enough to make this work at the level we want. Let’s sort that out first.”
So we did.
We cleaned up the basics, kept the old logo out of the spotlight, and built toward something better over time.
No confrontation.
No embarrassment.
Just clarity.
What this is really about
Inherited work is part of the job.
The real decision is whether you treat it as something to accommodate or something to be accountable for.
Your name ends up attached either way.
Acknowledge what exists. Be clear about the standard. Move the conversation to the real work.
That’s how progress happens without burning trust.
