Understanding Asymmetric Modernization

[fusion_builder_container hundred_percent=”yes” overflow=”visible”][fusion_builder_row][fusion_builder_column type=”1_1″ background_position=”left top” background_color=”” border_size=”” border_color=”” border_style=”solid” spacing=”yes” background_image=”” background_repeat=”no-repeat” padding=”” margin_top=”0px” margin_bottom=”0px” class=”” id=”” animation_type=”” animation_speed=”0.3″ animation_direction=”left” hide_on_mobile=”no” center_content=”no” min_height=”none”][slideshare id=43523587&doc=asymetricmodernization-150114151419-conversion-gate01]
Over the past two years Red Pill Development has steadily evolved its non-traditional approach to modernizing large portfolios of Notes applications using what we call Asymmetric Modernization. This journey started while working on the Transformer technology at GBS. While technically brilliant, Transformer failed to meet the commercial goals of convincing people to use the technology as a replacement for Notes client applications. After we decided to step back and take a fresh look at Transformer we realized that the mission itself was flawed. People didn’t want platform migration they wanted application modernization. Fidelity with the Notes client needed to go from being a primary goal to being a key reason NOT to do something! Not only that, but an approach was needed that would scale to the large numbers of applications typically found. And so it came to pass that four IBM champions (Keith, Nathan, Peter, and Tim) developed the concept of Asymmetric Modernization .

Since forming Red Pill Development in 2012 to build tooling and consulting services that supports this new approach the concept has evolved considerably. In my last blog entry I outlined the math that supports the need for this approach and the compelling numbers asymmetric modernization can deliver. The enclosed presentation above outlines the latest thinking on what defines the asymmetric approach and makes the outcome so different when attempting to modernize a large (> 100) portfolio of Notes applications.

With an estimated 80% of the current installed based of Notes users actively looking for something else to replace the Notes client it is important that a way be found for these organizations to move forward. The alternative is for organizations to do nothing allowing the gap between — (1) what Notes client applications deliver and (2) what the users of these applications expect — to grow.

In answer to the question we probably get asked the most…. No, you don’t need 100 applications. The approach will work with just one application, it is just that the cost savings start to become orders of magnitude better when reaching numbers above 100.

[slideshare id=42992292&doc=modernizationmath-141224113933-conversion-gate02]


Peter Presnell
Peter Presnell
CEO at Red Pill NOW. Strategist, technologist, blogger, presenter, and IBM Champion 2011/12. For years many companies have invested heavily in the Notes/Domino platform and I see my role as helping to find paths forward for that investment.


  1. in case you have thousand + applications I assume the job cannot be performed by Red Pill. What options do you have then? Re-use the framework you have developed?

  2. Peter Presnell says:

    @Patrick… We are working with customers with 1,000+ applications. Asymmetric modernization has no limits to the number of applications it can modernize. These same customers have quotes of between $20 million and $40 million to modernize their applications using traditional approaches. In most cases the option to not using Red Pill is to do nothing until that magic button finally turns up next to a crock of gold at the end of your nearest magic rainbow where the unicorns play.

Leave a Reply to Patrick Kwinten Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.