Brand Designer

When Pagedeck had ten people, the only thing it owned was a logo file a freelancer had delivered right after the company started. Everything after that, people made for themselves. Grace put together the deck she sent investors, Ravi made the images that went into ads, and Sofia designed the cover of the proposal that went out to customers.

The problem only showed up when those three things sat side by side. Three documents from one company, and the blue was slightly different in each, the headline typeface was different in all three, and in one the logo had been stretched sideways to fit a box. To anyone seeing them for the first time, they looked like three separate companies.

Nobody had done anything wrong. Deciding how the company looks from the outside simply wasn't in anyone's job. The other roles on the design axis mostly own what happens inside the product screen. But a company reaches people's eyes in plenty of places that are not a screen: ad banners, job postings, conference booths, investor decks, business cards.

A brand designer is the seat created so that one person owns all of that outside surface.

A day usually splits three ways: making new things, checking that what was already decided is being followed, and packaging the rules so other people can make things without asking.

1. Making — a set of images for a new campaign, the banner at the top of the careers page, the wall graphic for a conference booth. The raw materials are usually already fixed: the logo, the color palette that defines which colors the company has agreed to use in products and documents, and the typography rules that say which typefaces go on headlines and body text, at what sizes.
2. Checking — reviewing what other teams made and catching where it drifted. A banner whose blue is a hand-picked approximation rather than the specified value, or a logo with less clear space than the rules allow, so the headline crowds up against the mark.
3. Packaging — writing the rules down so the same correction doesn't have to happen twice. Brand guidelines are the document that records how the logo, colors and typefaces should be used and how they must not be, closer to an internal spelling rulebook than to a style opinion.

The third one moves the workload more than the other two. Before Pagedeck shipped a deck template, requests to "make me a document" came in around twelve times a week. After a template with a cover and body layouts went out, that dropped to three or four; everyone else just filled content into it.

The inside of the product isn't entirely someone else's problem either. A design system is the product-side standard that bundles colors, text sizes and spacing into one set, and if the base color there drifts from the brand color, someone who clicked an ad lands on a product screen that feels like a different company. So when those values change, the brand designer looks at them too.

The biggest difference from the other design roles is that there is no single team on the other side. A product designer usually sits with one product team and moves on that team's schedule. A brand designer gets requests from several teams, each running on its own calendar.

1. Marketers — the most frequent counterpart. Campaign assets, ad banners, and the hero image of the page an ad clicks through come from here, tied to a media buy date and hard to push.
2. The CEO — brings fundraising decks and company overview material. The volume is low, but the dates appear suddenly and tend to be the most urgent.
3. Product designers — the counterpart for drawing a boundary. What happens inside the product screen is theirs, but the colors and typefaces used in there get checked against what the company uses outside.
4. Sales — asks for proposal covers, booth material, and overview documents sent to customers. Much of it sits next to another company's logo, which makes size and clear space a recurring argument.
5. Engineers — the counterpart who makes the work render on the website. Which logo file to export for which screen size, and which version to use on a dark background, gets settled here.

When several requests arrive at once, who decides the order is a standing problem. Pagedeck puts brand requests on the same marketing calendar as everything else and sorts the order once a week. If four land in one week, the one with the earliest date needed goes first.

"The blue in this banner is slightly off from our brand color. Which file did you pull it from?"

A color that isn't in the palette got used, so swap it for the specified value.

"Please don't put text over the logo. The clear space rule is on page 12 of the guidelines."

Pushing a request back on a written rule rather than on taste.

"This is a branding item, so file it as a marketing request instead of the product backlog."

Same kind of design request, different queue, so use the other intake.

The place this role shows up most clearly at Pagedeck is the run-up to a quarterly campaign. When Ravi asks for five sets of ad assets, Noa keeps working on product screens and the brand side takes the banners and the hero image of the landing page.

What happens after the campaign matters as much. Somebody decides whether the format made this time goes into the template library. Put that decision off and six months later there are thirty near-identical banners living as files that differ only by name.

The most common mistake is reading the role as "the person who makes the logo." The logo is the most symbolic piece of the work, and at an early company it genuinely is the first thing made, so the assumption is easy to arrive at. But the logo is the starting point, and most of the time afterward goes into deciding where it sits and at what size, then holding that line. Treat the job as finished once the logo exists and leave the seat empty, and a year later the company has seven different blues in circulation, which costs more to untangle than the original work did.

Reading it as pure taste, where nothing is right or wrong, is the other frequent one. Picking colors and typefaces looks from the outside like personal preference. In practice there are tests it has to pass: does the logo still read when shrunk down, do the colors stay distinguishable on a dark background, does the piece still look like ours mixed in with other companies' material. Without those tests a review turns into a contest over whose taste is better, and the decision drifts toward the most senior title in the room.