Back to Blogs

5 first priorities for business change

The Contentstack Team●Oct 06, 2022

Talk to an expert

about something you read on this page

Contact an expert
Bob-Howland-Blog-Header_3.2.jpg

Bob Howland has helped drive business transformation in over 27 companies in industries ranging from retail to pharmaceuticals to software. In 2019 he joined Dawn Foods, the global bakery supplier, to do it again. As chief digital officer he took the 100-year-old company from a completely paper ordering process to a market ready e-commerce solution in just 22 weeks. 

We spoke with Bob about how he did it, why changing mindsets is often more important than changing technology, and what advice he has for other business transformation leaders. 

Turn executives into advocates

Moving a company to a new way of working is going to require high-level support and prioritization. Involve key stakeholders early in the process to close gaps in knowledge, collaborate on a plan, and ensure the executive team is confident in and excited about the changes ahead.

For Bob, an early priority at Dawn Foods was to meet directly with the chief financial officer to create a business plan. Giving the CFO full, transparent access to the expected costs and intended outcomes makes it possible to fast-track difficult conversations and align on the right metrics for the project.

The CFO can also recommend a trusted team member to act as the financial representative for e-commerce. By working with a finance partner to make estimates and approve any cost presented, you can build credibility within the organization as well as create a strong advocate in the finance department. 

Bob also recommends meeting with each board member individually to introduce the plan, address questions, and gather recommendations. These conversations give everyone a comfortable amount of time to get up to speed on e-commerce and, when it’s time to ask for approval, you’ll be able to present a plan that the board is already familiar with and has contributed to.

Take a crash course from customers 

Internal sources can get you up to speed on past and current priorities of the business, but answers about its future are found out in the field. Speaking directly with customers can help you identify internal blind spots, validate the need for change, and allow you to truly speak to the customer experience when making decisions.

Coming into Dawn Foods, Bob was well versed in e-commerce but not as knowledgeable about the bakery industry. So in his first two months he had “30 donuts in 60 days” as he visited dozens of bakeries to learn about the market, what customers valued most about the company, and what needs were going unmet. 

These market visits made it clear there was an urgent demand for e-commerce among customers and gave Bob a level of credibility with internal teams that helped get everyone on board with his recommendations. 

Prioritize people over pace

Once business transformation has customer validation and executive approval, you’ll need to work with people across departments to figure out the work it will realistically take to make it happen. Keep in mind that while the eventual maintenance of a new way of working might easily fit into a team’s responsibilities, the initial lift of the project can require a substantial shift in priorities, which can be met with resistance.

“In many cases, these are muscles that people that have never been in an e-commerce company don’t have,” Bob said. “So to come at it with a mentoring, a sponsorship, a teaching and training perspective is very important.” 

Change requires long-term objectives that will take long-term business relationships to achieve. After decades in the business, Bob said he’s learned to give people the time and space to come around to new ideas on their own terms. While this might slow down progress for the first few months, it builds the trust needed to move faster in the long run.

Make an MVP ASAP

Taking e-commerce off the whiteboard and putting it in front of the business is a way to quickly highlight the work that needs to be done on data, data structure, pricing, images and other assets to enable e-commerce. 

Bob and his team created the first minimum viable product (MVP) in six weeks, with the goal of showing the best possible commerce experience the company could put out without making any changes to business. 

“That MVP, the beta project, was one of the most embarrassing things that I have ever put my name on,” said Bob, “but it did show the company the gap between where we were today and what we needed to do quickly to enable an e-commerce business.

An MVP can also make it clear that the new way of working will affect many functions in the company. A visual, explorable product makes it easier for people to see how the change will relate to their own role and accelerates conversations about the collaboration needed from each department to bring a great experience to market. 

Remember, you’re just getting started

Getting the solution built is just the start. Transforming the organization and its mindset to one of continuous improvement is key to ensure you live up to customer expectations and demands.

Bob knew he wouldn’t have all the right answers by launch about what e-commerce should look like at Dawn Foods because that information would come from customer feedback and user behavior. So the team first focused on speed, launching a market-ready solution in 22 weeks. 

