ICE Model

« Back to Glossary Index

The ICE model is one such framework. ICE is an acronym for visions, associations, and attachments. This model was first introduced in 1996 by Wilson as “an effort to condense the literature of cognitive transformation.” Fostaty Young and Wilson have further developed to define three main stages of learning growth, from beginner to ability to expertise. ICE Scoring Model is an elegant prioritization mechanism that estimates tasks, ideas, and features on three scales. The ICE scoring model is an elegant prioritization mechanism that estimates tasks, ideas, and features in three metrics: influence, reliability, and comfort.

Of course, projects, ideas, and features with the highest ICE score should be prioritized first. ICE is a fast and straightforward way to determine where to focus, but it is problematic in being very subjective.

Agile environments are fast-paced and must make decisions quickly in short development cycles. Decision-makers need to consider as much information as they can without overwhelming themselves. It needs to be balanced, but ICE Model does an excellent job of providing the team with a snapshot of the most valuable activities.


In this model, ideas represent “components of learning.” These can be individual information (definition, facts, process steps) or individual skills (taking equipment measurements, removing disposable gloves.).


In the “Connection” phase, there is a “proper link” between this information and ideas. The process of this link includes “connecting new knowledge with what you already know in a wider scope” (in-course, in other courses, with personal or professional experience of individuals).


Rebuilds the power and knowledge of researchers.

ICE Model Approach

Because ICE models do not require a distinction between areas, they provide a more comprehensive approach to setting up the intended learning outcomes. ICE models support consistency between course elements to understand the meaning of learning. The ICE model provides an easy-to-use common framework for both teachers and students. Fostaty Young suggests that sharing and discussing this framework with students can promote a deeper approach to learning and encourage self-reliance.

The next time a Product manager develops course elements or completely redesigns his course, consider using the ICE framework to address the challenges in new ways.

Benefits of the ICE Model

  • ICE is a quick and easy way to determine which projects should be prioritized. It is so simple that the company might think the model is too simplified.
  • However, if the company multiplies the values, each criterion influences the final result.
  • It makes the difference between reliability 7 and 8 very large, and the final ICE score will show a more accurate relative ranking of the project.
  • However, this assumes that the value is accurate and that the ICE Scoring Model is unstable.

Disadvantages of ICE models

The main drawback of the ICE model is how subjective scoring is. Even in the same project or function, the values of “idea,” “connection,” and “extension” may differ significantly depending on the person.

For example, an executive might think adding new features is very easy, but a development team leader might know the necessary coding time in detail. A product manager may also appreciate his ideas better than others.

Closing Lines

The ICE model’s most significant selling points are speed and simplicity and help product teams narrow down their projects. However, its strength is also a weakness. Because the ICE model only evaluates the impact of an item on a single goal, organizations with multiple goals simultaneously will not be able to match the capabilities of other models. ICE model is a clever way of slimming things down, providing relative comparison points to decision-makers, even though they lack nuances and complexity. Moreover, when a product manager is trying to get a consensus, it can be as helpful to exclude something to decide which item is better.

ICE Model
Scroll to top