Working Calmly The sjTasks Blog

How to run projects without the noise — from the sjTasks team.

  1. What a task is

    One unit of work, one owner, one due date. Why "Redesign the site" is not a task, and what to write down instead.

    Working Calmly
  2. Compound tasks are how work gets lost

    The word "and" in a task title is the tell. Split it into two tasks, or admit it is a project, before it sits half-done for a month.

    Working Calmly
  3. Subtask or new project?

    A subtask only makes sense inside its parent. A project is something a client asks about by name. Here is how to tell which one you have.

    Running Projects
  4. How to structure a project

    A name, a key, the first ten tasks, and who is watching. Task lists only when you have phases. Everything else can wait.

    Running Projects
  5. Estimates without a timer

    Hours typed by hand beat a stopwatch nobody remembers to stop. What "are we over estimate?" tells you about how you price work.

    Estimates and Time
  6. Questions, not reports

    What did Sandy finish last week? What is on Joe's plate? Who is overloaded before Friday? Ask the question; do not build the report.

    Reports
  7. Clients in the room without charging for them

    Guests are free and uncounted on every plan. What a client sees when you let them into their project, and what they cannot touch.

    Clients and Guests
  8. The Monday email

    What a daily summary has to carry so you do not have to open the app to know whether your week is in trouble.

    Reports
  9. Complexity you switch on

    Time tracking, labels and task lists stay out of the way until the day you need them — and when something is off, its fields are not there.

    Working Calmly
  10. Moving off a spreadsheet

    A spreadsheet is a fine task list until the second person and the second client. What it does well, when it stops, and what to carry across.

    Getting Started

Subscribe by RSS — every article in full, in whatever reader you already use.