Form
Consistent structure in a primary notes app and cloud storage with four top-level areas (Projects, Areas, Resources, Archives), naming convention, list of active projects with outcome and deadline, list of Areas, and weekly review date.
RunsheetKnowledge Modeling
PARA Method
ComplexityMedium
Time1-3 h Setup, laufend
Participants1
FormatAsync
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Note app (Notion, Obsidian, Evernote, Apple Notes); cloud storage (Drive, Dropbox); bookmark tool (Raindrop, Pocket); list of existing storage locations; weekly review slot.
People / roles
Solo practice. In teams it is only conceptually adaptable; implementation remains individual.
Pre-read
Current storage locations (mail folders, cloud folders, notes stacks, browser bookmarks); active projects with outcomes and deadlines; responsibilities as Areas (for example, health, client relationships, finance); typical resource topics (templates, research, favorite articles).
Time needed
1-3 h setup, ongoing
Setup
Set up four top-level structures: 1) Projects (outcome + deadline), 2) Areas (responsibility without deadline), 3) Resources (topic knowledge), 4) Archives. Add a short description for each area. Define naming convention (for example, project = verb + object + deadline).
02
Core question
The one question this method answers
Where should this material belong so I can find it exactly when I need it?
03
Flow
Marker: Sektion
| Step | Duration | Action | Hint |
|---|---|---|---|
1Section 1: Inventory | 30-60 min | List all existing storage locations (notes apps, drives, mail folders, bookmarks). For each location note rough content category and volume. | Teams that forget one location duplicate storage. Inventory avoids parallel systems; forgotten locations surface within a few hours. |
2Section 2: Identify Projects | 20-30 min | List active projects with outcome (what gets done?) and rough deadline window. One folder or page per project; supporting material belongs in that folder. | 10-15 active projects are realistic. If you want 30+, you either mixed Areas and Projects or are overloaded. |
3Section 3: Areas of Responsibility | 20-30 min | Define Areas as ongoing responsibilities without an end date (for example, law-firm marketing, client relationship Schmidt, own bookkeeping). Typical count is 5-10 Areas. | Area is maintenance, Project is change. If the folder fills up but no outcome exists, it is an Area. Clear separation prevents mixing. |
4Section 4: Collect Resources | 30-45 min | Place topic knowledge without direct project or Area dependency into Resources. One entry per topic, with a meaningful title. | Resources is not a dump for anything interesting. Who stores everything there builds a graveyard. Accept only items with a clear reuse scenario. |
5Section 5: Set up Archives | 15-30 min | Move completed projects and no longer active Areas/Resources into Archives. Add date in title. Keep searchable, but out of active view. | Archives reduce load. Keeping everything active creates endless scrolling. Move at least a few items monthly, otherwise the active system grows too much. |
6Section 6: Weekly review | 20 min weekly | For each project check whether still active and whether a Next Action exists. Maintain Areas. Sort inbox material into P/A/R. Identify items for Archives. | Without weekly maintenance, PARA degrades within two weeks. Fix a recurring calendar slot, not 'when I have time.' |
04
Artifact
What comes out at the end
Versioning / ownership
Create initial setup note with date. For structure changes, add a migration note rather than silent edits. Run semiannual large reviews to identify stale Areas or hoarded Resources.
Tool alternatives
- Notion with databases per area
- Obsidian with folder structure
- Apple Notes with folder hierarchy
- Google Drive with matching top-level structure
para-method-working-template.md
Compact working template for PARA Method with context, input, output artifacts, and next step.
PARA Method Working Template
Goal
Organizes digital information into Projects, Areas, Resources, and Archives.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- PARA Structure:
- Project Notes:
- Knowledge Archive:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
05
Example output
Concrete filled scenario, fictional example
para-method-beispiel.md
Concrete filled scenario, fictional example
PARA structure — Sabine, setup 15.05.2026 in Notion + Google Drive
1. Projects (active, with outcome and deadline)
- "Finalize client tax filing 2025 for client Meyer, by 30.06.2026"
- "Onboarding checklist for new clients, v1 by 15.06.2026"
- "Complete DATEV training module 3 by 31.05.2026"
- "Homepage relaunch, live by 30.09.2026"
2. Areas (ongoing without deadline)
- Client master data (folder per client)
- Own bookkeeping
- Personal and health
- Law-firm marketing
- DATEV/software stack maintenance
- Bar association and continuing education
3. Resources (topic knowledge)
- Templates (fee agreement, NDA, standard letter)
- Research "Client confidentiality & KI tools"
- Article collection "Scaling a solo practice"
- VAT edge cases
4. Archives (closed or inactive)
- 2024 projects (for example, "Office move 2024")
- 2023 tax returns
- Old CRM evaluation Q1/2024
Naming: Projects = outcome + date; Areas = clear noun; Resources = topic/subtitle.
Weekly review: Sunday 18:30, 25 min.
06
Pitfalls
Recognize symptoms and steer against them
Trap
Projects and Areas mixed
Symptom
"Marketing" appears as a project with endlessly growing content and no outcome.
What to do
Ask: is there an outcome and a deadline? If no, it is an Area. Within an Area, create sub-projects with clear outcomes.
Trap
Resource graveyard
Symptom
Hundreds of articles and bookmarks, nobody reads, finds, or uses them.
What to do
Entry criterion: define a concrete reuse scenario. If scenario is missing, do not add the item. Review Resources quarterly.
Trap
Tool sprawl
Symptom
Structure in Notion, parallel in Drive, parallel in Notes; search fails.
What to do
Use one primary storage per item type: knowledge in notes app, files in Drive. Cross-linking yes, duplication no.
Trap
Archives never used
Symptom
Completed projects remain active and the active list grows.
What to do
Weekly review moves at least 1-3 items to Archives. Archive immediately when a project is completed.
Trap
Structure without maintenance
Symptom
Setup is done, then there is no review for 4 weeks; the system drifts and new content is added arbitrarily.
What to do
Make weekly review mandatory. After three missed reviews, reset the system or get coaching. Without maintenance, PARA is just ceremony.
07
Stop criteria
Done signals checkable in under a minute
The person uses only one central storage tool and has little material; PARA overhead is not worth it.
Work is primarily team-based with shared knowledge stores; PARA does not fit directly.
Weekly review discipline is not sustainable; the structure degrades.
Person frequently changes tools; PARA needs at least 12-16 weeks of stability.
Volume is too large for initial migration (5 years of notes); without pre-pruning, setup turns into an endless task.
Person needs real-time collaboration and shared access; individual PARA clashes with group workflows.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.