Jennifer Palais: The person between brand and product

Notes on path

Few people bridge brand and product, which is exactly why it matters

In a job market being simultaneously hollowed out by AI and reorganized around who can actually ship, the conversation about specialized expertise versus generalist capabilities misses the real edge. The strategists who will remain dangerously important aren’t the ones who can “do a bit of everything”, they’re the ones who can move fluidly between brand vision and product execution without losing fidelity in either language. They’re not T-shaped. They’re not full-stack. They’re something else entirely: people who can see the system whole and intervene at the level where brand philosophy becomes product architecture, where cultural intuition becomes roadmap decisions, where the story you’re telling and the thing you’re building are the same act of authorship.

Jennifer Palais has lived this for 15+ years at Mozilla, Media Arts Lab and R/GA and other agencies working on clients such as Apple, Netflix, Google, Hyundai and Intel coordinating engineers and creatives, naming products and browser engines, orchestrating 50 million dollar production budgets across nine partner agencies to create cultural moments and world class products. This conversation is about what that actually requires, what it costs, and why most organizations say they want this integration but structurally often prevent teams from achieving it.

The “unreasonable” space between

Kima: At Mozilla, you were described as someone who “ensured brand principles were reflected in all product and UX decisions.” That’s the work most organizations say they want but actively resist because it slows things down and forces uncomfortable conversations. When you’re in the room and you see a product moving in a direction that violates brand truth, not just aesthetic consistency, but philosophical integrity, how do you intervene without becoming the person everyone learns to route around?

Jennifer: The truth is that sometimes I was the person who was routed around, and sometimes I was actively sought out.

You can’t be great in every room. In the product orgs I worked in, some partners recognized the value of what I brought and pulled me in early and often. They understood that when I pushed, it wasn’t about taste or preference, it was about making the product stronger as a system.

Others didn’t. Especially with a legacy product like Firefox, where long tenure can make change feel personal. In those environments, even well-supported decisions can feel threatening, and curiosity can give way to defensiveness.

What I learned at Mozilla is that this ultimately isn’t a logic problem, it’s a belief problem. Even people who claim to be purely rational are operating from a set of values about what matters and what doesn’t. I had user research clearly demonstrating the need for stronger brand expression in the browser, but if someone fundamentally doesn’t believe that aesthetics, emotion, or identity belong in software, no amount of data will convince them.

Seeing isn’t believing. Believing is believing. Everything is religion.

The way you avoid being routed around isn’t by forcing the argument harder, it’s by understanding where belief already exists and choosing your battles accordingly. With the tech client I work with now, belief is shared. They hired experts precisely because they want brand DNA embedded in the product itself, not layered on later as an afterthought. That alignment changes everything: the speed for delivering value increases directly because there is trust and ultimately the quality of decisions is more sound.

And increasingly, this is becoming the norm. It’s very hard to argue that brand doesn’t matter given the volume of evidence we now have. Brand won’t save a bad product, but it can absolutely make a difference for a serviceable product. Liquid Death is just water, but it tells a very specific audience, I see you. And at the end of the day, that sense of belonging is a product feature whether teams admit it or not.

Kima: The Lady Gaga/Intel GRAMMYs tribute required you to orchestrate 9 partner agencies, translate between Intel engineers and Haus of Gaga creatives, and create a cultural moment that hadn’t existed before. You wrote: “The engineers were lit up in a way I hadn’t previously seen.” What were you seeing that others missed? And is that specific kind of seeing—the ability to recognize creative potential across wildly different disciplines—something you can teach, or is it more like synesthesia?

Jennifer: As a strategist and a writer, I’m deeply interested in people, specifically in what lights them up. I’m always asking: what’s activating someone here, and why? What’s the cultural mythology at work beneath the surface? Why this moment, why now?

I was in the room the first time Intel’s lead engineers and Haus of Gaga’s creative directors met to discuss the project and begin planning. This was one year out from The GRAMMYs. I emphasize that I was in the room. You have to get in that room, whatever that room is for you. I wasn’t the only one there, but I was the only who caught on to what was happening relationally and emotionally between the participants.

What I saw surprised me. The engineers weren’t politely indulging the creative conversation, they were genuinely lit up by discussions of choreography, costumes, and performance. That almost never happens in these collaborations because people already have jobs. We are coming in to layer another deliverable on top of what they are already having to deliver on. But despite this, there was electricity all around that was contagious.

