Solution · team and processes
A pipeline between departments: hand-off by button, and a return for rework is visible at once
A project that passes through several departments loses context at every hand-off. The solution is one project card that moves through the departments’ spaces by stage: hand-off by button, returns highlighted, and the final version of the calculation marked explicitly.
What it looks like
Mock-ups with demo data, no real data
📚Projects
| Project | Department | Stage | Status |
|---|---|---|---|
| Book “Example” | Editorial | 8 · Work | In progress |
| Book “Demo” | Sales | 4 · Contract | Returned |
| Book “Sample” | Back office | 13 · In print | In progress |
At a glance
- In production
- At a client under NDA
- Fits
- Sales → production → launch: agencies, studios, product teams
- Needs
- Only Notion
Result at the client
4 departments
in one system at the client
Estimate for your company
≈4 h
a week clarifying statuses between departments
Assumption: 4 departments × ~1 hour a week of “what stage is it at” messages (our assumption)
This is a calculation, not a promise: plug in your own volumes and the figure changes.
Before
- At hand-offs it gets lost who did what and where the project is now.
- A return for rework drowns in chat.
- Different departments look at different versions of the calculation.
What was built
Department spaces
Each department has its own space, but there is one project card.
Stages and hand-off
Numbered stages; hand-off to the next department with one button.
Returns and versions
A returned project is highlighted; the final version of the calculation is marked explicitly.
Stack
- Notion
- Notion buttons
- Linked databases
Where it runs
Questions
How many departments can be connected?
As many as the process has stages: the pattern is the same — a space, stages and hand-off buttons.