01About
zibble
A status meeting, written down and sent on time
Zibble is a workspace for distributed teams: task boards, async standups, timelines and workload views, all fed by the same daily check-in.
02The problem
the call was never really about the call
Distributed teams meet to find out two things: what is moving, and what is stuck. The meeting is a slow way to learn them, and it favours whichever time zone happens to be awake.
The answers already exist. They sit in cards someone dragged, in notes someone typed, in a message that said a task would slip. They just never end up in one place.
Zibble collects them there.
- The old wayOne hour that suits some people. Notes in one person’s document. A timeline fixed by hand later in the week.
- The Zibble wayThree questions answered when convenient. One digest, posted at the hour the team chose. Bars that shift on their own.
03Principles
four rules the product is held to
- i.
write it once
A check-in should update the board, the timeline and the workload view. If a status has to be typed twice, the feature is unfinished.
- ii.
time zones are the default
Nothing in Zibble assumes everyone is online together. Digests post at one agreed hour, and reminders respect each person’s morning.
- iii.
say what is stuck
A task that has not moved in two check-ins reaches the project lead the same day. Bad news travels better when it does not depend on someone volunteering it.
- iv.
keep the screen quiet
Fewer badges, fewer colours, one active item at a time. The workspace should be calm enough to read at nine and forget by ten.
04Made and supported
how it is built, and who answers when it breaks
paid once, per plan
Sketch, Roadmap and Expedition are each a single payment. There is no per-seat meter to watch as the team grows.
changes are written down
Every release gets a plain note describing what changed and why. Nothing moves in your workspace without a line explaining it.
support is an inbox
Write to support@zibblestudios.com. Replies come from the people who maintain the product, with the answer first and the apology only if it is owed.
05Where it is going
what gets built next
A short list, in the order the work is being done. It will change as teams tell us what gets in their way.
- Now
voice check-ins, finished
Faster transcription, and a clearer way to skim a spoken update without playing it back.
- Next
blocker rules you can edit
Choose how many missed check-ins count as stuck, and who hears about it first.
- After that
timeline exports
A timeline as a PDF, for the few people who still ask for a file.
06Get started
retire the status call
Choose a plan, invite the team, and read your first digest tomorrow morning.
Get started