Cost of Delay Results

❕ For the results to be valid, the unit of time measure should all be consistent and the cost of delay normalized to that time frame. For example, all values in the column should be "7 days" or "30 days".

Problem to Solve

Cost of delay

per (unit of time)

Duration of effort

CD3 Score

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.

There are no rows in this table

⁠

About CD3 Score

CD3 is an abbreviation of "Cost of Delay Divided by Duration"

⁠

When we have a collection of potential feature and their CD3 scores, the CD3 score tells us know which option should be delivered first. It does this by considering which feature incurs the largest cost of delay (the cost we incur as long as the feature is not available) compared to how quickly it could be delivered.

About Cost of Delay

The first thing you may have noticed is that entering data for Cost of Delay asked a lot more questions about your features. The reason for this is that a lot of discussions around value include assumptions. The questions help individuals and groups come to a clearer common understand of a feature, and a better understanding of the value of doing it.

Another change is switching from the looking at the value a feature provides, and instead the value that is lost by not having a feature.

This more advanced technique is not to be used in all situations. If you can make a good enough prioritization decision without discovering the cost of delay and CD3 score for every feature, you should do it. Use cost of delay between a small set of items, or when the stakes are high, to get very precise guidance on sequencing features.

⁠

Cost of Delay & CD3 Links

⁠

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.