The 'Parking Spot' Phase of Software

Geoff Teehan posits that we are currently in the early stages of software maturity, which he calls the "parking spot" phase. Drawing a parallel to the early adoption of digital cameras, he notes that people initially used them exactly like film cameras. It wasn't until later that people began using digital cameras for novel tasks, like photographing their parking spots to remember where they left their car. Teehan argues that software is currently in this transition; we are replicating old processes without fully leveraging the unique capabilities of the medium. He believes we have yet to see the true potential of software design because we are still focused on digitizing existing workflows rather than inventing new ones.

From Consumer Principles to Enterprise Infrastructure

Transitioning from high-profile consumer roles at Facebook to building payments infrastructure at Lightspark, Teehan challenges the notion that B2B software must be inherently boring or poorly designed. He argues that even in complex, technical domains, the end users are still human beings. By applying consumer-grade design principles—such as sound design, intuitive hover states, and frictionless interaction—to enterprise tools, designers can increase efficiency, build trust, and turn users into advocates. At Lightspark, this manifests in how they pitch their infrastructure: they create high-fidelity, consumer-like mockups of how a payment system would look inside a client's app, allowing partners to visualize the end-user experience before committing to the backend integration.

The Philosophy of Internal Tools and 'Rows'

Discussing the creation of his project tracking tool, Rows, Teehan highlights the value of building software specifically for one's own team. When existing tools like Notion or Jira felt either too complex or misaligned with the needs of a small design team, he built a custom solution. He emphasizes the importance of "zero friction" and shipping quickly. However, he notes a critical distinction: turning an internal tool into a public product requires a fundamental shift in responsibility. Once you release software to the public, you must honor the trust and time users invest in it, which necessitates a massive increase in overhead—from marketing sites and signup flows to data deletion practices and long-term maintenance.

Reflecting on his time at Teehan+Lax and later at Facebook, Teehan describes a pattern of proactive reinvention. When the agency model faced saturation and margin pressure, he and his partner John Lax chose to pivot rather than compete on price. This involved taking time to step back from client work to rethink the future of the industry. His move to Facebook taught him how to operate at massive scale, while his subsequent work with David Marcus on crypto and payments taught him how to navigate the complexities of large-scale organizational projects. His advice for designers is to remain curious about verticals that might seem uninteresting at first glance, as the most impactful work often lies in solving tangible, real-world problems.