“On the quality side, however, I knew that I needed to have the team and process in place to do an amount of development work post-launch so we could quickly address all the feedback from the customer,” Bob said, sharing that more developer hours were used in the six weeks post-launch than used to get to launch. 

To this day, the team continues to commit to that cycle of improvement, releasing new features every two weeks and rolling them out to customers monthly. 

“I built a whole army and process and protocol to get to launch, but before I launched I had already built the governance, the process, the protocol to run the business,” Bob said. “I think those two things combined are why we’ve been so successful as a company.”

 

Share on:

Talk to an expert

about something you read on this page

Contact an expert

Recommended posts

Aug 09, 2023 | 3 min. read

There is no growth without support

We hire people because we believe they can do the job and help our organizations grow. And, yet, often, managers fall into the micromanaging or the no-managing-at-all trap. On the one hand: "I'll tell you how to do it and when." On the other hand: "Welcome and good luck!"I don't like to think about leading as "managing" at all. I think of it as "supporting." As leaders, our number one goal should be to support our team to reach their full potential and, in turn, enable the company to achieve its goals.There is no growth without support. Here are the three areas where I focus my support.Giving clear directionYour team can't row in the same direction without knowing where the company is headed and why. If the company aims to be the most beloved solution in the category, then a strategy might be prioritizing customer service. Every person across sales, engineering, marketing, partner development, and more should have a plan for how they contribute to that goal. But a step comes before that: ensuring your team is aligned on the values.Your people need to be clear on how they are expected to show up in the communities they serve. Without this, you may find your team achieving goals in a way that creates friction. The behaviors might ultimately work against the North Star, like the high-performing salesperson who is a nightmare collaborator or that leader who rules with fear instead of empathy. Remember that identifying people who will model the core values happens before you hire them. Review company values with potential candidates upfront and ask candidates which resonate with them and why. Also, consider including interview questions about how candidates get through challenging situations or help people succeed and about their community involvement to go beyond a simple values "gut feeling."Greenlighting the right toolsTools are table stakes when it comes to support. There are inevitably things your team will need to accomplish the goals at their highest potential. It could be an e-commerce solution or a collaboration or analysis tool. Often, it's department-specific.As a Solutions Architect for REI's content and experience management platform, Jason Greely oversees a team of engineers. In a recent episode of our People Changing Enterprises podcast, he said he looks for "established solutions that have robust SDKs and APIs, are well documented, and can tackle our capabilities." That's because he's responsible for a team of engineers and prioritizes tools that allow them to experiment and be "happy."I loved this extra layer of evaluation. Yes, tools should help people get the job done. But the sometimes uncredited benefits that come with them – like user happiness – can be even more potent as they lead to increased effectiveness, productivity, and innovation. Some studies show happy employees are 12% more productive, but that number is downplayed.Jason's colleague Kat Valdre, engineering manager for REI's platform organization, added: "Developers are happiest when they get to explore. Just having the possibility of flexibility is what most developers want – freedom. Also, managers who encourage that exploration."One tip from the REI team: make sure the end users of the tool are involved in evaluating the potential options. In Jason's case, as they considered new content management systems, the engineers "contributed their criteria and assessed based on the proof of concept they built. Without end-user involvement, expect a disappointing tool onboarding and acceptance process down the line.Building trust through autonomyMy leadership philosophy is essentially: hire great people and get out of the way. While it may seem counterintuitive, the "getting out of the way" part is one of the most significant ways to show leadership support.Part of that is encouraging that exploration Kat mentioned. Another aspect is showing your support for a project publicly. This executive engagement also involves unblocking as needed. As a leader, you've illuminated the goal, your team paves the path to get there, and you support them by removing the roadblocks. Sometimes, those roadblocks require an executive's touch as they can involve tricky conversations with other executives. Here's the catch: Leaders don't have to necessarily agree with the path to get out of the way. If my CMO wants to do something, my job is to enable her to do it and only raise a flag if I believe it may conflict with our values. Autonomy is an important show of support because it builds trust. And trust keeps the engines running.If I had to boil the concept of support down to one question, it'd be: How can I help my team be successful? It's about giving clear direction on values and end goals, providing the tools to make the team work smarter and not more complex, and letting people run with their skills and ideas. With these elements in place, growth follows.

