From Assessment to Action: When Strategies Move Beyond Paper

Across ministries, holding companies, and large organizations, assessments are conducted and detailed reports are prepared. Yet months later, it is not always clear how many of the identified problems have actually been resolved.

  • How many of the problems identified in the last assessment have actually been resolved?
  • What risks does this weakness create for the organization?
  • What actions must be taken, by whom, and by when?
  • How can the next assessment show whether the situation has genuinely improved?

Assessment Should Not Be the End of a Project

In the traditional view, IT assessment is often a periodic activity. A team of specialists reviews the current state, calculates scores, prepares a final report, and presents the findings to management.

From a management perspective, however, this is only the starting point. The purpose of an assessment is not merely to identify problems; the organization should be able to make better decisions based on what it learns.

For example, if an assessment finds that a company is weak in IT service continuity management, management needs to understand the risks this creates, which strategic objective the issue affects, what corrective actions are needed, who is responsible for follow-up, and how the next assessment will measure actual improvement.

An assessment creates value when it connects the current state, strategic objectives, and executive actions.

Without Knowing the Current State, Strategy Can Become an Aspiration

Digital transformation, stronger security and resilience, higher productivity, better service quality, lower costs, and data-driven decision-making are among the goals found in many organizations’ strategic plans.

Yet subsidiaries and affiliated organizations are not equally prepared to achieve these goals. Imagine a holding company that prioritizes intelligent technologies and data analytics, while its assessment finds that several subsidiaries still face serious issues with data quality, system integration, or foundational infrastructure.

In that situation, it would not make sense to require every company to launch advanced artificial intelligence projects at the same time. Some may first need to improve their infrastructure and data quality, while more mature organizations can begin advanced intelligent technology projects.

Strategy defines where we want to go; assessment shows where we stand today.

Bringing the two together makes it possible to design a more realistic path forward.

From Assessment Results to Clear Mandates

One of the challenges of IT management in ministries and holding companies is turning assessment results into clear executive expectations for affiliated organizations.

A report stating that a company scored poorly in information security is a useful starting point, but it is not enough to create change. The company needs to know exactly what it is expected to do.

For example, if an assessment identifies weaknesses in backup and data recovery management, the mandate could include reviewing the backup policy, setting recovery objectives, conducting periodic tests, and documenting the results.

If a company has poor IT service management, priorities might include defining an incident management process, setting service-level indicators, or establishing a system to register and track service requests.

At this stage, the question changes from “What is wrong?” to “What must we do to fix it?”

Feedora Connects Assessment with required actions

After each technical assessment cycle is completed, its results are made available to authorized management levels. A holding company can review the assessments of its subsidiaries, compare their status, and see how it has changed over previous cycles.

This information helps identify weaknesses, risks, and corrective needs. Feedora’s Assessment Mandates feature also allows a holding company to register a specific mandate document for each company and assessment cycle and make it available to that company.

In multi-level structures, access is defined according to organizational roles. Intermediate holding companies can view information about their own subsidiaries, while the parent holding company has a broader view of the organizations under its supervision.

Each company’s mandates are recorded in connection with its relevant assessment cycle, making it easier to refer back to that cycle’s results and supporting documents.

Assessment results are not published only to inform managers; they can also provide a basis for requiring corrective action from companies.

The Action Plan: Where the Company Takes Ownership of Improvement

Once mandates have been issued, the company must explain how it intends to carry them out. A useful action plan should go beyond broad statements such as “improve information security” or “upgrade technology infrastructure.”

For each action, it is helpful to specify the activity, the person responsible, the schedule, the required resources, the expected output, and the indicator that will be used to measure success.

For example, if a company is asked to improve its readiness for data recovery, its action plan could include the following steps:

  • Identify critical systems and information
  • Set recovery time objectives and acceptable data loss limits
  • Review backup policies and procedures
  • Conduct a practical data recovery test
  • Document the results and address the identified gaps

