MIT Sloan has published a case study titled "Driving adoption of a newly-launched product at Toast," examining how the restaurant technology company approached one of the hardest problems in product management: getting a new product into the hands of customers who are already busy running a business.

The case centers on Toast, the Boston-based company whose point-of-sale and restaurant management platform serves food-service operators. Toast's core business grew by selling integrated hardware and software into restaurants, and the case frames the question any product team at a scaled company eventually faces: when you launch something new to an existing customer base, what actually drives adoption rather than mere awareness?

For practicing product managers, this is the gap between shipped and used. A launch can hit its press-cycle metrics — announcements, demo requests, even initial signups — while weekly active usage of the new product stays flat. Adoption cases like this one are typically used in the classroom to force students to choose between competing levers: pricing and packaging changes, in-product surface placement, sales-team incentives, customer success outreach, or wait-and-iterate on the product itself.

What can product teams take from a case like this?

Cases built around an operating company like Toast tend to reward a few disciplines that translate directly to Monday-morning product work:

• Segment before you push. A restaurant group with 50 locations and a single-location café have different switching costs, different decision-makers, and different capacity to absorb a new workflow. Blanket adoption campaigns usually convert the users who needed no persuading anyway.
• Separate awareness from activation. If the metric is adoption, define it precisely: registered, first-used, used weekly, used in a revenue-critical workflow. Each threshold implies a different intervention.
• Watch the channel conflict. At a company with a direct sales force, a new product can stall if sellers are compensated to push the old bundle. Adoption problems are often incentive problems wearing a product costume.
• Instrument the failure path. Teams that only measure successful adopters cannot tell whether the leak is discovery, setup friction, or post-setup value. The case format pushes students to hypothesize which one dominates before proposing a fix.

Why Toast makes a useful subject

Restaurant technology is an unforgiving adoption environment. Operators work long hours, staff turnover is high, and any new tool competes against muscle memory at the counter during a lunch rush. That context matters: adoption frameworks that perform well in self-serve SaaS — in-product tours, free trials, virality loops — often underperform in operator-busy, high-touch markets where trust and hand-holding carry more weight. Any framework applied to this setting should be stress-tested against those conditions before it is trusted.

The tradeoff worth preserving here is the classic one: aggressive top-down pushes (sales mandates, forced bundle placement) can buy fast adoption numbers while eroding trust and generating churn risk, while purely organic strategies protect relationships but may never reach the activation threshold the business case assumed. Cases like this one exist precisely because there is no clean answer — only a defensible allocation of effort given the segment, the incentive structure, and the maturity of the product.

As product organizations move from growth-at-all-costs to proving that launched products actually stick, adoption-focused case studies of operating companies like this one are becoming core reading for teams that want their roadmaps judged by usage, not announcements.