Reckon - The decision journal that helps you calibrate

Most decisions feel resolved the moment you make them. Reckon keeps what hindsight erases: the prediction, the confidence, the reasoning. Check-ins capture what changes before the outcome: new info tagged positive or negative, confidence updated. At resolution you log what happened; weeks later it asks if you'd still make the call. A year in, you see where confidence overshoots, where it undershoots, where judgment is sharpest. iPhone and iPad. iCloud sync, no account. One-time purchase.

Add a comment

Replies

Best
Hey Product Hunt, Roland here, maker of Reckon. I built this because I noticed the same thing keeps happening to me: I make a call, the outcome arrives a few weeks later, and by the time I remember what I had predicted, the story has already been re-written by hindsight. The version of me that hesitated, that wasn't sure, is gone, and with it anything I could have learned. A note app captures what happened. A journal captures how I felt. Neither captures what I predicted, or how confident I was before I knew. So I built the thing that does. Reckon is a decision journal where the moment of choice is the beginning, not the end. You log a prediction with a confidence percentage and a review date. Between then and resolution, check-ins capture what changed: new information tagged positive or negative, updated confidence. At resolution, you log the outcome and how satisfied you are. 30 to 60 days later, the app asks again: would you make this call again? Because satisfaction doesn't always align with "would I do it again". After enough decisions, calibration becomes something you can see: where your confidence overshoots outcomes, where it undershoots, which domains your judgment is sharp in. It's for anyone who has ever felt their judgment is good but couldn't prove it, or the contrary, doesn't have confidence in theirs and needs a history. Founders, parents, planners, investors, people who care about thinking clearly. Not pitched at the forecasting community, but legible to them. I would love your honest feedback! I'm especially curious if "calibration" makes sense for non-forecasters, or does the framing need to improve?
Sounds really useful for PMs or directors, with the accountability it might help prevent hindsight bias and dumb principal problems. Really excited to test it next time I’m leading a team.

 let me know how it goes!

Hey

Outcomes can be right for the wrong reasons, so tracking the reasoning & confidence feels way more useful than a normal decision journal.

  exactly what I thought of when I decided to build it.

maybe an odd request, but I'd like to see some sample decisions to help jumpstart my activity on the app....the unknown size/shape of an opinion can feel daunting.

 I think the App Store screenshots contain a detailed decision that I hoped would help with that and serve as a good example, but I’ll see how I can integrate it and a few more as a “here’s an example” on first install.

if i can later provide judgment as context for agents that will dope, the judgment layer should be coined as the new context layer :)

 I'm not sure I understand what you mean.

i make marketing calls on gut feeling more than i'd like to admit 😅 the hard part isn't logging decisions tho, it's coming back to score them later. how do you get people to actually return? that's where i'd fall off

 Reckon does help on just this, with two notifications: one before the review date (in a future version one on the review date), and another one after you resolve it, the "would you do this again" question. All date intervals are customizable.

  The 'would you do this again' question after resolving is such a nice touch – that's exactly the part hindsight usually eats. What review interval do people actually stick with? I'd probably set 2 weeks and then snooze it forever haha

 I don't really know, I don't have analytics in it, but it also depends on the timeframe of the decision. Something that requires a followup in 3 months? I'd probably set a checkin reminder two weeks prior, but set 1 week for something that requires a followup in 1 month.

But next version will have a reminder for: checkin, review, overdue review, so at least you get three shots at it 😄

  Ha, three shots is much better odds than one. Can I turn them off individually though, or is it all or nothing? I'd probably kill the middle one and keep 'overdue' as my guilt trip

to answer your question directly - calibration absolutely makes sense outside forecasting, I just don't think most people would use that word for it. I screen early-stage startups fast, sometimes dozens a day, and the thing I never have is a record of how confident I actually was on a pass or a yes before I knew how it turned out. hindsight rewrites that instantly. the 30-60 day "would you still make this call" check-in is the part that sold me, that's the exact gap between a note app and a real record of judgment. one question - when the new info you tag as "positive" or "negative" mid-decision turns out to be irrelevant to the actual outcome, does that get factored into the calibration score at all, or does it just sit there as a log entry with no scoring consequence

 Thanks for the detailed reply! I'm glad it clicks with you and regarding "calibration" as a word... I always felt it's a bit clunky, even though it made sense to me, so it just stuck. Curious if you have any other alternatives?

Regarding your question, it does not get factored in. Calibration is solely based on your confidence vs outcome (averaged across your decisions). What you log along the way is more like a history for yourself (and positive/negative also helps to easily scan the history).

 makes sense, that's a cleaner split than I expected - so the log entries are really just for you to spot patterns later, not part of the score itself. on alternatives to "calibration" - I don't have a better single word honestly, most of the ones I'd reach for (accuracy, judgment) undersell the confidence part. maybe something like "track record" framing could work as a subtitle even if the feature stays named calibration internally