Experience-Aware Instructional Design

The real problem

An experienced learner can be over-taught, under-supported, or falsely promoted. Years in a role, a senior title and familiarity with one toolchain are context, not a substitute for evidence. The engineering task is to route a learner from an observable target outcome, visible prior evidence and a current diagnostic signal—then change only the support, challenge and practice needed to reach a common exit-evidence bar.

The owned artifact is Experience-Aware Instructional Design Contract v1. It makes route compression auditable instead of turning “experienced” into a permission slip.

Lesson boundary

MKN-001 owns experience-aware instructional routing. AGN-015 owns SaaS multi-tenancy architecture; MKN-002 owns the project/JiTT learning loop. This lesson may reference prerequisite evidence and future project practice, but it does not absorb those outcomes.

Four route states are useful here: FOUNDATION, REPAIR, EXPERIENCED, and BRIDGE. They change support and challenge; they do not change the target competency or waive exit evidence.

Mental model: outcome → evidence → diagnostic → route → practice → feedback → transfer → common exit evidence

Start from what the learner must observably do. Bind relevant prior evidence to that target and judge its strength. Add a diagnostic signal for the current context. Only then choose a route.

EXPERIENCED is justified when evidence is strong and current enough to compress exposition. REPAIR isolates a fragile prerequisite. FOUNDATION makes missing structure explicit. BRIDGE handles context/tool access gaps without pretending conceptual competence disappeared. Every route converges on the same exit evidence.

The 14-dimension contract

The contract records learner profile, target competency, prior evidence reference and strength, diagnostic signal, route state, scaffold level, challenge level, practice opportunity, feedback signal, transfer task, exit evidence, repair trigger and review owner.

The decisive separation is profile vs evidence. A profile can say “senior backend developer”; it cannot close a prerequisite. prior_evidence_ref and diagnostic_signal must carry the decision. Likewise, scaffold level and challenge level describe instructional treatment; they are not mastery states.

Why experience should compress exposition, not the evidence bar

Clear learning objectives define what observable performance matters. Aligned assessments ask learners to demonstrate that performance. For an experienced learner, repeating every explanation may be wasteful, but skipping the demonstration is a different decision.

That is why route compression should remove redundant explanation or routine practice while preserving decisive challenge, feedback, transfer and exit evidence. If prerequisite evidence is contradictory, a senior title cannot rescue the experienced route. If conceptual evidence is strong but the current tool is unfamiliar, a bounded tool bridge is more accurate than declaring conceptual failure.

Baseline example

Learner LP-EXP-01 must demonstrate CMP-RETRY-IDEMPOTENCY. Prior evidence includes a recent reviewed design and a debugging artifact that both support the concept. A diagnostic asks the learner to distinguish operation identity from retry-attempt metadata; the answer is structurally correct.

The contract selects EXPERIENCED, uses MINIMAL scaffold, HIGH challenge, and a production-like transfer task. The learner still must produce EV-EXIT-IDEMPOTENCY-01. Nothing about the route waives the exit artifact.

Common failure modes

1. Seniority oracle: “10 years experience” silently becomes mastery.
2. Experienced without diagnostic: prior evidence is referenced but not checked against the current target/context.
3. Contradiction overwrite: one strong artifact hides a conflicting prerequisite result.
4. Evidence waiver: the experienced route has a weaker exit requirement.
5. Tool familiarity confusion: unfamiliar UI/library is treated as loss of conceptual competence.
6. Blanket replay: a tool gap causes the learner to replay the full foundation route.
7. Transfer copying: the baseline route label is reused after the context changes.

Compression, repair and bridge trade-offs

EXPERIENCED saves attention by reducing redundant exposition, but it requires strong evidence and a diagnostic signal. REPAIR costs time but localizes a fragile prerequisite rather than replaying an entire module. BRIDGE adds context-specific support without downgrading conceptual evidence. FOUNDATION is appropriate when decisive structure or evidence is genuinely absent.

Do not optimize these choices into one opaque score. Keep the evidence, route reason and owner visible.

Production bridge

In a real system, keep the learner profile separate from append-only evidence references. Version diagnostic rules and route decisions. A later contradictory artifact must remain visible rather than being overwritten by a newer positive route.

Toolchain access can be modeled as a bridge dimension. If the learner understands the concept but cannot yet navigate the current SDK or deployment workflow, provide targeted orientation and one context-specific practice; do not replay conceptual teaching unless evidence says the concept is fragile.

Guided and independent practice

Build the baseline contract using all 14 dimensions. Then mutate one field at a time: replace strong prerequisite evidence with contradictory evidence while keeping the “senior” profile; remove the diagnostic reference while retaining EXPERIENCED; waive exit evidence for the experienced route; change only tool familiarity.

For independent practice, route a third learner with strong conceptual evidence and unfamiliar toolchain. Produce a bounded bridge, preserve the common exit evidence bar, and explain what support was removed, retained or added.

Verifiable evidence

Ask five questions: Is the target observable? Does the route trace to prior evidence rather than profile labels? Does the diagnostic justify route compression or repair? Are scaffold/challenge choices explicit? Does every route require equivalent exit evidence for the owned outcome?

The offline lab uses synthetic records only. Missing, contradictory or stale decisive evidence must stay HOLD, UNKNOWN, CONTRADICTED or REVIEW_REQUIRED rather than being forced into a positive route.

Assessment and transfer

Assessment covers boundary retrieval, baseline construction, diagnosis of seniority-with-contradictory-evidence, and the tool-unfamiliarity transfer. The transfer result must be recomputed from changed evidence rather than copied from the baseline route.

A valid bridge keeps conceptual evidence intact while adding targeted tool practice. It still converges on the same exit evidence as foundation, repair and experienced routes.

Sources and freshness

FACT: Carnegie Mellon Eberly Center guidance links useful learning objectives to observable learner performance and emphasizes alignment among objectives, assessment and instructional activities. FACT: CMU guidance also notes that advanced and novice learners can require different balances of guidance and autonomy. INFERENCE: prior experience should therefore alter support only when target-aligned evidence supports the change. DESIGN: MAKNOW route states, bridge semantics, typed holds and the common exit-evidence bar are local authority.

Freshness checked 2026-09-14. Recheck by 2027-01-15 or earlier if the cited guidance materially changes.