That was the signal. If I felt it, others would too. That’s when I knew the story wasn’t just the performance, it was the act of co-creation. So we built the narrative around the making of the show: the robots, the lighting, the technology, and the partnership with Haus of Gaga unfolding in real time. Intel didn’t sponsor a moment; they co-authored it. And by opening that process up, we invited the audience into something real.

As for whether that kind of seeing is teachable, I don’t think it’s synesthesia, but it is a kind of emotional sight.

I’ve always been able to sense what people are experiencing beneath what they’re saying. For a long time that was a curse. Over time, I’ve learned how to read the signal without being overwhelmed by it. That ability is empathy layered with cultural literacy and pattern recognition. You can teach taste. You can teach craft. You can teach critique.

But you can’t teach someone to care about any of it. Meaning you can’t teach someone to notice when a room shifts, or when something alive is trying to happen if it doesn’t already matter to them. And sometimes it feels a bit like I’m Cassandra, I see it before others do, and I have to convince the room.

In this case, I was able to sell the idea in and it worked.

The cultural reality that product people ignore

Kima: Steve Jobs famously said “customers don’t know what they want until you show it to them,” but he was obsessed with understanding what people were ready for culturally. You’ve worked on Apple, Netflix, Google—brands that succeeded not just through execution but through cultural timing. When you’re building product strategy, how do you distinguish between “the market isn’t ready” versus “we’re not explaining this right” versus “this is genuinely too early”? What are your signals?

Jennifer: I rely heavily on gut but it’s a trained gut.

This is something Rick Rubin talks about: make the thing you want to exist in the world. But that only works if the person doing it has spent years listening, watching, and paying attention. It’s the human element of taste that everyone is talking about so much more now that AI has entered the picture.

I’ve studied culture for a long time. When something feels right to me, it’s not magic, it’s just attunement. It isn’t only about seeing patterns, which I do think AI can do well with large data sets. It’s about pulling in from inputs so disparate over such a long time that the attunement, the taste comes to the fore quite naturally.

To your question, I separate those three scenarios you mentioned by listening for different signals.

If the market isn’t ready, I usually feel curiosity less than urgency. People lean in, they ask questions, but they don’t feel compelled to change their behavior (which is what we want). The idea makes sense intellectually, but it hasn’t landed emotionally. In that case, you wait or seed the market.

If we’re not explaining it right, the signal is frustration. People want it, but they’re tripping over language, framing, or something else we need to uncover. That’s almost always a storytelling problem, not a product problem. When reframing unlocks understanding quickly, you know you’re early-but-viable.

When something is genuinely too early, the response is flat. No pull. No resistance. No heat. That’s the hardest one, because founders and teams are so bought in. It’s difficult if someone can’t see what is so clear to you.

I think my confidence in my decision making comes from breadth. I read across generations, across subcultures. I read high-brow and low-brow. I talk to people with wildly different lives and values. Over time, all of that creates a kind of internal radio tuned to the zeitgeist. When something hits, I know it. There’s no doubt. And when it doesn’t, I don’t pretend otherwise.

I learned this lesson early. My first job out of graduate school, I worked on Fiji Water. The aquifer had just been purchased. I sat in the design meetings for the bottle and label and genuinely thought the branding was too precious, that it was too pretty to work. I really hated that bottle! And I was wrong. I wasn’t a trained strategist yet, I hadn’t developed my own taste fully and so couldn’t really understand what others might want.

So today, I don’t ask, “Is this a good idea?” I ask: Is there emotional readiness? What cultural work is this product going to achieve? And whatever the answers are, do I believe this enough to stand behind it? I keep pushing on all fronts until I feel that lock in, that attunement.

Kima: Most product people treat “understanding the market” as competitive feature analysis and user surveys. But you’ve talked about being a “lifelong learner” who goes deep, who reads obsessively, who studies things that seem unrelated until suddenly they’re not. What cultural shifts are you tracking right now that you think product leaders are completely missing because they’re too busy looking at their category?

Jennifer: I like to say whenever everyone is going left, choose to go right. Right now everything is AI. So I would go towards the most human experiences possible. Live events.

I love AI in a lot of ways. I don’t have an existential dread about it because I use the products. They don’t scare me - they just help me right now. The kind of work I do, I just can’t see them doing all of it. I’m not naive though. I see it is taking certain jobs but I’ve also been around long enough to have seen this happen with a lot of things. Web 2.0 wiped out Flash developers for example. My job has morphed and changed. I used to be a digital producer and then product manager etc. My skills have deepened and there has been a progression but we don’t have digital producers anymore. It’s not a job.

I also tend to be a very optimistic person and I am aware of that but I do think you get what you look for to a degree. If you eat too many apples you will get sick. Phones use is fine unless you doomsroll for hours.

