Genesys Casual

We often share the success stories, but I'm curious to hear the other side too-what's something in your orchestration journey that didn't go quite as planned or simply took longer to land than expected?

From experience, orchestration can feel quite straightforward at first: map the journey, define the logic, automate the flow. But in reality, the real work often lies in something less technical-getting alignment on what "good" actually means across different teams and perspectives.

It's also very easy to over-design when the capability is there. The challenge, and often the real breakthrough, comes from stepping back and simplifying-focusing on what genuinely helps the customer move faster and makes life easier for the agent.

For me, it's shifted from "Can we build it?" to - "Have we taken the time to agree on why we're building it this way?"

Would love to hear what others have experienced-where has the reality been different from the original plan?

#General

------------------------------
Namrata Pujara
Senior Project Manager
------------------------------

Great question this definitely resonates.

One thing that didn't go as planned for us was how "simple" orchestration looked on paper vs how complex it became once multiple teams got involved. Technically, building the flow was the easy part, the real challenge was aligning on what "good" actually looks like across teams.

We also ran into this with a CRM integration. Initially, we tried to fully automate ticket creation within the flow, but it ended up creating unintended outcomes (like duplicate/ghost tickets). We had to step back and shift the approach moving that action into an agent-driven script step instead. It gave more control and actually improved accuracy.

It was a good reminder that just because something can be automated doesn't always mean it should be.

We also found ourselves over-engineering early on trying to handle every edge case upfront. The real progress came when we simplified and focused on core journeys first, then iterated based on real interaction data.

Completely agree with your point the shift from "can we build it?" to "why are we building it this way?" is where orchestration really matures.

This resonates a lot with what I've seen in Customer Success and orchestration initiatives.

One of the biggest lessons for me was realizing that orchestration challenges are rarely about the technology itself. Most platforms today are incredibly capable. The harder part - and the part that usually takes much longer than expected - is aligning people, expectations, priorities, and definitions of success across the organization.

I've seen projects where technically everything worked perfectly… but adoption struggled because different teams had completely different views of what the "ideal journey" should look like.

Operations wanted efficiency.
Business wanted speed.
IT wanted scalability.
Agents wanted simplicity.
Customers just wanted their issue solved with less effort.

And that's where orchestration becomes less about workflows and more about empathy, communication, and change management.

I also completely agree with your point about over-designing. Sometimes we become so excited about what the platform can do that we accidentally create experiences that are too complex to maintain, explain, or evolve. Some of the best outcomes I've seen came from simplifying the experience, reducing friction, and focusing on clarity for both customers and agents.

As a CSM leader, one mindset shift that became very important to me was:
"Optimization without alignment creates complexity."
But orchestration with shared purpose creates adoption.

The projects that succeed long term are usually not the ones with the most advanced flows - they're the ones where teams collectively understand the why behind the experience being designed.

Really great reflection and an important conversation for anyone working with CX orchestration today.