assorted color bricks

Success with composable means starting small and focusing

This article was based on the interview with Jim Tattersall of Rotate by Greg Kihlström for The Agile Brand with Greg Kihlström podcast. Listen to the original episode here:

One key takeaway from the conversation with Jim Tattersall of Rotate is the importance of starting small and solving business problems when implementing a headless or composable commerce approach. Tattersall emphasizes that this approach should never be the end goal, but rather a means to address specific challenges and opportunities within the organization.

To operationalize this approach, the organization needs to prioritize data. Having clean and accurate data is crucial for effective implementation, whether it involves AI, search, or other aspects of the business. It is essential to determine the source of truth for the data and ensure it is stored in a suitable location.

Additionally, working with API-first vendors and SaaS platforms can greatly facilitate the implementation process. These platforms allow for seamless integration and communication through data and APIs, making it easier to leverage technology and solve business problems.

The speakers also highlight the importance of not trying to solve all problems internally. Instead, organizations should focus on their core business problems and delegate other issues to third-party vendors. This includes concerns like privacy, security, uptime, and scaling. By relying on best-in-breed platforms and outsourcing certain problems, organizations can free up resources to concentrate on their unique challenges.

Tattersall also addresses the question of whether organizations need to fully commit to the headless or composable approach from the start. The answer is no. Organizations can start small and iterate, gradually breaking down dependencies and solving specific business problems. This allows for a more agile and risk-averse approach, avoiding the need for a big bang transformation that carries significant unknowns and risks.

In terms of identifying when an organization should consider moving in this direction, the speakers suggest looking for signs of frustration within the business. This could include a lack of agility, an inability to offer the desired customer experience, or a cyclical pattern of declining website or experience quality. Additionally, platform dependencies can be a source of frustration, as organizations may feel locked into a single platform and unable to control their own destiny.

It is important to start small and solving business problems when implementing a headless or composable commerce approach. By focusing on specific challenges and opportunities, organizations can leverage technology to address their unique needs. This approach allows for greater flexibility, agility, and control, ultimately driving customer satisfaction and business growth.