top of page
Search

Why We Roadmap Every Project Before It Starts

Writer: Jon Irwin
Jon Irwin
Sep 15
4 min read

I think we've all been there, on one side of the table or the other. You're the in-house marketer who finally got the rebrand or the new site approved. You get in the kickoff room with the agency you just hired, excited, ready to go. What you get in that room is a few slides, a mood board, and if you're unlucky, someone busting out a conga line and calling it strategy. What you don't get is the actual plan, every step, every date, the real number, before you're already committed.

That plan usually gets built after the fact, once the agency team puts away their Hawaiian shirts and goes away to figure out what the job actually takes. And when they come back with the real timeline and the real cost, you're the one explaining to your boss why the number moved, or why the launch date slipped, on a project you already signed off on.

Or maybe you've sat in the other kind of kickoff. The plan was already laid out before you ever said a word about your actual problem, formulaic, off-the-shelf pricing dressed up as a solution. Easy for the agency to hand you, whether or not it's the right fit for what you actually need. It's simple to productize a service when you're solving the same problem for the same kind of customer over and over. I've been doing this a while, and I've never worked the same project twice.

The problem most creative shops never solve

"We'll figure it out as we go" is the default in this industry. Scope it loosely and overprice it for "margin of error," discover the real plan somewhere in the middle of the engagement, and let you find out about timeline slips, missed deliverables, and change orders as they happen instead of before they start. I try to see the good in everyone, so I don't think anybody actually plans to work this way. It's just what happens when nobody built the plan before the work did.

Same process, never the same roadmap

There are repeatable patterns in the work. I'll build a new logo, a visual identity system, a website, an ad campaign, for a lot of clients, and from a distance it can look like the same job. But the planning underneath it is never the same twice. A startup needs a logo and a VIS to get to their next funding round. An established enterprise client wants the same kind of deliverable to support a legacy brand with twenty years of equity behind it. Same headline. Different everything else, quality, quantity, process, timing, all of it changes depending on who's actually sitting across the table.

What's actually in the roadmap

I'll admit it, this is the nerd in me. I love planning out every step of a process in more detail than most clients ever see. I think of the plan itself as the first deliverable, the one I probably won't get paid for directly, but the one that does the real work: it forces me to scope the engagement honestly, and it gives you real visibility into what you're getting and when, instead of a vague promise dressed up in a proposal. That matters more than almost anything else I do.

Where this happens

So where does that plan usually come from, when it exists at all? Sometimes a client emails "I want a website," and someone on the agency side turns that into a formal document and a number, then kicks off the team. Sometimes the agency hands them a templated SOW that loosely resembles the last project that looked kind of like this one. Either way, everyone's surprised later, added steps, extended deadlines, blown budgets. None of it is fun. Not for the client, covering the overage, and not for the agency realizing it sold the wrong plan.

I build the roadmap before any of that happens because it's what actually produces a good outcome, a client who knows what's coming, and a team that knows what they're building and why. When everyone on both sides of the table knows what's expected of them and when, the whole engagement runs differently. I care about this more than almost anything else in how I run projects. Can you tell?

And the plan isn't locked the moment I hand it to you. That's actually the point of sharing it early. Once you see the whole roadmap, you can push back on it, tell me where it doesn't fit your team's workflow, your approval process, or what actually matters for your specific goals. I'd rather adjust the plan before we start than force you into a process that was never built around your business. You know your team and your constraints better than I do walking in the door.

What this looks like in practice

Take SportsHub Network. High level: an established company evolving three existing product brands into one new parent brand. The engagement scoped into two workstreams, a full brand identity system and a Figma-based website design system, each mapped out month by month before any design work started. Brand identity kicked off in June and was complete by July. The website system and page templates are being built out now, running through October, with a full buffer month reserved at the end for review and closeout. The client knew what was getting built and roughly when, before they signed anything. No mid-project surprises about scope or timeline.

Before you hire a creative partner

Ask two questions before you sign anything. Has this agency shown you the full roadmap, not just some bullets in an SOW and a price? And do you know what quality, quantity, and timing look like for every deliverable before day one? If the answer to either is no, you're not buying a plan. You're buying a promise, and you'll find out what it actually costs later.

Who would you follow up Everest? The guide who says he's been there and promises you'll make it, or the one with the plan, every step mapped, every calorie accounted for, every item preplanned for your pack, and the training regimen laid out before you ever leave home?

If you want to see how I actually build one of these, set up a call. I'll walk you through it.

 
 
 

Comments


bottom of page