A product manager told me our design system was 'just a style guide' last week

We were in a planning meeting for a new feature, and I was explaining how our component library would cut dev time in half. He cut me off and said, 'That's nice, but it's just a style guide for colors and fonts, right?' It happened in our main conference room, the one with the broken projector. I had to spend the next ten minutes explaining how tokens, components, and documentation actually work together. Has anyone else had to fight this basic misunderstanding from a key stakeholder?

2 comments

2 Comments

faith_smith1mo ago

Watched a designer friend have to pull up their actual Figma library in a budget meeting once. Some finance guy kept calling it "the font book" and asking why updating a button cost real engineering hours. She had to walk through the entire design-to-code handoff process for a single input field.

blair_butler471mo ago

Look, maybe he has a point from his side. If the system only changes colors and fonts on the surface, calling it a style guide isn't totally wrong. Product managers care about shipping features, not design theory. They see the output, not the backend tokens. Spending ten minutes in a planning meeting to explain the basics might mean the value isn't clear to them yet. The real fight is showing how it gets features out the door faster, not proving it's complex.