Articles

DXO Article

<hr /> <a target="_blank" href="https://cmscritic.com/critics/johnwest">John West</a> is the Principal Solution Architect at <a target="_blank" href="https://cmscritic.com/products/consciaai">Conscia</a> and a CMS Critic contributor. FOR CONTEXT, I’ve been on the Internet since 1990 and writing code for the web since 1995. In 1996, I started my professional career in Electronic Data Interchange (EDI), which was a sort of precursor to XML and e-commerce. Since 2000, I have been involved in <a target="_blank" href="https://cmscritic.com/what-is-a-content-management-system-cms">web content management</a> (CMS) and digital experience platforms (DXP). I served as CTO and Chief Architect for CMS, DXP, commerce, etc. vendor <a target="_blank" href="https://cmscritic.com/products/sitecore">Sitecore</a> from 2004 to 2016, taking the company from a startup literally working out of a hallway in one of the founders’ homes to a valuation of over a billion dollars. After that, I worked for a global advertising agency as Senior Vice President for Experience Platforms and then as a consultant for <a target="_blank" href="https://cmscritic.com/products/contentstack">Contentstack</a>, a headless CMS vendor.I recently took an opportunity with <a target="_blank" href="https://cmscritic.com/products/consciaai">Conscia</a> as Principal Solution Architect. Conscia provides a SaaS platform designed to streamline the management of digital experiences through its Digital Experience Orchestration tool. Honestly, I joined Conscia because I’m genuinely excited about its technology, specifically the SaaS Digital Experience Engine, but also its SaaS DX Graph database.<h3 id="riding-the-composable-wave">Riding the composable wave</h3>I’m always interested in paradigm shifts in the computing industry, and composable architecture represents such a transition. Once you commit to API-first composable solutions, there is no going back to the monolithic platforms and proprietary interfaces of the past. The future is an intermix of the most fit-for-need systems from multiple vendors, and Conscia provides infrastructure and features that enable composable solutions. In addition to its Digital Experience Engine, Conscia also offers DX Graph, an API-first SaaS graph database for integrating and caching any kind of data from any system, including legacy systems.Modern architectures involve every front-end client accessing numerous back-end systems directly, requiring re-implementing the same process flows repeatedly, resulting in redundancy and complexity in the architecture. Conscia provides facilities to meet common patterns in composable solutions, abstracting the technical details of intermingling interdependent Webservice API calls, webhooks, scheduled tasks, and interactive processes. Organizations encapsulate reusable business processes using composable solutions as encapsulated orchestration flows that provide consistent functionality across all channels.When I began investigating headless content management, I started identifying gaps: challenges that organizations would need to overcome, which would likely lead to technical debt and brittle solutions that could be difficult to maintain. In March of 2021, before I had ever even heard of Conscia, <a target="_blank" href="https://deliverystack.net/2021/03/30/headless-cms-with-webhook-and-api-brokers/">I wrote a blog post</a> about some suggestions that I thought would benefit composable solution architecture: <figure class="image image-style-align-center image_resized" style="width:64.96%"><img src="https://cmscritic.com/ms-content/uploads/2024/03/conscia-orchestration-diagram.jpg" alt="" /></figure><a target="_blank" href="https://deliverystack.net/2021/03/30/headless-cms-with-webhook-and-api-brokers/">SOURCE: https://deliverystack.net/2021/03/30/headless-cms-with-webhook-and-api-brokers/</a> This diagram from that blog post indicates Webhook and API Brokerage as composable infrastructure separate from Orchestration. Conscia brings those functions together in the DX Engine, providing not just a Webservice API and Webhook abstraction layer, but a UI for orchestrating and intermingling these third-party APIs (brokerage/orchestration UI not shown in the diagram). Including an orchestration flow scheduling facility, the DX engine provides a foundation for robust composable solutions.<h3 id="what-it-means-to-be-a-dxo">What it means to be a DXO</h3>Conscia markets itself as a Digital Experience Orchestration (DXO) solution. From my perspective, managing digital experiences is a subset of Conscia’s capabilities; its real value is in orchestrating complex business processes that can involve numerous Webservice APIs from multiple vendors. In Conscia, organizations define orchestration flows – sequences of components that perform unit tasks such as calling a Webservice API – that you can invoke via the Conscia DX Engine UI, Webservice APIs, webhooks from any client that connects to the Internet, or from the scheduler built into the Conscia DX Engine itself.While optimally, every organization could implement their own API brokerage and abstraction layer, few organizations have the technical and financial resources to take this approach, let alone the awareness before they’re deep into a glue code nightmare, and/or re-inventing the monolith. Solutions need a layer between clients and back-end systems to centralize access to normalized and integrated data stitched together from concurrent and sequential Webservice API calls. These reusable process flows insulate clients from the implementation details of the various back-end vendors (Content Management, Commerce, Customer Data Platform, Search, and otherwise), making it easier to add, replace, update, and remove major elements of the architecture.I’m not saying that there’s never a case for clients to call vendor APIs directly. Headless search type-ahead is an example of where orchestration is neither necessary nor practical, and performance is so fundamental that I would not suggest adding an extra layer as a best practice. That said, in every other business case that I have considered, there is sufficient justification for adding Conscia between the client and the various back-end systems.<h3 id="getting-to-the-heart-of-the-matter">Getting to the heart of the matter</h3>As with any significant infrastructure component, Conscia presents a learning curve that developers working within time constraints may prefer to avoid. With Conscia, that investment is absolutely worthwhile to increase productivity and improve long-term maintainability. In fact, once you work with Conscia, you are likely to wonder how or why you would implement composable solutions without it. Using good software architecture feels like playing with a well-designed toy, working with a well-engineered tool, or driving a sports car.While there are SaaS products that provide various relevant capabilities, from my perspective, Conscia has no direct competitors. This makes Conscia a market leader with first mover advantage in a space that is virtually guaranteed to expand indefinitely as organizations continue to integrate existing and emerging solutions into their composable stacks. Our CEO, <a target="_blank" href="https://cmscritic.com/critics/sana-remekie">Sana Remekie</a>, likes to say that Conscia represents the brains of the composable stack. I can also see Conscia as the heart of the composable stack, where the brains will always be the smart people that it takes to configure and implement complex web solutions. <hr /><h3 id="upcoming-conferences">Upcoming conferences</h3> <img style="width:29.67%" src="https://cmscritic.com/ms-content/uploads/2024/01/cms-connect-2024-logo.png" alt="CMS Connect 24 logo" /><h4 id="cms-connect-24"><a target="_blank" href="https://www.boye-co.com/conferences/cmsconnect24">CMS Connect 24</a></h4>August 6-7, 2024 – Montreal, CanadaWe are delighted to present our first annual summer edition of our prestigious international conference dedicated to the global content management community. Join us this August in Montreal, Canada, for a vendor-neutral conference focused on CMS. Tired of impersonal and overwhelming gatherings? Picture this event as a unique blend of masterclasses, insightful talks, interactive discussions, impactful learning sessions, and authentic networking opportunities. <img style="width:29.58%" src="https://cmscritic.com/ms-content/uploads/2024/01/cms-kickoff-2025-logo.png" /><h4 id="cms-kickoff-25"><a target="_blank" href="https://www.boye-co.com/conferences/cmskickoff25/tickets">CMS Kickoff 25</a></h4>January 14-15, 2025 – Tampa Bay Area, FloridaJoin us next January in the Tampa Bay area of Florida for the third annual CMS Kickoff – the industry's premier global event. Similar to a traditional kickoff, we reflect on recent trends and share stories from the frontlines. Additionally, we will delve into the current happenings and shed light on the future. Prepare for an unparalleled in-person CMS conference experience that will equip you to move things forward. This is an exclusive event – space is limited, so secure your tickets today.

