Transcript

Note: The following is the transcription of the video produced by an automated transcription system. 

Hi, this is Akshay Sura from Konabos. Today we'll be talking about headless burger delivery. It's a play on words, billion API serve play on words with McDonald's as well. And there's reason for that. The other day, Matt and I were talking about, you know, what did what was our first job and it came up that, you know, I worked at McDonald's. And he thought it was a very interesting parallels between compostable dxp and the proof of value work, which we do all the time. But the story I was telling him about how it was at McDonald's. So, going to a little bit of a story back in the day and then in the in the 1990s, I studied in England, I was studying in Gloucester, but working in Cheltenham. Cheltenham has a McDonald's, it's a pretty big McDonald's, we had about eight to 10 tills, or POS systems. And during the weekend, we would have lines through, like out the door, all eight or 10 lines. And our average was 17 seconds per customer from the time you took the order for that to the time you delivered, what the customer ordered. And I think the industry average at that moment was 32 seconds. And so, we were really efficient, the team all loved each other, we had a lot of fun, but at the same time, it was challenging it the work isn't easy. At all, every station poses a different risk. So, if you're in the fry station, when you put your arm under the heat lamps for the 100 times the day, it burns.

Same thing with the griddle, if you're working in the freezer, you're going in and out getting food in the noun. If you're washing dishes, it's extremely hot water, you're wearing these heavy rubber pads and rubber gloves. And so, it's challenging, but every unit did their own job really well. So, when the person who is assembling it is helping the person taking the order runs out, all they have to do is go to these different stations and pick it up. And then they assemble the order. So, thinking about the movie, the founders of McDonald's, were also doing kind of like a POV proof of value, right? Doing the mock orders figuring out, hey, you know, let's put the layout this way. And then let's act as if someone ordered a mold, someone ordered fries, someone ordered three burgers, and they acted it out to an extent where they thought, you know, this, we got it. And then once you go into production, and once you start building things, you find out that, you know, maybe there's still room for more tweaks. And you it's an always learning process. So, when looking at this, we thought, you know, like Matt said, there's a lot of parallels with composable dxp.

When we look at it, we have our customers. So, our customers are the channels we provide things from which is our website, our mobile app, gaming, POS systems, IoT, anything you can think of. And then our front counter is we're selling for lack of a better word at this moment in time, because we in our world, it could be for sale Netlify, whoever it is who's actually the face of it. And so, it's a little bit tricky. Depending on if you're using API's and things it might be your headless system or commerce, but the lack of a better word. So, what we're trying to really get to is, you could have an environment where it is not uncommon to see multiples of a piece of technology. So multiple CMS is multiple commerce system, different ways of looking personalization. So, you could have uniform, you could have segment, you could do a lot of things in terms of composable dxp, which is you can reuse what you already have to find efficiencies in what you do, because your team is more capable of doing it. Or you could get the best of breed to do what you need it to do, where the technology gaps are.

So, from a business and technology challenges perspective, you can look at the gaps and fill those with what you already have, or get something get something new. Remember from a composable dxp perspective, it's also very agile, you can move you have flexibility, you can do things differently. You can do it over a period of time, it's not all at once. So, it's take your time do it properly. composable. The XP also lets you pick things which work for your team. It's also something you can take into account. You can change the configuration or the things you use at any moment, but you can be agile, you can be faster to market so we thought that this was a good way for us to showcase it. I hope you thought there was a funny little story and how composable really matches up with what was done in terms of how different stations did their job, right. So that's another thing in that every station is proficient at what they do.

So, if you have, for instance, the best of breed for you for a damn perspective, for a few product projects, that might be the case, but for something else, maybe it's something else you need to do. That's why the concept of multiple CMS isn't so far fetched anymore. Hope this helped. We try to come up with a lot of videos to help people understand composability XP headless so let us know if you need any help ask us questions. We are out there on social. Thank you and I hope this was useful.

If you have any questions, please get in touch with me. @akshaysura13 on Twitter or on Slack.