Note-taking method
Best Weekly Review for Designers
A regular rhythm of reflecting and resetting priorities. For designers, the working week is scattered moodboards, design critiques, and research that never gets referenced again. The rest of this page is the method, cut for that week.
By tentus team · Updated 2026-09-20
What Weekly Review actually asks of you
Once a week, everything is processed: inboxes emptied, the last week skimmed, the next one chosen.
Same slot, same steps — clear captures, close or re-commit open loops, pick a focus. The review is the system; the notes are just its raw material.
How designers put it to work
- 1
Critique with its context
Feedback lands captured next to the frame it refers to — including the feedback that contradicted last week's. Design rationale lives in the record, not in the designer's memory of the meeting.
- 2
A pattern shelf, not a moodboard pile
Inspiration is stored by the problem it solved — empty states, pricing pages, onboarding — so the shelf answers a brief, not just a vibe. Sources stay attached for when the client asks where it came from.
- 3
The dropped-direction log
When a direction dies, the reason is captured next to the work. Six months later, when someone suggests the same direction, the link answers before the meeting does.
The capture habit, the linking, and the retrieval are the parts tentus automates — weekly review without the daily upkeep.
Try it with tentus
tentus makes Weekly Review practical for designers. Capture, link, and retrieve without the busywork.
Other methods worth trying
Weekly Review for other roles
Product Managers
juggling research, specs, stakeholder feedback, and launch plans across multiple tools.
Software Engineers
losing context between code reviews, incident postmortems, and technical research.
Researchers
drowning in PDFs and citations with no way to connect findings across projects.
Writers
notes spread across drafts, interviews, and research that should connect but don't.