Commonwealth Bank of Australia was interested in helping customers and businesses build close connections. They believed the way to do this would be by creating richer interactions around different forms of payment. The bank approached IDEO to explore these opportunities, and the result is a new retail business platform—Pi—and a portable payment device—Albert.

Pi brings a new level of flexibility, functionality, and customization to the face-to-face interaction between a cashier and a customer, improving everything from the process of splitting the bill in a restaurant to helping a guest find more personalized experiences at a hotel.

Insights

In the team’s research in Australia, the UK, and Germany, they found a few key insights that informed the design. First, they saw that an ideal platform should support the full spectrum of human behaviors around payment. Second, platforms can add value by improving the relationships among banks, merchants, and customers. And third, the payment experience should be customized to fit a specific setting, working one way in a luxury boutique and another in a gas station.

IDEO, CBA, and Wincor Nixdorf worked together closely to steward the design of Pi And Albert through product development and implementation, and to gather feedback from merchants during rapid, iterative cycles.

Results

The platform is flexible enough to benefit organizations of all sizes: Larger merchants can incorporate Pi as part of their existing network, while smaller merchants can grow their business using powerful business tools. And customers of all kinds can easily access a variety of payment methods and helpful applications.

Albert offers a large touchscreen that’s intuitive to use, the safety of virtually encrypted PIN entry, and a variety of ways to access data connections. A large battery provides power when retailers are on the go, and a modular housing means that Albert can be used in all kinds of situations. The device is built to handle current card payment methods but can also adapt to how cards might be accepted in the future, and even eliminates the need to swivel a screen from cashier to customer during the payment process.

Forty million Americans became newly eligible for health coverage when the Patient Protection and Affordable Care Act (ACA) was fully implemented in 2014. Some enrolled in health insurance for the first time, while others were able to get better access to affordable health coverage.

In preparation for the millions of applications, states were required to develop ways for people to sign up for health insurance online for plans that were operated by state and federal governments under the ACA. To help public and private agencies to meet the requirements, a coalition of nine national and state-based foundations, led by the California Health Care Foundation (CHCF) developed a digital enrollment prototype, and hired IDEO to lead the consumer research and design effort.

After a yearlong collaborative process, the resulting 300-page design manual and design reference prototype illustrates a customizable approach to public and private health insurance enrollment.

The flexible set of design standards developed for Enroll UX 2014 aims to make online health insurance enrollment simple, intuitive, and easy to navigate at scale.

To encourage PhD candidates to think differently about how they tackle tough science problems, the University of California, San Francisco (UCSF) and IDEO embarked on a fruitful collaboration.

Three PhD candidates were tasked with the following challenge: Cultivate new audiences and uses for a microscope. Drawing inspiration from cell phone microscope CellScope, the trio arrived at a prototype that was less reliant on technology and easily disassembled and reassembled. How? By using the most basic building blocks: Legos.

Made of custom 3-D-printed parts and standard toy building blocks, the LegoScope, which functions as a microscope, can easily snap pieces in and out to hold different components. Both the device and the team-based process are now being used in various other campus projects to change how researchers think about conducting and advancing scientific research.

“The best work in the future is going to be done by teams of people with very different expertise, who know different things and think about things in different ways, who come together to focus on one big problem,” said Keith Yamamoto, vice chancellor of research at UCSF, who led the initiative.

Arye Barnehama and Laura Michelle Berman wanted to take their invention—a headband that measures brain wave activity, focus, and concentration—to the next level. As a part of IDEO’s startup-in-residence program, Barnehama and Berman collaborated with IDEO on the product’s rebranding, hoping to refine and emphasize the product’s promise: When people improve their focus, they feel more mindful, confident, and productive.

With IDEO’s help, the company changed its name from Axio to Melon, delineated their brand, refined its product, developed its user experience, and prepared a Kickstarter campaign that garnered considerable press coverage. The new name, Melon, reflected the friendly, scalable character of the company. The name also suggested the intent of the product—using neuroscience data to inform a personal activity.

