Version 4.3Shipped
- Export any report as a PDFYou voted for this
- Sign-in stays on after the app closes
How it works
From customer noise to a clear decision
ProductOS runs the operations of product management. The decision stays with you.
Where the week goes
Product professionals spend 27% of their time on strategy
27%
Actual (2019)
- 51%
- What individual contributors say it should be
- 60%
- What product executives say it should be for them
Hand it over
Seven of eight tasks, handled or drafted
Automatic 3
- One inbox Reading requests in five tools
- Customers, votes, score Counting who asked
- Email and portal notices Answering each customer
AI draft 3
- Problems with evidence Grouping duplicates by hand
- Statement and approach Writing specs from scratch
- One item per problem Writing the changelog
One click 1
- An epic, one issue per problem Retyping it all in Jira
Stays with you 1
- The strategy Deciding what to build
The cycle
Collect, understand, decide, ship, tell
-
Step 1 of 5
Collect
Every request in one inbox.
- LUM-I12 Export the report as PDF Portal 3 customers · 8 votes
- LUM-I13 PDF of the monthly report Support Possible duplicate of LUM-I12
- LUM-I16 Login drops on mobile Sales 2 customers · 5 votes
- LUM-I14 Weekly report by email Import from requests.csv
-
Step 2 of 5
Understand
Requests become problems, with evidence.
Reports are hard to share
LUM-I12 LUM-I13 LUM-I14 LUM-I15 +8 more
Written by AI · from 12 ideas
Customers need the report outside Lumen, mostly to show it in meetings. Most ask for a PDF; a few want it emailed every week.
“We print the report every Monday to take it to the board.”M.K., portal
12 ideas · 31 customers · 84 votes
-
Step 3 of 5
Decide
A versioned spec and a score.
- v1First draft
- v2Scope cut
- v3Saved · sent to Jira
Statement
31 customers can’t get a report out of Lumen to share it: they ask for a PDF, or for the report by email.
Acceptance criteria
- Any report exports as a PDF with its filters.
- A weekly email carries the same PDF.
Team points A.L.3 R.M.4 T.S.2 9
-
Step 4 of 5
Ship
Releases made of problems, sent to Jira.
ProductOS release
LUM-R3Version 4.3
- LUM-P7Reports are hard to share
- LUM-P8Unstable login on mobile
Dry run first
Jira Cloud
EpicLMN-214Version 4.3
- StoryLMN-215Reports are hard to share
- StoryLMN-216Unstable login on mobile
Status flows back
-
Step 5 of 5
Tell
Everyone who asked hears back.
October
49 emails sent In every voter’s portal
One cycle
From 96 requests to 49 people told
- 96 requests from 5 channels
- 3 problems with evidence
- 1 release shipped
- 49 people notified
Every morning
The day starts with what needs a decision
A queue by reason, and a weekly brief written by AI.
- Ideas to triage12
- Problems to confirm3
- Tickets due4
- Replies due2
Written by AI · weekly brief
Grew: “Reports are hard to share”, 9 new votes from 4 customers.
Shipped: version 4.3, with 2 problems.
Told: 49 people, by email and in the portal.
Hand over the operations. Keep the decisions.
Start without an AI key and see the first problems in your own data.