# Penda — full text

> Penda is an independent editorial publication about getting meaningful work done: proven focus methods explained step by step, and clear-eyed guidance on choosing productivity apps by criteria rather than hype.

# How to Break Down a Project Into Actionable Tasks

> Break a project into tasks by defining the finished outcome first, listing its major deliverables, and splitting each deliverable until every task has one visible result, one owner, and a clear completion test. Write task names as verb-plus-object actions, identify dependencies and decisions, estimate in ranges, and place only the next executable actions on today's list. Keep milestones separate from tasks, and revise the breakdown when new information appears instead of pretending the first plan was prophecy.

Source: https://penda-app.com/how-to-break-down-a-project/  
Publisher: Penda  
Published: 2026-09-01  
Updated: 2026-09-01

## A project becomes manageable when "done" becomes visible

To break a project into actionable tasks, define the finished outcome first, list the major deliverables that create it, and split each deliverable until every task has one clear result, one owner, and an unambiguous completion test. Write tasks as verb-plus-object actions, mark dependencies and decisions, estimate in ranges, and put only the next executable actions on today's list.

That is the method. The common mistake is starting with activity: brainstorm, research, discuss, work on. Those words can describe a very busy week without describing anything finished. Start from the other end. What will exist when this project is complete that does not exist now?

"Redesign website" is not a task. It is a fog bank wearing a due date. "Approve homepage wireframe" is a task. The work of decomposition is turning one into enough of the other that progress stops depending on remembering what you meant last Tuesday.

## Step 1: write the finish line

Write one sentence that names the result, the people who must accept it, and the final condition. Make every part concrete:

> The workshop project is done when the event has run, the coordinator has approved the recording, and every registered guest has received the follow-up message.

Examples:

- The workshop is done when 30 registered guests receive the materials, attend the live session, and get the follow-up recording.
- The office move is done when every team can work from the new location, required services are active, and the old space is returned as agreed.
- The portfolio is done when six approved case studies are live on the new domain and the contact form delivers a tested message.

Add exclusions. If the portfolio project does not include a new logo, say so. Scope becomes clearer when the attractive side quests are politely shown the door.

Also name the deadline source. A legal filing date, event booking, or client commitment is real. "It would feel nice to finish by Thursday" is a preference. Both can inform planning, but they should not be confused.

## Step 2: identify deliverables, not departments

Deliverables are pieces of the final outcome: documents, decisions, approved designs, configured systems, trained people, delivered events. List five to ten major results before writing individual tasks.

For a small webinar project, deliverables might be:

- approved topic and audience;
- confirmed speaker and date;
- registration page;
- presentation deck;
- promotion assets and schedule;
- rehearsal and technical setup;
- live event;
- recording and follow-up message.

This is more useful than organising the plan under "marketing," "design," and "operations." Departments describe who may work; deliverables describe what the project must produce. Ownership comes later.

Check completeness by walking through the project from the user's perspective. How do they discover it, join it, receive value, and know what happens next? Then walk through the backstage path: approvals, access, testing, handoffs, support, and closure. The boring edge cases are where projects keep emergency snacks.

## Step 3: split each deliverable into tasks

Take one deliverable and ask, "What must be true immediately before this exists?" Keep working backward until you reach actions someone can begin.

For **registration page live**, the breakdown might be:

1. Confirm title, date, speaker bio, and attendee promise.
2. Draft page copy.
3. Review copy with speaker.
4. Configure registration form and confirmation email.
5. Add privacy wording and required consent fields.
6. Build page.
7. Submit test registration on mobile and desktop.
8. Fix failed tests.
9. Obtain final approval.
10. Publish page and verify the live URL.

Each line creates a visible state change. "Work on registration page" creates only calendar residue.

Use subtasks for components that belong to one owner and one parent result. Use separate tasks when work has a different owner, date, dependency, review process, or status that matters to the team. Asana's current guidance makes the same practical distinction: subtasks help capture components of multi-step work, while work with different deliverables may deserve separate tasks or a project.

## Step 4: write executable task names

Start each title with a verb that describes the action:

