Dairy Queen Gives Phil Crawford a Broad Technology Mandate

International Dairy Queen, Inc. announced July 7, 2026, that Phil Crawford had joined as executive vice president and chief technology officer. He leads corporate IT and restaurant technology.

His remit covers more than 7,800 DQ restaurants worldwide, with a reporting line to President and CEO Troy Bader. Crawford succeeds Kevin Baartman, whose retirement was planned for later in the year. Dairy Queen's announcement identifies both the scope and the succession.

For franchisees, the appointment places a named executive over decisions that can cross several departments before reaching a restaurant. That matters when responsibility for an order, a payment or a support problem falls between systems.

Experience across the restaurant and its vendors#

Crawford previously led Adyen N.V.'s global food, beverage and hospitality verticals. Earlier CIO or CTO roles included CKE Restaurants, Godiva, Shake Shack and Yard House. His stated goal at DQ was to connect commerce across drive-thru, delivery, in-restaurant ordering and digital platforms. The July 7 release did not announce a platform selection or rollout timetable.

That experience is relevant to a job spanning restaurant operations and technology suppliers. It does not establish which vendor Dairy Queen will choose. The useful question is how the incoming leader will organize decisions among the people who sell, maintain and use the systems.

Consider an illustrative order that reaches the payment system successfully but arrives at the restaurant with incomplete instructions. The customer may receive the wrong order even though the payment went through. Internally, resolving it may involve the ordering provider, the payment team and restaurant support.

For that hypothetical incident, a support plan should assign someone to follow the order across each system and resolve the customer's problem. It should also identify who can approve a lasting fix. The breadth of the CTO role makes that coordination a reasonable test of future plans. The appointment provides no evidence of a completed improvement.

A global strategy needs a store-level plan#

The size of an executive's remit is different from the number of restaurants using a particular product. A global network count cannot tell an owner which equipment, software or support arrangement applies to their location.

Future project plans will need to make those boundaries explicit. A pilot in one operating configuration may reveal little about a restaurant with a different menu or ordering setup. The stores included in a test should therefore be identifiable, along with the conditions the test is meant to represent.

An operating plan also needs to distinguish installation from readiness. A device can be connected before employees know how to handle a failed transaction. Training and support arrangements belong in the launch decision because they determine whether a manager can keep service moving when the normal process breaks.

Cost follows those responsibilities. Owners need to know who performs configuration, who provides training and who handles support after installation. A hardware price alone cannot answer those questions or supply a complete budget. The appointment release disclosed no franchisee investment obligation, fee or replacement requirement.

Preserve decision history through the leadership handoff#

Baartman's planned retirement also makes continuity relevant. The announcement gives no detailed handoff schedule, so it cannot establish how long the two executives will work together.

A useful transition would preserve the reasoning behind existing technology choices. A configuration that appears unnecessarily complicated may accommodate a restaurant workflow or a contractual obligation. Knowing that history lets a successor evaluate a replacement without rediscovering every constraint during implementation.

The handoff should distinguish a temporary workaround from a deliberate standard. For example, an exception created for a discontinued ordering channel could be ready to retire. One still needed by a restaurant format may require continued support. Those are hypothetical decisions that a record of the original reasoning would make easier.

Future technology proposals can make that broad mandate concrete. Franchisees will be able to judge them through the responsibilities, costs and support arrangements attached to the projects that reach their restaurants.