The Decision Audit: 25 Questions to Ask Before You Screw Up

Every bad startup decision has a bias behind it. You build the wrong feature because you only listened to users who agreed with you. You hold onto a failing product because you already spent six months on it. You hire too fast because everyone on Twitter says you should.

The problem is you don't see the bias while you're in it. You just feel like you're making a reasonable choice.

This is a list of questions to ask yourself before big decisions. Not theory. Just questions that force you to check your thinking before you commit time, money, or months of your life to something.

Save it. Come back to it. Use it.

Before You Build a Feature

1. Did at least 10 users ask for this unprompted? If not, you might be building what you want, not what they need. Confirmation bias loves to find three enthusiastic users and ignore the hundred who stayed silent.

2. If I launched this tomorrow and it flopped, what would I blame? Write it down now. If you already have excuses ready, you already know it's weak. This forces you to confront what you're ignoring.

3. What's the smallest version I can ship to test if this matters? Planning fallacy makes you think you need the full version. You don't. If the idea is good, a ugly prototype will show signal. If it needs to be polished to work, it probably won't work.

4. Am I building this because users want it or because a competitor has it? Bandwagon effect is real. Your competitor might be wrong too. They probably are.

5. If this feature didn't exist in 6 months, would anyone notice? Be honest. Most features don't move the needle. They just make you feel productive.

Before You Hire

6. Would I still hire this person if I had to decide in 24 hours? If you need weeks to convince yourself, that's a no. Your gut already knows.

7. Am I hiring because I need help or because I think I should have a team? Vanity hiring kills indie companies. Every person you add increases complexity. Make sure you're solving a real bottleneck.

8. What happens if this hire doesn't work out in 3 months? If the answer is "it would be very bad," slow down. You're not ready to take that risk. Pre-mortem thinking saves you from optimism bias.

9. Can I describe exactly what this person will do in their first week? If you can't, you don't actually know what you need. You're hiring a role, not a solution.

10. Am I hiring to avoid doing something I don't like? Sometimes that's valid. Often it's avoidance. The thing you're avoiding might be exactly what you need to learn.

Before You Set or Change Pricing

11. What's my price based on? If the answer is "what competitors charge," you're anchoring to someone else's guess. Price based on value delivered, not market defaults.

12. Have I actually asked users what they'd pay? Not "would you pay for this" but "what would you pay." The first question is useless. Everyone says yes. The second reveals truth.

13. Am I afraid to charge more? Underpricing is usually fear, not strategy. Fear that people won't pay. Fear that you're not good enough. The market will tell you if you're wrong. Charge more and find out.

14. If I raised prices 20%, what would actually happen? Most founders imagine mass exodus. Reality is usually a few complaints and higher revenue. Loss aversion makes you protect the wrong thing.

Before You Pivot

15. Am I pivoting because of data or because I'm bored? Boredom is not signal. Shiny object syndrome kills more startups than bad ideas. If you're pivoting without clear evidence, you're just running away.

16. Have I given this enough time to work? What's enough? Depends on the product. But most founders quit too early because growth is slower than they imagined. Planning fallacy again.

17. What would I need to see to keep going? Define this before you decide to pivot. If you can't name a clear threshold, you're making an emotional decision.

18. Am I blaming the idea when the problem might be execution? Ideas rarely fail. Execution fails. Distribution fails. Positioning fails. Make sure you're diagnosing correctly before you throw everything out.

Before You Kill Something

19. Am I killing this because it failed or because it's not growing fast enough? Expectations matter. If you expected 10x and got 2x, that's not failure. That's your expectations being wrong. Check your baseline.

20. How much have I already spent on this? Now forget that number. Sunk cost is gone. The only question is whether future investment will return value. Past investment is irrelevant.

21. Did I give this a real chance or did I sabotage it? Sometimes we kill things because we never fully committed. Half-effort produces half-results. Be honest about whether you actually tried.

22. What will I learn if I keep going one more month? If the answer is "nothing new," kill it. If there's still signal to gather, maybe it's worth the extra time.

Before You Spend Money

23. Would I spend this money if it was coming from my savings account? Revenue feels like free money. It's not. Treat every dollar like it came from your pocket. Because it did.

24. What's the expected return and how will I measure it? If you can't answer this, you're not investing. You're gambling. Define success before you spend.

25. Am I spending because it will help or because I feel like I should be spending? There's pressure to invest in tools, ads, contractors, software. Most of it is noise. The best indie companies stay lean longer than feels comfortable.

How to Use This

Don't try to memorize all 25. Instead:

Before any big decision, find the category and read those 5 questions. Take two minutes. Write down your answers.

If you can't answer honestly, you're not ready to decide.

If your answers feel like excuses, you already know what to do.

The goal isn't to avoid every mistake. That's impossible. The goal is to avoid the obvious ones. The ones where you look back six months later and think "I knew that was wrong and I did it anyway."

That's what the audit prevents. Not bad luck. Just bad thinking.

Use it.