To distinguish Melon as a standout in the crowded quantified-self category, IDEO designers made the logo a faceted orb that references the gear-shifting mind, with “Melon” written in a distinctive font born from that same logo. The team went with fruit colors—cantaloupe, honeydew, watermelon—to evoke the sweet, refreshing experience the Melon headband promises.

Together, the Melon and IDEO teams also developed an app that shows increases in concentration after performing certain tasks and features a game in which you “fold” origami through mental focus to hone concentration.

Melon’s new brand strategy and UI set it apart from your typical fitness tracker, engaging the user in an elegant, joyful, and customized experience with every interaction.

Melon: a headband and mobile app to help you measure focus.

The process culminated with the creation of Edison, a dynamic, interactive lighting installation for the hotel’s entrance. It’s a permanent architectural element that physically represents the networking and trafficking of data that’s happening all around us, especially in Silicon Valley—the hidden stuff that makes this place what it is.

Edison is a moving sculpture controlled by open-source code in which 100 light bulbs continually change position and brightness to visualize different data flows. The idea started half-jokingly: we were kidding around about the idea of attaching a light bulb to a system of pulleys so it would follow you through the lobby and alight above your head, glowing like a bright idea—the Epiphany, get it? After the cheesiness of that idea subsided, it led to a more serious exploration of the possibilities of the light bulb and ways to modernize the old, inefficient technology with hyper-efficient LEDs. The re-engineered bulbs would represent the idea of Silicon Valley standing on the shoulders of past inventors, and would also simply be beautiful to look at. From there, we mapped out how to make the bulbs live, move, and respond to the space.

Once we had all agreed on the concept, we launched into an entirely atypical design and engineering process, which I would loosely describe as, “OK… go!” We needed to make certain elements: a bulb that hung on a wire, a spool that rotated to move the bulb up and down, a motor to power the spool. But the design specifications of each of those elements were interconnected: for example, the weight of the bulb would dictate how powerful the motor would have to be, the motor would dictate the spool design, the spool design would dictate the motor controller needed to achieve the motion, and the motor controller would dictate the power supply we would need. But the design of the light bulb, and likewise every other part, was pretty nebulous at the beginning.

‍

So we separated out what we did know: we’d have to transfer power from the spool to the wire, which is constantly rotating, in order to illuminate the bulb. We could begin to solve that problem (slideshow above), but we had to design the solution to be adaptable to integrate with a constantly evolving spool design. Likewise, we specified capabilities for the spool (slideshow below), knowing that whatever we created would have to be able to adapt to different motors and different bulb designs, depending on what kind of bulb we ended up using and how fast we wanted it to move.

The same went for the software and electrical elements. We didn’t know what exact motor controller we were going to use, but we knew it was going to have to process position and velocity commands and acceleration rates (slideshow below). From these basic starting points, the entire team began working in parallel, keeping each element as modular as possible so elements and features could be switched out as needed while still being able to integrate with one another.

This kind of parallel process is not all that unusual with software development, which is why we have version control software like GitHub, which lets you continually push the most recent iteration to a central place so everyone stays updated. Unfortunately, there is no equivalent system for a process that spans electrical, mechanical, and software engineering, three totally unique domains, each with its own tools and protocols. So our interface was literally face-to-face: “I think this thing I made will work; will it work with the thing you made?” We would make sure whatever we were making would integrate with the current state of what everyone else was making, and then we’d all go off and figure out a few more things. Every time one piece of the puzzle was locked into place, other elements became more defined.

Central to the aesthetic and effect of Edison is the bulb, which was both a technical and visual challenge. We wanted to give a nod to the original Edison bulbs but use modern LED technology. We tried—and scrapped—countless prototypes made by repurposing off-the-shelf components (bulbs rummaged from Marine supply stores, bulbs imported from Europe and Australia, even a ready-made glass shell in which we placed our own custom-designed PCB, which used a clear solder mask to create the warm copper color of the original Edison filament bulb). Fortunately, we were introduced to EfficientNow, a local LED startup that worked with us to co-design a variant of their AC bulb that operates on DC power, which is a less expensive and more efficient choice for programmatically controlled dimming. As a finishing touch, we dressed the bulb assembly in a machined aluminum housing that reflects the other lights around it and helps create the warmth and effect we wanted.

