• Communities
    • Advertising
    • Production
    • Marketing
    • Film
  • Submit Post Here
  • Editorial Spotlights
    • AdChat QuickChat™
  • Business Directory
  • About Us
March 27, 2023
  • Advertise with Us!
  • Contact Us
- Advertisement -
  • Communities
    • Advertising
    • Production
    • Marketing
    • Film
  • Submit Post Here
  • Editorial Spotlights
    • AdChat QuickChat™
  • Business Directory
  • About Us
Author

Bottle Rocket

thinkers. makers. experts. We are dedicated to creating meaningful connections between brands and people.




Marketing
Bottle Rocket Explains How to Make Data-Driven Decisions About Your Digital Product
Bottle Rocket Posted On March 13, 2023


How can you see the impact of every change you’re considering for your digital product before you build it?

We all know that Design systems tell a visual story of your product, architecture documents tell a technical story, test plans tell a stability story, and analytics tell a behavior story. But what can tell a clear and complete story of all users’ experiences? A Product Map is the answer.

Product maps are a multi-dimensional 10,000-foot view of every screen and interaction in your digital ecosystem. Not just flows and journeys, but every outcome, edge case, and potential experience for customers or users of any kind. With it, you can forecast how a seemingly simple change may impact the entire product, even screens and flows your team typically doesn’t touch. You’ll catch bugs you didn’t realize were lurking and estimate the full scope of work that changes might lead to.

Much like a roadmap, a Product Map is a foundational point of reference that can benefit internal and external stakeholders alike. As your digital ecosystem becomes more complex, it’s increasingly difficult for anyone to see every impact of new features and changes – whether they’re a marketing manager, CTO, or the QA and user experience team. A Product Map is a one source of truth document that reveals the full picture of the product in a way that every stakeholder can understand.

From our expert perspective, here are 10 instances where we know we wouldn’t want to be caught without a map.

  1. When big team changes are on the horizon – This could be new internal teams, new partners, or even team blending from organizational changes. Also, when you’re shifting to or from nearshore or offshore development teams or partners. Don’t risk losing historical knowledge that’s locked away in someone’s head.
  2. When embarking on a massive overhaul of a feature/section – Big changes can feel scary. The effort is unknown at first and the scope can feel ever-changing. A Product Map can be an invaluable tool to bring extra clarity and nail down exactly what the future will hold. Every kind of stakeholder can work from the same shared foundation and collaborate on everything from the happiest path to the smallest error state. The best part? A Product Map can drive a new level of quality for QA teams. From end-to-end, behaviors are clear and expected from the start.
  3. When replatforming or “cleaning up” an existing digital product – Replatforming or adding a new third-party tool could have broad and complex impacts across your experience. In addition, with mature products the need to sunset legacy systems that are no longer being used can arise.
  4. When rebranding or redesigning screens — Are you launching a full rebrand or updating any core components of your experience? The Product Map helps you see how often you’ve used logos, icons, and other visual devices in your work to understand the depth of changing your visuals (i.e., visual design guidelines, brand guidelines).
  5. When it’s time to develop new code for an existing digital product – Is your development team likely to rearchitect a portion of your navigation? Are there areas where code can be re-used to minimize level of effort? A Product Map ensures greater quality when QAs are testing the product so that they have something to refer to for what should be happening in a digital experience.
  6. When software changes hands with mergers & acquisitions – As new product owners or executives come into the picture, oftentimes the digital product undergoes some major changes. Having a Product Map before you purchase a product could help you understand things like API calls, dependency driven displays, business rules and logic.
  7. When you are moving into new geographic regions or new business units are emerging – Anytime you plan to use one digital product to help you “go faster” or create other versions or varieties of the same product, this tool could come in quite handy. For example, a Product Map can help you understand where you will need to account for legal requirements when entering a new country or market or where to account for regional preferences for screen density among users.
  8. When building long-term roadmaps for your digital product – To fully understand the possibilities for the future or as a tool to identify opportunities to enhance your existing customer touchpoints at various stages in a customer lifecycle.
  9. When you need executive buy-in on a new experience, feature, or interaction – This tool can be invaluable to succinctly and comprehensively explain impact and gain buy-in from those that aren’t as close to an overall digital experience. Really, it’s helpful for any stakeholder to digest the massiveness of a mature product and also can illustrate the growth, balance and robustness of newer products.
  10. When you are seeking to deliver on users’ unmet needs – A holistic at-a-glance view in one central location allows for precise mapping of interactions and displays any given dependencies. From 10,000 feet in the air down to the minutia, this flexible and living tool outperforms more traditional documentation that imposes limits and removes rich context. Start by connecting logic together, translate this to preliminary designs, and pitch for consensus with approvals. Next, replace low-fidelity wireframes with high-fidelity documentation for a responsible way to manage new features or enhancements. 