- draft, compare, decide, call, test, revise, approve, send, publish;
- not strategy, website, budget, outreach, general planning, status updates, or the always-menacing "follow up."

Then add the object and result:

- **Weak:** Vendor research
- **Better:** Compare three captioning vendors against budget and turnaround
- **Weak:** Speaker
- **Better:** Email speaker the final brief and request approval
- **Weak:** Testing
- **Better:** Submit test registration on iPhone, Android, and desktop

A useful task description contains:

- owner;
- completion test;
- source file or starting link;
- constraints or decision criteria;
- prerequisite;
- expected output;
- due date, if it is real.

Do not make the assignee excavate context from six chat threads. Attaching the brief is not administrative fussiness. It is a gift to the person you will be tomorrow morning.

## Step 5: separate milestones, tasks, and checklists

These three objects do different jobs:

| Item | Meaning | Example |
|---|---|---|
| Milestone | Important state reached; usually no duration | Registration opens |
| Task | Work that produces one result | Publish approved registration page |
| Checklist item | Small verification inside a task | Confirm title tag |

People often turn milestones into tasks and wonder who should be assigned to "launch." Launch is the moment produced by completed tasks. Give the work owners; use the milestone to see whether the project reached the checkpoint.

Checklists are excellent for repeatable quality steps that do not deserve individual schedule management. A publish task may include checking links, metadata, mobile layout, and analytics. Creating four separately dated tasks for those two-minute checks adds tracking overhead without adding clarity.

## Step 6: expose dependencies and decisions

A dependency means one task cannot sensibly begin until another produces something. Record it explicitly:

- final design depends on approved wireframe;
- invitation depends on confirmed date;
- print order depends on final quantity;
- launch depends on passed payment test.

Then distinguish hard dependencies from habits. Drafting an FAQ may not truly require the final page design. Work that can happen in parallel should not wait merely because the task list was written top to bottom.

Decisions deserve tasks too. "Choose venue" should name the inputs, decision-maker, criteria, and deadline. Otherwise comparison work expands indefinitely because no moment of choice was designed.

For external waiting, create two items: the request and the follow-up. "Send contract to legal" is complete when sent; "receive legal approval" is a milestone or waiting state, not invisible dead time. Add a dated follow-up so the project does not rely on anxious remembering.

## Step 7: estimate in ranges and add uncertainty

Estimate the work after breakdown, not before. "Create campaign" is impossible to estimate honestly. "Draft three email versions from the approved brief" is less mysterious.

Use ranges when uncertainty is real: two to four hours, one to two days. Note whether the estimate means active work or elapsed time. A task may take 20 minutes of effort and three days of waiting.

Add explicit discovery tasks where knowledge is missing:

- interview two customers about the checkout problem;
- test whether the export preserves image captions;
- obtain and inspect a physical proof from the printer;
- prototype the risky integration;
- confirm which team owns the database.

The output of discovery is evidence or a decision, not the whole project. Plan to the next knowledge point, then revise. Pretending unknown work has a precise estimate does not make the plan accurate; it merely gives the surprise an appointment.

## Step 8: define acceptance before starting

A completion test prevents the final 10 percent from reproducing overnight.

Ask what someone can inspect:

- Copy is approved by the named reviewer and stored in the project folder.
- Form accepts a valid submission, rejects missing required fields, and sends the confirmation message.
- Report contains the agreed sections and figures reconcile to the source workbook.
- Room is booked, deposit recorded, access time confirmed, and cancellation terms saved.

Avoid "looks good" unless the task genuinely ends with one person's taste. Name the reviewer and the criteria. If approval requires several people, decide who breaks a tie and how long review may take.

## Step 9: choose the next actions

A complete project plan may hold 60 tasks. Today's list should not. Filter for tasks that are unblocked, owned by you, and appropriate to the available time and attention.

If a task still triggers avoidance, split it once more. "Draft proposal" might begin with "open last proposal and copy the section headings" or "write three bullet points for the problem statement." The first action should be physically obvious, not motivationally inspiring.