Having said all of that, I think that bespoke experiences are what brands should be building. Large and small. Live events when humans get to be as human as possible. Create things in a way that only humans can.

Draw, paint, skate, sing - whatever it is. Bodies moving, creativity flowing and all in a community environment. We will all be using AI tools in our jobs. No doubt about that. Ultimately though we want people to feel something viscerally and remember that feeling at the moment of choice.

The physical reinforcement is priceless, sight, sound, scent, touch. Get all of that folded into a memory alongside your brand or product.

There’s so much research on why live events are important for memory but because it is expensive many brands can’t or won’t invest in it.

The question of legitimacy

Kima: You’ve moved between creative agencies (R/GA, TBWA\Chiat\Day) to tech companies (Mozilla). Every time you cross into a new domain, there’s a moment where you have to establish credibility with people who speak a different language. Engineers don’t automatically trust brand people. Brand people don’t automatically trust product people. How do you earn legitimacy in rooms where your dual fluency initially makes you suspect? And has there ever been a time when you’ve deliberately hidden one side of your expertise to make the other more palatable?

Jennifer: At Mozilla I experienced culture shock as really the only brand leader in the company, in a company where brand is not valued. It was strange because I came on board because Firefox is such an iconic brand. There’s an exciting and timely story there to be told that I really wanted to tell, in the product and in culture.

The irony is that I was told I needed to hide my brand knowledge and experience in order to be taken seriously in the product organization. Ironic because a brand focus and a reasonable marketing spend is what would have solved a lot of Firefox’s problems. People know the name but think Firefox is no longer around, no longer relevant.

They didn’t really understand what I did. They all thought - she comes from marketing. The funny thing is that at that time I had very little actual marketing experience. Marketers were always my clients.

I had to work very hard to sell product ideas in a way that leadership and cross functional teams could understand. My shorthand no longer worked. It was no longer easy. I couldn’t rely on intuition because I didn’t have enough foundation yet. It was a rigor that grew me and that I’m grateful for. Productive but not enjoyable.

I’ve come to learn that when people trust themselves then they know if they can trust you. So I found that most of the distrust I encountered was based on their own fears of being wrong. When I came to the table with 100% confidence that is what would win the room over. If they could smell fear they went for the kill.

That kind of environment to the extreme is ineffective because you want to be able to share ideas and poke holes as a team. No one is 100% sure all the time, you need to be able to brainstorm.

But when a product isn’t doing well and a lot of things have been tried people can lose faith and begin looking to blame. It’s human nature to a degree and I had to remember it wasn’t about me.

Kima: There’s a specific kind of loneliness that comes with being able to see multiple systems simultaneously, you understand why the engineer is frustrated, why the creative is defensive, why the business lead is panicking, but you’re also the only person in the room who seems to see that all three problems are symptoms of the same misalignment. Does holding this dual lens ever make you feel like a translator who can never fully live in either language? Or is that exactly where the power lives?

Jennifer: This is such a poignant question and I have to thank you for asking it. The power is in having as many lenses as possible to address the work at hand. I love Farnam Street’s series on mental models because it is about bringing truth and insights from all the disciplines together psychology, economics, physics, biology, statistics etc The more models you internalize, the more patterns you start to see, and the faster you can cut through noise.

However, when I’m a strategist I don’t get to build, when I’m a product manager I’m kept away from brand and marketing decisions and when I’m a producer I don’t get to make strategic brand or business decisions.

No matter my title I realize the job is to communicate in a way that can be heard. If I do that then I will be successful in translating. I’ve had to go over heads a couple of times at crucial junctures. It didn’t make me popular with the leaders at that time but I’m not going to let a project fail. They knew I was right and adjustments were made, but to me it isn’t about being right. I want the project to succeed. I want the client to win. I want the creative to shine.

Where I am now at R/GA they hire for low ego and they want the ideas from everyone. They want everyone to participate no matter their title. Most places say this but we really are all empowered. There is the understanding that serving the client is a team sport. No single one of us is going to be the hero. We have to work together and that’s how I most love working. It’s fulfilling to all be pulling in the same direction and feeling that momentum.

When the synthesis becomes something else

Kima: You named and shaped an experimental browser as both a philosophical concept (feeling calm and in control online) and a technical product (a forked browser engine with custom UX). That’s not just “brand meets product” that’s building a world where the distinction doesn’t exist anymore. When does the integration of brand and product thinking become so complete that you’re not executing someone else’s vision but authoring something fundamentally new? And if that’s the endgame of the dual lens, why do most organizations never let strategists get there?