The benefits are for everyone.

When you think about it, there’s really no one person associated with a digital product team who couldn’t benefit from a Product Map. A Product Map can help ensure quality and efficiency in the continuous design and development process for mature products as well. Although the effort required to create it may be substantial, the benefits of completing it will greatly surpass the initial effort. We all know software is never actually done – let’s review the benefits that a Product Map can provide any well-oiled digital product team.

  1. Greater quality of your digital products
  2. Prevent costly mistakes over the life of the product as new features or enhancements are implemented
  3. Better metrics/measurement planning and reporting
  4. Better scenario-planning for teams
  5. Greater team collaboration and alignment, both internally and with partners
  6. Centralizes critical product knowledge in a form that can grow with your product
  7. Ensures customers/users can move freely between products in your ecosystem
  8. Helps achieve shared meaning quickly among teams

Each of these benefits contribute to providing one key thing for any successful digital product team. Does your team have a one-stop foolproof place to document everything about your digital product experience? A Product Map is a single source of truth that everyone on the team can look to for any and all decisions.

Isn’t this the same thing as a prototype?

Our answer is a resounding no. Prototypes are definitely a useful tool in the toolkit and we leverage them for their strengths and benefits as well. When interacting with users or customers, a prototype can be a useful means of demonstrating or dissecting one complicated interaction point within a digital experience. They are great for gathering user feedback before you create any code. But what a prototype can’t do is demonstrate all of the real dimensions that exist within a complex digital product experience. Product Maps can bring together multiple interaction points all into one nice view. They map screens, actions, conditions, pathways, and most importantly, outcomes. All in one nice tidy place.

Isn’t a product map hard to maintain?

All too often, documents that are owned and maintained by a single part of a team quickly get out of date and lose their usefulness. With all stakeholders benefitting from a product map, integrating its upkeep into the design and build process gets widespread support. Teams can continuously evolve it: adding to it for a new experience concept, updating it with new designs as part of the design sign off, building from it as map as a development resource, referring to it in test planning, and using it as a reporting visual that corresponds to the data.

It’s time to tidy up.

Hopefully, by this point, the value of Product Maps is clear. It’s a map, playbook, roadmap, prototype, vision document, and quality checkpoint all rolled into one nice, tidy package. Is it time for your team to get organized and get to Product Mapping? The task may seem daunting, but don’t worry, we’re always here to help.

The experience experts at Bottle Rocket are specialists in creating effective, efficient, memorable experiences for some of the world’s most well-known brands. We’ve learned a thing or two over our 15 years and have developed many best practices that our internal teams and many clients use each day. Product Maps are just one example of how we help product teams in companies of all shapes and sizes ensure they are getting the most from their digital product and that users keep coming back for more.

Raina Probst, Carla Salcedo, and Tyler Robb explore 10 expert use cases and 8 key benefits for any product-led organization.


Continue Reading
0
46 Views




Marketing
Bottle Rocket Tells Us the 2023 QSR Trends To Watch For Restaurateurs
Bottle Rocket Posted On February 10, 2023


Michael Kanne, restaurant lead and Experience Consultant at Bottle Rocket, discusses the 2023 trends most likely to shake the earth in the QSR sector.

Inflation is slowly beginning to level off, with December’s core consumer price index sitting at 6.5 percent. However, the cost-of-living crisis continues to plague the economy as consumers scramble to save. Diners are forced to think twice before eating out and when they do indulge in a little luxury, like a dinner with a loved one, or takeout after a hard day at work, they’re looking for good value – something that makes it worth it. QSR businesses will need to do everything they can to provide memorable experiences that keep their customers coming back.

