Sana Remekie的动态

I feel as if I have finally found a kindred spirit with Sana Remekie!! Your insights are deserving of a Professor U. Commerce #SealOfApproval for #thoughtleadership!!

FYI Rob Daynes and Shelby Britton. Interesting point of views and discussion.

Love the content and the discussion threads. I always tend to think about this in reverse, so if an Omnichannel Digital Experience is the desired state — what are the channels — and how best to I provide a unique digital experience across said channels — which may involve much of the rest of the diagram to meet my end goal(s).

Hey Sana, great post. An excellent digital experience requires flexibility within each component that make up the solution. So the question needs to look at the architecture and the tooling within each of the components. Please take a look at my recent newsletter post on business tooling! https://www.dhirubhai.net/feed/update/urn:li:activity:6932690558448529408/

Sana Remekie Great Post. Ironically I took an eCommerce focused approach on the exact same subject where I discuss a balanced approach that is not monolithic nor 100% (maybe 10%, 30% or 70%) best of breed composable. I would love for you to give it a read! I see that you tagged the Konabos Team...we keep good company. https://www.dhirubhai.net/posts/activity-6930525834252365824-rUBz?utm_source=linkedin_share&utm_medium=member_desktop_web Andy Wamstad

This is a very interesting topic and one I love! I think you have to apply this lense to not only your own companies tech stack but that of any vendor. A vendor should be building their solutions such that at any time they can swap the underlying components for something else at any time with having to require a rewrite of the code. At the same time a company wants to ensure their MarTech stack is composable such that they can swap out pieces and integrate them seamlessly with the rest. At the end of the day I would argue that whatever a company chooses to use vendor wise in their stack, they should both be thinking of building the same way. That is how companies and vendors create partnerships that truly drive great digital experiences.

I'll be Switzerland and stick with "composalithic." It was an awesome session, Sana – with some spirited discussion and input. Exactly what we aim for with this group. Great demo as well!

And what about the best of both worlds? Just like build vs buy, I don't think it's ever one or the other. What IT need/want/decide vs the business can differ greatly, so appeasing both sides is an ideal desired state. At the end of the day, what's right for the overall business? Imagine if there were a single tech platform that can operate headless where required, offers a development framework to do so thus keeping IT happy with the abilty to integrate to other headless applications (because no technology can do 100% of everything), but then also provides business users ready-to-use, self-serve interfaces to the same API layer without having to rely on IT. Such a platform could be built in a componentry way, allowing brands to license only what they need, including key capabilities like streaming data management, identity resolution, decisioning, orchestration and analytics, to name but a few. Imagine! ?? (I'm genuinely interested in the topic of conversation and keen to hear the opinions of more thought leaders).

I think Monolithic could also lend itself to Omnichannel as it is customizable and has API's. I guess the way to look at it is that this graphic is a good conversation starter. There are a lot of valid points and some which need more conversation.

when creating this mind map, I'd be interested to know which term you started this with? This definitely gets you thinking. Can a monolith be a "bundled" suite of composable solutions, within one company or curated and connected between several? Does that give customers more confidence and something tangible to sign off on and get behind?