The Human Blueprint of a Winning Scorecard
Overview Have you ever encountered a situation where a very scorecard which is fully developed, is rejected by an organization due to one or two variables are not usable due to incompatibility with...

Source: DEV Community
Overview Have you ever encountered a situation where a very scorecard which is fully developed, is rejected by an organization due to one or two variables are not usable due to incompatibility with their current systems? In order to ensure that there is smooth development and implementation of a scorecard, the collaboration between IT, risk management(strategy and policy), modeling, validation, and operational staff is crucial. This collaboration not only creates better scorecards, it also ensures that the solutions are consistent with business direction, prevent surprises, and enable education and knowledge transfer during the development process. Development of scorecards in isolation can lead to problems such as inclusion of characteristics that are no longer collected, legally suspect, or difficult to collect operational, exclusion of operationally critical variables, and devising of strategies that result that are unimplementable. Different personas are involved in a scorecard dev