“Culture isn't the words in an all-hands, it's what changes in the room after the meeting. At Thinkific I watched design culture take hold only when designers started bringing customer interviews into sprint planning and engineers saw those insights change what we built. Your head of design needs one visible win where the team feels the decision land differently because customer understanding showed up early.”

“Culture shows up in what gets shipped, not what gets said. At Family we made simplicity, fluidity, and delight real by letting it slow us down, because the alternative was another wallet no one remembered. Your head of design needs to change one thing engineers can feel: who gets veto power on polish, what the spec leaves out, and whether a pixel-perfect build is celebrated or treated as scope creep.”

“The eye rolls mean she hasn't changed how decisions get made yet. At Anthropic I spend a lot of my time pairing with engineers on the actual code, pointing them at our design system, and explaining why so they don't need me next time. Culture starts when the rest of the team can do better work without the designer in the room.”

“I’ve seen design culture fail when it starts as a department announcement instead of a change in how decisions get made. At Facebook and Dropbox, the designers who earned trust didn’t run more critique meetings; they showed up with prototypes that changed what we built and made the product visibly better.”

“Design culture isn't what gets announced in all-hands. It's what changes in the next sprint: a designer in the room when specs get written, a critique ritual engineers actually attend, one shipped thing that proves the user got closer to their goal.”

“Culture shows up in the rituals people can actually see. At Syndicate I built a design ops pillar because process, tools, and standards were the only way to make design scale beyond my own hands.”

“Culture starts when design changes how decisions get made, not how they're announced. At monday.com we ran a one-day Experience Hackathon where product, engineering, and design fixed 747 UX issues together, because the engineers needed to feel the friction disappear, not hear about it.”

“I have watched design leaders announce design culture while the engineers still write specs without a single wireframe, and the gap is always the same: culture shows up in rituals, not speeches. At Gameskraft we pushed design thinking into actual sprint ceremonies and cross-functional problem solving, because a head of design without a changed process is just a louder title.”

“At Philips, I learned culture changes when design shows up in the decisions engineers already make, not in a separate sermon. Your head of design needs to embed one designer into the next sprint, ship one thing that proves her language matters, and let the eye-rolling stop on its own.”