An anti-pattern is a common response to a problem that looks like a great idea but usually ends up making things worse.
An anti-pattern doesn’t mean it will also fail, but it does mean it is higher risk and so you should be cautious when using it. Some examples of Information Product Anti-Patterns are:
Information Product is just a report.
While a Information Product often results in a report or dashboard, into todays modern agile data world, it can more often than not be a data service that provides data via an API, a set of resuable metrics, sharing of datasets or an analytical model that creates a score on demand.
One Information Product to rule them all.
One of the goals of the Information Product pattern is to define a set of boundaries which enable it to be delivered in a small number of iterations. If your Information Products are massive, then this will be difficult. So a Information Product of “Customer Life Time Value” should probably be decomposed into smaller Information Products, for example Customer Revenue, Customer Cost, Customer or Product Margin, Customer Propensity to Churn and finally Customer Life Time Value.