Flowtask is the planning half of Ceyu. It shares the workspace and the project model with the whiteboard, so a task can point at the frame it came from and a board can show what is outstanding.
A task carries the usual fields, and they are all optional except the title:
@ mentionsLink tasks so that one waits on another. Dependencies drive the Gantt view and the critical path — see Gantt, capacity & time. Their real value is that a slip in one place becomes visible in every place it matters, without anyone having to notice.
Add the fields your process actually needs, per project — text, number, date, single select and more. Custom fields appear as columns in the list view and can be filtered on.
Worth resisting the urge to add ten of them on day one. Fields nobody fills in are worse than no fields, because they make every view look incomplete.
| View | Best for |
|---|---|
| Board | Day-to-day flow. Kanban columns with swimlanes and custom statuses. |
| List | Bulk editing and anything that needs to be scanned as a table. |
| Calendar | Due dates against the actual week, with Google Calendar events alongside. |
| Timeline | How projects overlap across a longer horizon. |
| Gantt | Dependencies and a critical path, for the plan you have to defend. |
| My Day / My Work | One person's work across every project. |
Each project defines its own statuses through the status editor, so a design project is not forced into an engineering vocabulary. Swimlanes split the board by assignee, priority or a custom field.
Build a query once — everything critical and overdue, assigned to this person, in these projects — and save it as a reusable view. Shared filters mean a team argues about the work rather than about whose list is right.
A task template spins up a piece of recurring work with its checklist already filled in. A recurring task goes further and creates itself on a schedule.
Between them they cover most of what a studio does every month and forgets about once a quarter.
Select an object on a board and send it to Flowtask. It becomes a task in the project attached to that board, keeping a reference to where it came from. Turning a brainstorm into a plan does not require retyping it.