Edison’s defining feature is its ability to dynamically respond, meaning the movements and the animations do not need to be preset but can be generated on the fly.

This lets people engage with the installation on different levels. You can understand and appreciate that it moves in response to data, or you can simply enjoy it on a purely visual level, without knowing anything else about it. Eventually you’ll even be able to direct its motion by typing in a few lines of code. We designed Edison to be able to respond to you and change the tone of the room, to make the space feel alive. I’m hesitant to use the word “magical” because it sounds cliche, but it describes a really meaningful experience of seeing something captivating and knowing that even though it looks effortless, there must be a world of complexity behind it, and yet the captivation halts your brain from diving into the “how” of it. That’s the experience I hope we achieved with Edison. You don’t really want to pick apart how it’s done; you just want to experience it.

Read more about Project Edison here.

It’s easy to rely on cliche and buzzwords when describing Silicon Valley, but expressing an authentic sense of place is a much more nuanced task. IDEO began working with Joie de Vivre hotels on their new Silicon Valley location before the building was even constructed, figuring out how to communicate the innovation and idealism of the valley through the building’s architecture

The Ha-Ori shelter was inspired by the folded leaves of the Hornbeam tree, which are lightweight and strong. People kept telling me that it was perfect for Burning Man, in both look and function. But what they didn’t know was that I hadn’t figured out how to add a good ventilation system for hot climates, so the shelter would actually have been way too hot for the desert. I vowed that I would only go to Burning Man if I brought a new iteration of the shelter with me, specifically designed for the desert weather. It took me a few years, but eventually I got together with a few other IDEO designers and we built a cool, shady Burning Man yurt. We’ve since brought the yurt to three “burns” and it still stands like a rock and is fully functional.

The idea for Blumen Lumen came up during one of those trips to the Black Rock desert. For most of the year, the Burning Man site is lifeless. The soil is dry and alkaline, so nothing grows there, and in the arid summer season, no animals ever cross it. It occurred to us that bringing flowers out there would bring a little bit of life, beauty, and love to the desert, which is a big part of what people are looking for at Burning Man. And we could use the same lightweight, folded construction that we had proven to be efficient and durable with the yurt.

The idea is for the installation to appear like a mirage in the barren, hostile desert. Seeing the flowers on the horizon, you’ll have little idea of their scale, but as you get closer, you’ll realize that it’s a true oasis: a gigantic garden of flowers up to 20 feet tall.

And then you’ll see that the flowers are discovering you as well: The blossoms open and close when they sense that people are nearby, and Arduino-controlled LED strips hidden inside the flower buds change color and intensity in response to movement and sound. The flowers contain infrared and ultrasonic sensors that detect a person’s approach, and a central computer parses inputs from the sensors and wirelessly controls and coordinates the individual blooms.

The opening and closing of the flowers is not only a beautiful motion, it is also an essential safety measure so the flowers can withstand the high winds in the desert, which can reach more than 60 miles an hour. Making the flower strong enough has been one of the biggest engineering challenges of the project.

The flower buds are made from two sheets of 5-by-10-foot corrugated polypropylene, which is very strong for its weight. We rout out lines on both sides of the sheet to create fold guides that determine where and in which direction the sheet should fold. (We learned when building the yurt that this process is very time-intensive when done by hand, so this time we outsourced it.) The sheets are then folded and welded together on both sides.

