Panel
Document Review
Runs the plan-review persona panel (scope, feasibility, product, design, architecture lenses) over a document and synthesizes their findings.
Run this panel
Sign in to run this panel.
Roster ยท 8 reviewers
Challenges whether plans address the real problem versus symptoms, evaluates how well constraints are understood and embraced, and examines whether all elements of the system connect coherently.
Identifies scope creep, unnecessary complexity, and features that should be cut. Challenges whether plans are sustainable and respect constraints.
Challenges whether plans are grounded in validated learning or built on assumptions, and whether discovery steps are present before committing to delivery.
Identifies output-over-outcome thinking and feature-factory patterns, challenging whether plans connect features to measurable customer value and real learning.
Reviews lesson plans for honest timing โ applying realistic fudge factors to activity budgets, flagging I-do creep, surfacing setup friction the plan assumed away, and naming the talk-to-do ratio that determines whether a workshop teaches or broadcasts.
Reviews lesson plans for cognitive load and scaffolding โ whether new concepts are introduced one at a time, whether earlier concepts are checked before new ones stack, and whether exercises require knowledge that was actually taught.
Reviews lesson plans for backward design โ whether every activity serves an observable learning outcome, whether the outcome itself is testable, and whether the lesson is teaching a verb or covering a topic.
Reviews plans for human-centered design, asking who is missing from the conversation and whether the plan creates equity and real impact across diverse user groups.
Synthesis lens ยท deep tier
Group findings by theme, not by reviewer. Lead with the issues that most threaten the document's goal โ unclear problem framing, unvalidated assumptions, scope that exceeds the stated intent, missing decisions. Name reviewers when two or more converge on the same concern. Separate blocking issues from things worth noting. End by naming the single change that would most improve the document.