With food service businesses still suffering from supply chain shortages, their hands are often tied when it comes to pricing, but they can still provide customer experiences that make a diner feel valued. Of course, they can do this by adhering to time-honored best practices like training their employees to be personable and attentive to customer needs, providing good food, and maintaining a clean and appealing in-store experience. However, in 2023 we will also see restaurateurs leaning into the latest digital innovations to improve order time, take a cognitive load off employees, and surface opportunities to surprise and delight customers by leaning into personalized experiences.

The Food Delivery Revolution

Food delivery platforms like Grubhub and DoorDash took center stage due to COVID-19, and 2022 saw food delivery apps remain a permanent fixture, with the average American making nearly 55 food delivery orders yearly. In 2023, QSRs will continue to embrace this ongoing food delivery revolution to reach new customer segments.

However, with delivery fees eating into restaurant profits, restaurants like Chick-fil-A are leading a movement to bring food delivery apps in-house. Expect this trend to continue as leading QSR brands look to steal a slice of the pie from the likes of Uber Eats.

No Stopping AI

Artificial intelligence continues its tireless march toward transforming every sector. For QSRs, AI promises to improve efficiency while opening new opportunities for personalization. In the drive-thru space, companies like McDonald’s are using AI to program menu boards that display items based on weather and the time of day. Voice technology, meanwhile, is increasingly used to automate ordering and free up human employees for more rewarding, high-impact tasks.

Ordering Online, on App or Through QR Codes

Apps continue to open new avenues to connect with customers and boost convenience. 40 million people downloaded the McDonald’s app in 2022, and YoY downloads of the top 36 QSR apps were up 6.6 percent in December. Mobile ordering allows customers to order en route to the restaurant, cutting down wait times, increasing the number of customers that can be served, and increasing sales. Advances in machine learning mean that expected wait times for an order can be automatically generated.

As an added benefit, digitizing a customer’s buying habits on an app allows QSRs to scrutinize buying habits and personalize their offer 

ing accordingly. Trends likely to hit the headlines in 2023 include dynamic pricing, personalized menu items and upsells, app-only offers, and deals based on individual preferences. Trends like contactless ordering have also seen QR codes and app clips enter the ordering ecosystem. App clips, small parts of a larger app that open without the need for a download, represent just one more example of reducing digital friction in a physical world.

Omnichannel isn’t Going Anywhere

On their mission to fuse digital and in-person experiences, perhaps the biggest pitfall facing restaurateurs will be going overboard with tech implementation. If QSR leaders have learned anything from 2022, it’s that technology will never completely replace human interaction. QSRs will want to make the most of the latest innovations, without losing sight of human and physical touches

An omnichannel approach that balances digital transformation and efficiency with human spontaneity remains the goal. The National Restaurant Association’s State of the Industry report found that 78 percent of restaurant leaders view digital solutions as a way to support staff amid labor shortages rather than replace them. In case you were hoping for the end of the sit-down dining experience, it’s still a long way away, with 68 percent of diners indicating that they prefer traditional dining service to delivery, takeout or drive-thru.

In 2023, food service brands looking to build engagement and conversion want to be building customer relationships across every possible touchpoint. That means looking at all the latest innovations and strategizing about how they can be seamlessly integrated into an omnichannel ecosystem. Every diner has their own unique preferences for interaction with a brand, and each point of contact should integrate seamlessly with every other. It is important to remember, the magic happens by considering the holistic experience, not just targeted parts of the diner journey.


Continue Reading
0
176 Views




Advertising
Bottle Rocket’s Rebecca Farr Tells Us 10 Reasons Organizational Change Fails
Bottle Rocket Posted On January 31, 2023


by Rebecca Farr 

It happens time and again. I’m sure you’ve either witnessed it or suffered through it — the failed attempt of a large change at an organization. Maybe it was with a new process or switching over to a new technology. Maybe it was a change to the structure or the metrics. Whatever it was, it was difficult and painful for everyone involved. The people who were impacted by it will not soon forget. If you were the one that was trying to implement the change, the tinge of failure is salt in the wound after all your hard work. All your dedication and efforts to try and make a great improvement — and for what?

If this has happened to you, it’s time to do some reflecting to ensure this doesn’t happen again. Allow yourself to be brutally honest and analytical. If you haven’t yet, ask for feedback. This is incredibly important because, with each failure, the inertia of change grows. People may be less willing to buy in as they lose trust in the ability to change. And while the result isn’t always so bleak, if you’re not learning from your failures, then you’re doing yourself (and those around you) a major disservice.

