What Gwen Is, and How to Use It Well
Gwen is more than a review queue. It helps you decide what to learn, capture it in the right form, and maintain it over time.
Gwen works best when planning, learning, and review all belong to the same system instead of being split across disconnected tools.
What Gwen Is For
Gwen helps you answer two questions clearly: what am I trying to learn, and what do I need to do today to keep it alive?
Not Just Review
Gwen is not only for remembering old material. It is for organizing learning objectives, doing meaningful study, and turning the results into durable knowledge.
A System With Shape
Projects, events, cards, exercises, and problems each do a different job. The goal is not extra complexity. It is to give each kind of learning an appropriate place.
Declarative + Procedural Knowledge
Gwen separates what you want to be able to recall from what you want to be able to do. That distinction sits at the center of the product.
Facts, Terms, Concepts
Use cards for knowledge you want to retrieve directly: definitions, concepts, names, rules, frameworks, distinctions, and short explanations.
Skills, Steps, Practice
Use exercises for knowledge that must be performed: solving a type of problem, following a process, applying a method, or executing a workflow.
Projects, Events, Cards, Exercises, Problems
If someone asks, "How am I supposed to use this?" this is the answer. Each part exists because it serves a different role in the learning process.
Project
A project is a learning objective. It holds the things you want to know and the things you want to be able to do.
Event
An event is a one-time learning activity: read a chapter, watch a lecture, work through a tutorial, or do a practice session.
Card
A card captures declarative knowledge. Ask for something you should be able to recall without working through a full procedure.
Exercise
An exercise captures procedural knowledge. It should require working through a method, not just giving an answer.
Problem
Problems live inside exercises. They give you multiple instances so you learn the procedure itself instead of memorizing one example.
What a Good Gwen Workflow Looks Like
The right question is not "How do I put everything into cards?" The right question is "What am I trying to learn, and what form should that learning take?"
1. Define the project
Start with a real objective. Examples: learn introductory accounting, study the causes of the French Revolution, or become competent at algebraic manipulation.
2. Create events to learn from
Add events for the actual work of learning: books to read, lessons to complete, videos to watch, lectures to review, or practice sessions to do.
3. Turn important facts into cards
When something should be recallable on demand, capture it as a card. Definitions, distinctions, principles, and conceptual prompts belong here.
4. Turn important skills into exercises
When something must be performed, make an exercise. Give it multiple problems so the general procedure, not a single instance, is what gets learned.
5. Review daily
After learning and capturing material, show up each day and do what is due. Gwen handles timing so you can focus on retrieval and performance instead of scheduling overhead.
Why Gwen Is Not Just Anki With Projects
The point of Gwen is not to wrap flashcards in more structure. The point is to give planning, learning, memory, and skill practice a coherent shape.
Cards are not enough
If you try to learn every kind of knowledge with cards alone, you often end up memorizing a narrow answer when what you really needed was broader skill.
Structure serves learning
Projects and events keep learning connected to real objectives. Cards and exercises preserve the results in forms you can maintain over time.
Learn More, Use It Well, Keep It
Gwen works best when you use it as a full learning system: decide what matters, capture it in the right form, and come back daily to maintain what you have built.
Download Free