Jennifer: I think this question is really about authorship and the reality that most strategists and product managers are not in roles where they’re able to truly author.

In the case of the experimental browser work you’re referencing, the starting point wasn’t a feature set or a market gap. It was a belief about the relationship people should have with technology, specifically, that software can reinforce calm, agency, and cognitive control rather than erode it. Once that belief is established as non-negotiable, everything else follows: naming, in-product sounds, logo, colors, defaults, interaction patterns, technical decisions, what the product explicitly refuses to optimize for. At that point, brand is baked into the product. They’re the same system. You can’t talk about one without invoking the other.

When meaning is structural, every downstream decision either strengthens or violates that logic. In my experience across both product organizations and creative agencies, that level of coherence is rare precisely because it requires trust in long arcs, comfort with ambiguity, and a willingness to let one person or a small group hold the frame before the proof exists.

The experimental browser I worked on had a very small core team. From the branding side, it was the Head of Firefox Product, the UX Desktop Director, and myself. We named it, chose the logo and icon, defined the in-product sounds, colors, and overall system, and I hired and managed the agencies involved and we had 1 user researcher and 10 engineers. Had all decisions been brought to committee, the coherence would have collapsed.

That’s why I’m drawn to working models where a clear, singular vision is allowed to exist, not because teams aren’t essential, but because authorship is. Larger teams are often needed to bring ideas to life, but without someone (or a small group), the visionary (or visionaries), holding the frame end-to-end, you will lose the magic.

Kima: When you look at the strategists and product people coming up now, the ones who are trying to become dangerously smart in the way you’ve become, what do you see them optimizing for that’s actually going to limit them? What are they getting wrong about what this dual lens really requires?

Jennifer: I don’t feel dangerously smart (though I appreciate the compliment!) but I do feel dangerously experienced. To that point, I think optimizing for a title is limiting. It is best if someone is excited about the experience they are going to have at a company or on a project.

I have pretty much run my career that way. I look for what problem I’m excited to solve and what project looks the most interesting.

I didn’t have much of a plan and while I don’t think that is a formula or something I would recommend to anyone who wants stability - please remember that there is little stability out there anymore to be had.

So I truly believe it is best to optimize for what excites you. Alternatively, you can optimize for what you are good at. Because being good at something is exciting in and of itself.

From the point of view of dual lens, I don’t think it is required to be focused on both product and brand. What I think is more important is to understand that if you are doing one you must consider the other. Respect the need for both.

If you are a product manager, make sure you pull in your marketing and brand team. You don’t have to be the one to do it - you only need to know it is as important as what you are doing. And vice versa - if you are the brand manager or product marketing manager, have respect for your product team. Know that they can pull in the brand in a way that will drive it home in the product. Understand they are up against many constraints and learn how to communicate with them in a language they can understand.

Synthesis question

Kima: If we’re honest, the dual lens isn’t about being “well-rounded” or “T-shaped.” It’s about being willing to live in the discomfort of never quite fitting into anyone’s org chart, never being fully legible to either side, and doing work that most people won’t understand until it’s already shipped (or in the case of the experimental browser, not shipped). So what makes someone actually want this? What makes it worth it to you?

Jennifer: I’ve never really fit cleanly into an org chart, and you’re right, it isn’t about being well-rounded which is an over simplification many make.

For a long time that was uncomfortable, even painful at times. Now it feels like a superpower, because this is exactly the skillset the moment is calling for.

As AI lowers the barrier to building products, people are also going to be building products, and by default, also building brands from scratch. Product creation and brand can’t be separated anymore, you have to bake meaning in from the start. You can outsource either, but you can’t pretend one doesn’t matter.

What makes the discomfort worth it is landing here, now, with a skillset that is genuinely distinctive. Most people come in from either the creative side or the product/business side. Having fluency in both is rare, and in my current role it’s not optional, you simply couldn’t do the work without it.

For a long time I couldn’t see where this path was headed, I would take roles because I was excited about them - not certain where they would lead. That uncertainty was the cost. But the path is more clear to me now in this market, and because of that I feel good about the tradeoffs I’ve made in the past that have brought me here.

Kima: Thank you, Jennifer. You've named something most of us feel but can't articulate: the loneliness of seeing multiple systems simultaneously, and the power that comes from refusing to choose between them. For those of us with mixtape careers, paths that look incoherent until suddenly they're not, watching you move between Mozilla and R/GA, between engineers and creatives, between brand philosophy and product architecture, it's permission. You didn't wait for a role that made sense. You made the work matter anyway. Thank you.