Optimizing the IT Project Portfolio at a Global News Company.

About the Client

Company N is a global news and information company.

Industry Context

For a global financial news and information publisher, accurately tagging and extracting the entities inside its own content — companies, executives, organizations, brands, public figures — is core infrastructure, since customers rely on that metadata to search, filter, and monitor coverage relevant to them. By the early 2010s, most large IT organizations had matured well beyond simple annual budgeting toward formal portfolio management approaches for prioritizing competing technology investments, since inconsistent project selection routinely led to the budget variances Company N’s IT Department was experiencing. Nine-box scoring grids plotting criteria such as customer impact against implementation difficulty had become a widely used visual way to make the relative project value defensible and easy to communicate to executives making funding decisions.

Current Situation

The company made substantial capital investments every year in its technology infrastructure and software, but actual expenditures often deviated widely from the original budget, due in part to competing priorities and an inconsistent approach to evaluating and selecting projects. Iknow, which had done several previous assignments for the company, was asked to help standardize the process of reviewing and selecting new IT projects.

• Significant budget variance year over year. Actual IT expenditures varied widely from the annual budget, driven in part by competing priorities across the organization.
• No standardized project evaluation approach. No consistent, standardized approach existed for evaluating and comparing proposed IT projects.
• Fundamentally different project types compared inconsistently. Different types of projects — strategic, foundational, and revenue-generating — had fundamentally different goals and evaluation criteria, making a single universal comparison misleading.
• No defensible basis for executive funding decisions. Senior business and technology executives needed a clear, defensible way to select which of many proposed projects should receive funding.

• Develop standard templates and metrics for describing and evaluating proposed IT projects consistently.
• Define and document the full set of candidate projects, including objectives, benefits, activities, deliverables, technical effort, and timeline.
• Group projects into meaningful categories reflecting their distinct goals and evaluation criteria.
• Facilitate an executive workshop to evaluate, rank, and select the projects for the coming year’s budget.

How Iknow Structured the Work

Iknow structured the engagement around standard templates and metrics, full project documentation, category-based grouping, visual scoring, and a facilitated executive workshop — reflecting Iknow’s enterprise technology strategy and roadmapping methodology for turning competing, differently shaped investment proposals into one defensible, prioritized portfolio.

Key Activities & Decisions

• Standard templates and evaluation metrics. Iknow developed standard templates for describing proposed projects, enabling apples-to-apples comparisons, and defined metrics for evaluating projects, including alignment with mission, goals, and strategy; alignment with customer expectations; cost; revenue generation; ROI; and time sensitivity.
• Full project documentation. IT project owners described their projects’ objectives, benefits, activities, deliverables, degree of technical effort, and timeline; 32 projects were defined.
• Three-category classification. Iknow grouped the projects into three distinct categories: Vision Shaping Projects, establishing top-down, strategic direction for the company’s metadata architecture; Foundational Projects, providing infrastructure supporting core data, content, and governance processes; and Revenue Enhancement Projects, generating new or expanded revenue from new or improved products and services.
• Nine-box scoring grid. Iknow developed a nine-box scoring grid to visually rank projects within each category along two selected evaluation criteria.
• Executive prioritization workshop. Iknow facilitated a day-long workshop with senior business and technology executives to establish consistent project definitions, propose new projects, agree on a common evaluation framework, and select the highest-rated projects for the roadmap; 13 projects were ultimately selected for the final portfolio.

Stakeholders & Collaboration

Iknow served as prime contractor, working with IT project owners across the organization and facilitating direct collaboration with senior business and technology executives, building on the trust established through several previous Iknow engagements with the company.

Comparing Fundamentally Different Types of Projects Fairly

Strategic direction-setting projects, infrastructure investments, and revenue-generating initiatives serve genuinely different purposes, and forcing all 32 candidates onto a single universal scale risked misleading apples-to-oranges comparisons. Iknow addressed this by explicitly grouping the projects into three distinct categories with tailored goals and criteria, then evaluating projects within each category rather than against the full, mixed slate.

Turning Subjective Priority Judgments Into a Transparent, Defensible Process

Without a shared framework, competing priorities across departments risked being resolved by whoever argued most persuasively rather than by consistent criteria. Iknow addressed this by building a structured nine-box scoring grid that visually plotted projects along consistent criteria, paired with a facilitated day-long workshop that gave senior business and technology executives a shared, transparent basis for evaluating and selecting projects together.

Quantitative Outcomes

• Projects assessed: 32 candidate projects defined and evaluated.
• Categorization framework: Three distinct project categories established: Vision Shaping, Foundational, and Revenue Enhancement.
• Scoring methodology delivered: A nine-box scoring grid developed for visual relative ranking within each category.
• Final portfolio selected: 13 projects ultimately selected for the final project portfolio through a day-long executive workshop.
• Engagement duration: Four-month assignment.

Qualitative Outcomes

The Information Technology Department now has a standard process for describing, evaluating, and selecting improvement projects, and capital investment and resource allocation decisions are made consistently — direct evidence the engagement produced a durable, reusable capability rather than a one-time project list. By grounding project selection in explicit categories, consistent metrics, and a transparent scoring methodology, the framework gave Company N’s executives a defensible way to resolve competing priorities that had previously driven significant budget variance.

Timeline to Impact

Within the four-month engagement, Iknow moved Company N’s IT Department from an inconsistent, variance-prone annual budgeting process to a standardized framework, culminating in a workshop-selected 13-project portfolio ready for the coming year’s budget.

Core Skills

• IT portfolio prioritization and investment decision-making
• Metadata and content architecture strategy
• Executive workshop facilitation
• Project evaluation framework design

Methods & Frameworks

• Standardized project templates and evaluation metrics
• Nine-box scoring and ranking methodology
• Multi-category project classification

Technologies & Tools

• Metadata and content architecture planning
• Project portfolio scoring and visualization