Practice material · entirely fictional
TaskFlow: the company you work for in this course
A fictional project-management company, invented for the exercises. Copy this page into context/company.md before lesson 1.3.
TaskFlow does not exist. No company, product, person or figure on this page is real, and nothing here should be quoted as market data. It exists so that the exercises have something concrete to bite on, and so that you never practise on your own customers’ data.
The one-liner
Project management software for teams that work across time zones. Positioned between a general work tracker and an engineering issue tracker, sold to teams who are spread across at least three time zones and who resent meetings.
Where the company is
| Fact | Value |
|---|---|
| Stage | Series B |
| Founded | 2021 |
| Team | 50 people, fully distributed |
| Customers | Roughly 10,000 active workspaces |
| Shape of revenue | Per-seat subscription, annual and monthly |
| Biggest account | 400 seats, renews in Q1 |
Your seat
You are Senior Product Manager, Activation & Onboarding. You own three numbers and are asked about them every month:
- Activation rate — the share of new workspaces that complete one real piece of work within seven days. Signing up is not activation. Creating an empty project is not activation.
- Time to first value — median minutes from account creation to that first completed piece of work.
- Week-one feature adoption — how many of the four core features a new workspace touches in its first seven days.
These definitions are deliberately precise. Half the point of the exercises is that a vague metric produces a vague document, whatever tool wrote it.
The standing problem
A new TaskFlow workspace is empty. The product is good once there is work in it and meaningless before that, and a meaningful share of trials never get past the empty state. Leadership believes this is a discoverability problem and wants a guided tour. You are not sure they are right, and Module 2 is where you have to make that argument properly.
Three people who disagree
Sarah Okonkwo
Buys on control: single sign-on, audit trail, who-can-see-what. Will not champion a feature she cannot govern.
Mike Delgado
Wants speed and the integrations he already lives in. Abandons anything that adds a step to filing a ticket.
Alex Renner
Needs to see where work actually is without asking. Reporting is the reason he opens the product at all.
What you already decided
- No new pricing tier this year. Settled, not reopening.
- Mobile is maintenance only until the desktop activation number moves.
- Single sign-on ships regardless of activation work — it is a renewal blocker on the 400-seat account.
House vocabulary
- Workspace
- What a customer creates. Never call it a project — a project is a thing inside a workspace.
- Activation
- Completing a first real piece of work within seven days. Never used loosely to mean signup.
- Thread
- An async discussion attached to a task. Not a chat.
- Handoff
- Passing a task across a time-zone boundary with the context attached. The feature the company was founded on.
Independent and unofficial. This site is published by readers of Antigravity, not by Google. It is not affiliated with, endorsed by or connected to Google LLC. Nothing is hosted here — no software is mirrored, repackaged or distributed, and no installer, licence key, sign-in or payment is ever requested. Antigravity itself is downloaded only from Google, at antigravity.google. Never enter a Google password, a payment card or an API key on this site — nothing here needs one.