Supply chain software had a multiverse long before Hollywood decided every superhero needed one.

We call them scenarios. Ask five vendors what that means and you may get seven answers.

For one, it's a saved version of a plan. For another, it's a sensitivity analysis. Somewhere else, it means changing a parameter, rerunning a model, and comparing the result. Sometimes, if we're being generous, it's basically "Save As" wearing a supply chain badge.

None of those definitions are necessarily wrong. That's part of the problem.

Supply chain teams use scenarios for different jobs. Sometimes they're managing the normal evolution of a plan. Other times they're asking a different question about the future.

Either way, you end up with multiple versions of reality. But the business can only run on one.

Sometimes a scenario is a version of the plan

However a team divides planning responsibility, by category, customer, supplier, or region, the common thread is that multiple people work from a shared starting point. Responsibilities may be separate or overlap, but eventually that work has to become a plan the business can use.

That's a scenario problem too.

Planning is rarely as simple as "Alice edits first, then Bob gets a turn." People work in parallel, start with different assumptions, and occasionally change the same thing in two perfectly reasonable ways.

Supply chains, unfortunately, have not agreed to become less complicated for the convenience of our software.

Sometimes a scenario really is a what-if

The other meaning of scenario is probably the more familiar one.

What if demand increases by 8 percent? What if transportation costs rise by 15 percent? What if we close a distribution center, add capacity somewhere else, change a sourcing policy, or shift volume between suppliers?

These questions are exploratory. You're deliberately changing assumptions, parameters, constraints, or inputs to see what happens next. You're rarely asking just one, either. Real planning means what-ifs at scale: dozens or hundreds of runs to find the handful that matter.

Software often treats these two worlds differently. Operational versions of a plan live in one construct; strategic experiments live somewhere else.

In Lyric Studio, we think about them as variations of the same underlying idea. A scenario can represent a working version of a plan or a deliberate what-if. The purpose changes, but teams don't need an entirely different mental model just because the question changed.

Creating scenarios is easy. Reconciling them is harder.

Most scenario conversations focus on creation: make a copy, change something, run it, compare the result.

Creating another version of a plan is rarely the hard part. Give us enough time and we'll create dozens, usually with names like "Final," "Final_v2," and "Final_v2_USE_THIS_ONE."

Suppose planners create scenarios around product lines, customers, suppliers, or geographies. Eventually, some of that work needs to come back together.

Lyric Studio merges scenarios back together. Pull in one change, a handful, or everything a colleague did. When two scenarios disagree, the conflict shows up on screen instead of vanishing into whichever version happened to be saved last, and a person decides which change wins with both options in front of them.

That matters because two scenarios can both be valid and still disagree. Say Alice raises the forecast on a product family after a customer call. That same afternoon, Bob caps supply on the same SKUs because a supplier flagged a constraint. Both changes are reasonable. Both cannot be chosen.

Declaring one scenario "the latest" hides the decision without resolving it.

The software should make that conflict visible and let people resolve it deliberately.

Collaboration without copying the world

Supply chain models can be large. Very large. Creating full physical copies every time someone explores an idea gets expensive and cumbersome quickly.

Lyric Studio uses a zero-copy approach to scenarios. Creating a scenario doesn't require duplicating the full underlying dataset. Instead, scenarios remain lightweight as users make changes.

That makes collaboration practical at scale, without every new branch of thought requiring another full copy of the world.

Changes are also tracked for auditability, so there’s a record of how the plan evolved and who contributed to it.

Beyond the what-if

What matters is whether a platform can support the way people actually work: sometimes together, sometimes independently, and sometimes making changes that don't agree.

So the next time a vendor says their platform "supports scenarios," ask for receipts. The phrase covers everything from "Save As" to a real reconciliation engine. Here's what to check:

• Both kinds of scenarios. Can it treat a scenario as a working version of the plan, built in parallel from a shared starting point, and as a deliberate what-if, where you change assumptions to see what breaks? A platform that only does one is solving half your problem.

• A path from what-if to plan. When an experiment proves out, can it graduate into the working plan, or does someone rebuild it by hand and hope nothing gets lost?

• Cheap creation. Does spinning up a scenario copy the whole dataset, or stay lightweight? If every branch is expensive, exploration gets rationed.

• Solo and shared commits. Can one person commit their own work without stepping on a colleague's, and can the team commit to a shared version when that's the right call? Both are legitimate. Forcing one is forcing a workflow.

• An audit trail. When a plan turns out wrong, the first question is who changed what and when. If the platform can't answer that, you're planning on faith.

• AI that carries real scenario work. Can an agent propose the scenarios worth running and explain conflicts in plain language, or does it only fill in a cell? One of those changes how a planner spends the day.

Every multiverse story ends the same way. Sooner or later, someone has to collapse the timelines back into one.

Creating alternate realities is easy. Getting everyone back to one universe is the hard part.

Now you know what to ask.