Then use a focus method to execute it. One [Pomodoro](/pomodoro-technique-guide/) can move a well-defined task; it cannot rescue a vague project title. A timer aimed at "new website" simply measures 25 minutes of deciding where to start.

Keep the project in whichever system passes your real criteria. Our [app guides](/app-guides/) cover capture, sync, recurrence, export, pricing, and completion friction. The decomposition method itself works on paper, in a spreadsheet, or on a whiteboard. The app is storage, not management intelligence.

## A reusable project-breakdown checklist

Before calling the plan ready, ask:

- Is the final outcome stated in one sentence?
- Are exclusions and real deadlines recorded?
- Does every major deliverable exist in the plan?
- Does each task begin with a concrete verb?
- Can one owner complete and verify each task?
- Are approval, testing, and follow-up included?
- Are dependencies visible?
- Are decisions named rather than implied?
- Do unknowns have discovery tasks?
- Are milestones separate from work?
- Are estimates labelled as effort or elapsed time?
- Is the next executable action obvious?

Review the breakdown after the first real work begins. Plans improve when they meet reality. New tasks are not proof that planning failed; hidden work becoming visible is one of planning's jobs.

Browse our [focus methods](/focus-methods/) for more ways to execute the work once it is clear. A project plan should make the next step boringly obvious. Save the drama for the project launch, where at least it can have catering.

## Sources

