Campaign analysis after launch: read beyond enthusiasm The announcement of a steak quesadilla combination, with fajita vegetables and a separate dip, drew enthusiasm, a request to offer the dressing with other dishes, and accounts of awkward store interactions. These call for different actions: explain the current offer, record a menu request and check a reported incident. Research question What needs our attention in the replies to this launch, and what should we do next? Input material The announcement and its intended message Dated public replies Confirmed menu and service rules CCNeed research workflow Bring the announcement and replies Add the campaign message, dated responses and product rules. Ask CCNeed which replies need follow-up and why. Inspect the themes CCNeed finds Ask for grouped findings with the original context. Follow up on replies that look similar but call for different work, and check the menu rules they refer to. Hand off specific follow-ups Request a review record linking each finding to its source, proposed action and responsible team. Keep the original incident with any operational handoff. What the replies support—and what follows Enthusiasm for the food | Some people express interest. This is not a purchase or satisfaction measure. | Creative: retain the combination demonstration; do not label it a conversion result. A request for dressing with other dishes | One reply asks for the dressing with burritos and bowls. | Ordering team: record the request; help the content team explain which menu items currently offer this option. Accounts of store friction | An individual describes disagreement over sides and ordering. | Operations: check the incident and local rules before generalising. Launch review record Separate menu requests from missing instructions. Content update: Show how to order the combinations currently offered. Menu request: Record the request to make the dressing selectable with burritos and bowls. Operations handoff: Send the specific store-friction account for checking, with its original context. The example separates interest, a request for wider menu availability and reported store friction, giving content, ordering and operations distinct actions. Application example based on public records. The analysis and deliverable illustrate a method, not a customer project or business result.