IT MANAGER LEARNING PATH

IT Manager Programme

A practical management path that explains infrastructure in business language, then builds the technical understanding needed for planning, risk, recovery, security, projects and lifecycle decisions.

Who this is for

An owner, IT manager, operations manager or technical decision-maker who needs to understand infrastructure without becoming a specialist in every platform.

How to use it

Follow the modules in order the first time. Return later by subject when you need a field reference.

End goal

You should be able to evaluate infrastructure proposals, identify missing questions, understand operational risk and require meaningful acceptance evidence.

Phase 1: Understand what you are responsible for

Build enough technical understanding to challenge assumptions and ask useful questions.

Business IT explainedSee how endpoints, networks, servers, storage, cloud, security and power support business processes.START HERE

Servers and virtualizationUnderstand why workloads are virtualized and what still depends on physical hardware.DECISION

Storage architectureSeparate file storage, block storage, capacity, performance and availability.DECISION

RAID and storage performanceUnderstand what RAID can survive and why it is not backup.RISK

Networking and segmentationUnderstand why departments can share switches while remaining logically separated.RISK

Identity and Active DirectoryUnderstand central employee identity, permissions and policy.IDENTITY

Phase 2: Availability, recovery and security

Turn technical controls into business questions about downtime, loss and exposure.

Backup, snapshots and replicationKnow which technology protects against which failure and what still needs recovery testing.RECOVERY

Windows recoverySee what an administrator actually needs to restore a failed server or service.RECOVERY

UPS and power protectionUnderstand load, runtime and what the UPS is expected to keep alive.POWER

Security operationsSee identity, endpoint, mail, network and evidence as one operating discipline.SECURITY

Firewall policyUnderstand why business flows should drive firewall rules.SECURITY

Monitoring and evidenceUnderstand why logs, time synchronization and baselines matter during incidents.OPERATIONS

Phase 3: Plan projects properly

A good project starts with requirements and finishes with evidence, documentation and ownership.

Project planningCapture users, services, dependencies, capacity, network, rack, power and acceptance requirements.PLANNING

Infrastructure health checksAssess what exists before approving a replacement or expansion.ASSESSMENT

Rack and data-centre fundamentalsUnderstand physical layout, airflow, power, serviceability and failure domains.PHYSICAL

Server commissioningKnow what evidence should exist before a new server enters production.ACCEPTANCE

Network commissioningDefine what must be tested before the network is signed off.ACCEPTANCE

Documentation and handoverMake sure knowledge survives the installer, supplier or staff member who built the system.GOVERNANCE

Phase 4: Make better lifecycle decisions

Use the technical foundation to evaluate change rather than simply buying newer equipment.

Virtualization HA, replication and backupUnderstand the difference between high availability and recoverability.LIFECYCLE

Storage performance troubleshootingRecognize when a capacity problem is actually latency, queueing or workload behaviour.LIFECYCLE

Change control and outage triageUnderstand why undocumented emergency changes often create the next outage.GOVERNANCE

Final design exerciseBring requirements, infrastructure, recovery, security, documentation and acceptance into one plan.FINAL EXERCISE

By the end of this programme

☑ Explain the business purpose of the major infrastructure layers.

☑ Distinguish availability, backup, replication and disaster recovery.

☑ Ask useful questions about identity, security, networking, storage and power.

☑ Review a project for dependencies, failure domains and operational ownership.

☑ Require commissioning evidence and documentation before accepting delivery.

☑ Make lifecycle decisions based on business risk rather than product age alone.

← Back to all learning paths