Founders: what decision do you keep reopening?
A pattern I keep seeing: a founder makes a decision, feels relief for a day, then quietly reopens it.
Usually that is not an information problem. One of four things was never made explicit:
1. Objective — What must become observably different?
2. Human pressure — What fear, loyalty, fatigue, or identity cost could distort the choice?
3. Reversible move — What can be tested without betting the company or the relationship?
4. Evidence threshold — What result means continue, change course, or stop?
If one line is blank, the decision often comes back disguised as “more research.”
We are building this principle into WizeMe so memory does more than retrieve what was said. It should preserve why a decision was made, what evidence supported it, and which unresolved pressure might cause it to drift.
I would value input from other founders: which decision keeps reopening for you—pricing, hiring, positioning, fundraising, a cofounder issue, or a difficult client conversation?
If you share one real situation without sensitive details, I’ll apply the four-line check here so the discussion produces a usable next move.
Replies
pricing is the one that keeps coming back for me. we shipped a plan structure, felt good about it for about a week, then found ourselves relitigating it after a couple of sales calls where it clearly wasn't the reason deals stalled. running your checklist on it: objective was never pinned down past "be competitive," which isn't observable. human pressure was real - nobody wanted to be the one who priced us out of an early deal. reversible move existed (we could've tested a narrower change) but we skipped it and did the full restructure instead. evidence threshold didn't exist at all, so every ambiguous signal after launch became a reason to reopen it.
the framework is useful mostly because it makes you notice which line you skipped in the moment, not after. we skipped the evidence threshold specifically because writing down "here's the number that would make us NOT change this again" felt like admitting the first decision might be wrong before we'd even shipped it.
for me it's how much roadmap time goes to one large customer's specific ask versus the general product. we say yes, build it, then a few weeks later someone asks why we're not further along on the thing everyone else needs. running it through your list, objective was never explicit beyond keep the big account happy, which isn't measurable against anything else competing for the same engineering time. evidence threshold is the real gap, nobody ever defined what would prove the one-off request was worth the tradeoff versus just being the loudest voice in the room that week.