Balancing the marketplace by enabling guests to book the bar.


As a product manager at OpenTable, I worked on the availability system that connects restaurants and diners. In OpenTable's supply-constrained marketplace, incremental availability has a direct, positive impact for the business, guests, and restaurants.

User research validated that the primary path to increasing availability was to enable restaurants to merchandise previously unutilized seats. And to do that, the product needed to enable restaurants to set guest expectations about their non-traditional dining experiences.

The results were fantastic. The initiative has added more incremental availability than existed in some smaller geographic markets and is still growing. Beyond bottom-line benefit, it layed the groundwork for OpenTable to power more memorable, unique dining experiences for guests.

  • Company
  • OpenTable
  • Role
  • Product manager

Discovery & analysis

User research


Product design

Determine table types

The 'outdoor' debate

Guest experience

Restaurant experience



Featured collections

Internal reporting dashboard






User research

In the fall of 2015, myself and several colleagues met with six restaurateurs in Los Angeles in search of ways to increase reservation availability on OpenTable's marketplace.

Questions focused on the reasons restaurateurs held back tables from OpenTable. If OpenTable could address those use cases, we could ostensibly increase table availability significantly.

We began the research open-minded. But after three interviews, all of us began zeroing in on an emerging opportunity: a way to set guest expectations around non-traditional seats such as the bar or counter.

“We need to manage people’s expectations about inside / outside / counter seating.

The counter seating MUST be booked on the phone. Unless OpenTable had a way to tell the guest …”

As of yet, OpenTable hadn't differentiated seating types. A guest simply makes a 'reservation'. And to most guests — especially those that have been with OpenTable since its fine-dining roots — a reservation meant table service in the main dining room.

It's easy to understand how guests could be upset:

  • Bar seating: Backless stools can be uncomfortable, the bar surface can be sticky, and parties larger than 3 will find conversation difficult.
  • Patio seating: Sun, wind and rain can cause discomfort. At some restaurants, the patio may be a less energetic experience than the main dining room.
  • High-Top seating: A High-Top is a raised table with raised seats that are sometimes backless. For parties with elderly guests or guests that use a wheelchair, High-Tops can be inconvinient at best and a show-stopper at worst.

Bottom line — guests need to know what kind of experience they're booking. For hot restaurants with limited availability, guests would be willing to compromise just to get in. And some guests simply prefer the bustling experience of dining at the bar.

If OpenTable could give guests the choice, restaurateurs could open up an additional 30 - 60 percent of their tables for reservations.

Product design



  • Identify themes in user research
  • Cross-reference with related guest research


  • Measure seating requests in guest notes
  • Infer # of non-traditional seats via floor plan data

Analysis yielded a clear, prioritized list of table types to support based on user behavior and table composition from the floor plans of live restaurants.

  1. Patio seating
  2. Bar seating
  3. High-Top seating
  4. Counter seating

Product design

The debate over outdoor seating

No issue was more hotly debated than whether patio seating should be included in version 1 as a table type.

The conceptual friction not only compromised the data model — it made it impossible to model bar seats located on the patio.

Technical constraints prohibited the obvious approach of modeling availability area attributes (indoor / outdoor) in addition to availability seating types (bar, high-top, counter, etc). This approach would more than double implementation time and require a significant redesign of search services powering OpenTable's diner apps. It would also explode the complexity of how OpenTable buckets availability types.

Deferring dedicated area modeling

The effort to clean up the data model in a future iteration was not significantly more than implementing it upfront. So, I descoped it — opting to halve implementation time and take on the very real risk that phase 2 would never happen.

Product design

The guest experience

Although I was technically only responsible for the restaurant experience, I worked closely with guest product and design teams to push the initiative forward.

Speed was favored over perfection. Personally, I wasn't thrilled with the design of the guest experience, but it was enough to launch and validate the concept.

Product design

The restaurant experience

The restaurant user experience was straightforward: select a table or lasso a group of tables, and adjust the table type in the sidebar.

Capturing a table's type had benefits beyond this initiative — it added structure for grouping tables together for future features.


Launch strategy

In a sales-driven two-sided marketplace such as OpenTable, a solid launch strategy is key to scaling adoption and engagement of a new feature.

The supply side needed to come first. Restaurants needed to be on board with accepting reservations on their bar, high-top, patio, and counter seats in order for guests to have the opportunity to engage.

Approach to supply side launch

  • Engage the sales team in a test market early in the development process to gather feedback and engender support.
  • Ensure all supporting collateral is ready for launch in test market
  • Work with sales leadership to determine sales strategy. In this case, position the feature not as an optional enhancement, but a fundamental update to how OpenTable functions. Include setup as part of regular meetings with restaurants.
  • Work with sales leadership to define incentive plan linked to adoption.
  • Be on-site for initial setup meetings with restaurants in test market.


Tracking progress

Tracking progress is an important part of any launch. At the time, data on supply-side and demand-side adoption and engagement lived in disparate systems. On nights and weekends, I designed & built a custom KPI tracking dashboard that enabled the product team to track progress and powered the sales incentive program with a built-in leaderboard.

The dashboard integrated with MongoDB, Salesforce, Mixpanel, and OpenTable's data warehouse to provide a 360° overview of the launch.

Note: actual numbers, names, and locations have been obfuscated or altered.


Public relations, training, and support

The public relations team did a fantastic job getting press in Eater and major metro news channels.

The training team created walk-through video tutorials and wrote documentation for OpenTable's community support site. Support leads helped train the support team to field questions from restaurants and guests about the new feature.


Happy restaurants, happy guets, and incremental revenue

Restaurants that accepted parties at their bar, counter, high-top and outdoor seats saw an increase in the average order amount — especially at seats that are traditionally glorified waiting areas.

This feature also made restaurants effectively bigger. Restaurants were able to better utilize their large tables by seating more two-tops at the bar. Eric Kirkenmeier of the James Beard Award-winning restaurant Cherry Circle Room said “…it’s allowed us to fit more people in the room, period.

“We noticed a change in our revenue immediately; we noticed a change also in the spirits of the bartenders. It’s nice that we know for sure certain seats will always be full every single night.”

—Lien Ta, Here's Looking at You

Because of the increased availability, guests were now more likely to find a spot at hot restaurants. As a bonus, many guests were excited by the option to choose the bar, which often offers a higher-energy dining experience.

The feature added more incremental availability than some of OpenTable's smaller geographic regions. As expected, incremental bookings quickly followed the increase in availability, adding directly to OpenTable's bottom line.

More Case Studies