Form
Daily planning note with five sections: Tasks, Length, Buffer, Decisions, Follow-up review; time estimates, priority symbols, end-of-day status; ideally linked with weekly review and long-term task system.
RunsheetOperations
ALPEN Method
ComplexityLow
Time10-20 min täglich
Participants1
FormatAsync
MaturityEstablished
01
Preparation
What needs to be ready before start
Materials
Notebook or Notion page with a daily template (task list, time, buffer, priority, follow-up review); calendar access for appointments; list of open commitments from inbox or task system.
People / roles
Single-person method: one user. Optional buddy for the weekly follow-up review, who reflects back the share of plans kept.
Pre-read
Known fixed appointments for the day; the person's energy peaks; waiting times and commute windows; deadlines for the current week.
Time needed
10-15 min the evening before or at the morning start
Setup
Open the daily template. Enter the date. Place the calendar with fixed appointments next to it. Put pen or cursor in the task column, set the timer to 10 min.
02
Core question
The one question this method answers
Which tasks truly belong in today's day, and with which time estimates, buffers, and priorities can they be fit in realistically?
03
Flow
Marker: Minute
| Step | Duration | Action | Hint |
|---|---|---|---|
10-3 min: A - Tasks | 3 min | List all tasks for the day: appointments, daily goals, open commitments, unfinished items from yesterday. | If the list exceeds 20 items, it is a wish list, not a plan. At the latest at step P, cut hard. |
23-6 min: L - Estimate length | 3 min | Estimate a realistic duration for each task. Use experience, not wishful thinking. | Bundle tasks under 5 min into a single small-stuff task. Split tasks over 90 min into sub-tasks. |
36-8 min: P - Buffer time | 2 min | Plan at most 60% of the available working time. Keep 40% as buffer for unexpected events, breaks, and transitions. | Anyone who plans 100% is planning a day that does not exist. The first disruption will throw the plan off. |
48-12 min: E - Decisions | 4 min | Prioritize and cut down. Put high-impact tasks first, delegate the rest, postpone it, or drop it. Max 3-5 main tasks. | If nothing is dropped, the list was already optimal or decision discipline is missing. Eat the Frog helps mark the first main task. |
5Evening: N - Follow-up review | 5 min | At the end of the day, compare the plan with reality: what was done, what was postponed, what was underestimated. Park postponed items for the next day. | Skipping the follow-up creates a method that never learns. After one week, the estimation errors will already show a pattern. |
04
Artifact
What comes out at the end
Versioning / ownership
File the daily note with the date as the title. Once a week, create a summary from the last seven notes (estimation errors, completion rate, friction topics). Evolve templates in a versioned way and leave old daily notes unchanged.
Tool alternatives
- Paper notebook or bullet journal
- Notion or Obsidian daily note with template
- Apple Notes or Google Docs with a daily template
- Todoist or TickTick with daily filter and time estimate
alpen-method-working-template.md
Compact working template for ALPEN Method with context, input, output artifacts, and next step.
ALPEN Method Working Template
Goal
A time-management method for daily planning across tasks, length, buffer, decisions, and follow-up.
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
- Daily Plan:
- Time Estimates:
- Review Notes:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
05
Example output
Concrete filled scenario, fictional example
alpen-method-beispiel.md
Concrete filled scenario, fictional example
ALPEN 18.05.2026
A - Tasks
- Architecture review for Q3 service
- 1:1 with @ben
- Reviewer for pull request #482
- Mail to supplier ACME about delay
- Small stuff (Slack inbox, expenses)
- Spec for search refactor
L - Length (in min): 1=60 / 2=30 / 3=45 / 4=15 / 5=20 / 6=90. Sum 260 min.
P - Buffer: Available time 7.5 h (450 min). 60% = 270 min. Plan fits narrowly.
E - Decisions: Eat-the-Frog priority: search refactor spec (frog), then architecture review. Task 4 delegated to @lisa. Task 3 postponed to tomorrow, due 19.05.
N - Follow-up review (evening): Spec done (90 min ok), review 75 min instead of 60 (underestimated), 1:1 extended to 45 min. Small stuff not done, sort it tomorrow.
06
Pitfalls
Recognize symptoms and steer against them
Trap
List becomes a wish list
Symptom
The daily plan contains 15+ tasks and many are pushed forward every week.
What to do
Set a strict upper limit: max five main tasks plus one small-stuff bundle. Re-evaluate postponed items instead of carrying them over automatically.
Trap
Buffer gets eaten up
Symptom
The day is planned to 100%, and every disruption pushes tasks backward.
What to do
Reserve at least 40% buffer. Treat the buffer block in the calendar like an appointment that cannot be overwritten.
Trap
Estimates without review
Symptom
Tasks are estimated at 30 min for weeks but regularly take 60 min.
What to do
Calculate estimation errors weekly. If underestimation is systematic, apply a correction factor of 1.5 or 2.
Trap
Follow-up review is skipped
Symptom
Energy is gone in the evening, the follow-up review is dropped, and the method becomes a daily list without learning.
What to do
Make the follow-up review a 5 min calendar event before the end of the workday. If mornings are easier, move reflection to the morning start.
Trap
Appointments are not counted
Symptom
Meetings are forgotten in the list and the planned task time does not match the calendar.
What to do
Look at the calendar with fixed appointments before step L. Subtract appointments as occupied time before planning tasks.
Trap
Method becomes mechanical
Symptom
The daily plan is executed without priorities being truly decided.
What to do
Turn step E into a decision moment: what will not be done today and why. Consciously note at least one item that gets dropped each day.
07
Stop criteria
Done signals checkable in under a minute
The day consists of more than 80% external appointments, so the person's own planning has no leverage.
No overview of open commitments is available, so the list would be incomplete.
There is no realistic experience with task durations, so estimates would be guesswork.
The person is planning for a team, not for themselves; ALPEN is a single-person method.
Evening reflection discipline has not been established over two weeks, so the method becomes a daily list.
The day falls into an acute crisis, and reactivity wins over planning.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.