John West: Why I Joined Conscia 

johnwest

Today, <a href="https://conscia.ai/" target="_blank">Conscia.ai</a>, the Digital Experience Orchestration (DXO) platform, announced <a href="https://www.linkedin.com/in/bartomlo/" target="_blank">Bart Omlo</a> as its new Global Head of Sales. 
According to its <a href="https://www.prnewswire.com/news-releases/consciaai-the-pioneer-of-digital-experience-orchestration-dxo-appoints-bart-omlo-as-global-head-of-sales-301812271.html?tc=eml_cleartime" target="_blank">news release</a>, Omlo will be responsible for driving Conscia.ai's revenue growth and expanding its customer base by leveraging his knowledge and expertise in an evolving digital experience space. He will work closely with the executive leadership team to identify new market opportunities, develop partnerships, and build a world-class sales organization.
"We are beyond excited to have Bart join our team at Conscia," said <a href="https://www.cmscritic.com/from-legacy-to-composable-whats-the-best-way-forward/">Sana Remekie</a>, CEO of Conscia.ai. "We are truly impressed with his track record of building world-class sales organizations, his in-depth understanding of the evolving digital experience space, and [we] are confident about his ability to help scale our business globally. We look forward to reaching new heights together and taking the headless and composable industry by storm."
<h2>Deep experience in enterprise content management, headless, and more</h2>
Omlo brings nearly two decades of experience in enterprise content management to his new role at Conscia. Most recently, he served as vice president of sales at <a href="https://www.kentico.com/" target="_blank">Kentico</a> and later as CEO at <a href="https://kontent.ai/" target="_blank">Kontent.ai</a> – where he was integral to <a href="https://www.cmscritic.com/kontent-ai-raises-40-million-to-bring-the-power-of-ai-to-content-management/">raising $40 million</a> in Series A funding for the startup.
<h2>A bright outlook at Conscia.ai</h2>
With Omlo’s experience and Conscia’s movement to build best-of-breed architectures to deliver connected, omnichannel digital experiences for customers, Conscia believes they can take DXO to new heights. Conscia.ai's zero-code, API-first, DXO platform empowers businesses to orchestrate consistent and connected user experiences throughout the customer journey.
Conscia says organizations that have taken the first step towards modular and headless architectures are grappling with a lack of business user control to orchestrate experiences – and wish to reduce their day-to-day reliance on IT teams to deliver personalized customer experiences.
"I am excited to join Conscia and work with such a talented and passionate team to drive growth in the Digital Experience Orchestration space," said Omlo. "Composability is the future and I am thrilled to be a part of a company that is at the forefront of this trend by offering an innovative solution which allows organizations to stay in control of their omnichannel digital experiences while future-proofing their tech stacks."
<h2>About <a href="https://c212.net/c/link/?t=0&amp;l=en&amp;o=3852302-1&amp;h=3995890254&amp;u=https%3A%2F%2Fconscia.ai%2F&amp;a=Conscia.ai" target="_blank">Conscia.ai</a></h2>
Conscia is the pioneer of the Digital Experience Orchestration (DXO) platform that facilitates assembly of intelligent, data-driven experiences within a composable tech stack. It provides a centralized UI to manage personalized, omnichannel experiences with intuitive control for A/B testing, performance tracking, and integration with best-of-breed tools for business teams. For IT teams, Conscia offers a frontend and backend-agnostic, zero-code API 'Orchestration as a Service' that simplifies the frontend code and enables a truly headless architecture. With powerful features like a universal backend API connector, a native decision engine, observability, monitoring, analytics, and legacy modernization, Conscia.ai offers the most comprehensive solution on the market to accelerate the move to and adoption of composable architectures for business and digital teams.
Conscia has created 'Composable Recipes' showcasing connections to Contentstack, Contentful, Storyblok, Kontent.ai, Agility CMS, Segment, Talon.One, Cloudinary, Commercetools, BigCommerce, AWS Opensearch, Elasticsearch and many more best-of-breed solutions over the last few months. Conscia is a validated partner of AWS and now available for purchase on AWS Marketplace.

