ISQ Connect & Learn project record · 2024

Migration dependency map

A semantic dependency map showing why platform migration, learning architecture, more than sixty course rebuilds and operational migration had to move concurrently inside the same three-month engagement.

Read the analysis

Three-month engagement

Shape the destination and the estate together.

The work stays coherent only if each stream can change another before its assumptions harden into rework.

  1. 01

    Destination

    Platform migration

    Replace Cornerstone with an ISQ-hosted Moodle environment the organisation could host and control directly.

    Informs → Learning architecture · Operations

  2. 02

    Shared structure

    Learning architecture

    Define the organising structures that both the platform and rebuilt courses would depend on.

    Informs → Platform migration · Course redevelopment

  3. 03

    More than sixty Storyline courses

    Course redevelopment

    Rebuild the learning estate while the destination was still being shaped, so recurring needs informed the platform rather than arriving after it.

    Informs → Learning architecture

  4. 04

    Continuity

    Operational migration

    Move the service without a gap for existing school users and reduce administrative work that did not improve learning.

    Informs → Platform migration

Delivery guardrails

What serial delivery would get wrong

  1. Do not freeze the platform too early

    Course redevelopment must still be able to reveal structural requirements.

  2. Do not delay the courses until the platform is “finished”

    The three-month engagement cannot support serial discovery and rebuild.

  3. Do not treat migration as copy-and-paste

    Inherited administrative complexity is part of the problem being migrated away from.

Why no reconstructed platform screen

The existing project analysis does not rely on learner-facing Connect & Learn screenshots for this claim. The useful artefact here is the dependency structure of the work, not a speculative recreation of the 2024 interface.

Evidence treatment

The dependency structure is represented as semantic ordered groups and explicit “informs” relationships rather than as a flattened process diagram, so the delivery logic remains understandable at enlarged text and with assistive technology.

Conflicting audience-size figures remain excluded. The analysis relies on the confirmed migration, course-estate and engagement facts only.