After receiving its mandates, a company can upload its action plan to Feedora as a PDF document. The company and authorized management levels can view the document, which remains associated with that assessment cycle. The company can also replace the document when an updated version is needed.

Assessment results → issued mandates → company action plan

This connection records the holding company’s expectations and the company’s proposed response in one defined place.

When the Action Plan Aligns with Organizational Strategy

This process creates the greatest value when mandates and action plans are not designed merely to raise an assessment score. Their purpose should be to address problems that affect the organization’s ability to achieve its strategy.

If the holding company’s strategy is to increase operational resilience:

Actions related to security, backup, data recovery, and service continuity become more important.

If the strategy is to improve productivity and control costs:

Actions related to infrastructure optimization, IT asset management, and better service processes should receive attention.

If the strategy is to expand intelligent technologies:

Actions related to data quality, information architecture, system integration, and workforce capabilities may become priorities.

In this view, assessment helps identify the gap between the organization’s current state and the capabilities it needs to achieve its strategy.

Every mandate should address a real need, and every action plan should move the organization one step closer to its strategic goals.

The Next Assessment: Have We Actually Improved?

After action plans have been carried out, senior management should ask: Did the actions produce the expected results? Preparing an action plan or completing a project does not automatically mean that the situation has improved.

A company may purchase new equipment and still experience service outages. A new system may be launched without improving user satisfaction. Security measures may be introduced while the main risks remain.

That is why the results of corrective actions should be reviewed in later assessment cycles. By comparing periodic assessments, Feedora helps managers see how the status of companies changes over time.

For example, if a company’s score in IT service management rises from 45 to 70, this may indicate improvement. To confirm the effectiveness of its action plan, however, the evidence of completed activities and the factors behind the score change should also be reviewed.

Periodic comparison shows what changed; reviewing the evidence helps determine how much of that change resulted from the actions taken.

From Managing One Company to Governing Dozens of Organizations

This process becomes even more important for ministries and holding companies. A ministry may oversee dozens of organizations, institutions, banks, and companies, each with different conditions, problems, and priorities.

Without a defined structure, tracking assessment results, mandates, and action plans can turn into scattered correspondence, multiple files, and reports that cannot be compared.

When this information is recorded in a shared platform, senior management can establish a clearer link between assessment results, issued expectations, and the plans proposed by each company.

Analysis across multiple organizations can also reveal common weaknesses that require decisions at a higher level. For example, if several companies have similar information security gaps, a shared holding-company program may be more effective than separate, disconnected efforts.

At this point, assessment moves beyond reviewing one company and becomes a tool for governing IT across the wider group.

A Management Cycle, Not a One-Time Report

The idea can be summarized as a continuous cycle:

  • Organizational strategy and objectives
  • Assessment of the current state
  • Identification of gaps and risks
  • Setting priorities
  • Issuing mandates
  • Preparing action plans
  • Implementing actions
  • Reassessment and measurement of improvement

This cycle helps connect long-term objectives with day-to-day activities. Assessment helps establish the current state; mandates define the required changes; action plans propose how to make them; and later assessments make it possible to review what has changed.

Implementation, project progress control, and measuring strategic outcomes still require management accountability, defined indicators, and follow-up mechanisms. By bringing assessment results, mandate documents, and action plans together, Feedora provides an important information foundation for supporting this cycle.

Closing: The Value of Assessment Lies in the Change It Creates

A ministry or holding company may receive hundreds of pages of IT assessment reports each year. Their real value is not determined by the number of pages, charts, or even the precision of the scores.

Their value becomes clear when management can answer a few questions: What problems were identified? What mandates were issued to address them? What plans did the companies submit? Which actions were actually completed? And how much has IT improved compared with the past?

By connecting assessment, mandates, and action plans, Feedora helps turn assessment results from management reports into a basis for progress and improvement.

The ultimate goal is not simply for organizations to know where they stand today. They should know where they need to go, what actions will take them there, and how they can measure their progress.