For the opening and closing mechanism, we built a telescoping “stamen” out of PVC pipe and connected it to 12 aluminum struts, which are then attached to the origami structure of the petals. The mechanism works like an upside-down parasol, which is lovely, but it means that we are fighting gravity, so we had to create a lot of force in order to close the flower. We experimented with pneumatic pistons, but bringing compressed air to the desert seemed impractical, and we felt we wouldn’t achieve an elegant enough motion. We’ve since gone through three different iterations of actuators, and we ended up with a 150lb, 18-inch linear actuator with a worm drive. It’s a lot slower than other actuators we tried, but it’s also cheaper, and it provides a lot of force in a small package. Best of all, it cannot be back-driven, which means we don’t need any electricity to keep the flowers shut.

The stem is made from a 4-inch PVC pipe, which slides over a 10-foot-long steel pipe that is screwed into a base in the ground. The base is also made of steel and is dug three feet into the earth, with four 4-foot outriggers that reach out horizontally and are also buried underground. We wanted the stem to have a graceful, natural curve, but we found out that bending 4” PVC pipes is not easy. We ended up using a weed burner to soften the PVC and then bending it over a curved wooden template. To make sure the tube doesn’t collapse, we capped it on both sides and slightly pressurized it.

The diverse challenges of this project required a whole team of industrial and interaction designers as well as mechanical and digital engineers, all passionate (crazy?) enough to spend many nights and nearly every weekend for months making this surreal flower garden a reality. As you might have guessed, every person on the team either works at IDEO now or has in the past. Where else would you find such talented wackos?

You’ll be able to check out Blumen Lumen even if you don’t make it out to Burning Man—we received an initial grant of $6,000 from the Black Rock Art Foundation to show the piece in public spaces around San Francisco. The grant facilitated the exploration and prototyping phase, but to fulfill our complete vision of the project, we are now trying to raise $10,000 on Kickstarter to build the rest of the flowers and buy four solar panels, batteries, and a small generator. Chip in, and come see us in the desert!

The core team for Blumen Lumen includes Beau Trincia, Jesse Silver, Jimmy Chion, Remy Pieron, Nivi Ramesh, and Joerg Student; we had big contributions from Chris Glaister, Steve Moore, and Marco Triverio.

When I moved to the Bay Area to join IDEO, I had never even heard of Burning Man. But once I got here, it came up almost every time I showed someone my Ha-Ori shelter, a collapsible origami structure I designed and built while studying at the Royal College of Art in London.

Throughout all those years, from the machine shop to the digital shop, regardless of the technology we’re using or the problem we’re trying to solve, what has really gotten things done is ingenuity and creative thinking—especially in the face of dire cost and time constraints. A little bit of luck never hurts either.

So without further ado, here are my four favorite workarounds of my last decade and a half at IDEO.

2001: Using an Oscilloscope to save the sunroof

The challenge: The sunroof in your car is an invitation to luxury—catch some rays, feel the wind in your hair. The problem is, when driving at certain speeds with the sunroof open, a distinct and unpleasant booming noise can occur, making the experience rather less glamorous. The sound, a quick, repetitive thumping, is called “buffeting.”

Carmakers couldn’t figure out what to do about it. A luxury automobile company hired IDEO to find a way to make it stop.

IDEO’s workaround: My colleague Thomas Enders and I borrowed a brand new Mercedes-Benz and went for a ride! We brought along an oscilloscope (or “O-scope”) to measure the frequency and intensity of the sound waves of the buffeting effect at various speeds. With Thomas at the wheel, I held the O-scope, connected to a barometric sensor. This way, we were able to measure what was happening every time the buffeting started up.

What we discovered was that closing or opening the sunroof a small amount would change the dynamic of the air space in the car, and the buffeting noise would stop. So we designed a circuit that could detect buffeting and automatically adjust the opening of the sunroof to get rid of the annoying noise. Cruise on, in unimpeded luxury!

2002: Turntable-testing stylus materials

The challenge: Handspring, a company that produced hand-held PDAs (remember those?), looked to IDEO to find the best, most durable material to use for their stylus pens. We narrowed it down to a few polymers of various densities, but we had to figure out how to effectively test the materials for wear and friction over time.

IDEO’s workaround: We bought an $8 record player at the local Salvation Army, and replaced the needle with the various materials we were testing. Then we started it up and used a tachometer to track revolutions and measure distance and speed. Now we can brag about our DJ skills.

