# A calmer weekly planning workflow

A practical weekly review for turning a busy task list into a few clear outcomes, useful issue descriptions, and visible next steps.

Canonical URL: https://blog.vikan.dev/posts/a-calmer-weekly-planning-workflow/
Author: vikan team
Published: 2026-09-22
Language: en

A weekly plan is useful when it makes the next decision easier. You should be able to open it on Tuesday afternoon and understand which task deserves attention, what progress means, and what is waiting on someone else.

Try the following routine in vikan. Start with a short review, choose a small set of outcomes, and make the active issues easy to act on. Adjust the amount of work to the time you actually have.

## 1. Review the work already in motion

Open My Issues or a filtered view of your team's active work. Read through the tasks in progress before adding anything new.

For each issue, ask whether its status still reflects reality. Close completed work. Add a comment when a decision or dependency has changed. If something is waiting, record what it needs and who can provide it, so the next review does not start from the same uncertainty.

This pass gives the new plan an honest starting point.

## 2. Choose a few observable outcomes

Write down what should be different by the end of the week. “Work on the website” leaves the finish line unclear. “Publish the revised getting-started page” describes an outcome you can check.

Choose fewer outcomes when your calendar includes support, meetings, or other responsibilities. Leave room for work you cannot fully predict. The plan should help you make tradeoffs when new requests arrive.

## 3. Turn each outcome into useful issues

Create or refine the issues needed to reach those outcomes. Keep each title concrete and put enough context in the description for someone to resume without asking you to repeat the background.

A simple description can use three headings:

```markdown
## Context
What problem are we solving, and for whom?

## Next action
What is the first useful step?

## Done when
What result can we check?
```

Assign responsibility where it is clear. Break a large issue into child issues when the steps need separate ownership or status.

## 4. Make the plan easy to revisit

Use a list to review details, or a board to check how work is moving through statuses. Save a useful filtered view so the next daily check begins in the same place.

Keep related explanations in issue descriptions or project documents. A plan is easier to maintain when a change can be recorded beside the task it affects.

## 5. End with a short handoff to yourself

Before finishing a session, leave one sentence on the next active issue: what you learned and what you will do next. During the next weekly review, compare the intended outcomes with what happened and adjust the following week.

If you expect to work without a connection, open the workspace and relevant descriptions beforehand. Our [local-first preparation guide](/posts/local-first-project-management/) covers what to check.