Grape
Adaptive quizzes for product managers

Find the gaps before somebody else does.

A quiz written from a quarter of notes shows the difference between having read something and knowing it. Useful in the middle of planning, and more useful the week before that.
Questions generated from the note in front of you
The difficulty follows how you are actually doing
See which topics you keep getting wrong
Works on the phone, so waiting anywhere becomes practice

Reading is not knowing

A quiz shows you the difference in about two minutes.

Targets the weak spots

Answers you miss come back around, the ones you know do not.

One note, one quiz

No question bank to build and no separate app to keep in sync.

Ten questions, not a hundred

Short enough to run before a lecture, long enough to tell you something.

Practice in a queue

The quiz is on your phone, so five spare minutes becomes revision.

Straight back to the note

Every question points at the line it came from, so you can go and reread it.
Results

Three things that stop being a problem

Feature lists are easy to write and hard to care about. This is what changes for product managers.

Get the follow ups out of the meeting

Record, then ask for what you agreed and who owes what, before the next call starts.

Answer why we built it that way

Search by the decision, not the doc title, and get the note that explains it.

Turn ten customer calls into one theme

Ask what came up repeatedly across a folder of interviews and get it summarised.
In practice

What that looks like for product managers

A few moments in a normal week where the app earns its place.

Discovery

Record every call into one folder and let search do the pattern finding.

Spec writing

Draft in the note where the research lives and link to the decisions it depends on.

Planning

Ask for a summary of everything you captured about an area this quarter.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Leave with the notes written.

Customer calls, specs, decisions and the reason behind them in one searchable library, so the context does not live in your head or in a chat thread.