2012: Making the functional fashionable with paracord

The challenge: We worked with Vodafone and fashion designer Richard Nicoll to create a purse that could charge a mobile phone, while also being stylish enough to work the catwalk at the London Fashion Show. Part of the design was a small charm that hung outside the purse and flashed LED lights to signal incoming calls and text messages. We needed to find a coating for the charm that would protect the LEDs without being a fashion faux pas.

IDEO’s workaround: While we were brainstorming materials, I looked down at the bracelet I was wearing. It was made of paracord, commonly used for the strings of parachutes. Paracord is extremely durable, and it’s sold in a plethora of colors and patterns. We ordered a few strands online and found that we could remove the sheathing from the outside of the cord. We dressed the charm’s electrical cord with the sheathing from paracord, and voilà ! It gave the high-tech handbag a clean look and feel that was fit for the catwalk.

2013: Cooking circuit boards in a toaster oven

The challenge: Today’s electronics can be minuscule, and that means soldering up a printed circuit board (PCB) by hand can take forever. People who build a large number of PCBs use reflow soldering technology, but the necessary equipment is extremely expensive.

IDEO’s workaround: We decided that, given the type of rework electronics we do, it would be a good idea to tap into the mindset of the DIY community. Taking a page from their book, we bought a standard toaster oven. We fired it up and tested different temperature profiles and various types of solder paste, and soon came up with a working reflow soldering system.

Illustrations by Ina Xi

In my 15 years at IDEO, I’ve had a hand in roughly 130 projects. Some of the technologies I’ve worked on have become obsolete, like component research that required dozens of part catalogs (now, we just use the Internet). Many, though, have become the foundation for newer technologies, like discrete components, which were developed into MEMS sensors. And some, like the first Olympic torch to use LEDs rather than a flame, have been the very first of their kind.

IDEO New York developer Francis Tseng is—in his spare time—searching for a solution to the problem by exploring its root: the relationship between content and code. Tseng received a grant from the Knight Foundation to develop Argos*, an online news aggregation app that intelligently collects, summarizes and provides contextual information for news stories. Having recently finished version 0.1.0, which he calls the first “complete-ish” release of Argos, Tseng spoke with veteran journalist and documentary filmmaker Jason Cohn about the role technology can play in our consumption—and comprehension—of the news.

How would you describe to my mom, who just got her first smartphone, how Argos works and why it’s useful?

I’d say that it collects all of the important news and tells you exactly what you need to know about it. Instead of tracking separate publications, it pulls in new articles from a variety of different sources (right now, just a few major publications) and condenses everything into a set of bullet points. Argos uses a technique called “hierarchical agglomerative clustering” (HAC) to organize news stories. HAC takes each individual article and compares it to every other article, and comes up with a number representing how similar they are, on a scale of 0-1. If the similarity is above some threshold—say, greater than 0.7—the articles are considered to be talking about the same event, and they are grouped together into “event clusters.” The same HAC clustering technique is then applied to the event clusters to organize events into “story clusters.”

A sentence ranking algorithm generates a summary of each event cluster by analyzing the text of every article in the cluster and assigning an “informativeness” value to each sentence. It then takes the top five highest-ranked sentences and forms a summary. Right now I have a very simple version implemented, but the long-run focus will be on improving these core algorithms that do the heavy lifting.

Are journalists necessary anymore? Have I been replaced by an algorithm?

I personally don’t think that journalists will be replaced, at least not for a long time. Someone still needs to go out and do the research and the original reporting to get the information that the algorithm uses, which seems like the hardest and most valuable part of journalism.

It seems like some new tech applications derive from the recognition of a new technical capacity, which you then look for novel ways to use. In other cases, it begins with the recognition of a need, and you look for extant technologies that provide a possible solution. Which way did you approach Argos?

