TIBLR
    Analytics

    Fewer numbers, better questions.

    A dashboard with forty metrics tells you nothing, because you cannot act on forty things. TIBLR reports on a handful that reliably precede real problems: work stopping, blockers accumulating, and load landing unevenly on one or two people.

    Free to use · No credit card required

    AnalyticsLast 7 weeks
    Tasks completed per week
    88
    Completed
    3
    Blocked
    5
    Stale
    A position we will defend

    Measuring individuals makes the data worse

    The moment a completion count is attached to a person's review, the count stops describing reality. Tasks get split to inflate volume, hard work gets avoided, and the honest signal you needed — that something is stuck — disappears under the noise. TIBLR's analytics are deliberately team-shaped, and personal tasks are excluded outright.

    Throughput

    Is work still moving?

    Completion volume per week, plotted. Read it for shape rather than level: a steady line that drops for three weeks running is worth a conversation, while a number that is slightly lower than last quarter usually is not.
    • Tasks completed per week over time
    • Current blocked and stale counts alongside the trend
    • Filter to a single team
    • Personal tasks excluded from every figure
    AnalyticsLast 7 weeks
    Tasks completed per week
    88
    Completed
    3
    Blocked
    5
    Stale
    From number to conversation

    The chart tells you where to look, the meeting does the rest

    Analytics is diagnostic, not conclusive. When the blocked count climbs, Meeting Mode is where you find out which tasks and who is waiting on whom — with the actual work on screen rather than an aggregate.
    • Jump from a metric to the tasks behind it
    • Blocked and stale work grouped for the weekly sync
    • Objective progress alongside raw throughput
    • Activity feed for reconstructing a specific sequence of events
    How Meeting Mode works
    Meeting ModeLast 7 days
    Completed since last sync4
    Blocked — needs a decision2
    No movement in 7 days5
    In progress9
    Objective · Launch v2.072%
    What is measured

    The metrics that earn their place

    Completion trend

    Tasks finished per week over time. Useful for spotting the weeks work stopped moving, and asking why.

    Blocked over time

    The count of blocked work, tracked. A rising line is the earliest reliable signal that something structural is wrong.

    Workload distribution

    Open tasks per person. Uneven distribution is common, invisible without a chart, and usually fixable.

    Stale work

    Tasks with no activity inside your window. The backlog rot metric — the number you want trending down.

    Team activity feed

    A chronological record of what changed and who changed it, for when you need to reconstruct how something happened.

    Objective progress

    How completed work maps onto the outcomes it was meant to move, rather than volume alone.

    Common questions

    Keep exploring

    For managers

    Using these signals without turning into a status-collection service.

    Objectives & OKRs

    Progress against outcomes, not just volume of work completed.

    Tasks & views

    The underlying task data every chart here is built from.

    Ready to simplify your team's tasks?

    Set up a workspace, invite your team, and run your first stack review today. Free, no credit card required.