Read the article
Jul 21, 2023 | 3 min. read

Retail reinvented: The top 5 takeaways from our conversation with REI

The convenience and accessibility of online retail have revolutionized the way people shop, especially after the last few years when in-person retail experiences were put on hold. In fact, by 2026, 24% of retail purchases are expected to take place online, totaling $8.1 trillion. To be able to react to customer needs faster, retailers are going composable.What does that mean? It means companies are ditching their traditional monolithic systems and trading them in for more agility and flexibility. Now, more than ever before, it’s important for brands to reduce transactional friction. Retailers need to be able to quickly adapt to changing customer demands and deliver consistent experiences everywhere their customers are — all without having to rebuild their entire infrastructure.Earlier this month, we had an insightful conversation with Matthew Schaeffer, Senior Manager of Data and Content Operations for REI. Matthew shared some eye-opening learnings about REI’s composable journey and how REI implemented new systems to bring their iconic green vest customer experience online. In partnership with CMSWire, we dove into how composable technology transforms retail experiences and how online retailers architect their digital experience infrastructure for peak engagement and demand. Below, we’ve recapped the top five webinar takeaways. You can listen to the full webinar recording here if you missed it.Brands today are not prepared to meet the rapidly evolving needs of customers.Sites like Amazon are raising the expectations for how people shop. Consumers want experiences that are more meaningful and more relevant to them. And whether it's to purchase something, find information, do research, or whatever they're trying to do, they want it to be easy.Evolving your systems is critical for delivering more personalized experiences.As a brand, your online experience has to be supported by your technology systems to create the best possible digital shopper experience. Delivering relevant and personalized experiences across channels at scale is the new revenue-critical trend. For systems that are already redlining, it's a challenge to evolve them. The next generation of customer experiences means being able to provide insights, information and personalization to win the loyalty of your customers. To do this effectively, you need to build a marketing tech stack that aligns to your future goals, not just today’s.Deconstructing the monolith is the key to scale and flexibility.Breaking down your monolithic platforms into more streamlined and more organized chunks gives you a lot more flexibility, not only in the ability to make updates and changes but also in choosing the right tools and the right integrations that you need to better engage your customers.Going composable doesn’t and shouldn’t require a rip and replace of existing technologiesWhile it may seem ideal to just pull everything out and start from scratch, the beauty of a composable platform is that it enables businesses to build what they need without abandoning tools they already know and rely on. Matthew said it best, going composable can't require a full rip and replace. The architecture to do the types of things retail businesses are trying to do online takes a number of different systems. Full-scale retail operations have search data, product content, different kinds of media, analytics tooling — the list goes on. Once you evaluate the capability sets of your different tools, you can figure out where to implement plug-and-play solutions.Define the value of going composableLastly, before you begin your composable commerce journey, it’s important to ask the following questions:Will your team really be able to innovate faster and be more agile? Will this technology help you adapt to your customer’s evolving needs based on what those look like today and you can anticipate them being in the future? How much is all of this going to cost? What will the impact on revenue look like? It’s important to be very clear on the vision and value you can deliver to your customers and your teams. And, then, find the people within your organization who will join you in advocating for transforming your digital experiences. Curious to hear the whole conversation? Watch the webinar here and stay tuned for next month’s webinar.

Read the article
Jul 19, 2023 | 3 min. read

The power of documentation for innovation

