Bill Buxton is a Canadian computer scientist and designer who spent years as a Principal Researcher at Microsoft Research. He is best known for his work in human-computer interaction, specifically his advocacy for low-fidelity sketching in the design process and his "Long Nose of Innovation" theory, which maps how long it takes for new technologies to mature. This profile breaks down his practical approach to building hardware and software, focusing on historical context, device ecosystems, and the realities of human behavior.

Part 1: Sketching vs. Prototyping
- On the nature of sketching: "The fundamental thing about sketching is that it is about asking, not telling." — Source: [Sketching User Experiences]
- On cognitive gaps: "If you want to get the most out of a sketch, you need to leave big enough holes for the imagination to fit in." — Source: [Sketching User Experiences]
- On social artifacts: "Sketches are social things. They are lonely outside the company of other sketches... and they definitely are happiest when everyone in the studio working on the project has spent time with them." — Source: [Sketching User Experiences]
- On the defining difference: "Sketches are disposable, unfinished, and ask questions. Prototypes answer questions and suggest a concrete design." — Source: [Jon Udell Interviews]
- On early prototypes: High-fidelity prototypes suggest a concrete answer too early, creating inertia and resistance to changing the core concept. — Source: [MIX10 Keynote]
- On vocabulary: Sketching is not limited to drawing on paper; it is a mindset that applies to hardware, interactions, and systems. — Source: [Sketching User Experiences]
- On cost: Teams must keep the cost of making mistakes low so they can afford to make the necessary errors to find the right direction. — Source: [Microsoft Conversations]
- On ambiguity: A good sketch embraces ambiguity, allowing multiple viewers to project their own interpretations and solutions onto the work. — Source: [Sketching User Experiences]
- On iteration: The goal of early design is generating many alternatives rather than refining a single early concept. — Source: [ACM SIGCHI]
- On commitment: A prototype represents an investment and a commitment to a direction, whereas a sketch represents a temporary hypothesis. — Source: [Sketching User Experiences]
Part 2: Getting the Right Design
- On the ultimate goal: "Our job is not to answer questions, it's to ask the right questions... that get us to the right answer." — Source: [Sketching User Experiences]
- On problem setting: Problem setting (getting the right design) must precede problem solving (getting the design right). — Source: [Microsoft Research Podcast]
- On engineering focus: A perfectly engineered solution to the wrong problem is a total failure of design. — Source: [CanUX Keynote]
- On process sequence: Exploring alternatives guarantees a better outcome than taking the first plausible idea and polishing it. — Source: [Sketching User Experiences]
- On evaluating concepts: Do not judge a design strictly by how well the mechanics work, but by how well it addresses the human need it was built for. — Source: [Interaction 19]
- On failure: The failure to explore the design space adequately is the single biggest cause of failed products. — Source: [Sketching User Experiences]
- On the role of design: Design defines what a product should be at the beginning, rather than applying aesthetics at the end. — Source: [Microsoft Conversations]
- On design as literacy: We must move beyond the myth of the "designer as god" and engage directly with the literacy of the people using the system. — Source: [CHI 2008 Plenary]
- On asking questions: If a design artifact does not provoke a question from its audience, it is a specification, not a design tool. — Source: [Sketching User Experiences]
Part 3: The Long Nose of Innovation
- On overnight success: "Anything that comes out in the next ten years that is amazing has already been around for ten years." — Source: [The Long Nose of Innovation]
- On the illusion of invention: True innovation skips pure invention in favor of prospecting, mining, and refining an existing idea until it works at scale. — Source: [Microsoft Research Podcast]
- On historical timelines: It reliably takes 20 years for a technology to move from first clear articulation in a lab to a billion-dollar industry. — Source: [The Long Nose of Innovation]
- On true contribution: Those who can shorten the long nose of adoption by 10 percent make as great a contribution as the original inventor. — Source: [The Long Nose of Innovation]
- On the danger of newness: Fixating on the "next big thing" blinds companies to the mature, unexploited technologies already sitting in their labs. — Source: [BillBuxton.com Essays]
- On refining ideas: An idea may start with a spark, but the vast majority of economic value comes from its gradual augmentation over years. — Source: [The Long Nose of Innovation]
- On technological diffusion: Technological prowess matters much less in the spread of an innovation than understanding the social conditions required for adoption. — Source: [Interaction 19]
- On recognition: The newer an idea is, the more likely people are to dismiss it as "done before" without appreciating the massive effort required to bring it to wide practice. — Source: [The Long Nose of Innovation]
- On predictable futures: The only way to engineer the future tomorrow is to study the research labs of yesterday. — Source: [Sketching User Experiences]
- On surprising obviousness: A truly successful innovation feels like a breakthrough, but in hindsight, its success feels entirely obvious and inevitable. — Source: [Microsoft Research Podcast]
Part 4: The Ecology of Devices
- On device ecosystems: We are no longer designing isolated computers; we are designing a diverse ecology of devices that must communicate seamlessly. — Source: [CHI 2011 Keynote]
- On the Swiss Army Knife trap: Building one device that tries to do everything usually results in a device that does nothing particularly well. — Source: [CBC Radio Spark]
- On specialization: "Everything is best for something and worst for something else." — Source: [Microsoft Research Notes]
- On transitions: The magic of modern computing lies in the transitions and handoffs between devices, rather than the features of a single screen. — Source: [BillBuxton.com Essays]
- On complexity: A single simple device is easy to use, but an uncoordinated ecosystem of simple devices leads to overwhelming, cumulative complexity. — Source: [CanUX Keynote]
- On relationships: The next major leap in technology will be a change in the relationships between existing objects, rather than a single new product category. — Source: [Interaction 19]
- On appropriate form factors: A watch, a phone, and a wall screen should not run the same interface; their physical form dictates their interaction style. — Source: [Microsoft Conversations]
- On ambient interfaces: Technology should move into the background when not actively needed, functioning quietly as part of the environment. — Source: [CHI 2011 Keynote]
- On physical space: The physical location and posture of the user dictate interaction success as much as the pixels on the screen. — Source: [The Buxton Collection]
Part 5: History and Precedence
- On the lone inventor myth: Innovation is a cultural and evolutionary process, completely removed from the romantic idea of a solitary genius in a garage. — Source: [Microsoft Research Podcast]
- On institutional amnesia: The tech industry suffers from a profound lack of historical knowledge, causing teams to constantly reinvent the wheel. — Source: [The Long Nose of Innovation]
- On studying failure: Examining why a technology failed fifteen years ago provides the exact blueprint for how to make it succeed today. — Source: [The Buxton Collection]
- On standing on shoulders: All modern innovations remain inextricably bound to the "tire tracks" of decades of government and university research. — Source: [Microsoft Research Notes]
- On finding fresh perspectives: "The real voyage of discovery is not in seeking new landscapes, but in having new eyes." — Source: [BillBuxton.com Essays]
- On the value of archives: Physical collections of old devices are not museums of obsolescence; they are libraries of interaction patterns waiting for the right moment. — Source: [The Buxton Collection]
- On bad ideas: "In terms of stifling innovation, good ideas are far more dangerous than bad ones" because they create inertia that blocks better alternatives. — Source: [Sketching User Experiences]
- On technological evolution: The multi-touch screen wasn't invented for the smartphone; it evolved slowly through decades of niche applications and lab experiments. — Source: [MIX10 Keynote]
- On continuous refinement: There is no final version of a technology, only the current state of a continuous historical refinement process. — Source: [The Long Nose of Innovation]
- On recognizing patterns: Innovation becomes a repeatable profession for those who study the history of previous technological shifts. — Source: [Microsoft Research Podcast]
Part 6: Experience Over Artifacts
- On what we actually sell: "Ultimately, we are deluding ourselves if we think that the products that we design are the 'things' that we sell, rather than the individual, social and cultural experience that they engender." — Source: [Sketching User Experiences]
- On the journey: A product’s value comes from the experience of how the user gets to their goal, rather than the final destination itself. — Source: [Sketching User Experiences]
- On human-centered design limits: Traditional human-centered design fails when it ignores the broader social and cultural reality surrounding the tool. — Source: [CanUX Keynote]
- On physical interaction: Interacting with a computer is a bodily act; ignoring physical ergonomics destroys the digital experience. — Source: [The Buxton Collection]
- On user adaptation: Good experiences adapt to the user; bad experiences force the user to adapt to the limitations of the machine. — Source: [Interaction 19]
- On natural user interfaces (NUI): The goal of an interface is to feel natural to human behavior, rather than perfectly mimicking physical world metaphors. — Source: [MIX10 Keynote]
- On community: Instead of isolated utility, designers must build digital spaces that foster actual culture and connection. — Source: [Interaction 19]
- On attention: A well-designed experience respects the user's attention and only demands cognitive load when absolutely necessary. — Source: [CHI 2008 Plenary]
- On evaluating success: You cannot measure the success of an experience in a lab; it must be observed in the messy reality of the user's daily life. — Source: [Sketching User Experiences]
Part 7: Ethics and Human Context
- On Kranzberg's First Law: "Technology is neither good nor bad; nor is it neutral." — Source: [CHI 2008 Plenary]
- On moral responsibility: Every design choice, down to the placement of a button, is an ethical decision with social consequences. — Source: [Microsoft Research Podcast]
- On unintended consequences: Designers must anticipate how their products will be misused or how they might degrade baseline human interaction. — Source: [CanUX Keynote]
- On digital culture: We are responsible for the culture our tools create, whether that becomes a culture of surveillance or a culture of connection. — Source: [Interaction 19]
- On inclusion: If you design for the average, you design for no one. — Source: [Microsoft Conversations]
- On the impact of simple things: Even a paperclip changes how an office functions; software has exponentially more power to reshape human behavior. — Source: [CHI 2008 Plenary]
- On the limits of technology: Software cannot solve fundamental human relationship problems; it can only amplify existing dynamics. — Source: [BillBuxton.com Essays]
- On privacy: Designing an ecology of ubiquitous devices requires a foundational respect for human privacy and agency. — Source: [CHI 2011 Keynote]
- On human values: Successful innovators spend as much time understanding human values and beliefs as they do understanding software engineering. — Source: [The Long Nose of Innovation]
Part 8: Leadership and Organizational Culture
- On corporate signals: "If you have the best designers in the world working for you and you don't have an executive who is at the power of the CTO directly reporting to the president... you are telegraphing to your entire organization that you don't take this seriously." — Source: [Sketching User Experiences]
- On empowering design: A design team without executive backing will never be allowed to succeed, rendering their work useless. — Source: [Sketching User Experiences]
- On protecting the status quo: Few managers realize that their operational training, designed to protect the existing business, actively works against the forces needed for innovation. — Source: [The Long Nose of Innovation]
- On cross-disciplinary teams: Innovation happens at the edges between disciplines; isolating engineers from designers guarantees a mediocre product. — Source: [Microsoft Research Podcast]
- On investment: Companies drastically underinvest in the problem-setting phase because it doesn't produce immediate, measurable code. — Source: [BillBuxton.com Essays]
- On leadership's role: Executive leadership must clear the path for the long nose of innovation, protecting fragile ideas from premature optimization. — Source: [The Long Nose of Innovation]
- On the definition of risk: The biggest risk an organization takes is assuming that maintaining their current product line is safer than exploring its replacement. — Source: [MIX10 Keynote]
- On corporate memory: Organizations must intentionally build corporate memory of past failures and successes, or they will pay to learn the exact same lessons twice. — Source: [The Buxton Collection]
- On evaluating designers: A great designer does not just draw beautiful interfaces; they facilitate the organizational conversation necessary to find the right product. — Source: [Sketching User Experiences]