Questions — The Content Creator Role (flow undefined)

← tree index · open questions

v3 introduces Content Creator as the fifth role — “Designs for application and reinforcement, not consumption” — but does not specify the day-to-day workflow. The recommendation is explicit: don’t draft the flow until a working session answers two questions.

The two forcing questions (verbatim intent from v3)

1. What signals from Platform Manager and Instructional Strategist would actually change what you build next?
   • i.e., what makes a cohort-gap signal actionable vs. just noise?
   • What granularity (per-question? per-strategy? per-school-profile?) triggers new content?
2. What does “designed for application” mean in practice — what makes a microlearning item application-oriented vs. consumption-oriented?
   • This definition becomes the acceptance test for every library item.
   • It likely implies: a try-it prompt, a classroom artifact, a reflection hook — not a video to watch.

The answers define the Content Creator’s dashboard and what triggers their work.

The four provisional responsibilities (from §5e)

Until the session happens, design assumes the Content Creator owns:

1. Pre-engagement assets — workshop intro text (focus points + reminders) [B1], incl. TTS variants.
2. Pulse-check authoring — the 3 MCQs per workshop, mapped to focus points [C2].
3. Microlearning library — reusable items the IS recommends [G3], built for application + reinforcement.
4. Gap-driven backlog — prioritize new microlearning from PM + IS cohort-gap signals.

Downstream design questions these raise

• Backlog data contract: what shape does a “gap signal” take when it lands in the Content Creator backlog? (See data model.)
• Library taxonomy: how are microlearning items tagged so the IS recommendation engine and the intervention layer can match an item to a stuck participant’s specific gap?
• Authoring vs. assignment: does the Content Creator publish into the same content-visibility state machine as other assets?
• Feedback loop: does the Content Creator see whether their microlearning actually moved time-to-apply? (Closing this loop would make the role data-driven rather than request-driven.)

Recommendation

Run the working session before Phase 4 of the roadmap; the role’s flow and dashboard are blocked on its output. In the meantime, build the backlog-feed plumbing (PM/IS → Content Creator) so the signal is captured even before the consuming workflow exists.

Related

• Roles and goals
• Intervention layer (microlearning is its ammunition)
• Source: §5e of recommendations doc