May 12, 2025
At Brightidea I gradually stopped being just the designer. Leading Programs, Idea Box, and then Whiteboard from zero to one, I worked directly with the CEO on vision and strategy, then owned the roadmap, the backlog, the release cadence, and the launch. This spanned the whole product-lead job, with design folded inside it.
Then I went back to being a designer, on purpose. That round trip – from designer, to designer-who-owns-the-roadmap, back to designer – changed how I work more than any course or book. Here’s what came back with me.
Prioritization is a design discipline nobody teaches designers
As a designer, I used to experience the roadmap as weather: decisions that arrived from elsewhere, sometimes baffling, occasionally ruining a perfectly good plan. Owning it cured me of that permanently.
When every “yes” is visibly a “no” to three other things — when you have to face the customer whose request got bumped, and the engineer whose quarter you just rearranged — you stop evaluating features on whether they’re good and start evaluating them on whether they’re better than everything else we could do with the same weeks. Most things are good. Almost nothing clears the second bar.
Designers are trained to advocate for the user and for quality, and we should. But advocacy without opportunity cost is just enthusiasm. The strongest design argument isn’t “users need this.” It’s “this beats the alternatives, and here’s what I’m willing to give up for it.” PMs and leadership hear the second argument as speaking their language. They hear the first as a stakeholder to be managed.
The backlog is a design surface
Running the backlog taught me something unglamorous: how a problem is written largely determines how it gets solved. A ticket that says “add bulk export” gets you bulk export. A ticket that says “idea managers doing quarterly reviews can’t get their data out fast enough” might get you something better, cheaper, or both.
I started treating problem statements and the words used to craft them as carefully as I’d treat an interface. Because they are one. It’s the interface between what we know and what gets built. Sloppy framing compounds into sloppy products long before any pixel goes wrong.
Cadence beats heroics
The Idea Box team honed a quarterly release rhythm: plan, build, harden, launch, repeat. Watching it from the owner’s seat convinced me that a reliable cadence is worth more than any individual release being bigger. Predictability compounds: marketing can plan launches, sales can promise dates, engineering can pace itself, and design gets a drumbeat to design ahead of instead of scrambling behind.
As a designer I now actively design to the cadence. It’s better to right-size, split work, or re-use a component so that something whole ships every cycle, rather than fighting for the oversized version that slips. A smaller thing that ships teaches you more than a bigger thing that doesn’t.
What design loses when you own everything
Honesty requires the other half. Wearing both hats, my design work got thinner. Not because of hours, because of stance. The PM’s job is to converge: narrow scope, kill options, commit. The designer’s job, in its crucial early phase, is to diverge (and I love this part so much): hold the problem open, explore, resist premature closure. One brain can’t fully do both on the same feature; convergence pressure always wins, because the roadmap is watching and engineering is knocking.
I caught myself designing the version I already knew we’d build — skipping the exploration that sometimes finds the version nobody asked for. That’s the quiet tax of the hybrid role, and it’s why, given the choice, I returned to design and partnered with PMs instead: the tension between the roles is a feature. The healthiest products I’ve worked on came from a designer and a PM who each did their own job well and debated in the open.
Hiring your first designer?
Early-stage founders often need one person to cover both roles for a while. I’ve done it, it’s doable, and knowing the PM job makes me a far better partner to whoever eventually owns it. But if you’re hiring a designer who’s never owned a roadmap, know what you’re getting; and if you’re hiring one who refuses to ever think in trade-offs and dates, know that too.
The best thing I brought back from the PM seat isn’t a skill, it’s a reflex: before advocating for anything, silently pricing it. Design that knows what it costs is design that gets built.