DineTogether: Discriminating Tastes? Custom Case Solution & Analysis

Evidence Brief: DineTogether Case Study

1. Financial Metrics

Host Occupancy Rate: Marcus experienced a decline from 90 percent occupancy to 20 percent occupancy following a profile picture update.
Platform Fee Structure: DineTogether collects a 15 percent service fee from guests and a 3 percent processing fee from hosts per booking.
Growth Targets: The company seeks a 40 percent increase in active monthly users to secure Series B funding.
Customer Acquisition Cost: Current data suggests acquisition costs are rising in urban markets where host diversity is highest.

2. Operational Facts

Platform Mechanics: Guests browse host profiles which include photos, menus, and ratings before requesting a seat.
Host Profile: Marcus holds a 4.9-star rating with over 100 verified reviews.
Algorithm Function: The search ranking prioritizes hosts with high acceptance rates and recent booking activity.
Response Time: Marcus maintains an average response time of under 2 hours, placing him in the top 5 percent of hosts.
Geographic Focus: Operations are concentrated in major metropolitan areas including New York, Chicago, and San Francisco.

3. Stakeholder Positions

Sarah (CEO): Concerned about brand reputation and the ethical implications of platform bias but fears losing the social connection aspect of the app.
Marcus (Host): Believes the drop in bookings is a direct result of racial discrimination by guests once his ethnicity became visible.
Lena (Head of Product): Advocates for data-driven interventions but worries about friction in the user experience if photos are removed.
Investors: Prioritizing scale and user retention; wary of any PR scandals related to discrimination.

4. Information Gaps

Comparative Data: The case lacks a broad statistical breakdown of booking rates across different ethnic groups for all hosts.
Churn Metrics: Data on how many minority hosts have left the platform due to low booking rates is missing.
Legal Exposure: Specific internal counsel regarding the Fair Housing Act or similar public accommodation laws is not detailed.

Strategic Analysis

1. Core Strategic Question

Does DineTogether prioritize the social preferences of its guest base or the equitable access of its host community?
How can the platform eliminate racial bias in the booking process without eroding the trust required for a home-based dining experience?

2. Structural Analysis

Applying the Jobs-to-be-Done framework reveals that guests use DineTogether for two distinct reasons: a unique culinary experience and social connection. When bias enters the selection process, it compromises the culinary value proposition by filtering out top-tier talent like Marcus based on non-performance criteria. The Value Chain analysis indicates that the selection stage is the primary point of failure. The current transparency in the pre-booking phase allows for discriminatory filtering, which creates a negative feedback loop in the search algorithm.

3. Strategic Options

Option	Rationale	Trade-offs
Anonymized Booking	Hides host photos and names until the booking is confirmed.	Reduces bias but may decrease the perceived social intimacy of the platform.
Instant Book Mandate	Removes the host approval step for guests meeting specific criteria.	Increases efficiency but reduces host control over their own home environment.
Algorithmic Correction	Adjusts search rankings to boost minority hosts experiencing low conversion.	Addresses the symptom but not the underlying guest bias; may be seen as social engineering.

4. Preliminary Recommendation

DineTogether must implement Anonymized Booking immediately. The data from Marcus proves that transparency before confirmation enables discrimination. By shifting host identity details to the post-confirmation stage, the platform ensures that guests select meals based on quality and reviews. This protects the brand from litigation and ensures that high-performing hosts remain active on the platform.

Implementation Roadmap

1. Critical Path

Week 1-2: Technical audit of the booking interface to identify all points where host photos are displayed.
Week 3-5: Beta test the anonymized interface with a small subset of urban users to measure impact on conversion rates.
Week 6-8: Roll out the update to the full platform, accompanied by a policy update regarding community standards.
Week 9-12: Monitor Marcus and similar hosts to verify if booking rates return to historical norms.

3. Key Constraints

User Friction: Guests may feel uncomfortable booking a seat in a home without seeing the host first, potentially leading to a short-term drop in total bookings.
Host Safety: The platform must ensure that while host identity is hidden, guest verification remains stringent to protect the hosts.

4. Risk-Adjusted Implementation Strategy

The strategy includes a fallback mechanism. If guest bookings drop by more than 15 percent during the beta phase, the platform will introduce a verified badge system that highlights host experience and safety ratings as a primary trust signal, replacing the reliance on profile photos. This ensures that the transition focuses on professional credibility rather than personal appearance.

Executive Review and BLUF

1. BLUF

DineTogether must anonymize host profiles during the pre-booking phase to eliminate documented racial bias. The 70 percent drop in bookings for a 4.9-star host following a photo change is an indictment of the current system. Failure to act threatens the supply side of the marketplace, creates significant legal risk, and undermines the brand. The platform will hide host names and photos until a booking is confirmed, forcing guest decisions to rely on objective quality metrics like ratings and menu descriptions. This shift is necessary to maintain a meritocratic marketplace and secure the upcoming Series B funding.

2. Dangerous Assumption

The analysis assumes that guests value the culinary experience enough to accept a blinded booking process. If the primary driver for guests is actually a specific social aesthetic rather than the food, the platform may face a permanent decline in the total addressable market as users migrate to more transparent competitors.

3. Unaddressed Risks

Host Backlash: Existing hosts who enjoy the personal branding aspect of their profiles may feel the platform is becoming too transactional.
Safety Perceptions: Without a photo, guests might perceive a higher personal safety risk, even if that perception is rooted in bias, leading to increased cancellation rates.

4. Unconsidered Alternative

The team did not consider a tiered subscription model for hosts. A professional tier could offer instant booking and featured placement in exchange for higher platform fees, which might allow high-performing hosts like Marcus to bypass the traditional discovery path entirely. However, this does not solve the underlying discrimination issue and might create a pay-to-play environment that alienates smaller hosts.