What has your team already decided without writing it down?
A product lead points Learning Nodes at two ClickUp lists. It reads the tasks once, and comes back with the situation, the decisions still open, and the ones the team has been acting on without ever recording them.
An example of what Learning Nodes returns from ClickUp lists. The team and its tasks are made up for the example.
INTERACTIVE VERSION · TWO MINUTES
Click through a product lead's session in the Workstation, one step at a time. A short note explains each screen. No sign-up, and nothing is saved.
The situation, as typed
Read once from ClickUp
Features
- Ship onboarding v2In review
- Define pricing tiersIn progress
- Migrate billing to StripeIn progress
- Single sign-on for enterprise accountsTo do
- Audit log exportTo do
UX
- Rework the sign-up flow for the new tiersBlocked
- Annual billing toggle on the pricing pageIn review
- Churn survey at cancellationDone
Learning Nodes reads titles, statuses, descriptions, assignees, due dates, priorities and tags. It reads once, stores no token and never writes anything back to ClickUp.
The decision Learning Nodes proposed
Choose between shipping onboarding v2 now and holding it until the pricing tiers are final
- Ship onboarding v2 now
- Hold onboarding v2 until the pricing tiers are final
You have to choose between shipping onboarding v2 now and holding it until the pricing tiers are final. It turns on how much of the sign-up flow the new tiers will change and on what six more weeks of the old onboarding costs you in new accounts.
Decided without being written down
Payments run on Stripe.
Three tasks assume it ("Migrate billing to Stripe", "Annual billing toggle", "Rework the sign-up flow"). No task or comment records the choice or what it was compared with.
Enterprise is a target this quarter.
"Single sign-on" and "Audit log export" were both added in the same week. Nothing says who decided to pursue enterprise accounts, or what it displaces.
Annual billing ships before any monthly discount.
The annual toggle is in review while no task exists for monthly discounts, although the pricing tiers task mentions both.
What would make each option right
Ship onboarding v2 now
The new tiers change only the pricing step of the sign-up flow, and the old onboarding is losing more than new accounts lost per week accounts a week.
Hold onboarding v2 until the pricing tiers are final
The new tiers change more than the pricing step, so shipping now means rebuilding the flow twice within six weeks.
The words in angle brackets are a line only you can set. Learning Nodes never makes that number up.
The questions in the way
- Which steps of the sign-up flow do the new pricing tiers change?
- How many new accounts a week drop out of the current onboarding?
- Who decided to pursue enterprise accounts this quarter, and what was set aside for it?
- Was Stripe chosen against an alternative, and is that comparison recorded anywhere?
Claims nobody had checked
three enterprise prospects have asked for single sign-on
Two of the eight tasks exist because of this. If it is one prospect asking three times, the enterprise work is ahead of its evidence.
Cheapest test: Ask sales for the three account names and the date each one asked.
What the product lead committed (illustrative)
Ship onboarding v2 now, with the pricing step left as it is
Product lead
- The tiers change only the pricing step, confirmed with design
- The Stripe choice and the enterprise push are now recorded as decisions of their own, each with an owner
- The enterprise claim is being checked with sales before single sign-on is scheduled
Frozen when committed. ClickUp keeps the tasks. This keeps why.
See the same case in the product, one step at a time.
The task list knew what the team was doing. It did not know what the team had decided, or that three of those decisions had never been made out loud.
