How Prodlog works
Start with what you have already written. Keep it going in two minutes a week. Get it back in whatever shape you need.
Start with what you already have
Your career is in two places. Everything before this job is on LinkedIn: import it once and it becomes your backfill, the roles and launches and the things you would put on a resume anyway. Everything since is in a note somewhere, a Slack thread to yourself or a phone note or a half-finished doc. Paste that in and Prodlog splits it into dated entries, pulls out what you owned and what moved, and flags the ones missing an outcome.
Try it without signing up- Mar 12, 2026Led
Shipped the onboarding redesign
OutcomeActivation up since launch - Mar 19, 2026Coached
Scope call with Maya
OutcomeAdd the result while you still remember.
Keep it going without thinking about it
Install the Slack app and Prodlog asks once a week, Friday at 4pm: what shipped this week? Reply in the thread and you are done. Type /log any time something happens instead of waiting. Email and the app itself both work too.
Skip three weeks and nothing bad happens. It just asks again on Friday.
ProdlogApp
ProdlogApp4:00 PM
What shipped this week?
1 reply
you4:12 PM
shipped the usage alerts thing tues, tickets already down a bit
Get it back in whatever shape you need
Review season, a recruiter call, a resume update, an interview on Thursday. The same entries compress differently for each: a review draft built from your own work rather than a blank page, bullets with outcomes attached, STAR stories from things that actually happened. Generated, then edited by you.
Review
In Q1 I led the onboarding redesign through two scope cuts and shipped it in March; activation is up 9% in the four weeks since. The harder call was killing the loyalty feature after discovery came back flat, which freed an eng pod for the bug backlog mid-quarter. I also coached Maya through the enterprise scope call, where we cut v1 by a third and kept the committed date.
Recruiter
- • Led an onboarding redesign that lifted activation 9% within four weeks of launch.
- • Killed a loyalty feature that discovery showed was flat, and moved a full eng pod onto the bug backlog.
Resume
- • Led onboarding redesign; activation +9% in 4 weeks.
- • Killed flat loyalty feature; recovered one eng pod.
- • Cut enterprise v1 scope by a third with no date slip.
Interview
- Situation
- Loyalty had been on the roadmap for two quarters and leadership expected it to ship.
- Task
- Decide whether to build it anyway or walk it back, with discovery coming back flat.
- Action
- Rebuilt the retention model with the data team, presented the kill case to leadership, and redirected the pod to the bug backlog the same week.
- Result
- Saved a quarter of eng time, cleared 40% of the bug backlog, and the call held up in the next planning cycle.
Publish a portfolio when you want one
Twenty-two card types: decisions you made, features you killed, metrics you moved, tradeoffs you chose, skills, case studies, writing you published. Nothing is public until you publish it.
See a real oneFree forever. Unlimited entries, no card.