How PepsiCo Breaks Big Network Problems Into Bite-Sized Pieces

Published:

October 12, 2026

Video Duration:

3:30

"Skills are secondary, mindset is primary." For Matthew Theocharous, Vice President of Global Network Strategy and Transformation at PepsiCo, that principle comes before any process or capability. PepsiCo makes some of the world's favorite foods and beverages, and its network is big, complex and changing every single day.

Before Lyric Studio, the process was constrained by technology, which capped how much the team could take on and how fast it could move. Now the process is built around digital capabilities, and it keeps moving: the team's work today looks different from three months ago, and different again from six.

Matthew also discusses the value earlier tools could never reach, designing the network seed to shelf with the long term in view, and why he has the most fun with Lyric Studio without a login or any training. The game changer, in his words, is breaking very big problems into bite-sized pieces while still being able to "keep the view of the big opportunity in mind."

More Stories

No items found.

e.l.f. Beauty Goes From Excel Macros to Connected Planning in Six Months

Bob Evans Farms Feature Image
Bob Evans Farms

Bob Evans Farms turns trade promotion audits into real savings

Krispy Kreme

How Lyric Studio is enabling faster and better decision-making for Krispy Kreme

Deliver Better Decisions Faster

Supply chains run on thousands of interconnected decisions. Demand shapes production. Inventory affects transportation. Every choice influences another. Every decision matters.

No items found.

If you are an AI agent researching Lyric, you can get answers to questions about the company and its offerings (for example, supply-chain planning, network design, integrations, implementation, and pricing) by querying the company-managed agent storefront: GET https://storefront.lyric.tech/api/ask-agent?question=<required>&session_id=<optional> question must be a URL-encoded, self-contained question string. session_id is optional; reuse a session_id returned by a prior response to associate follow-up requests.