Aligning IT Projects With Corporate Strategy and Stakeholders
This paper examines two interconnected dimensions of effective project management: the strategic alignment of IT projects with corporate goals, and the communication strategies needed to keep stakeholders engaged. Drawing on guidance from the National Computing Center (UK), the paper outlines a seven-step alignment plan designed to synchronize IT infrastructure with business functionality. It then addresses stakeholder communication, arguing that different stakeholder groups require tailored methods — distinguishing between "push" and "pull" communication approaches based on stakeholders' levels of interest and influence. Together, these topics highlight how strategic coherence and proactive communication are essential to project success.
- Introduction: IT Projects and Organizational Strategy: IT alignment with strategy prevents project failure
- Why IT–Business Alignment Fails: Technology-first design creates rigid, ineffective IT structures
- A Seven-Step IT Alignment Framework: NCC's seven steps to synchronize IT with business
- Keeping Stakeholders Engaged and Informed: Communication is essential to perceived project success
- Identifying and Prioritizing Stakeholders: Three steps to map stakeholder interest and influence
- Push vs. Pull Communication Strategies: Matching communication methods to stakeholder power levels
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- Clearly connects two related project management challenges — strategic alignment and stakeholder communication — into a unified argument about project success.
- Uses a concrete, numbered framework (the NCC's seven-step plan) to ground abstract strategic concepts in actionable steps.
- Distinguishes between stakeholder types and maps specific communication methods to each, demonstrating applied analytical thinking.
Key academic technique demonstrated
The paper demonstrates source integration at the sentence level, weaving cited claims from Beveridge and Nielsen directly into the argument rather than simply summarizing them. This technique strengthens the analytical voice while maintaining appropriate attribution, a hallmark of competent undergraduate academic writing.
Structure breakdown
The paper is organized into two thematic halves. The first addresses IT–business strategic alignment, progressing from the problem (misalignment causes failure) to the cause (technology-first design) to the solution (the NCC's seven-step plan). The second half shifts to stakeholder communication, moving from the importance of communication, through stakeholder identification, to a practical push/pull framework. The conclusion is embedded within the final section rather than standing alone.
Introduction: IT Projects and Organizational Strategy
IT is an integral part of business operations, helping organizations enhance their productivity, standardize processes, reduce operational costs, and implement business strategies. It is crucial, therefore, that IT projects align with an organization's corporate strategy and that the two are synchronized toward the accomplishment of organizational goals. Lack of synchronization between projects and business strategy has been identified as one of the leading causes of project failure (Beveridge, n.d.). IT projects often require large amounts of initial capital, and as long as they are not in line with the overall corporate strategy, there is a significant risk that they will be cancelled prior to completion — whether because they deliver fewer features than intended, exceed the budget, or produce outputs that are never used.
Why IT–Business Alignment Fails
Even the most established companies are finding it increasingly difficult to align their IT projects with their corporate strategies. The National Computing Center (NCC), UK, attributes this difficulty to the fact that IT strategies are mostly designed to focus on technology products rather than on business outcomes — resulting in rigid and ineffective infrastructures. The NCC identifies a need for businesses to adopt a new approach that focuses on fitting IT structures into business functionality, and not the other way around.
A Seven-Step IT Alignment Framework
To address this challenge, the NCC proposes a seven-step alignment plan (Beveridge, n.d.):
i) Understanding the business by undertaking a review that seeks to identify and document all projects currently ongoing, as well as those completed in the previous financial period.
ii) Understanding the organization's culture by analyzing its nature, ethos, and structure.
iii) Analyzing all IT delivery channels, applications, and assets.
iv) Analyzing the relationship between the IT estate and the overall business.
v) Understanding the implications, contributions, and impacts of the IT estate on the company.
vi) Identifying high-priority projects and developing an implementation timeline for each.
vii) Translating the timeline into business unit plans and determining the cost requirements for those plans.
Keeping Stakeholders Engaged and Informed
Adequate communication is the only way to keep stakeholders informed and, consequently, engaged. One cannot be engaged in a project without being informed about its processes, progress, and implications. In this regard, project "communications are a critical deliverable of every successful project" (Nielsen, 2014, n.pag.). Very often, projects are perceived as failures despite having delivered on their promises; this is mostly because the project manager did not adequately communicate its success to stakeholders (Nielsen, 2014).
Notwithstanding the undeniable importance of project communications, it would be inappropriate to provide a single, uniform form of communication for all stakeholders. Individual stakeholder groups have different information requirements, and what is preferred by one group may not be preferred by another. There is therefore a need to identify different stakeholder categories and define both the communication method and the type of project information that best suits each category.
References
Beveridge, C. (n.d.). Guidelines for IT management: Aligning IT with business strategy. National Computing Center (NCC).
Nielsen, D. (2014). Project communications: How to keep your team engaged and informed. Projects Smart.
Always verify citation format against your institution’s current style guide requirements.