Why do so many initiatives fail — even with what we feel like is proper execution? Why does change continue to be so hard? With the amount of change we’re adapting to all the time, you think we’d be more amenable to it. But we’re not. Humans generally don’t like change and we’ll go out of our way to resist it. We’ll stay in jobs we hate, cities we loathe, and with people who don’t treat us the way we deserve. We’ll continue our relationships with archaic technologies that don’t scale, outdated policies that make everyone’s life tough, and strategies that got us to where we are thinking they’ll take us to the next level. Why?

At the end of the day, it’s easier to not change. Change is the unknown, and that’s scary. What if things go sideways and it’s even worse than it is now? WHAT IF WE CAUSE THE APOCALYPSE? But what if things were…better? While this article will focus on reasons organizational changes fail, if you’re interested in getting a different perspective on change in general, I’d recommend Who Moved My Cheese? by Spencer Johnson.

Here are some of the top reasons I’ve seen initiatives fail time and again.

1. You didn’t have (or provide) the right motivations. 

Why are you proposing this specific initiative? Why is this the change that we need? If you don’t know, no one else will either. Make sure your reasons are the right ones. I’ve seen organizations change for the wrong reasons, it’s really painful to both watch and participate in. Even if it succeeds because it can be forced, no one likes it, or wants it, and you ultimately lose a ton of leadership capital, and potentially great employees. In order to get others motivated, determine how they can benefit and create your argument around that. Focus on how it helps them. Why they should want to help this initiative happen. Data works wonders here, but so does appealing to employees’ emotions.

2. You didn’t evangelize it (enough). 