What does innovation look like to you? Raise your hand if you think about paperwork. Nobody? You probably thought about scribbles in journals, crazed hours working on your computer by lamplight, intensive brainstorming sessions, or even getting into the field and talking to potential customers, partners, and investors. I doubt you thought about documentation. But that can be your organization’s biggest ally in creating something new and unlike anything on the market. Documentation was useful for REI, the outdoor retail brand, as they implemented their new digital composable experience. Kat Valdre, engineering manager for REI’s platform organization, and Jason Greely, Solutions Architect for REI’s content and experience management platform, came on our “People Changing Enterprises” podcast to discuss it.It got me thinking: Documentation is often one of those overlooked, even annoying, parts of the business. But the benefits are clear: collaboration, clarity, and iteration. CollaborationWhen we think about documenting our processes, we primarily consider it a safeguard for when people – and the knowledge in their heads – leave. Kat made a great point on the podcast: the people who start a project aren’t always the ones who finish it. If you’ve documented your processes, it’s easy to introduce new people into the mix.While that’s a valid reason to start documenting how organizations do things the way they do, it’s not the only reason.One of the most powerful byproducts of documentation is collaboration. No matter how hard we try to break down silos, it’s still second nature for separate business departments to stay separate. Ongoing documentation can actually blow up those invisible boundaries. We’re constantly building things at Contentstack. Here’s how we kick it off: when our product managers begin working on a new product request, they fill out a product requirement document (PRD) that lists details like the problem it solves and different scenarios it will use. They send that PRD to our engineering team and create a technical specification document – the features and how we will build them – with that information. Once these two baseline documents are complete, they are broken down into tasks and assigned deadlines in Jira, our ticketing system.That process works the same way every single time. Why? Because we’ve documented it, everyone is on the same page, answering the same questions and working with the same expectations.ClarityIf you haven’t guessed yet, we capture all our knowledge and processes at Contentstack. If that sounds grueling or repetitive, stay with me — there’s a reason for it.That reason is clarity. The organizations that move the fastest and deliver high-quality results are the ones that work toward extreme clarity with their teams about their roles, responsibilities, and expectations. Never assume that everyone knows every process's details and role in them. Most of the time, that’s not true. I love a quote about leadership: “It’s equally vital as a leader that you speak with your people in a way that not only can be understood by them but, just as importantly, cannot be misunderstood.”When processes and roles are on paper, it’s pretty hard to misunderstand who is doing what and why. That’s why, during their digital transformation, the team at REI held meetings and made sure they wrote down:What they discussed What they decided and agreed uponThe reasons behind those decisionsNot only did it hold everyone accountable for the decisions and the execution, but it made sure everyone was on the same page.Ensuring everyone knows where they stand and what they’re doing produces remarkable speed and agility. It also produces confidence; over time, the combination of all these elements becomes something even more valuable: trust.IterationDocumentation sounds complicated, but it doesn’t have to be. It doesn’t have to take twenty pages — it could be a bulleted list. My team uses Confluence to capture our processes; it integrates with Jira and makes async collaboration simple with tagging and more. The REI team even talked about moments where Excel comes in handy.And just because a process is down on “paper” doesn’t mean it stays the same forever. In fact, it’s actually the opposite. It's easy to see where things can be improved when you’re staring at what’s being done and why. My teams’ processes are constantly changing. We always look at what we do and give feedback on what we can improve. This brings me to another good point: not everything needs to be made from scratch; sometimes, it just needs to be tweaked. Sometimes, the saying “If it ain’t broke, don’t fix it” is wise. If a process is working above 60% effectiveness, salvage it. Innovation doesn’t always trump iteration.Documentation is not the most glamorous part of innovation, I’ll admit. But it’s simple and effective. All we have to do to take advantage of the benefits is make it a habit.

Read the article
Jun 14, 2023 | 3 min. read

The beauty of a composable digital experience platform: It can be whatever you need

