stackifiedExplore guides ↗

Everyday productivity

Turn a repeated task into a system

Take one task you repeat and turn it into a short, ordered set of steps you can follow the same way every time.

  • 20–30 min
  • Beginner
  • Checklist + walkthrough
  • Notes app or paper

Before you start

What you’ll work toward

You will have a one-page written routine for your task, tested on a second real example.

What you’ll need

  • One task you repeat, ideally chosen with the guide “Choose a useful task to improve”
  • A notes app, a document or paper
  • Two real examples of the task, such as two past emails or two past jobs

Cost

  • No paid tool required

Scope

  • A manual planning walkthrough; nothing is connected or automated

STEP 1 OF 4

Choose the task and its finish line

Name one repeated task and say what “done” looks like.

  1. Write the task as a short verb phrase, such as “Reply to a new-client enquiry”.
  2. Write one sentence describing what exists when the task is finished.
  3. Write down how you will check that sentence, for example by reading the result once.
Worked example. Task: Reply to a new-client enquiry. Finish line: the person has my availability and one clear next step. Check: read the reply for both.

Expected result

A task name and a finish line sentence at the top of your page.

Check your work

Ask yourself: could a colleague tell from your sentence whether the task is done? If not, make it more specific.

If something goes wrong
  • If you cannot write a finish line, the task may be too vague. Pick a smaller piece of it.
  • If your finish line contains “and” twice, you may have two tasks. Choose one.
Read all steps

  1. Choose the task and its finish line

    Name one repeated task and say what “done” looks like.

    1. Write the task as a short verb phrase, such as “Reply to a new-client enquiry”.
    2. Write one sentence describing what exists when the task is finished.
    3. Write down how you will check that sentence, for example by reading the result once.

    Worked example. Task: Reply to a new-client enquiry. Finish line: the person has my availability and one clear next step. Check: read the reply for both.

    Expected result. A task name and a finish line sentence at the top of your page.

    Check your work. Ask yourself: could a colleague tell from your sentence whether the task is done? If not, make it more specific.

    If something goes wrong

    • If you cannot write a finish line, the task may be too vague. Pick a smaller piece of it.
    • If your finish line contains “and” twice, you may have two tasks. Choose one.

  2. Map the trigger and the output

    Write down what starts the task and what it produces.

    1. Write the trigger: the event that tells you the task needs doing.
    2. List the inputs you need before you can begin.
    3. Write the output: the thing you hand over or save at the end.
    4. Note who receives the output, even if it is only you.

    Worked example. Trigger: an enquiry arrives by email. Inputs: the email, my calendar for this week, my price list. Output: a reply email. Receiver: the person who asked.

    Expected result. Three labelled lines on your page: trigger, inputs and output.

    Check your work. Check that every input is something you can actually get at the moment the trigger happens.

    If something goes wrong

    • If the trigger is “whenever I remember”, write down what you could notice instead, such as a time of day or a new email.

  3. Write the actions in order

    Turn what you do into a short numbered list, with a note for the awkward cases.

    1. Think back to the last time you did the task and write each action in the order you did it.
    2. Combine actions that always happen together, and aim for five to eight lines.
    3. Mark any point where you make a decision, and write the choices beside it.
    4. Add one line for what to do when something is missing or goes wrong.

    Worked example. 1. Read the enquiry. 2. Check my calendar for two free times. 3. Decide: new client or existing client? 4. Copy the matching reply template. 5. Add the two times and one next step. 6. Read it once, then send. If details are missing: ask one question and wait.

    Expected result. A numbered routine of five to eight actions, with decisions marked.

    Check your work. Read the list aloud. Each line should start with a verb and be something you could do without guessing.

    If something goes wrong

    • If the list is longer than ten lines, group related actions under one heading.
    • If you skip a line every time, remove it.

  4. Test the routine on a second example

    Check that your routine works on a real case that is different from the first.

    1. Pick your second real example of the task.
    2. Follow your written routine exactly, without relying on memory.
    3. Mark any line that was unclear, missing or unnecessary.
    4. Fix those lines and save the routine where you can find it again.

    Worked example. Second enquiry came from an existing client. The routine had no line for that, so I added “If existing client, skip the price list and ask what has changed.”

    Expected result. A tested routine on one page, edited after real use.

    Check your work. Compare the result with your finish line from step one. If it meets the line, the routine works.

    If something goes wrong

    • If you ended up improvising, the routine is missing a decision. Add it and test again on a third example.
Everyday productivityGuide

Choose a useful task to improve

Pick one repeated task worth improving, using three plain questions and a clear finish line.

5 min · BeginnerRead guide
Everyday productivityGuide

Map a simple process

Write down the trigger, inputs, actions, decisions and output of one real task so anyone could follow it.

6 min · BeginnerRead guide
Everyday productivityGuide

Write a reusable checklist

Turn a task you know well into a short checklist with a verification step you can use every time.

5 min · BeginnerRead guide