Contact for a consult

OUR APPROACH

Complex work.
A clear way forward.

A shared plan connects the academic purpose, technical requirements, and people responsible for delivery. Each phase ends with something concrete to review.

Find your starting point

FIVE PHASES. CLEAR DECISIONS.

Know what happens.
Know what comes next.

The depth of each phase depends on the engagement. A single-course refresh can use a lighter process than a program build or integration involving several institutional systems.

01

Discover & define

Clarify the learners, institutional goals, existing environment, and the problem the project must solve.

Starting inputs
Project goals, learner needs, existing content, platform landscape, and the institution’s constraints.
Working outputs
A discovery summary, initial scope, assumptions, and a list of decisions still needed.

Decision pointAgree on the problem, the intended outcome, and who can approve the work.

02

Design & align

Agree on scope, outcomes, responsibilities, deliverables, and the evidence needed for acceptance.

Starting inputs
Academic standards, required qualifications, technical requirements, review capacity, and acceptance expectations.
Working outputs
A blueprint or technical specification, deliverable inventory, milestones, and responsibility plan.

Decision pointApprove the scope and review criteria before full production begins.

03

Develop & connect

Create the academic assets or configure the technical solution in manageable, reviewable increments.

Starting inputs
Approved plans, source materials, authorized access, templates, and contributor assignments.
Working outputs
Working drafts, configured components, documented decisions, and progress against the deliverable inventory.

Decision pointReview a representative module, prototype, or integration path before expanding the work.

04

Review & validate

Use faculty review, quality checks, and appropriate testing to resolve issues before release.

Starting inputs
Faculty feedback, agreed quality criteria, appropriate test accounts, and the issue list.
Working outputs
Reviewed materials, test findings, revision records, and identified exceptions.

Decision pointInstitution-designated reviewers accept the work or identify a specific remaining action.

05

Launch & hand off

Complete approved delivery, transfer working materials, and equip the designated team to maintain the result.

Starting inputs
Accepted materials, release approvals, ownership arrangements, and named operational contacts.
Working outputs
Final working files, relevant configuration documentation, training materials, and a transition plan.

Decision pointConfirm where the work lives, who maintains it, and the boundaries of any ongoing support.

WAYS TO WORK TOGETHER

Choose a starting point.
Define the scope together.

Timing, fees, contributor availability, and support are determined by the agreed scope. These models do not represent fixed-price packages or standing staffing commitments.

SHARED WORK. CLEAR OWNERSHIP.

Decisions stay
with the right people.

Projects need more than contributors. They need a named owner for content, access, decisions, and final acceptance.

Institutional sponsor

Sets priorities, resolves major scope decisions, and approves the engagement.

Academic reviewer

Approves subject accuracy, learning outcomes, assessments, and instructional expectations.

Technology owner

Authorizes access, validates institutional requirements, and approves production changes.

Delivery lead

Coordinates agreed contributors, milestones, review cycles, issues, and handoff.

PREPARE FOR THE FIRST CONVERSATION

A useful brief starts
with six questions.

You do not need all the answers. These questions make the first discussion more concrete and reveal where discovery would help.

  1. 01

    What needs to change?

    Describe the problem and the result you want to see.

  2. 02

    Who is the work for?

    Identify learners, faculty, staff, or the program being supported.

  3. 03

    What already exists?

    List available content, templates, systems, and previous work.

  4. 04

    What must the work fit?

    Note the LMS, institutional standards, calendar, and other constraints.

  5. 05

    Who will decide?

    Identify the academic sponsor, reviewers, and technical owners.

  6. 06

    What defines completion?

    Describe the deliverables, acceptance evidence, and handoff you expect.

ENGAGEMENT QUESTIONS

Set expectations
before the start.