Every part of a lesson must connect to a user's needs. This includes the introduction, the explanation of importance, and the summary. These parts should address both obvious and hidden user needs.
By Pawan Nayar · from the LLOS AI Learning record
Every part of a lesson must connect to a user's needs.
This includes the introduction, the explanation of importance, and the summary. These parts should address both obvious and hidden user needs.
A lesson's introduction should show why the topic is important. This part should address a user's clear and immediate needs. The explanation of why the concept matters should also connect to deeper needs. The summary or transition to the next topic should link to a user's hidden needs. These hidden needs often run through the entire lesson.
A teacher creates a lesson about fractions. The introduction explains how fractions are used in cooking (surface need). The 'why it matters' section discusses how understanding fractions helps with problem-solving skills (deep need). The summary connects fractions to understanding data in the news (latent need).
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
Tags help a system decide which group of users should get a question. They act like filters.
A content section should never feel like a dead end. The user needs to know what to do next.
A 'surface' layer gives basic information. A 'class' layer adds more context to the 'surface' information.
A headline should name a user's biggest worry. It should then promise a way to solve that worry.
Every part of a lesson must connect to a user's needs. This includes the introduction, the explanation of importance, and the summary. These parts should address both obvious and hidden user needs.