Helping CIOs, CDOs, and Transformation Leaders translate strategy into outcomes


If your digital/business initiative does not deliver strategic outcomes, your CEO will likely consider it a failed initiative. Henry created a strategy translation process that takes your initiative from corporate strategy to an architecture that blends necessary technology and business innovations. Henry also created powerful practical tools to help you apply this process. Now organizations can have a predictably strategic architecture before they make further investments. Tools include an eBook on strategy translation and nearly 30 articles as a CIO Contributor. Henry also contributes to international conferences hosted by Strategic Management Society. He received exec education at Columbia Business School NYC and that included McGrath's strategy program.

Turbo-boosted Cognizant's growth by creating competitive differentiation

1996-2007 Cognizant

Cognizant was tech-centric like its competitors. Henry differentiated Cognizant by bringing crucial new perspectives to its software practice. First, he introduced user-centric design methods, which Indian competitors didn’t have. Then he introduced business-centric design methods, which its international competitors also didn’t have. Used in 450+ projects, these innovations delivered new value to customers – spiking customer acquisition and retention, thus turbo-boosting Cognizant’s growth.

Brought user-centric skills to tech-centric Indian IT industry

1996-2007 Indian IT indusry

Indian IT industry was tech-centric and didn’t have world-class user-centric design skills that customers wanted. Henry brought user-centric design education through 7 annual national conferences that featured over 15 international speakers. Over 1000 participants from 100 companies learned.

Repositioned global technical writers for prominent new role

Late 1990s Technical writers worldwide

Tech writers worldwide had a task-driven method. Henry created for them a software usability driven method and published it in a book. According to R. L. Upchurch, ACM Computing Reviews, Henry's 1998 book "advocates a view that gives the technical writer a more prominent role in life cycle activities ... Technical writers educated in the model (described in the book) would be valued members of a development team." UNISYS USA and others trained their tech writers to use the method.

Upgraded TCS' copyediting practice to technical writing practice

1989-1996 Tata Consultancy Services (TCS)

In the late 80s, user interfaces were not as intuitive as they are today. User manuals were therefore important for customers, but TCS didn’t have the needed technical writing capability. Henry set up a technical writing group, wrote a book called User Documentation Handbook (for internal use), and trained and created technical writers.