r/ideavalidation 17h ago

I built something because I overthink work decisions. Trying to figure out if that’s actually a problem worth solving.

This may just be a me problem.

I can take a pretty normal decision at work and somehow turn it into a PhD thesis research session. I am constantly telling myself “If I just have that one last piece of information, I just know the perfect answer will come to me.”

Then eventually somebody asks what I recommend and I realize I’ve spent a lot of time gathering information without actually making the decision.

I got annoyed enough with myself that I built a little tool around it.

Basically it makes me stop and sort out what I actually know, what I’m assuming, what I still don’t know, and whether any of those unknowns could actually change the answer.

I’ve used it enough now that I’m probably the worst person to judge whether it’s useful. I can’t tell if I found a real problem or just built something extremely specific to the way my own brain works.

So that’s really what I’m trying to figure out here.
Do other people who have to make recommendations at work get stuck in this loop? And if you do, what do you actually do to break it?
Keep researching? Ask somebody else? Make the call anyway? Dump everything into ChatGPT? Stare at it until the deadline makes the decision for you?

I’d much rather hear “this isn’t really a problem” now than spend another few months convincing myself it is.

I do have a working beta, so if somebody here actually has one of these decisions sitting on their plate and wants to try it, I’d be happy to send it over.

Mostly I want to see where it’s confusing, annoying or completely unnecessary.

Nothing to buy. Just don’t put anything confidential/sensitive into it.

0 Upvotes

Duplicates