Applied Learning Platform — Knowledge Tree

A structured synthesis of the two source deliverables (the v3 Workflow Recommendations and the Enhanced Dashboard User Stories v2) into navigable concepts, open questions, and ideas. This tree is the working reference for planning and building the platform.

Framing question for every capability: “How do we reduce the time between learning and improved practice?”

The platform is not an LMS, repository, or async course library. It is a digital extension of Inspired Instruction’s in-person professional-development work for teachers — designed to drive behavioral change (applying a strategy in the classroom), not content consumption.

How to read this tree

knowledge-tree/
├── 00-overview.md            ← start here: vision, the shift, the five roles
├── concepts/                 ← the durable building blocks of the product
│   ├── applied-learning-cycle.md
│   ├── roles-and-goals.md
│   ├── intervention-layer.md
│   ├── context-layer.md
│   ├── time-to-apply-metrics.md
│   ├── content-visibility-states.md
│   ├── pulse-check.md
│   ├── intro-video.md
│   ├── locked-resources.md
│   └── business-loop.md
├── questions/                ← what must be decided before / during build
│   ├── open-questions.md
│   ├── content-creator-role.md
│   └── data-and-integration.md
├── ideas/                    ← opportunities and design directions
│   ├── feature-ideas.md
│   ├── data-model.md
│   └── dashboard-designs.md
└── reference/                ← maps back to the source material
    ├── source-docs.md
    ├── user-story-map.md
    └── implementation-roadmap.md

Source documents live in ../source-docs/ — the full v3 recommendations markdown, the user-stories markdown, and the 16 flowchart images.

The shape of the product in one diagram

                 PREPARE → ENGAGE → PRACTICE → APPLY → REFLECT → ADJUST ┐
                    ▲                                                    │
                    └───────────────── next engagement ─────────────────┘   (business loop)

   Roles (top→bottom):  Platform Manager · Instructional Strategist · Learning Admin
                        · Participant · Content Creator
   Wrapping all phases: the AUTO INTERVENTION LAYER (fires on ABSENCE of expected behavior)

Each phase × role cell describes what that role produces. The intervention layer is a cross-cutting band beneath every phase. See concepts/applied-learning-cycle.md and reference/source-docs.md (Figure 1).

The single most important design principle

Every phase, on every role’s dashboard, must answer: “What’s the next behavior I expect from this user — and what triggers fire if it doesn’t happen?” If a screen can’t answer that, it shouldn’t ship.

This principle is the acceptance test applied throughout the tree.

Entry points by intent