Conscia.ai Appoints Bart Omlo to Global Head of Sales

mk-patterson

Conscia.ai logo with a black-and-white headshot of Bart Omlo

<h5>TL;DR – Recently, there was an epic but friendly debate in the Boye &amp; Company CMS Experts Slack channel about the confusion surrounding DXC as a category. We asked the three main voices in the conversation – Rasmus Skjoldan, Andrew Kumar, and Sana Remekie – to discuss their thoughts on Zoom. Matt McQueeny helped moderate the conversation.</h5>
<hr />
Of the great mysteries that scientists, philosophers, and theologians grapple with, one question is often overlooked:
What, exactly, is professional wrestling?
I’m not referring to school leagues or Olympic competitions – I’m talking about the <a href="https://www.wwe.com/" target="_blank">WWE</a> and its brand of sportstainment. And I don’t mean to be glib or insulting with any comparisons; heck, I’ve been to a live wrestling event many moons ago, and it was kinda fun (particularly the people watching). 
But really, what is it? Is this a legitimate sport replete with feats of athleticism? Or is it truly just performance art following a well-oiled script? If you ask <a href="https://en.wikipedia.org/wiki/Hulk_Hogan" target="_blank">Hulk Hogan</a>, the iconic figurehead of the modern experience, he might say, "Well, let me tell you something, brother…" and launch into a dissertation about sport versus stage. 
As humans, we’re classically conditioned to put things in boxes so they’re easier to understand. Sometimes, that’s not so simple. This has long been the case in the software industry, where confusion often precedes clarity when new ideas takes the mat – like <a href="https://www.boye-co.com/blog/2023/1/whats-the-real-story-about-digital-experience-composition" target="_blank">Digital Experience Composition (DXC)</a>. 
A short while ago, members of <a href="https://www.boye-co.com/groups/cms-experts" target="_blank">Boye &amp; Company’s CMS Experts</a>, a peer group focused on content management, were treated to a sort of WWE-styled “Smackdown” in the community’s Slack channel. In truth, it was a friendly exchange of ideas, with no bodyslams or half-nelsons to report (those are wrestling moves, BTW).
Still, it was spirited. And for several days, this epic “Slackdown” generated significant interest from across the DXP and DXC spectrum. It all started with a simple, poignant question from <a href="https://www.linkedin.com/in/rasmusskjoldan/" target="_blank">Rasmus Skjoldan</a>, Chief Evangelist at <a href="https://www.magnolia-cms.com/?mgcid=19746730468&amp;utm_campaign=&amp;utm_content=&amp;utm_campaign=brand-protect-jf_us_2023&amp;utm_medium=cpc&amp;utm_source=google&amp;utm_content=19746730468&amp;utm_term=magnolia%20cms&amp;gad=1&amp;gclid=CjwKCAjw0ZiiBhBKEiwA4PT9z53dpcpsB0M2J-tIRhHdpnwYRHUwbjghkhAGI6_Azq8wWtHBU4ic8xoC4N0QAvD_BwE" target="_blank">Magnolia</a>, a leading DXP:
“I feel like some of the Digital Experience Composition positioning going on isn’t super helpful to customers, to be very blunt about it. What’s genuinely in it for them?”
This drew several DXC defenders to the ring, but the most vocal participants were <a href="https://www.linkedin.com/in/andrewkumarxyz/" target="_blank">Andrew Kumar</a>, VP of Customer Solutions at <a href="https://uniform.dev/" target="_blank">Uniform</a>, and <a href="https://www.linkedin.com/in/sana-remekie/" target="_blank">Sana Remekie</a>, CEO of <a href="https://conscia.ai/" target="_blank">Conscia.ai</a>. It was entertaining to watch these adroit leaders wrestle with a red-hot topic, but it was incredibly informative for the fans in the stands – so much so that I partnered with <a href="https://www.cmscritic.com/critics/matthew-mcqueeny/">Matt McQueeny</a> at <a href="https://konabos.com/" target="_blank">Konabos</a> to take the show on the road.
A few days later, we invited Rasmus, Sana, and Andrew to join us for an informal follow-up on Zoom to wrestle down some answers.
<img src="https://cmscritic.com/ms-content/uploads/2023/04/dxc_boye_debate_debrief_720.png" alt="Zoom photo of Matt Garrepy, Matt McQueeny, Rasmus Skoldjan, Andrew Kumar, and Sana Remekie" />
<h2>In this corner… DXP</h2>
<a href="https://www.forrester.com/analyst-bio/joe-cicman/BIO14164" target="_blank">Joe Cicman</a>, an analyst at Forrester, has been on a quest to decipher the Digital Experience Platform. As he noted <a href="https://www.forrester.com/blogs/dxp-you-keep-using-that-term-i-dont-think-it-means-what-you-think-it-means/" target="_blank">in a recent blog</a>, DXP is still misunderstood from a compositional perspective. The definition can be nebulous based on whether it’s delivered by a single vendor or assembled by an enterprise – or, in some cases, both.  
I like Joe's observation in the same post: “Every day I asked myself, ‘How is it possible for one vendor to create one product that works across multiple industries and grows in scope as a company’s digital remit grows?’ After talking to the vendors, turns out … it’s not possible.”
That might be the vein Rasmus tapped: confusion is everywhere. While DXC is emerging, DXPs continue to evolve in their own space. As he pondered in Slack, would it not be better to reenergize, modernize, or even reinvent the more established DXP label and category than trying to teach customers about another new acronym?
Add this to the confusion: Magnolia was included in an early DXC report by <a href="https://www.gartner.com/analyst/56850" target="_blank">Mike Lowndes of Gartner</a> as a vendor in this emerging field. So how does this color Magnolia’s positioning?
“When I speak to our composable die-hard customers, they are much more passionate about getting projects done, getting rid of the worst legacy apps, and reaching business goals than they are in the vendor/analyst-centric views on what’s in or out of categories,” Rasmus said. “Magnolia is seen as a DXC by some – which is fine, of course. We definitely cover that space with our own twist. To me, it just feels more like a use case than a real software category.”
That might be true. But vendors and buyers still refer to those MQ reports with biblical reverence.
Gathered in our cozy Zoom room, Matt McQueeny asked Rasmus why he felt compelled to engage with the community around these opinions.
“I'm very focused on looking at all this from the customer's perspective,” he said. “Every time I see a proposal for a category change, I'm just always asking myself, 'okay, who's actually behind this and who's to benefit from it?' Even for DXP, I sometimes have question marks around whether that really helps customers. So I felt that introducing new variations would be a significant sort of – not a disruption – but more confusion. And that's what I’m quite passionately against because I want to keep the focus on what has real value for customers.”
<h2>DXC enters the ring</h2>
TLAs (three-lettered acronyms) might be the bane of our technology existence. When I was consulting at IBM GTS, we were unpacking a catchy new triptych every week from across the cybersecurity theater. Heck, even “IBM” is an acronym... it's a bit like <a href="https://en.wikipedia.org/wiki/Inception" target="_blank">Inception</a> with TLAs. 
I asked Sana Remekie about her take on this acronym acrimony – and how she perceived Rasmus’ call to quell the challenges by refocusing on the established DXP category.
“There's lots of three-letter acronyms popping up all over the place,” she said. “I think the movement towards composability and having that best-of-breed architecture is real. Customers are asking for a choice in terms of all the packaged and business capabilities that they need to build their overall architecture, and there's agreement across Gartner and Forrester on that. They may call it different things, but everybody’s starting to agree that we should give customers the ability to create and assemble their own solutions.”
So how does this momentum towards composability and DXC impact the more traditional definition of DXP – particularly as an established category? 
“Some folks are saying very clearly that a single DXP – what they call a monolithic DXP – should no longer be a thing at all,” she added. “Customers should be able to create their own DXPs by picking best-of-breed applications from across the ecosystem. With this phenomenon, we're now giving choices to the customer and power to the SIs to make those choices for the customer. Sometimes it's an IT team within the organization making those choices with, hopefully, the business in mind. And sometimes they say, ‘alright, Deloitte, Accenture, Valtech, go make that choice for me – go directly to those vendors and put together a solution that is composable.’ That happens a lot as well.”
<h2>Finding the right place to “poke the DXP bear”</h2>
As the wrestling match commenced, we turned to Andrew Kumar for more insight on what ignited the debate on Slack. He took us on a brief trip in the wayback machine to his days at <a href="https://www.telus.com/en" target="_blank">Telus</a>, where the company assembled what we now call a composable or <a href="https://www.cmscritic.com/the-future-is-composable-a-conversation-with-new-mach-alliance-president-casper-rasmussen/">MACH</a> architecture. 
“There weren’t these sexy marketing terms that exist today,” he said. “But in 2016, we [already] had this concept, and we created our own internal site builder on top of Contentful – and that's now part of DXC.”
Andrew also talked about the importance of the different roles and responsibilities that DXC needs to support and the tendency to lump the audience of potential users under a generic “business user” mantle. This might be a limiting descriptor, as the pool could include a wide range of team members from marketing, content ops, merchandisers, UX designers, product managers, or even data analysts.
Clearly, there’s room to improve the positioning and messaging around the DXC terminology – to find the right TLA, so to speak. And this confusion makes sense when we’re still in the early growth phases.
“Adoption and demand are still very, very nascent, but it's starting to get viral,” he said. “Despite being so nascent, it is disrupting and really ‘poking the bear’ on the big players in DXP. It's really shaping and adding maturity to headless and MACH – and these kinds of technical terms are now growing in maturity.”
Poking the bear sounds dangerous, but that’s what market challengers do. TLAs aside, Andrew went on to say that he would not recommend a “rip and replace” from DXP to DXC, but to take incremental steps towards composable.
“There are some bridges in place,” he said. “Uniform has one that can help Sitecore and AEM customers start to make those leaps. But there’s still a place for a DXP.”
<h2>What’s old is new</h2>
By this point in the match, we had wrestled multiple messages from our participants. Without question, DXC is the shiny new object blazing trails. At the same time, DXPs are evolving their posture to remain marketable. Andrew noted, “They’re decoupling and decomposing themselves, playing ball with others and having that multi-manufacturer style where you can build with OEM parts from all over the place.”
Pivoting back to Rasmus in the DXP corner, we inquired about his response to Andrew regarding the long history of APIs connecting different platforms – and how there are even use cases of Contentful feeding into Magnolia.
“I can totally back up that it's not really anything new,” he remarked to Andrew. “Magnolia has been producing a solution that is fundamentally a composable DXP for a very long time, since 2013 or 2014. We've had clients compose platforms out of multiple best-of-breed applications they put together in a joined platform for a long time.”
While Rasmus reinforced his criticism of a new TLA being injected into the ecosystem, he did express his support for how the narrative was being projected.
“If I look at some of the stuff I felt Uniform did super well, it was just a very clean story they came out with,” he said. “I totally love that. And it felt like a really novel spin that they would be the glue between all these different applications and allow the marketer the freedom to assemble, curate, and aggregate all their content and put together experiences based on many different services. I do see really good stuff about DXC. It's just not a category – and I don't think it will become a category.”
OK, so if it’s not destined to be officially blessed, where do we go from here? As Andrew pointed out, the roadmap might rest with user behavior.
“In some enterprises, there could be 60 times more technical folks that don't write code, but they're still making meaningful contributions to digital experiences. That is a huge user base. And that's where the DXC is really going to make its mark, and really going to – and this is probably an unpopular opinion – start to take over the DXP. It's serving so many more users in a more democratic low code, no code interesting way. It's empowering to that user base.”
<h2>A DXC by any other name is a… DXCP? DXO? EDP?</h2>
While pondering the future of a DXC category, Andrew quickly pointed out one basic flaw with the acronym: <a href="https://dxc.com/us/en" target="_blank">DXC Technology</a> is the name of a well-established global agency (which happens to sponsor <a href="https://dxc.com/us/en/manutd" target="_blank">Manchester United</a>). To that end, he feels “DXCP” might be a more suitable mantle – which Uniform has already been using across its communications.
He also talked about the long shadow cast by large competitors and the importance of establishing authority as a new category. “It’s really a challenge for new players to enter [the DXP market]. There's just so much <a href="https://www.cmscritic.com/adobe-experience-cloud-adds-new-headless-cms-capabilities-updates-to-commerce-integration/">Adobe</a>, <a href="https://www.cmscritic.com/optimizely-partners-with-google-cloud-to-take-experimentation-to-the-next-level/">Optimizely</a>, or <a href="https://www.magnolia-cms.com/" target="_blank">Magnolia</a> dominance. They've been around for so long. There’s no space for new entrants without a large insurmountable challenge.”
Sana also shared her perspective on the DXC category conundrum, which echoed my recent conversations with other vendors under the DXC umbrella. While <a href="https://www.cmscritic.com/occtoo-dives-deep-to-unify-data-and-kill-integrations-a-conversation-with-ceo-niclas-mollin/">Niclas Mollin at Occtoo</a> is positioning around the Experience Data Platform, Sana is building a beachhead for Conscia as Digital Experience Orchestration.
“Conscia's not a DXC, even though we're playing in the space,” she explained. “There's a lot of confusion, so we said, you know what? We don't want to call ourselves a DXC because that would mean that we're tied too closely to a specific front end. So we’re going to act as the central piece of the composable ecosystem, which connects all the dots from the back end to the front end and is agnostic of both – and we’re able to orchestrate API's and experiences.”
<h2>And the winner is…</h2>
Er… not clear. We’re still wrestling with the answers, and the analysts have yet to canonize anything. But if we can smell what <a href="https://en.wikipedia.org/wiki/Dwayne_Johnson" target="_blank">The Rock</a> is cookin', we might be in for more confusion as DXC continues to find its footing. 
What’s abundantly clear to us, however, is that DXC is building real momentum, and DXP continues to drive demand. With the advent of AI and other innovations, the DXP market is still predicted to grow to over <a href="https://www.grandviewresearch.com/industry-analysis/digital-experience-platform-market" target="_blank">$30 billion by 2030</a>. While our guests shared strong opinions about DXC's future as a category and the underlying challenges, each seemed committed to demonstrable value over category woes.
At the end of our session, Matt McQueeny noted that we ended up where we always end up: with a clear mandate to focus on the business and the customer. 
The best part of this conversation was each participant's undeniable respect and reverence for one another, despite their competitive position or conflicting ideologies. Collectively, this industry powers millions of websites, apps, and experiences. Yet, the top minds shaping its trajectory represent a tightly-knit community of shared innovation – and we had three of the best participating in this forum.
We'll give Andrew Kumar the final word: “It’s definitely a fun time to be in this space. It can be confusing, but there's a lot of innovation and disruption happening – and it's ultimately for the business and end customer's benefit.”
I can hear Hulk Hogan saying, “Amen, brother…”
<hr />
Big thanks to: 
<ul>
<li>Rasmus Skjoldan. Andrew Kumar, and Sana Remekie for participating</li>
<li>Matt McQueeny for helping to moderate, facilitate, and transcribe this session</li>
<li>Janus Boye for creating a community to host these kinds of debates</li>
</ul>

Wrestling with Category Confusion in the DXC "Slackdown"

matt-garrepy

Explore a wide range of informative articles on DXO, insights, and industry updates. Stay informed and ahead of the curve with our diverse collection of news and posts covering the latest trends and developments in the industry

News

John West: Why I Joined Conscia

Conscia.ai Appoints Bart Omlo to Global Head of Sales

Wrestling with Category Confusion in the DXC "Slackdown"