Have you ever tried designing a website from a template? It can be challenging. First, there are so many options to scroll through (that all somehow look the same) your head will spin. When you do pick a template, you have to build it the way you want, meaning a lot of customization. When that doesn’t work — because inevitably, you always hit the end of what the template can offer — you have to puzzle your way through custom code. That can become a tangled web very quickly.Imagine that process for an established enterprise like Sephora or even a fast-growing start-up. Think about the manual process of integrating each tool needed for e-commerce or inventory management. You think you are “done” building,  but wait — the market is evolving and you need to start selling on a new-ish platform like TikTok or BeReal.A traditional legacy CMS environment is tricky: Change one thing and you risk the entire machine stalling. The beauty of composable architecture is that your website can become whatever you want, whenever you need it — easily. Jurre van Ruth, digital strategy consultant at PostNL, came on our podcast, “People Changing Enterprises,” to discuss how the company took that concept to heart and made their composable DXP work for them. But to make it work for your company like PostNL did, we need to level-set definitions and expectations. There’s a lot of confusion in the market about composable architectures — like what is a “composable DXP” in the first place — that I want to clear up. What is a composable DXP?I like how van Ruth said it in the podcast: “We see [composable] as an ecosystem of technologies that aim to create and offer a consistent digital experience for all our customer segments across all digital touchpoints.” I specifically love the word "ecosystem" he uses. CMSWire describes a composable DXP as providing “integrated, consistent solutions that are modular and tailored to microservices and yet connect the gaps of digital experience. This is a unified and seamless approach that eliminates siloed user experiences and all-in-one solutions.”To further flesh out that picture, I often describe composable architecture as a Lego tower: Each block is a tech tool and they each function together to make up one, larger tower, aka the customer’s digital experience. However, unlike a sculpture — or legacy enterprise suites — you can more easily change the look and function of the entire tower by swapping out each block within. For example, if your next marketing goal is to target potential consumers with more personalized advertising and content, those tools are easier to plug into a composable environment than traditional suites. Creative teams get to pursue the digital experience platform of their dreams, and there is much less frustration, less custom code and fewer heavy integration requirements for IT to handle on the back end.Then where does headless — AKA a headless CMS like Contentstack — come in? It’s simply a cornerstone block in your Lego tower. For a marketing environment, the headless CMS acts as a foundation. Every tool — like e-commerce, automated translation, or SEO tools — can integrate into it to make content the central hub of your ecosystem.Moving beyond one-size-fits-allEvery enterprise is different, which means that the capabilities they need will also be different. However, when it comes to traditional legacy martech systems, it tends to be one-size-fits-all. The problem is that one size actually doesn’t fit all, and those environments are slow and difficult to change. It takes extreme customization via code, contacting multiple vendors for help, and a lot of inter-dependencies that aren’t always caught until something breaks.  One of the best benefits of composable is that integration is much easier and more natural with APIs inherent to a composable environment. Like clicking a Lego into place, that tool is now part of the environment. For PostNL, they invested in tools for headless content and digital experience analytics, which were easily plugged into their composable environment.An e-commerce enterprise can integrate all the tools they require, whether it’s an online storefront platform, a product catalog with elements like descriptions or visual assets, or any personalization tools it might need. But, for example, a hospitality service will need a different set of tools, and they can have them inside a composable environment.Enterprises are no longer satisfied with a one-size-fits-all approach. The beauty of composable architectures is that, in a market that changes like the wind, organizations’ digital experiences can also evolve just as easily.

Read the article
Jun 02, 2023 | 5 min. read

How to create a 5-star content strategy: Tips from Juliette Olah of Booking.com

