I am a bridge

Being a bridge means you can bring insights from both sides to create value and solutions that are greater than the sum of their parts.

A bridge helps span an obstacle, and provides passage over it. I consider myself a bridge. I stand in the middle of design and development. It's a grey and misunderstood area, but I really love this complex space.

This space I sit within is considered an obstacle by many. It's a space where miscommunication often happens: designers and developers are infamously known to not communicate well with one another, and not understand each others' perspectives. When you sit in the middle, as I do, you really understand both sides. I understand designers because I am one. I understand developers because I am one. Armed with skills from both camps, I am able to empathize with the challenges of each role, make contributions from both angles, and am able to move conversations along in a productive manner. Like a bridge, I bring people together. I help people get to their destination with greater ease. I help people, and projects, get to places they wouldn't be able to arrive at otherwise.

But being a bridge is not glamorous. Sometimes people walk all over you. But I am strong as steel and remain standing through turbulent times. As a bridge, you are not the origin or the destination. I am not regarded as an expert designer or an expert developer. Some people view this negatively and use phrases like "spread too thin". But being between spaces doesn't mean you're spread thin at all. Being a bridge means you can bring insights from both sides to create value and solutions that are greater than the sum of their parts.

Thank you to John Maeda, who I had the honor of meeting last May, for helping me understand my value as a bridge. May we continue to value bridges and help overcome more obstacles.