FR EN
AEES

AEES Executive Certificate in Information-systems governance

Judge an IS portfolio, an access right and technical debt. This AEES certification attests information-systems governance.

  • AssessmentProfessional assessment
  • Attempts2
  • PreparationIncluded
  • France
  • Canada
Description

Information-systems governance

A vague familiarity with “Information-systems governance” is no longer enough. This belongs with Cybersecurity and sovereignty. You hold cyber risk, the information system, privacy and continuity. People are hired to decide, not just to name the topic. This AEES certification is for professionals, managers and leaders who want to judge an IS portfolio, decide an access right and limit technical debt. No diploma is required. What is required is a working command of written French, and the will to show the subject on a real file, in a company, a public body or a partner organisation.

You are not joining a long degree. You take “Information-systems governance” seriously enough to use it, and seriously enough for someone else to read it on a file. Everything happens online, around a job you already have. You prepare if you need to, then you sit a professional assessment. The AEES Executive Certificate, if it is issued, is proof in your name, and it can be checked. It holds in a CV, a move or a cooperation. It is a short specialisation, issued by a higher-education institution. You see at once what you are buying: a targeted title, not a course catalogue.

Afterwards you can carry “Information-systems governance” into a team, a file or a new responsibility, and explain your choices to a manager, a funder or a partner institution. Others will see that you can judge an IS portfolio, decide an access right and limit technical debt, including outside your own organisation. If you succeed, AEES issues an AEES Executive Certificate in your name, with a unique serial number that can be checked in the public register. The award stays in your workspace. It shows a professional judgement you have demonstrated, useful for a CV, a new post or work in common.

Skills

What this certificate attests

The capabilities the assessment attests if you pass.

  • Judge an IS portfolio
  • Decide an access right
  • Limit technical debt
  • See the risk of a system nobody understands anymore
  • Hold the vendor to the result
  • Decide who cuts
ESCO classification — European Skills, Competences, Qualifications and Occupations

ESCO, the European skills vocabulary

This is the European Commission’s classification of skills, competences, qualifications and occupations. This certificate is linked to it through the skills below. Each link opens the official record.

Knowledge & research

Related scientific readings

Scientific readings related to this certificate.

Preparation included

To prepare for the assessment

After purchase, a preparatory course is available: 6 written modules, without an instructor, at your own pace. You are not required to follow it before opening the assessment. Each module sets out the notions, a commented case, the points to keep and a FAQ. It covers Portfolio, Business demand, Access and Debt.

When you are ready, you enter the assessment: a file already open, incomplete facts, conflicting views. You move through successive decisions. This is not a full taught programme with pedagogical supervision.

Structured written course

Notions, objectives and concrete examples, organised progressively.

Applied case

A commented professional situation to anchor the theory.

FAQ and preparation

Frequent doubts, then questions to go further on your own.

  1. Portfolio: Decide which system lives, which one stops An IS portfolio is the practical list of systems, platforms, and services your organization pays for and relies on to operate. It includes customer facing products, internal applications, data platforms, integrations, and the shared infrastructure that binds them. Governance of that portfolio is about deciding where money, attention, and risk will go next. It is not a theoretical exercise. It sets who gets funded, who is maintained, and who is sunset. In a busy organization, portfolio choices compound. A small deferment today becomes higher run cost and lower agility next year. A vendor left unmanaged drifts from promised outcomes. A system without a clear owner gathers technical debt that turns into outages. Governance exists to stop drift. It sets criteria, runs a cadence, and records decisions in a way that can be explained to executives, auditors, and the people who have to execute.
  2. Module 2/6, Business Demand Every organization generates more ideas and requests than it can fund or deliver. Unfiltered demand clogs backlogs and blurs accountability. This module shows how to shape raw requests into decisionable packages that can be prioritized against strategy, risk and capacity, instead of becoming endless tickets. You will learn a practical path from intake to choice. You will distinguish incidents from demand, frame value in business terms, size options at the right fidelity and use transparent criteria to recommend a course of action. The result is a traceable decision and a delivery agreement that can be governed.
  3. Module 3/6, Access Access governance is the daily discipline of deciding who can do what in information systems, then proving those decisions remain correct over time. The public synopsis for this module is simple and sharp: give the useful right, remove the forgotten one. You will translate that into concrete actions that align people, process, and technology across your portfolio of applications and data. As a working manager or practitioner, you already see the friction: urgent access requests, unclear ownership, inherited admin rights, and periodic audits that disturb operations. The way out is to fix decision points and evidence. You standardize how requests are made and approved, how entitlements are described, how risks are judged, and how removals are triggered and verified. When this is in place, you spend less time firefighting and more time reducing real exposure.
  4. Module 4: Debt Every organization accumulates information-systems debt. Shortcuts taken to deliver a feature by a deadline, postponed upgrades, a vendor product kept beyond support, a script written by the only person who still remembers it. Debt is not a moral failing. It is a predictable byproduct of real-world constraints and trade-offs. The governance question is not whether you have debt. It is whether you can see it, explain its risk to the business, and decide what to do, in what order, with accountable owners. The most dangerous form of debt is not the old code you can see. It is the opaque system nobody understands anymore. It sits in the middle of a process that still works, until it does not. People are afraid to touch it. Incidents take too long to resolve because teams cannot trace dependencies or reproduce failures. Audits raise findings because controls are partial or manual. When one person’s unavailability can stop production, you are not managing a system. The system is managing you.
  5. Vendor: Holding External Providers to Results in Information-systems Governance Vendors are part of your information system. They host, build, and run critical services. If you govern them by tracking hours and tasks, you get motion without progress. If you govern them by outcome, you align incentives, reduce waste, and protect your enterprise from quiet deterioration that only shows up when a system fails. This module shows how to specify results the vendor must achieve, not just the inputs they will spend. You will learn how to define an outcome, measure it fairly, reflect it in the contract, and run the governance rituals that keep attention on value. We will also cover risk allocation, security and supply chain obligations, and how to manage multi-vendor situations without finger pointing.
  6. Module 6, IS Incident: Decide Who Cuts, Who Communicates, Who Owns When an information-systems incident hits, confusion is the first enemy. Systems slow down, phones ring, dashboards light up. If no one knows who is in command, who can stop the bleeding, and who must speak to whom, minutes are lost and damage compounds. This module shows you how to anchor decisions in governance, so that the right person cuts, the right person communicates, and the right person owns the outcome. You are not writing a playbook for engineers. You are defining decision rights and escalation paths that let your technical teams act fast within clear guardrails. You will learn to appoint an incident commander, authorize a kill switch, separate operational truth from public message, and set thresholds that trigger regulatory notification. You will also see how to keep vendors aligned with your authority, and how to maintain evidential discipline during response and recovery.