When it comes to content strategy, Juliette Olah knows that a key part of reaching a vision is planning a smooth journey to get there. As senior manager, Editorial at Booking.com, she skillfully blends the needs of customers, technologies and creative teams to define the editorial roadmap for the global travel brand. Olah recently spoke with us about creating high-value content, getting organization-wide support for change, and the advice she has for other leaders driving editorial strategy. Keep the focus on the customer When Olah joined Booking.com in 2020, the editorial content was mainly used for paid social media ads. She quickly saw an opportunity to use these long-form articles in a much broader way to support the brand’s own social, organic and email channels.“I wanted to show that potential but, at the same time, keep focus so that it didn’t seem like I was trying to solve all content challenges through editorial,” Olah said. “If you go too broad, too quickly your message can start to become lost.”A key part of defining and keeping a focused content strategy is taking a customer-first approach — creating a roadmap and choosing themes based on what is most valuable for your audience and then figuring out how to tightly weave business objectives and marketing goals into the plan instead of the other way around. “A customer-first approach is essential; otherwise you lose relevance and value very quickly,” Olah said. “Audiences are incredibly sensitive and perceptive to anything that is slightly off or slightly irrelevant. If your content and your messaging isn’t coming across seamlessly you’ll lose attention immediately, and you’ll also lose trust.” Maximize the value of each piece “Editorial content does take a lot of resources to produce,” Olah said, discussing the research, writing, visuals and translation work required. “So if we’re going to do this, we need to make each and every story work to serve needs and fill gaps so that we’re supporting the brand rather than just adding more content.” Maximizing the value of content starts in the planning phase. For Olah and her team, this includes working with in-house researchers to identify travel trends, with localization specialists to make sure ideas are culturally relevant and with the social and email teams to create pieces that can serve the strategies of multiple channels. It’s also key to set up content for long-term value. This can include structuring content on the back end in a way that makes it easy to reuse across different channels, or enhancing the tagging and taxonomy of your archive to get more out of the content you’ve already invested in. “Editorial at Booking.com has been going on for many years, so we have thousands of pieces of content,” Olah said. “Surfacing that content in a relevant way, being able to curate it, to search through it and filter it efficiently is now really important for audiences to be able to get the most value out of it.” Build a 360 business case for technology change To reach their multichannel ambitions, Olah knew the editorial team needed a technology solution that would let them create, curate and optimize content more efficiently than would be possible with their incumbent, homegrown platform.  Having worked with a headless content management system (CMS) in previous roles, Olah started exploring if this approach was a right fit for Booking.com. Through many discussions with tech and product leaders, as well as the creatives on her team, she built a business case that looked at the technology justification and functionality needs, as well as the impact on efficiency and editorial strategy. “The business case is part showing a comprehensive, 360 view of the technical benefits of the platform and part showing that you’ve done your homework on a robust content strategy,” Olah said. “From examples of execution, to tying in brand storytelling and campaign amplification, to details around distribution and channel use cases of the content.” Presenting an aligned, measurable plan for change was key to getting different stakeholders to understand the potential of editorial content and to get the buy-in needed to make the change successful. “Advocacy is needed at all levels and functions, from a leadership level that signs off to the people that are actually involved in using the products and the systems day-to-day,” Olah said. “They need to be happy and settled and feel confident that this is going to make their jobs easier and more efficient.” Don’t change for change’s sake To ensure the move to the new content solution went smoothly, Olah was careful to avoid a common stumbling block she’d seen at other organizations. “When companies launch a new platform, there’s a tendency to launch 10 other things at the same time— a new platform plus new brand guidelines, or an entirely new content strategy, or a refresh of everything that’s associated with the particular platform,” Olah explained. “I was very conscious of not doing that because that is extremely stressful and, in my opinion, unnecessary.” Instead, change was rolled out in stages and, where possible, tied in existing ways of working to make people feel comfortable during the transition. For example, the editorial team was very happy with the workflow that was created around the previous content platform. While a headless CMS might be able to support more efficient processes, Olah decided it was best for the team to first roll out the new platform in a way that worked with the existing workflow. “Don’t try to change everything under the sun at the same time,” Olah advised. “If something is working, keep it, and keep the business case focused on the current challenges that need to be solved.” Plan for potential Breaking transformation into independent steps, rather than a big-bang approach, is also an opportunity to create a content and technology framework that supports continuous change. “Once we launch, there’s still a lot of potential for editorial at Booking.com, and what we’ve been able to do with this platform is build for that potential so that the structures are in place,” Olah explained. For instance, with an API-first approach Booking.com is able to structure content so that it isn’t locked into only being presented as a static long-form article on the site. As the team explores new channels, third party syndication, testing tools and further optimization for local markets they can adapt existing content and processes to meet new needs. “This is a huge benefit of headless,” Olah said. “We don’t know what we will necessarily need in another five years, but we absolutely need something that is flexible and adaptable enough to accommodate that.”“There’s only so far ahead that you can possibly plan for,” she continued. “You need a system that helps you to flex and change in this environment.”   

Read the article