Configuration fatigue

Project management
without the setup.

Somewhere between choosing the tool and using it, the tool became the project. There is a person on your team who knows how the workflow schemes work, and everyone is quietly relieved it is not them. That person did not apply for that job.

14-day trial · £2.49 per seat per month · viewers are free

THE REAL COST

Configurable is not free.

Every setting is a decision somebody has to make, defend, and re-make when a new person asks why it is like that.

  • The owner tax

    One person ends up owning the configuration. They are interrupted for every field change, they are the bottleneck when they are on holiday, and none of that work shows up as work.

  • Decisions nobody wanted

    Should this be a sub-task or a linked issue? A custom field or a label? Both answers work, which is precisely why the argument takes twenty minutes and happens again in three months.

  • Setup outlives its reason

    Configuration made for a team that no longer exists, for a process nobody follows, that everyone works around and nobody dares delete.

WHAT LAVER DOES

Fewer decisions,
on purpose.

Laver is opinionated and small deliberately. That is the product, not a stage it is going through.

  • One way to look at a board

    Columns you name, left to right, one of them marked as the completion column. No view builder, because there is one view. Nobody can configure it wrong.

    Boards
  • A ticket has the fields a ticket has

    Title, rich-text description, assignees, labels, priority, due date, subtasks, comments, attachments, history. The same on every board, so nothing has to be agreed before you start.

    Tickets
  • Templates instead of a setup phase

    Start a board from a template and it arrives with named status columns, labels and a few example tickets already in place — a working board in one step rather than an empty one plus an afternoon.

HONEST FIT

The trade is real.

Fewer decisions means fewer options. If you need the options, this is a downgrade and you should not switch.

A good fit when

  • Nobody on the team wants to be the tool's administrator.
  • Your process is "move it right when it moves right", and the ceremony around it is the part that grates.
  • You would rather change how you work than change how the tool is configured.

Not what this is

  • No custom fields, no issue hierarchy, no epics, no dependencies.
  • No workflow engine — you cannot express "this needs approval before it moves".
  • No automation rules, no integrations, no marketplace.
  • Wiki pages are readable by every workspace member; there are no page permissions.

READY WHEN YOU ARE

Skip the setup phase.

A workspace, a board and a wiki exist the moment you sign up. There is nothing to configure before you can use them.

Start your free trial

Keep reading