How do you expect people to properly follow through with something they don’t know about? People have a lot of other things going on and the most important thing in your mind is probably not the most important thing to them. Get ready to talk about the same thing multiple times. Do it in different ways so it has the potential to reach more of your audience. Go to various team huddles to talk about it. Bring it up in the leader meetings. Talk at any venue where you can get just a couple of minutes to cover the why, when, and how. Remember that you shouldn’t just be talking about it, you should be inspiring people. And when you think you’ve evangelized it enough, do it more. Chances are, there will always be someone listening for the first time, whether they’ve attended a previous session or not. And to spark their interest, make sure you’re telling a story! Start with the problem or current state, then go to what’s been tried before and failed, then go to your solution. Especially in larger (or poorly communicating) companies, you’ll notice a lot of people don’t really understand what the change is for, what the plan is, etc. It’s kind of like playing the Telephone game. This is also how detractors might be created. Get to know your detractors and work with them to mitigate their concerns — especially if they’re an influencer (see reason #4). You can use their feedback to specially craft any future communications and get ahead of any damage control you might need to perform.

3. It wasn’t the right change. 

Does the proposed change actually solve the problem at hand? How can you be sure? If you need some exploratory methods, you can try a proof of concept (POC). From there, you might decide to do a pilot. Both can be incredible assets in determining if your solution is the right one and how it can be improved. Learning the pitfalls is equally important as identifying what works because it helps you iterate and improve the ultimate result. If the first solution you proposed doesn’t work, reflect on why. Did you not do enough research? Was the downfall obvious? Or should you have done the POC in the first place to really find out?

4. You didn’t get buy-in from the influencers. 

Everyone is influencing everyone else in some way, shape, or form. Who is your key audience or those most impacted by the change? Who do they listen to and trust the most? If you don’t know, then you’ve already done yourself a disservice. Find out. Build up relationships with them before you need them to love your new idea. If you’re not sure how to do that, I wrote this article previously. If the influencers say nice things about what you’re trying to do (especially to others), then you’ll most likely have a much easier time getting buy-in from everyone else. Additionally, incorporate these people into your strategy group. Finding like-minded individuals who are passionate about the initiative will be to your benefit. And when they contribute, make sure you give them credit — especially publicly. Not only does this show that you can be trusted to share the rewards, but it positively reinforces their help.

5. You didn’t collaborate. 

We’ve probably all been there — you hear about a change coming that doesn’t make any sense. It actually does the opposite of what it’s intended to do. Why? Because no one consulted with the subject matter experts or people that it impacts. Sometimes, even just a single conversation with a knowledgeable person would have set the solution on a different path — a better path. Maybe it’s due to ego, inability to delegate, or some other weakness, but this never goes well. It is important to get different perspectives in order for a change to succeed.

6. You didn’t have easily navigable references or reminders. 

I get it. Very few people like to create documentation. But this is a non-negotiable of any successful change. How can people know what to expect or follow through if they don’t know what to do or where to go to find it? You need to make it as easy as possible to review documentation or else very few will put in the effort to find it. Don’t bury it five clicks in, come up with a catchy name for the initiative so there’s an assumed word or phrase to search for in your company’s knowledge base. Paste a link to it everywhere, throw it into your internal email signature if you need to, do whatever it takes for everyone to know where it is and for it to be incredibly accessible. Then make sure the documentation is readable, easy to follow, and captivating (enough). Make sure there are as many pictures and images as is reasonable instead of large blocks of text.

7. The process was overly complex. 

Let Occam’s Razor be your guide, which states that the simplest answer is usually the right one. Regardless, you may want to have trainings on the new changes. Make sure that as much as feasible, the employees impacted are motivated to follow the process. This could take on a few different looks, whether it’s financially motivated, or quality of life at work, etc. You must make sure it is easy for the adopters to take part in.

8. You didn’t communicate to your colleagues in leadership OR leadership doesn’t (really) support it. 

You’re ready to release the change. Your organization is aligned and rearing to go. But what about the others? Have you talked to the leaders and team members of the other parts of the business? Will this change impact them, even if not directly? It’s one thing for the leaders to say “yes, this is good” and another for them to really understand and have the conviction to support it, and to have their org prepare for the change as well. People are smart. If their leaders don’t show that the change is important to them, they’ll notice. This will either cause confusion or conflict or both.

9. There was poor planning/execution. 

Arbitrary deadlines can cause the most well-intentioned change to fail. There needs to be thought and reason behind the execution timeline, with a little buffer to account for when things don’t go as planned, people get sick/take vacation time, etc. But aside from the actual planning and performance, it’s possible that this just isn’t the right time for the change. Maybe there are aspects of the company culture that just aren’t ready for it, maybe there’s no leadership buy-in, and maybe the budget won’t allow for it. When you’re thinking about making a large organizational change, you need to think about the cultural, political, and technical landscape. Put yourself in the shoes of all the departments this would impact and think of what message this will send them. Make sure you’re able to cultivate the conversations in the light you’re trying to shine. If you’re having trouble with thinking through the problem, V2MOMs are useful.

10. The value wasn’t properly represented. 

Define key data points and measure them before and after the change. It’s important that the metrics chosen aren’t vanity or fluff. I’ve worked in organizations where the metrics either didn’t make sense (calculations were wrong, etc.) or they didn’t actually measure the right things to prove their point. People can see through this, and it creates a distrust of leadership, of the system, and you lose buy-in on the change because people can tell it doesn’t really matter. After the change occurs, review the data. If they didn’t change how you expected them to, maybe you didn’t choose the right path after all. But if there’s a significant difference, you have some major evidence that your change was effective. And it will most likely be a lot easier to get support for the next change you want to lead.

Is successful organizational change even possible?!

Yes! But keep in mind that these kinds of things are difficult. Many leaders and companies struggle with this, especially if they’re used to just telling people what to do from a top-down approach. Now, many companies are working in a more employee-empowered environment, which can be a new experience for some. You can do this! Chances are, you won’t get the change 100% right the first time. You’ll most likely need to make tweaks and adapt. This is normal, so don’t get discouraged. And remember that not every failure has to define you, but every failure is a chance to grow.

original content

Continue Reading
0
160 Views




Advertising
Bottle Rocket Earns Spark AR Creator Certification for Meta | Helps Brands Unleash Creative and Connected Experiences
Bottle Rocket Posted On September 28, 2022


Bottle Rocket recently announced that the company is one of a select few worldwide that has earned the formal Spark AR Creation Certification from Meta.

This certification further strengthens the company’s deep technological expertise and signifies their continued focus on finding new and unique ways to help brands unleash creative and connected experiences in the Metaverse. Bottle Rocket is an experience-focused consultancy that designs and builds mission critical mobile and web applications for the world’s most beloved brands.

Earning a Meta Certification at the company level means that Bottle Rocket is recognized as having proven digital expertise through verified certifications. The certification was earned by Bottle Rocket’s technology team after completing the formal training for advanced-level creators through Spark AR Studio and represents the company’s ability to deliver AR experiences for Facebook, Instagram and the Metaverse.

“This certification is an important tool in our arsenal and will help us create even more immersive and impactful experiences for our clients” says Rajesh Midha, Bottle Rocket’s CEO. “This certification proves that we are not only capable, but also recognized by Meta as a leader in our space, as well as a highly-skilled developer of AR solutions for our clients. This certification and skill set is a logical extension of our current capabilities and solutions that we create for our clients.”

David Harrison, Bottle Rocket’s VP of Technology adds, “When we talk about AR and the Metaverse I think a good term to use is ‘Real World Metaverse.’ Rather than moving people into a new non-real ‘verse,’ we are focused on bringing the data to them in the real world, focusing on the Reality part of Augmented Reality.” Harrison goes on to mention that this capability “has been in Bottle Rocket’s wheelhouse since we were founded. Delivering connected experiences to customers in a manner that isn’t intrusive, meets them where they want and allows them to get things done and get on with their day has always been one of Bottle Rocket’s greatest strengths.”


Continue Reading
0
241 Views




Marketing
Bottle Rocket’s Dustin Hasset Explains Why Foodservice Walks a Tightrope Between Physical & Digital Experience
Bottle Rocket Posted On September 6, 2022


Now more than ever, restaurateurs are operating in an experience economy. Customers are interacting with competitor brands over multiple channels every hour of every day, and they expect every digital experience to measure up to the Amazons and Ubers of this world.

Just like the behemoth tech brands, foodservice businesses need to deliver personalized, intuitive, and seamless digital experiences for their guests – without forgetting added in-person ingredients like warm decor and friendly interactions with staff. With restaurants under more pressure than ever to retain customers, the brands who can make their IRL experiences memorable while also leveraging digital technology to make ordering, paying, and engaging with the brand quicker and easier will ultimately win the day.

Digital Is Never An End In Itself

A QSR’s tech stack might have all the bells and whistles, but if it isn’t finely tuned to the customer’s needs it’s basically redundant. A thoughtfully designed digital experience should meet a customer wherever they are and make their journey easier without stealing the spotlight from in-person experiences – and that takes planning. So, before they set about developing a new digital experience, foodservice CTOs and CIOs need to strategize.

If the end goal is to build engagement and ultimately conversion, foodservice businesses will need to build a relationship with their customer wherever they’re spending their time. Every touchpoint in an omnichannel customer experience needs to communicate the brand values and add to the physical experience of picking up or dining in at a brick-and-mortar establishment. And, because customers’ preferences for interacting with a brand differ widely depending on demographics or even time of day, digital experience will have to be holistic, allowing customers to drop off one channel and pick up another while still being able to see their closest pick-up point or customized offers.

In this landscape, convenience trumps technical virtuosity because it is frictionless. Case in point: app clips, small parts of a larger app experience that launch in seconds without download, breach the boundary between physical and digital experience because the barriers to jumping in and out of the digital ecosystem are so low. A customer can scan a QR code at the door or on their table and immediately begin designing their order, booking a table, or paying for their meal. After experiencing the benefits of the app clip, customers are more inclined to download the full app to make the most of personalized offers and location information.

Once a customer’s buying habits are digitized on an app, valuable data can be collected for use down the line. If this information is surfaced effectively, employees can surprise and delight their customer at their table by showing how well they’re known and valued, all but guaranteeing a memorable interaction.

Tech Should Support Employees

Employees straddle the border between digital and physical, so their buy-in is vital when introducing new digital experiences.

Happily, there’s no reason for conflict between physical and digital dimensions of experience. According to the National Restaurant Association’s 2022 State of the Industry report, 78 per cent of leaders in the restaurant sector see digital solutions like mobile point of sale as a way to remove manual processes and support staff through labour shortages. Rather than threatening jobs, they’re boosting retention. And, at the same time, 68 per cent of consumers still prefer traditional service when dining, suggesting that all stakeholders benefit when the digital and the in-person coalesce.

For example, Chick-fil-A and Bottle Rocket’s cutting-edge mobile ordering system cuts down on queues on arrival. The GPS-enabled application notifies restaurants of orders while customers are still en route, meaning more customers can be served, sales can be increased, and staff can concentrate on delivering a memorable experience for their guests.

Ultimately, brands walk a tightrope between getting left behind in the race for digital efficiency and losing focus on the customer by bringing in too much tech too quickly. We’re never going to see the death of the full-service restaurant, but the brands that stray too far from this delicate equilibrium risk falling by the wayside.

Dustin Hassett is a Senior Product Manager at Bottle Rocket. A digital product specialist with eight years’ experience in the digital product space, he works particularly with QSR brands to bring innovations to the restaurant industry


Continue Reading
0
541 Views




Marketing
UX APIs Can Make or Break a Customer Journey | Bottle Rocket Offers up Key Info for Companies
Bottle Rocket Posted On June 21, 2022


In today’s digital-first world, customers expect to be able to interact and transact with a brand digitally. Expectations are ever-changing and brands must figure out how to remain relevant or risk becoming obsolete in customers’ minds. Although there are a variety of distinct types of online customers, there is one thing they all have in common: the overall lack of time and willingness to endure experiences that do not immediately meet their needs. No one has time for a bad experience.

As Bridget van Kranlingen, Senior Vice President of IBM Global Markets, has said: “The last best experience that anyone has anywhere becomes the minimum expectation for the experience they want everywhere.”

But what makes for a bad experience? Honestly today, it does not take much. Our expectations have been set by the likes of Apple, Netflix, and Uber, and many other superior experiences in the market today. One too many screens in a mobile checkout flow could be all it takes for a customer to begin buying products somewhere else. A bad experience for the customer equals bad business. It is not like any brand sets out to build or create a bad mobile/web experience on purpose. The problems can often stem from somewhere below the surface of the mobile/web application. If everything on the surface that is needed to ensure a positive experience is there, there is a problem enabling the experience. Enablement is one of the main responsibilities of client-facing APIs. If API consumers — the mobile developers in this case, but also pretty much all the stakeholders in any business — are not enabled to produce the mobile experience as desired, the end customer experience will often fall short of expectations. Digital product owners and developers need the APIs to support the overall end customer experience — and not just any APIs. Let us talk about Experience APIs.

The Experience API Difference

At a surface level, an Experience API will look like any other API. The technology employed, specification format used and the presentation in general will all be familiar to any seasoned developer. Instead, an Experience API is a philosophy. It is a philosophy that calls for APIs to be intentionally designed with a focus on the experience a developer or stakeholder will have when using them. Converting a SOAP API to REST or migrating to session-less authentication are both notable examples of things that make API consumers (again, referring to developers in this instance) happy. However, those examples are merely table stakes for an API powering a customer-facing experience. The experience flavor of API should not exist by happenstance nor because some tool generated it as a, simple, project formality. Experience APIs should be carefully designed to ensure support of the customer experience which only happens by making the API a priority and not just another thing to be done. From a technical perspective, the API should be responsive (150–300ms response times are a respectable goal) and the request/response schemas should be tailored for maximum intuitiveness. From a hierarchical perspective, an Experience API will reside at the top of the API stack. It should be considered the tip of the spear in an organization’s API attack plan on customer experience friendly APIs.

Compound Effects of Experience APIs

An API that works is not enough, at least not for an Experience API. It must work the way developers need or want it to work. Developers should not have to perform miracles when it comes to making API calls just to represent a complete entity that an average customer would understand. For example, a product in a customer’s mind is not split between product information in a PIM (Product Information Management) system, image assets in a CMS (Content Management System) or metadata from some key-value store. The product is the whole enchilada, visuals included. Developers will have a much more enjoyable experience integrating an API into a customer experience if they do not have to make multiple API calls for every single resource. If a developer is finding their experience consuming an API to be delightful, they will have an easier time mapping design concepts to API resources. Experience Design (XD) can come to fruition a lot quicker if a developer knows what they need and where to find it. A well-designed Experience API will foster trust with developers and allow them to speak with their own level of confidence about what is/is not possible to downstream stakeholders. As much as an API is a representation of underlying entities, a mobile or web experience is a representation of the underlying API. In general, an Experience API should be designed with simplicity, consistency, and ease of use in mind. Furthermore, and more importantly, Experience APIs should be designed to support the client’s workflows. This can be achieved more consistently by designing an API early in the project, a process known as API Design-First.

The Road to Experience APIs with API Design-First

The API Design-First process is simple from a theoretical perspective. Briefly, the process simply calls for the API design process to happen before implementation of the respective API. It is easy to talk about designing an API first, but oftentimes hard to do in practice. Committing to the API Design-First process can be challenging for some teams because it requires ongoing communication between developers and stakeholders to ensure the best API is built for the job. This is especially challenging for teams that are not used to communicating with stakeholders outside their development silos. Stakeholders can include anybody that has a personal stake in the success of the overall experience; however, it will usually include the following roles: customer (internal and end-user), design, and platform developer. Out of the roles mentioned specifically, API developers should get comfortable communicating with designers as they are the people visualizing the experience imagined by/for customers and eventually, built by platform developers. In other words, an API that closely matches application design is more likely to make the customer happy because developers were enabled to do so. There is no definitive guide on the API Design-First process, but it can be broken down into two high-level project phases: design and implementation. These phases can further be broken down as such:

Design Phase
1. Discovery and Requirements Gathering
2. Assess Self-Understanding and Validate with Strategists and XD
3. API Design
4. Validate with XD and Stakeholders
5. Repeat steps 3 and 4 as necessary

Implementation Phase
1. Receive (Positive) Feedback on API Design
2. Implement
3. Validate
4. Design (design never ends)
5. Repeat steps 2–4 as necessary

Repeatedly getting validation is a direct sign of the constant dialogue that must be happening between the API implementation team and stakeholders. It is easy to scoff at this and consider it a waste of time, but the alternative result might be vastly different from what the customer is wanting. Take the time early to get buy-in from stakeholders before moving further down design and/or implementation paths with an inadequate product. Locking down on a solid API contract allows for the use of API mocking tools as well. Mocked APIs will allow front-end developers to be unchained from the back-end’s software development lifecycle (SDLC). Give your client-facing APIs priority, make it one of the first things worked on, and keep an open dialogue with stakeholders. Do this and you are more likely to create something that customers will enjoy.

Experience APIs are Important…

With all the emphasis about APIs and the priority thereof, it’s important to remember that APIs are not the most important thing in a digital endeavor. Developers and stakeholders are clamoring for access to a business’ all-important data; It is what they seek to fill the screens of their respective experiences. Data is king; data is the most important thing. The argument can be made that the behaviors and functions APIs expose are of equal importance, but what an unsatisfactory feeling it would be to not see the results of your work — the data on the other side. This detour down data lane does not diminish the role of an API yet solidifies its rank amongst other priorities. Data needs its digital ambassador and that is the perfect role for an Experience API. Practitioners of the API Design-First process should take considerable pride in implementing Experience APIs as this could be the decision point between a long-standing customer or a customer lost. Customers see the data through the experience that has been crafted for them to see it in. The experience does not stop in the customer’s hand or on their desktop; experience carries down to the API. The API must embrace the challenge of representing and serving the data in a simpler manner, so that consumers can easily meld the data into the customer’s experience.

Moving Forward with Experience APIs in the Fold

Information is what customers and developers seek in the end. Experience APIs exist to expose this information in a way that is easier to understand and consume. The Experience API journey should be a concerted effort to ensure that the pathways between the customer and the business are straight-forward and pleasurable to navigate. Communication, like for many other things in life that are done as a team, is key to implementing an Experience API. There is no possible way a single person or siloed group will know what is best for the customer and what they need. Experience APIs may not be the only priority, but they should take their rightful place as one of the main priorities in the pathway to superior customer experiences.

Published by Danny Baggett in Customer Experience, Product, Development, API

Continue Reading
0
248 Views




1

  • Events Calendar

    March 2023
    Mar 30 2023

    AAF Dallas Career Starter Fair

    Saatchi & Saatchi Dallas, 2021 Mckinney Ave, Dallas, TX, US, 75201
    Mar 30 2023

    Medium Giant’s Webinar | Google Analytics 4: How to smoothly transition to GA4 and gain actionable audience insights

    Mar 30 2023

    2023 Exxon Mobil Lecture Series | PepsiCo Brands’ Sustainability Story

    Angelika Film Center Dallas
    April 2023
    Apr 19 2023

    Digital Fight Club

    Granada Theatre
    No event found!

2023 AdChat™ trademark and content property of AdChat LLC with all rights reserved. All other trademarks and content belong to their respective owners.
Press enter/return to begin your search