# Study and note-taking guide Use one page per lesson. The aim is to turn an idea into a testable observation, not to collect agile vocabulary. ## Capture Write the lesson’s central claim in your own words. Add the source or learning aid it came from. Mark whether the point is a source-backed statement, an instructional synthesis, or your own workplace inference. This prevents an example from quietly becoming a universal rule. ## Challenge Write one counterexample or constraint. For instance, an early prototype may be inappropriate when it exposes personal data, bypasses a statutory control, or cannot be safely reversed. Ask what would make the lesson’s default advice unhelpful here. ## Apply Name one piece of work, one uncertainty, one person or group able to provide relevant feedback, and one decision that feedback could change. Keep the proposed test proportionate. A low-risk reminder wording can be tested differently from a clinical procedure or regulated filing. ## Review Set a date to review the result. Record what happened, what you learned, and whether to continue, adapt, stop, or use more predictive planning. “We completed the activity” is not evidence that the idea worked; it is only evidence that you participated. Use the [template pack](fmap-template-pack.md) if you prefer prompts ready for copying.
Markdown
FMAP study guide
A structured study guide for revisiting the major concepts, trade-offs, and practice prompts in FMAP.
Exports are generated in your browser; no template content is uploaded.