Both. I’ve always had a fascination with artificial intelligence, and that fascination has probably made me more sensitive to problem areas where AI approaches could be applicable. Personally, I find information overload, especially when it comes to keeping up with the news, really anxiety inducing and overwhelming, and I think because I was already familiar with some of these text processing techniques, it made sense to try applying them to this particular problem.

I’m glad you brought up information anxiety and overload. I think it’s a huge barrier to understanding the news today. There is so much information and analysis, but I don’t trust any of it, and I don’t know how to begin to get to the bottom of what’s really happening. Do you think Argos, or technology in general, can be an aid in this problem?

That's a particularly good example of the fact that there are different kinds of information overload. There’s one that is just about having too much information, but there’s another that is about figuring out which information you can trust. In general I would say technology has the potential to salve these kinds of anxieties, but it can just as easily do the opposite. More than anything, I hope Argos reduces the problem rather than adds to it, but one of the big failings I’ve felt with this first version is that it doesn’t accomplish that; it ends up generating more noise. Based on the feedback I’ve gotten, I'm looking at new designs and reevaluating techniques in order to rectify that.

What did you learn through building the first version that will influence the next one?

When I originally conceived of Argos, I was (and probably still am) naive about the extent of the issues that plague digital journalism. The more I looked into it, the more problems came up. Initially, the idea was about reducing information overload, mostly by supplying missing context to stories. But after completing this first version, I think that reducing overload and providing context might be really big and different issues. So right now I’m trying to determine how—and if—they can be solved simultaneously.

You mean because providing more context increases—by a lot—the amount of information a news consumer requires?

Exactly. The other main goal was increasing the understanding one got out of reading the news, which is what context is supposed to help with. But that’s kind of useless if all that information ends up driving people away from reading the news in the first place.

What changes are you planning for the next version of Argos?

In the first version the design was focused more on providing an experience similar to a traditional news publication or news reader. The app was organized around different feeds, or streams, presented as full-screen images with the title and summary of each event.

One issue was that the design wasn’t distinct from other news readers—you can’t really tell from looking at it that it’s offering anything different from a traditional RSS reader or news application. And it’s really hard to expect that every news story will come with a nice big image. Also, though, I think that in approaching the app as a traditional news publication, I missed the point of what I was trying to accomplish. The feedback I've gotten has helped me understand that Argos can have a more useful and unique place in being kind of a “daily scan” of the day's news events. So the new designs are more akin to brief updates about events around the world, to provide people with an entry or starting point for reading more and getting involved in discussions.

And you give them avenues for digging deeper into contexts and definitions?

Yes. The original source material is there to read, and context is optionally provided. You can choose to read more about the event itself, or about the people, places, organizations, etc. that are involved.

What about the issue of bias? As journalists, we’ve always had to be wary of our sources. And as consumers of news, it’s always been a good idea to assume that someone with an agenda is feeding reporters their information. How does Argos handle biases and opinions that are embedded in a story?

The issue of bias in journalism is one of those big problems that cropped up when I looked more closely at what I wanted Argos to do. It seems like a perennial issue. One potential solution is that, if you sample a large enough set of publications, bias might “average out,” so that any summary that is formed from their aggregate has less bias than any individual article. I don’t know if that works in practice though. My cop-out answer would be that Argos isn’t really trying to solve the problem of bias, but personally I hope that one day it can. Looking at the history and associations of the author who wrote the piece could actually be a very good technique. In the new version of Argos, I want to incorporate more community dialogue around the events and stories. In my experience, a lot of these issues about bias—being as complex and nuanced as they are—are best hashed out by individuals discussing them.

I think I have to disagree with you on that! My feeling about web comments on news stories is that they rarely shed much light relative to heat.

It is very difficult to pull off correctly. A lot of comments devolve into knee-jerk shouting matches. Occasionally, though, I’ve found something really insightful. On Reddit, sometimes experts will come in and succinctly explain things, and every once in a while you see a very levelheaded discussion about a story. I think the potential is there, but it’s hard to get it right.

One thing I’ve been focusing on is that I’m trying to get my hands mostly on reporting that’s coming from the field. The rest is just analysis, which, in my opinion, is more susceptible to ideological influence.