- [Asana: When and How to Use Subtasks](https://asana.com/resources/asana-tips-subtasks)
- [Asana: Create a Project Timeline](https://asana.com/resources/create-project-management-timeline-template)
- [Atlassian: How to Track Project Progress](https://www.atlassian.com/work-management/project-management/project-progress)

## Frequently asked questions

**What is the difference between a project and a task?**

A project requires multiple actions and produces a larger outcome; a task is one trackable piece of work with a clear finish. 'Launch the newsletter' is a project. 'Draft the welcome email' is a task. If an item contains several verbs, owners, handoffs, or completion dates, it probably needs decomposition. If you could start it now and unambiguously mark it done, it is probably task-sized.

**How small should project tasks be?**

Small enough that one person can understand, estimate, and finish each task without discovering a hidden project inside it. Large enough that tracking it provides useful information. A task lasting several minutes may belong in a checklist; one spanning many days or handoffs probably needs splitting. Use clarity rather than a rigid hour limit: if 'done' is debatable or the next action is unclear, break it down again.

**How do I break down a project when I do not know all the steps?**

Create discovery tasks instead of inventing certainty. 'Interview two users,' 'confirm export format,' or 'prototype payment flow' can produce the information needed for the next breakdown. Mark assumptions and decisions explicitly, plan only to the next knowledge point, then revise. Unknown work is not unplannable; it simply needs a task whose output is reduced uncertainty rather than the final deliverable.

**Should subtasks have their own due dates?**

Use dates when a subtask has a real deadline, dependency, handoff, or owner who needs scheduling clarity. Do not assign ceremonial due dates to every five-minute checklist item; that creates a calendar full of fake emergencies. The parent deliverable needs a date, and critical steps need dates far enough ahead to leave review and correction time. Work backward from the real external commitment.

**What makes a task actionable?**

An actionable task begins with a concrete verb, names the object or result, includes the context needed to begin, and defines what completion means. 'Budget' is a topic. 'Compare the three vendor quotes and select one by Friday' is actionable. Attach the relevant file or link, name the owner, and record any prerequisite. The task should answer: what do I do next, with what, and how will I know it is done?


---

# How to Choose a To-Do List App: 7 Features That Matter

> To choose a to-do list app, evaluate candidates against seven criteria instead of feature lists: capture speed (a task recorded in seconds), reliable cross-device sync, real recurring tasks and reminders, an organization model that matches how you think, data export, honest pricing whose free tier covers your workflow, and frictionless check-off. Shortlist two apps, then trial one for a week with real tasks before paying.

Source: https://penda-app.com/how-to-choose-todo-list-app/  
Publisher: Penda  
Published: 2026-07-19  
Updated: 2026-08-16

## How to Choose a To-Do List App

To choose a to-do list app, ignore feature lists and start with criteria: how fast you can capture a task, whether it syncs across your devices, how it handles recurring tasks and reminders, whether you can export your data, and what the free tier actually includes. Test your top pick with real tasks for a week before committing to a paid plan.

That's the whole method. The rest of this guide explains each criterion, why it matters, and how to run a fair one-week trial.

## Why Criteria Beat "Best App" Lists

Roundups of the "best to do list app" go stale fast — features ship, prices change, apps get acquired. Criteria don't. If you know what to look for in a task manager app, you can evaluate anything on the market, including apps released after this article was written.

There's a second reason: the best app is personal. A freelancer, a student, and a parent managing a household need different things. A ranked list can't know your needs; a checklist of criteria lets you rank apps yourself.

## The 7 Features That Matter

### 1. Capture Speed

Capture speed is the time between thinking of a task and having it safely recorded. It's the single most important criterion, because a to-do app only works if you actually put tasks into it. If adding a task takes more than a few seconds, you'll stop bothering.

Look for a quick-add shortcut, a widget, or natural-language entry (typing "call dentist tomorrow 9am" and having the date parsed automatically). Test it standing up, on your phone, with one hand.

### 2. Cross-Device Sync

Your task list needs to be wherever you are: phone, laptop, and ideally a browser tab on someone else's machine. Check three things:

- **Platforms.** Does it run natively on every device you own?
- **Reliability.** Does a task added on one device appear promptly on the others?
- **Offline behavior.** Can you add and check off tasks without a connection, with changes syncing later?

Some excellent apps are single-platform by design. That's fine — but only if you genuinely live on one platform.

### 3. Recurring Tasks and Reminders

Most real to-do lists are full of repeating obligations: pay rent, water plants, weekly review. Check whether the app handles genuine recurrence ("every second Tuesday," "3 days after I complete it") or only simple daily/weekly repeats. Then check reminders: can a task notify you at a time you choose, and do those notifications actually fire reliably on your devices?

### 4. Organization That Matches How You Think

Apps organize tasks with some mix of lists, projects, tags, priorities, and due dates. More options are not better — unused structure becomes clutter. Ask instead: does the app's model match how you already sort work in your head? If you think in projects, you need projects. If you think in "today vs. later," a simpler app will serve you better than a powerful one.

### 5. Data Export

Before you invest months of task history in an app, confirm you can get your data out — as CSV, JSON, or another readable format. Export matters for two reasons: apps shut down or change hands, and your needs change. An app with no export path is quietly charging you a switching cost you'll pay later.

### 6. Honest Pricing

The free vs. paid question comes down to one test: **does the free tier cover your actual workflow, or is it a demo?** Common paywall lines include reminders, attachments, collaboration, and caps on the number of lists or projects. Neither model is wrong — a sustainable paid app is often a safer bet than a free one with no visible business model — but you should know which features sit behind the paywall *before* you build habits around them. Pricing changes frequently, so verify current plans on the developer's own site.

### 7. Low Friction to Check Things Off

Completing a task should feel instant: one tap, no confirmation dialog, no lag. The check-off moment is the app's core loop, and small friction compounds across dozens of daily interactions. Also note how the app handles overdue tasks — does it nag you into avoidance, or make rescheduling painless?

## Quick Evaluation Checklist

| Criterion | Pass looks like |
|---|---|
| Capture speed | New task recorded in under ~5 seconds |
| Sync | Works on every device you own, including offline |
| Recurrence | Handles your real repeating tasks and reliable reminders |
| Organization | Matches how you already sort work |
| Export | CSV/JSON or similar readable export exists |
| Pricing | Free tier covers your workflow, or paid price is one you'd sustain |
| Check-off friction | Completing and rescheduling tasks feels instant |

## Run a One-Week Trial

Shortlist two apps that pass the checklist, then live in one for a full week with your real tasks — not sample data. Capture everything, complete things, reschedule things, let a recurring task come due. A week surfaces the friction a five-minute demo hides.

One caution: a to-do app stores your commitments; it doesn't execute them. Pairing your list with a focus method like the [Pomodoro Technique](/pomodoro-technique-guide/) is how tasks actually get done. And when you're ready to evaluate other categories of tools with the same criteria-first approach, our [app guides](/app-guides/) cover them.

Pick the app that disappeared into your week. That's the winner.

## Frequently asked questions

**What is the most important feature in a to-do list app?**

Capture speed — the time between thinking of a task and having it recorded. A to-do app only works if you consistently put tasks into it, and every extra tap or menu makes that less likely. Look for quick-add shortcuts, widgets, or natural-language entry, and test capture on your phone, one-handed, before judging anything else about the app.

**Are free to-do list apps good enough, or should I pay?**

It depends on where the paywall sits. Apply one test: does the free tier cover your actual workflow, or is it a demo? Common paid-only features include reminders, attachments, collaboration, and caps on lists or projects. A sustainably priced paid app can be a safer long-term bet than a free one with no visible business model. Always verify current pricing on the developer's own site, since plans change frequently.

**How do I test a to-do list app before committing?**

Run a one-week trial with your real tasks, not sample data. Capture everything that comes up, complete tasks, reschedule a few, and let at least one recurring task come due so you can see how reminders behave. A full week surfaces the friction that a five-minute demo hides. If the app disappeared into your week — you used it without thinking about it — that's your winner.

**Why does data export matter in a task manager?**

Because task apps shut down, get acquired, or stop fitting your needs, and months of task history is expensive to lose or re-enter. Before committing, confirm the app can export your data in a readable format such as CSV or JSON. An app with no export path is quietly imposing a switching cost you will pay later if you ever want to leave.


---

# Pomodoro Technique: What It Is and How to Start (5 Steps)

> The Pomodoro Technique is a time-management method where you work on one task for 25 minutes, then take a 5-minute break, repeating the cycle and taking a longer 15–30 minute break after every four rounds. Each 25-minute interval is called a pomodoro — Italian for tomato — named after the kitchen timer Francesco Cirillo used when he developed the method in the late 1980s. All you need to start is a timer and a single, clearly defined task.

Source: https://penda-app.com/pomodoro-technique-guide/  
Publisher: Penda  
Published: 2026-07-19  
Updated: 2026-08-16

## What Is the Pomodoro Technique?

The Pomodoro Technique is a time-management method in which you work on a single task for 25 minutes, take a 5-minute break, and repeat — with a longer break after every four rounds. Each 25-minute work interval is called a "pomodoro," Italian for tomato, named after the tomato-shaped kitchen timer its creator, Francesco Cirillo, used as a university student in the late 1980s.

The method's appeal is its simplicity: you need nothing more than a timer and a task. Its real power, though, is psychological. A 25-minute commitment is small enough that your brain stops negotiating. You are not promising to finish the report — you are promising to work on it until the timer rings. That reframing is what makes it one of the most durable techniques in the [focus methods](/focus-methods/) toolbox.

## How to Use the Pomodoro Technique in 5 Steps

You can start your first pomodoro in the next two minutes. Here is the full cycle.

### Step 1: Choose one task

Pick a single, specific task before you start the timer. "Work on the presentation" is too vague; "draft the first three slides" is right. If your tasks live scattered across sticky notes and inboxes, it helps to gather them in one place first — our guide to [choosing a to-do list app](/how-to-choose-todo-list-app/) covers what to look for.

### Step 2: Set a timer for 25 minutes

Any timer works: your phone, a kitchen timer, a browser tab. The tool does not matter. Starting the timer does — it marks a clear boundary between "deciding to work" and "working."

### Step 3: Work until the timer rings — nothing else

For 25 minutes, the chosen task is the only thing you do. If a distraction pops into your head ("reply to Sam," "look up flights"), jot it on a piece of paper and return to the task. If a genuine emergency interrupts you, the pomodoro is void — handle it, then start a fresh one. A pomodoro is indivisible: there are no half-pomodoros.

### Step 4: Take a 5-minute break

When the timer rings, stop — even mid-sentence. Stand up, stretch, get water. The break should be genuinely restful, which usually means staying off feeds and inboxes; five minutes of scrolling tends to leave you less refreshed than five minutes away from the screen.

### Step 5: After four pomodoros, take a longer break

Every fourth cycle, take a longer break of roughly 15–30 minutes. This is when you eat, walk, or let your mind wander. Then the sequence starts again.

## How Long Is a Pomodoro?

A standard pomodoro is 25 minutes of focused work. The classic rhythm looks like this:

| Interval | Length |
|---|---|
| Work session (1 pomodoro) | 25 minutes |
| Short break | 5 minutes |
| Long break (after 4 pomodoros) | 15–30 minutes |

One full cycle of four pomodoros — work plus short breaks — runs about two hours before the long break. The 25/5 split is a convention, not a law. Cirillo's original method uses it, but many people settle into 50/10 for deep work or 15/3 when focus is hard to come by. The principle matters more than the numbers: fixed work intervals, protected breaks, one task at a time.

## Does the Pomodoro Technique Work?

For many people, yes — with honest caveats. The technique directly targets two of the most common focus problems:

- **Procrastination.** Starting is the hardest part of most tasks, and a 25-minute commitment lowers the cost of starting to almost nothing.
- **Distraction drift.** The ticking timer gives ambient interruptions — a notification, a stray thought — something to bounce off. You are "mid-pomodoro," so it can wait.

It also builds a useful side skill: estimation. After a few weeks you will know that a weekly report takes about three pomodoros, which makes planning your day far more realistic.

Where it struggles is equally clear. Jobs built around constant availability — support queues, on-call work, back-to-back meetings — leave few unbroken 25-minute windows. And people already in a deep flow state sometimes find the timer jarring, since it forces a break they did not need. If that is you, longer intervals or a looser stopping rule may serve better. No timer fixes an overloaded schedule; the method organizes the work you have, it does not shrink it.

## Common Mistakes to Avoid

- **Skipping breaks.** The breaks are the mechanism, not the reward. Powering through them turns the method back into ordinary grinding.
- **Batching unrelated micro-tasks into one pomodoro without a list.** Fine to group small tasks — but write the batch down first so you are not deciding mid-interval.
- **Treating the timer as a productivity scoreboard.** A day of four honest pomodoros on the right task beats ten scattered ones.
- **Answering "quick" messages mid-pomodoro.** Quick messages are how pomodoros die. Note it, finish the interval, then reply.

## Getting Started Today

Pick one task you have been avoiding, set a 25-minute timer, and start. That single, slightly reluctant first pomodoro is the entire onboarding process — everything else is refinement.

## Frequently asked questions

**How long is a pomodoro?**

A standard pomodoro is 25 minutes of uninterrupted work on a single task, followed by a 5-minute break. After four pomodoros, you take a longer break of roughly 15–30 minutes. The 25/5 split is a convention rather than a rule — many people prefer 50/10 for deep work or shorter intervals when focus is difficult. The core principle is fixed work intervals with protected breaks.

**Does the Pomodoro Technique actually work?**

It works well for two common problems: procrastination, because committing to just 25 minutes makes starting easy, and distraction, because the running timer gives interruptions something to wait behind. It also improves your ability to estimate how long tasks take. It fits poorly with jobs requiring constant availability, like support or on-call work, and some people in deep flow find the forced breaks disruptive.

**What do I need to start using the Pomodoro Technique?**

Just a timer and one clearly defined task. Any timer works — a phone, a kitchen timer, or a browser tab. Pick something specific like "draft the first three slides" rather than a vague goal, set the timer for 25 minutes, and work on only that task until it rings. Dedicated Pomodoro apps exist, but none are required to begin.

**Can I change the 25-minute interval?**

Yes. Francesco Cirillo's original method uses 25 minutes of work and 5 minutes of break, but the lengths are adjustable. Common variations include 50 minutes of work with a 10-minute break for deep, absorbing tasks, or 15 minutes with a 3-minute break when concentration is hard to sustain. Keep the structure — fixed intervals, real breaks, one task at a time — and tune the numbers to your work.


---