Enter Cost of Delay Data

Answer key questions about your features to surface assumptions and determine their cost of delay and duration.

❕ Among all your features, unit of time should be consistent, so choose either "week" or "month" and stick with that value.

if the CCID isn't unique to each choice, we won't be able to link the finalized item setup attributes for those styles to the correct choice rows in a MAP Buy

when current retail value is null in MDM, we pull original retail, which impacts our POs

I have more than 12 programs in my assortment

Would like to see a sum of the number of choices that are listed in the buy plan portion of MAP in the aggregations summary vs having to manually count and see if I have enough or have over-choiced.

I get an error when I try to add a choice and the vendor field is populated.

I use the group choices by function in every single buy plan, but it goes away when you get to the weekly receipts. Can we have it show up there + on the buy plan when you export into Excel?

Product attribute values don't tell me enough (dept, class, selling channel)

When a KP2 is not attached to a program, the calculation comparing KP2 to my buysheet is wrong

IMU subtotal calc is incorrect

Better attached KP2 indicator

Really annoying to have to open vary dates but scroll for days to try and manipulate the dates by cluster. Would rather open vary dates and have the column open as wide as it can.

As Read Only viewer, we cannot see the entire style name for the style. Hovering over doesn't show the style name and also cannot click on the style. We have to export to see what the style name is.

Problem to Solve

if the CCID isn't unique to each choice, we won't be able to link the finalized item setup attributes for those styles to the correct choice rows in a MAP Buy

What is the idea/problem/opportunity?

What type of benefit does it provide?

How will it generate this benefit?

Cost of delay

per (unit of time)

What are any assumptions that need to be tested?

Duration of effort

⁠

About the four types of value:

Increase revenue

This type of revenue is often related to attracting new customers, or more revenue from existing customers through the development of new products, services, or entering new markets.

Protect revenue

This type of value is to lengthen the life-cycle of current revenue streams, and avoiding current revenue streams from falling. Investment here does not generate new revenue, it protects the revenue we already have.

Reduce costs

This type of value looks to reduce any costs we are currently incurring.

Avoid costs

This type of value captures the costs we could incure in the future, and putting measures in place to avoid them. The easiest example of this are features that need to be completed by some date in order to avoid regulatory fines.

"Cost of delay" + "per (unit of time)"

This figure represent how much value is lost per unit of time by not having a feature in the market.

⁠

Cost of Delay Results⁠

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.