Currently an independent consultant, Pradeep Henry is known for his contribution to the fast transformation of a promising venture into Cognizant Technology Solutions, where he was previously employed as director. His contribution (1996-2007) involved devising and executing three strategic themes, which included software practice innovations that delivered differentiated customer value.

Henry is the creator of a method for strategy translation in software projects. He has written a book (draft) on strategy translation and contributes to international strategy conferences. A member of the Strategic Management Society, Henry received executive education at Columbia Business School, and that included Rita McGrath's program "Leading Strategic Growth and Change."

Since 1987, Henry has been been engaged in various roles in more than 500 software projects executed for more than 150 organizations, including the likes of AAA, DHL and IBM.

Henry is recognized for advancing software practice (at company, national and industry levels) through his innovations and change initiatives. He’s been interviewed by CIO India, TrendHunter Canada, Forrester Research USA and several media organizations. His works have received favorable reviews by ACM, IEEE and other organizations.

You can find Henry's website at, and he can be reached at

The opinions expressed in this blog are those of Pradeep Henry and do not necessarily represent those of IDG Communications Inc. or its parent, subsidiary or affiliated companies.

Articles by Pradeep.Henry

Strategy Translation

How to enable SDLC for strategy translation

SDLC is not just a method for engineering. It is where strategy translation can take place. So it's critical for CIOs to ensure that their SDLC is enabled for strategy translation. We need 3 broad changes to SDLC. Make strategic outcomes the goal. Set up business-centric discovery and design. Check for strategic outcomes.
May 23, 2016
Strategy Translation

2 things that determine your project’s strategic potential

Discovery and design determine whether or not your software or technology project has the potential to eventually generate strategic outcomes. If you are considering executing a project, use a discovery and design method that is driven by business strategy.
April 27, 2016
Strategy Translation

Why your IT strategy may not help translate business strategy

Strategy translation in software practice is about ensuring strategic potential before investing in technical and business change implementation. Such a critical activity must get its inputs directly from your organization’s overall business strategy rather than from a potentially "siloed" IT strategy.
March 28, 2016
Strategy Translation

If tech implementation is not the first thing to focus on, what is?

To execute business strategy through technology, start with a focus on strategy translation. Make the Business phase of software practice a strategy translation phase, rather than just a requirements analysis phase. Ensure that what you would eventually implement, deploy, and use has strategic potential.
February 3, 2016
Strategy Translation

Why the business phase of software practice needs improvement

Software practice has been continually improved. Yet, the C-suite is disappointed due to technology’s poor contribution to organizational strategic agenda. The reason: we made strategy-related improvements in IT governance, but we did not make strategy-related improvements in software practice.
January 11, 2016