Growth Series BLOG

Its a Premium BLOG template and it contains Instagram Feed, Twitter Feed, Subscription Form, Blog Search, Image CTA, Topic filter and Recent Post.

All Posts

Agile Taxonomy Development - an Oxymoron?

Product Taxonomies, on the whole, are iterative in nature. If your company starts selling products it's never sold before, you might need to add new taxonomy. Are customers or site metrics saying your navigation is bad? New taxonomy. 10,000 products in one miscellaneous category? More new taxonomy!

An agile methodology seems at first to fit in nicely. After all, you're maintaining these categories in a very dynamic environment where priorities might shift, actual changes are being made all the time and the cost of rework can be high. There is a lot of collaboration among product managers, product data teams, merchandisers, IT, management and more. According to the tenants of Agile, it's a perfect match.

Except it's not. In Agile, each iteration (or sprint) is empirical and followed by feedback from the business. In other words, you may deliver changes to a product category that may be followed by suggestions to make additional changes to that same category in the next sprint. In the world of taxonomy maintenance, incorporating this feedback won't reduce the cost of rework because the downstream effects of those changes remain the same. More products will need to be categorized or re-categorized. Those products will then need to be tagged and their attributed data populated. The changes made during each iteration are defined and need to be repeated each time, which relates much more closely to traditional project management principals than Agile. Also, because taxonomy maintenance is ongoing the lowest priority tasks won't be removed from the project altogether and will instead be scheduled for a later date. After a short while, you may find your project teams are running traditional increments that just keep growing in scope rather than actual agile iterations. 

Your teams can borrow elements from Agile without having to upend the way projects are managed now. For example, holding cross-team meetings to present taxonomy changes is a great practice, but force-fitting an Agile methodology where it doesn't belong may cause more harm than good.

Earley Information Science Team
Earley Information Science Team
We're passionate about enterprise data and love discussing industry knowledge, best practices, and insights. We look forward to hearing from you! Comment below to join the conversation.

Recent Posts

Designing AI Programs for Success - a 4 Part Series

Recorded - available as on demand webcast AI is plagued by inflated and unrealistic expectations due to a lack of broad understanding of this wide-ranging space by software vendors and customers. Software tools can be extremely powerful, however the services, infrastructure, data quality, architecture, talent and methodologies to fully deploy in the enterprise are frequently lacking. This four-part series by Earley Information Science and Pandata will explore a number of issues that continue to afflict AI projects and reduce the likelihood of success. The sessions will provide actionable steps using proven processes to improve AI program outcomes.

The Missing Ingredient to Digital Transformation: Scaling Knowledge Communities and Processes

The holy grail of digital transformation is the seemingly conflicting goals of high levels of customer service and pressure to reduce costs. “Digital Transformation” has become an all-encompassing term – in a piece in this column about customer data platforms, I asked whether the term has lost its meaning: The phrase “digital transformation” can mean anything and everything — tools, technology, business processes, customer experience, or artificial intelligence, and every buzzword that marketers can come up with. Definitions from analysts and vendors include IT modernization and putting services online; developing new business models; taking a “digital first” approach; and creating new business processes, and customer experiences. The overarching objective of a digital transformation program is to improve end-to-end efficiencies, remove friction from information flows, and create new value streams that differentiate a company’s offerings and strengthen the customer relationship. Having assisted large global enterprises with building the data architecture, supporting processes, and governance for multiple digital transformations, in my experience, there are two broad classes of initiatives that seem to get funding and others that miss the boat in terms of time, attention, and resources.

4 Reasons B2B Manufacturers need Strong Product Data

There are many manufacturers who have started to take the leap forward in the digital space, but there are still a great number who rely solely on their distributors to manage their product data. We are going to look at 4 key reasons why its so important that manufacturers own their product and dedicate the time and resources to build it out.