Design might tell itself that good ideas win because they are good, while it is quietly running on an entirely different assumption. Pretending otherwise is how the field keeps losing some of its best people.
In 2006, Douglas Bowman joined Google as its first visual designer. The company was then seven years old. Plenty of designers were already on staff, most of them with computer science or human-computer interaction degrees. Bowman built a visual design team from scratch and introduced visual design to Google as a discipline. Before quitting three years later, he wrote down exactly why he quit.
He talked about how one team at Google couldn’t agree on which of two blue colors to use for a link. Instead of making a designer-led decision, they tested 41 shades in between to see which color users clicked more and, thus, performed better. Bowman had also just spent time arguing about whether a border should be three, four, or five pixels in width, and had been asked to prove his case. “I can’t operate in an environment like that,” he wrote on his last day.
Champion Advertisement
Continue Reading…
But his actual diagnosis of Google’s culture went deeper than fatigue. Google had designers, he said, but “none of them were in high-up, respected leadership positions,” and “without a person at (or near) the helm who thoroughly understands the principles and elements of Design, a company eventually runs out of reasons for design decisions.” Thus, once the reasons run out, data fills that gap because it makes the one argument nobody in the room can pull rank on.
It’s imperative that this was a claim about power rather than about taste. Bowman was a pioneer who built the visual design team at Google, hired top talent, and launched work that he was proud of. But not having anyone senior enough for a design judgment to survive contact with an engineer who wanted a test is what led him to quit. He called Google an aircraft carrier and himself a dinghy trying to push it a few degrees north.
What Design Teaches Instead
Designers’ experience is that someone worth admiring might give a different account of how this works. They might say that good work speaks for itself and quality is visible, so if an idea is strong enough, people will recognize that. Taste and conviction should be enough as long as you’re willing to actually build something. Designers have heard this message all too often in their career.
If we look at a designer’s portfolio, we might find a paragraph of narration that cuts to six screen designs or a long-form, descriptive case study. What’s disappeared from the record is a full year of contested and committee-mauled work and meetings.
Design school does the same thing in miniature. Students pin their work up and tutors and classmates deliver a verdict on it. That verdict ends up standing in for a market that none of them has ever met. Magazine profiles compress nine months of organizational grinding into stories of one person who saw further—and an award often goes to a single name on a slide when forty colleagues and eleven months of meetings produced the work.
These are easy stories to believe because they assign worth to our own craft and promise that getting better is the way to matter more. Underneath sits a second lesson that hardly, if ever, appears in a syllabus, but sinks in anyway: that going after influence is faintly grubby, campaigning for your own idea is beneath the craft, and working out who decides and what worries them is somebody else’s job.
Champion Advertisement
Continue Reading…
What Ideas That Launched Had in Common
Slack’s situation was the opposite of Bowman’s. In July 2013, two weeks before the preview release, Stewart Butterfield sent his team a memo that later got published as “We Don’t Sell Saddles Here.” Most of the memo argued that Slack should be selling organizational transformation instead of group chat, but the part that matters here is the demand he made on craft. “We have to find all those petty irritations and quash them,” he wrote, and that every rough edge had to be polished “until this product is as smooth as lacquered mahogany.” Then he settled the question of standing outright by stating: “Ensuring that the pieces all come together is not someone else’s job. It is your job, no matter what your title is and no matter what role you play.”
The argument that Butterfield made about quality was no better than the argument that Bowman was making at Google. For Bowman, the difference was that it was the CEO making it, in writing, to the whole company, two weeks before launch. A designer at Slack arguing for a rough edge to be fixed had the backing of a founder’s memo, while Bowman arguing for a four-pixel border had a spreadsheet backing it.
Airbnb ran on the same principle earlier, and it was messier. In 2009, the company’s revenue had flatlined at $200 a week, and the three founders were sitting with Paul Graham at Y Combinator going through the New York listings when Joe Gebbia noticed that the photos were terrible, mostly camera-phone shots pulled off classifieds sites. Graham told them to fly to New York, rent a camera, and reshoot the lot. “There wasn’t any data to back this decision originally, they just went and did it.” Revenue doubled to $400 a week. The insight was Gebbia’s, the permission was Graham’s, and at that stage of the company, Graham was the only person whose permission would have counted.
Steve Jobs at Apple formalized the same thing. Paul Graham notes that Jobs ran an annual retreat for the hundred people he considered most important at Apple. “These were not the hundred people highest on the org chart.” Access got allocated by judgment rather than reporting lines. Jobs personally decided who got to carry an idea into the room.
An Idea Moves Along the Channels a Company Already Trusts
Jobs had happened to sit through a demonstration at Xerox’s research center in Palo Alto in 1979 and came away saying that the graphic user interface (GUI) they showed him had blinded him so completely that he barely registered the other two inventions they showed him that day. Xerox had shown him the Alto, a machine Xerox built back in 1973 that had a graphic user interface, a mouse, overlapping windows, Ethernet, and an editor that displayed a document that was formatted the way it would come out of a printer. Xerox then shipped its own version, the Star, in 1981, but it sold poorly. The executives back in Rochester read that result as proof the whole line of research had been a mistake. So the ideas walked out of the building and made other people rich—at Apple, then at Microsoft. Those researchers had been right for eight years, but being right had got them almost nothing.
Everett Rogers spent his career dealing with this same problem outside of technology. A professor of rural sociology at Ohio State, he pulled together more than 500 separate studies of how new ideas spread, then published his synthesis as Diffusion of Innovations in 1962. His argument was that an innovation travels through a social system, along the channels that the system already trusts, and that its merits are rarely what decide the matter. Rogers took from Katz and Lazarsfeld the idea that a message reaches a few respected people first and everyone else takes their cue from them, which is why he treated opinion leaders as the point where an idea actually gets evaluated.
When we look at all of these cases, the ideas that got through had someone to whom the room already listened behind it.
Why Influence Gets Built
Designers—or in fact, anyone at all—tend to look at politics in companies as a distraction from the real work. In fairness, it often is. But people beget politics, and every case that we described earlier came down to somebody higher up choosing to put their weight behind an idea. Therefore, when we dismiss politics as somebody else’s business, we are dismissing the thing that determines whether our work gets built at all.
Peter Merholz, who co-wrote Org Design for Design Orgs and advises executives about design, puts that tendency in terms UX designers ought to recognize. In some of his writings, he calls it ironic that the same people who insist on working outside in for customers turn around and work inside out the moment they want to do something themselves. Designers get caught up in their own mission and assume their job is to educate and persuade their way to influence. But designers get hired to sit with a stranger and work out what that person needs and what worries them. The stakeholders sitting around the table rarely get the attention we would give a stranger during a usability-test session.
Where a Design Team Reports Changes What It Can Do
For a designer with no title as currency, the move is translation. Merholz points to Hannah Jones, who spent sixteen years as Nike’s first Chief Sustainability Officer and later as the Founder and President of Valiant Labs, Nike’s business incubator. Jones found that sustainability was argued as sustainability went—nowhere until she put the same idea to the board as risk mitigation, to the CFO as a financial benefit, and to the CEO as a growth opportunity. Then the idea started to move. “Make everybody else the hero in the story” was one of her mantras. It shows that the case usually gets made in somebody else’s terms, which is a different job from sharpening an idea further on our own.
For a designer running a team, the job description itself changes shape. Kaaren Hanson, Chief Design Officer at Chase Bank, with more than eight hundred people under her, named four things she was there to do. These were to build a senior team, nurture executive relationships, establish UX metrics, and evolve how products get made. Achieving two of these four goals was about who she knows and how senior they were, while the third turns design into numbers that the business already tracks, which is what gives the first two some currency to trade in.
This lever is more about structural fluidity. The 2025 UX/Design Organizational Health Report found that where a design team reports changes how healthy that team is. Teams reporting through Engineering or Marketing came out consistently the least healthy, while teams reporting to Digital or straight to the CEO came out the healthiest. Merholz had long assumed the reporting line mattered less than things like company size or industry, but he says this finding changed his mind. Going back to the Bowman story, Google—an engineering company where no designer held a senior seat—was sitting in the worst configuration on that chart.
Merholz is blunt about what all three of these levers amounts to. At the end of that same piece, he asks, “Does this mean you’re playing politics?" then answers himself, “Yep. That’s the job.” A designer who already knows how to work out what a stranger needs is better equipped for that job than someone without that ability—that is, most of the people in the building.
The Loop Keeps Running
When an idea has a designer behind it—and maybe even a couple of colleagues—but none of them is a person the room listens to, it might still get built, but smaller, later, and not quite working the way it was meant to. However, the decision that led to an idea’s diminution never gets written down anywhere. People do not say out loud who is at fault either—although the atmosphere speaks in silence anyway, pointing at whoever’s name sits against the work in the org chart, which, when it comes to design, are the designers. Some of them accept this and stay, not knowing any workarounds for the problem, while others resign later. The company moves on and replaces these designers like nothing has happened, and the whole thing repeats in a loop with a new designer or another colleague taking the same hit again.
The designers who leave read the loss as a verdict on their own craft because that is what the field has taught them to do. So they go somewhere else hoping to sharpen their craft. Yet, more often than not, the next place is built the same way, with similar reporting lines and the same empty seat near the helm, so the loop picks up where they left off. Hopefully, the designers who leave can find somewhere else to work that is organized differently. That is what Bowman went looking for.
Anamol is a UX Specialist with an MSc in User Experience Engineering from Goldsmiths, University of London, and a Baymard Certified UX Professional. He has worked as a UX designer, product designer, researcher, and digital designer for companies such as Nourish Care, Buster + Punch, and Goldsmiths, leading UX and product design initiatives that have driven significant business impact, including an ecommerce campaign that generated more than £3 million in revenue in 2024. His research-driven approach combines empirical evidence, in-depth analysis, and user-centered design to optimize digital experiences. Beyond User Experience, he has collaborated with global clients, including brands with millions of followers, delivering creative and digital solutions that enhanced engagement and business growth. Read More
Subodh is a technology entrepreneur and software-quality professional with over a decade of experience in software testing, quality assurance, product delivery, and technology operations. He began his career as a Software QA Engineer and went on to co-found Alpas Technology, where he currently serves as Chief Operating Officer. In this role, he oversees the company’s overall operations, product delivery, resource allocation, financial management, and software-quality function. He holds a Bachelor’s degree in Computer Engineering and an MBA in Entrepreneurship from Westcliff University, combining a technical foundation with an entrepreneurial perspective. He works closely with multidisciplinary teams to turn product ideas into reliable, user-focused, impactful digital solutions. His professional interests include software quality, user experience, product delivery, technology operations, entrepreneurship, and building practical digital products that create meaningful impact. Read More
Aarshiya is a Senior Product Designer specializing in UX research, product design, accessibility, and design systems, with more than five years of experience designing user-centered digital products for complex business-to-business (B2B) and business-to-consumer (B2C) platforms. She holds a Master of Science in User Experience Engineering from Goldsmiths, University of London, and has led end-to-end design initiatives for organizations that include Grosvenor, Kemat Consulting, Kaprad Studio, and Infosys. Her research-driven approach combines user interviews, usability testing, and evidence-based design with meticulous visual craftsmanship to create intuitive, accessible experiences. A certified accessibility designer, she has successfully led Web Content Accessibility Guidelines (WCAG 2.1) compliance initiatives while building scalable design systems and collaborating closely with cross-functional teams to deliver high-impact digital products that balance user needs, technical feasibility, and business objectives. Read More