ISQ Connect & LearnDesigning the platform and course rebuild as one system
ISQ Connect & Learn

Platform and content concurrency

Designing the platform and course rebuild as one system

Independent Schools Queensland moved professional learning from Cornerstone to an ISQ-hosted Moodle environment while more than sixty Storyline courses were redeveloped in parallel. Inside a three-month engagement, platform, learning architecture, course-estate and operational decisions had to inform each other rather than proceed as serial hand-offs.

Why examine thisThe interesting constraint was not simply migration speed. Freezing the destination before understanding the rebuilt course estate would have embedded the wrong structures; waiting for the destination to be complete before rebuilding courses would have made the delivery window impossible. The work had to remain coupled long enough for each stream to teach the others.

Four coupled streams

One delivery problem, not four hand-offs.

  1. 01
    Platform

    Move from Cornerstone to an ISQ-hosted Moodle environment the organisation could control.

  2. 02
    Learning architecture

    Set structures early enough for redevelopment to proceed, but late enough to reflect what the courses needed.

  3. 03
    Course estate

    Redevelop more than sixty Storyline courses while the destination environment was still being shaped.

  4. 04
    Operations

    Reduce inherited administrative overhead without creating a gap in service for schools already using the platform.

Inspect the dependency map

The tension

Sequential delivery would have made the wrong decisions look final.

Platform migrations invite sequential thinking: configure the destination, move the content, then tidy operations. That sequence works only when the content model is already stable. Here the course estate itself was being redeveloped, so content decisions were still revealing what the platform needed to support.

The move

Design the destination while learning what the estate requires.

Treat platform migration, learning architecture, course redevelopment and operations as one delivery system. Set enough structure early to enable production, but keep that structure revisable while recurring course needs and operational friction are still becoming visible.

  • Cornerstone was replaced with an ISQ-hosted Moodle environment the organisation could host and control directly.
  • More than sixty Storyline courses were redeveloped while the destination environment was being shaped.
  • Learning architecture had to be settled early enough to prevent redevelopment churn and late enough to reflect the needs exposed by the course estate.
  • The migration preserved service continuity for existing school users rather than treating the platform change as a clean-slate launch.
  • Administrative processes that consumed staff time without improving learning were treated as part of the migration problem, not as immutable operational requirements.
  • The subsequent ISQ eLearning Design System formalised recurring learning patterns and production standards that the migration work had exposed.

Systems principle

Platform structure and content structure are one design conversation when they constrain each other.

A platform migration is not complete when content merely fits. The migration had to produce a destination that the rebuilt learning estate could inhabit without immediately generating another round of redesign.

Evidence boundary

What this Record can support

This Record supports the platform migration, the more-than-sixty-course rebuild, the three-month engagement and the documented concurrency between platform and content decisions. It does not publish the unresolved audience-size figure or claim learner-evaluation outcomes.

  1. Implemented

    Connect & Learn moved from Cornerstone to an ISQ-hosted Moodle environment that Independent Schools Queensland could host and control directly.

    Existing Connect & Learn project record.
  2. Implemented

    More than sixty Storyline courses were redeveloped in parallel with the platform migration inside a three-month engagement.

    Existing Connect & Learn project brief and reframe. This claim describes the delivery scope; it does not publish learner numbers or evaluation outcomes.
  3. Implemented

    Platform decisions and content decisions could not be sequenced one after another; learning architecture had to remain responsive to what the rebuilt courses required.

    Existing Connect & Learn project reframe.
  4. Implemented

    The migration addressed administrative processes that consumed staff time without improving the learning experience, rather than carrying those processes forward unchanged.

    Existing Connect & Learn project situation and outcome. The project record supports reduced administrative overhead but does not publish a quantified time saving.