DEV Community: Otper

What Should a Good Project Delivery Report Actually Tell You?

Otper — Thu, 17 Sep 2026 11:23:52 +0000

A project report shouldn't just tell you how many tasks exist.

For a team managing work every day, a useful report should help answer a few simple questions:

What did we actually finish?
How much work is still in progress?
What's overdue?
Where is work getting stuck?
Who is carrying the current workload?
Start with the work itself

One problem with traditional status reporting is that someone has to manually collect the information.

A person checks different boards, asks for updates, updates a spreadsheet, and eventually creates a report.

By the time the report is ready, some of the information may already be outdated.

A better approach is to derive reporting from the work the team is already doing.

When a card moves from In Progress to Done, that activity can become part of the delivery data automatically.

Useful metrics for a team

Some of the metrics we find particularly useful are:

Completed work — how many tasks actually finished during a period.

Throughput — how many cards were created compared with how many were completed.

Work in progress — how much active work the team currently has.

Bottlenecks — which workflow stage is taking the longest.

Overdue work — which tasks have passed their due dates and who owns them.

Stuck work — cards that haven't had activity for an extended period.

Workload by owner — how active work is distributed across the team.

These metrics provide more context than simply counting open tasks.

The goal isn't more charts

A report is useful when it helps a team make a decision.

For example, if one workflow stage consistently takes longer than the others, that may be worth investigating.

If one person is carrying significantly more active work, the team can decide whether to rebalance it.

If completed work is consistently lower than incoming work, the team can see that before the backlog becomes a bigger problem.

The report shouldn't make the decision for the team. It should make the relevant information easier to see.

Reporting should come from real activity

This is the approach we're taking with Otper.

The reporting data is derived from the cards teams already move through their boards, including completed work, throughput, bottlenecks, overdue work, workload, and delivery risk.

The idea is simple:

Less time collecting status information. More time discussing what to do about it.

A good project report isn't just a collection of numbers. It should help a team understand what is happening in the workflow right now.

Kanban for Teams: A Practical Guide to Managing Work

Otper — Wed, 16 Sep 2026 07:39:06 +0000

As a team grows, keeping track of work can quickly become difficult.

Tasks get assigned in different places, priorities change, and it's not always obvious what someone is currently working on.

A Kanban board gives teams a simple visual way to see what's happening.

What is Kanban?

Kanban is a workflow method where work is represented as cards and moved through stages.

A basic team workflow might look like:

Todo → In Progress → Review → Done

Each card represents a piece of work and can include an owner, priority, due date, and other useful information.

Why Kanban works well for teams

The main benefit is visibility.

Instead of asking for updates repeatedly, team members can look at the board and quickly understand:

What needs to be done
What is currently being worked on
Who owns each task
What is blocked
What has been completed

This becomes especially useful for remote and distributed teams.

Keep the workflow simple

One common mistake is creating too many columns.

A team doesn't necessarily need a separate stage for every small step. The board should reflect the actual workflow the team follows.

It's also useful to limit how much work is happening at the same time. Too many tasks in progress can make it harder to finish anything.

Make ownership clear

Every important task should have a clear owner.

When ownership is unclear, tasks can remain visible on the board but still not move forward.

A simple combination of task + owner + due date + status can make accountability much clearer.

Kanban is about visibility, not just task lists

A useful Kanban board should help answer a few basic questions:

What are we working on?
Who is responsible?
What's blocked?
What's coming next?

That's where Kanban becomes more than a task list. It becomes a shared view of how work is moving through the team.

We originally explored these ideas in more detail in our guide on Kanban for teams.

If you're setting up a Kanban workflow for your team, start simple and add complexity only when the workflow actually requires it.

We Launched on Product Hunt: Here’s What Happened

Otper — Tue, 15 Sep 2026 06:51:31 +0000

We recently launched Otper on Product Hunt.

Otper is a Kanban project management tool we’re building for teams that want a simpler way to manage tasks, ownership, and delivery.

The launch was a good learning experience.

A few things stood out:

Getting people to notice a launch is harder than expected.
A clear explanation of who the product is for matters more than a long feature list.
Early feedback is often more valuable than launch-day numbers.
People notice small workflow problems that the team building the product can easily overlook.

The biggest takeaway for us was simple: launching isn't the finish line. It's the beginning of getting real feedback.

We're continuing to improve Otper based on what teams actually need and how they work.

If you're interested in following the journey, you can find the Product Hunt launch here: Product Hunt.

Why “In Progress” Isn’t Enough

Otper — Mon, 14 Sep 2026 09:38:21 +0000

A Kanban board can look busy without actually showing how work is moving.

You might have 10 cards marked In Progress, but that doesn't tell you:

Who owns each task?
Which task is blocked?
How long has it been sitting there?
What should be finished next?

For small engineering teams, a simple workflow can make this much clearer:

Todo → In Progress → Blocked → Done

Add a clear owner and due date to each task, and suddenly the board becomes more than a list of work. It becomes a quick view of what is actually happening.

This is one of the ideas we've been exploring while building Otper: make delivery status easy to understand without adding unnecessary process.

Sometimes, better visibility doesn't require more tools or more meetings. It just requires making the right information visible.