Yes! I have been thinking a lot about how to incorporate grassroots and community reporting. I’m dissatisfied with Argos’s current approach of relying on major publications, but it’s just easier at this stage.

Do you need to have content licensing relationships with news organizations to harvest the data or can you just… borrow it?

It’s possible this usage of the content falls under the terms of “fair use.” All the original articles are cited, and I’m hoping that these high-level summaries can interest people in reading the original posts. Since things are still quite experimental, I’m not worrying about the potential legal consequences now, but at some point I will want to talk to the publishers.

It seems to me that one really useful type of story for Argos is something like the lost Malaysian airliner. There was a big burst of real news when the plane disappeared, and then there was an endless cycle of conjecture and empty reportage with very little actual “news.” If you were following that story on Argos, would you avoid being updated every five minutes to discover that they still haven’t found the missing plane?

Yes, if the clustering algorithm works well enough, it should be able to recognize that these articles are talking about exactly the same thing as the ones from last week, so it’s not a new event.

It would be nice if cable news worked like that.

Maybe with Argos it will!

*Argos is a personal project of Francis Tseng's and is not affiliated with IDEO.

‍

Digital journalism has evolved to a point of paradox: we now have access to such an overwhelming amount of news that it’s actually become more difficult to understand current events.

I help organizations cut through complexity by shaping how they show up, through brand strategy, identity, and storytelling.

Working at the intersection of brand and business, I bring an editorial eye and a bias toward making—turning ideas into tangible experiences that people can understand, trust, and believe in.

My work spans government, healthcare, financial services, media, and consumer goods, from launching Gen Z-focused ventures to building innovation labs and reimagining legacy brands. I relish moments of ambiguity and enjoy translating across teams, perspectives, and priorities to move ideas forward.

I started my career in editorial and digital design, shaping cross-platform experiences and identity systems in publishing and agency environments. That foundation still shapes how I work today: I’m detail-oriented, collaborative, and overreliant on the Oxford comma. I hold a BFA in Visual Communication from the School of the Art Institute of Chicago.

For 25 years, I've asked the same question: Who does this design exclude—and what are we going to do about it?

My work spans human-centered strategy, inclusive design, and qualitative research, with clients ranging from Microsoft, Google, and Verizon to the National Science Foundation, and San Francisco Unified School District.

Before IDEO, I taught elementary school in East Palo Alto and spent a decade doing design work with social service organizations—where I learned firsthand what it costs people when systems are built without them in mind.

I am currently writing User Error, a nonfiction book about digital access and the design decisions behind it. I live in Oakland, California.

‍

My expertise spans brand, communication, and product design across tech, education, the arts, and social impact.

I believe great work demands both high-level vision and obsessive attention to detail, and only happens through collaboration.

I bring an inclusive, hands-on approach and a deep understanding of business, which enables me to consistently deliver excellence while always asking why.

Before joining IDEO, I worked at the brand firms Pentagram and VSA Partners. I began my career as a designer, leading teams at the School of the Art Institute of Chicago and the Milwaukee Art Museum. I hold an MFA in graphic design from Maryland Institute College of Art and a BFA in communication design from the Milwaukee Institute of Art & Design, and have taught at some of the best design schools in the US.

I am responsible for IDEO’s long-term success in China and working with clients to use design as a tool to enable growth. Specifically, I have helped Chinese companies design holistic brand solutions through the development of their products, communication, services, and innovation teams, and I have helped multinationals expand their presence and influence in China.

I advise global leaders on developing China-led innovation and capabilities.

In over 15 years in IDEO Shanghai, I have worked on projects that use design to elevate the quality of the experience of healthcare products and services, streamline processes that increase productivity, create spaces and programs that promote and enable inclusive communities, and build next generation mobility solutions that are planet-positive.

Before joining IDEO, I worked at Philips Electronics and the Electrolux Group in Italy, the Netherlands, and Singapore on a number of breakthrough commercial products. I am a member of the Young President Organization in Shanghai.