Skip to main content
VantaSoft
Back to Insights

How to Evaluate Technical Decisions When You're Not Technical

You do not need to code to evaluate technical decisions well. Three tests show whether your team has done the thinking behind a recommendation.

Working with developers 6 min read

Your development team tells you it needs to rebuild the backend in a new framework. The work will take eight weeks, and the team says it is important. You ask a couple of questions, get answers full of acronyms and approve it, because you hired the team to make these calls.

Three months and $80,000 later, you are still waiting on the rebuild, the old system is barely holding together, and you are wondering whether the work was necessary at all.

This happens often, and usually not because founders are careless. Most advice for non-technical leaders comes down to "trust your team" or "learn to code," and neither helps much. You do not need deep technical knowledge to evaluate technical decisions well. You need a few tests that show the quality of the thinking behind a recommendation, whatever the technology involved, and a sense of the three most expensive mistakes non-technical founders make.

We use these three with every client.

1. The options test

The biggest warning sign in a technical recommendation is a single option: "We need to switch to React," "We should move to AWS" or "We have to rewrite this module."

Good technical thinking always involves tradeoffs. If someone recommends an approach without explaining what they considered and rejected, either they have not done the analysis or they are steering you toward a preference without showing their reasoning.

When a developer or CTO brings you a recommendation, ask three questions:

  • What other approaches did you consider?
  • What are the downsides of the approach you're recommending?
  • Under what circumstances would you recommend something different?

You do not need to understand the technical details of each option, because what you are judging is how rigorous the process was. A strong engineer will have a clear, concise answer to all three, along the lines of: "We looked at keeping the current system and patching it, but the auth module can't support multi-tenant access without a rewrite either way. We also considered migrating just the API layer, but that creates two systems to maintain for six months. The full rebuild costs more upfront but gets us to a single system faster."

You can evaluate a decision explained that way. Compare it with "We just really need to move to microservices," which is a preference presented as a conclusion.

2. The explain-the-risk test

Every technical decision carries risk, and your team should be able to explain it without you having to drag it out of them. If they cannot say clearly what could go wrong, they probably have not thought about it carefully enough.

We worked with a company that approved a migration from Heroku to a self-managed Kubernetes setup. The team estimated four weeks of engineering time but did not raise the ongoing operational complexity. Six months later, the company was still paying a DevOps contractor just to keep the infrastructure stable.

The founder was not technical, but asking "what's the ongoing cost of maintaining this after we ship it?" would have given her a very different picture. If the team had no answer, that would have told her something too.

For any significant technical decision, ask your team three things: the worst realistic outcome if it goes wrong, what it costs beyond the initial build in time, money or complexity, and what you give up by choosing this path.

If your team treats these questions as annoying or unnecessary, take note. Engineers who have lived through bad decisions welcome them, because they know the projects that fail badly are usually the ones where nobody asked what could go wrong.

3. The translate-to-business test

This test tends to catch the most problems. Ask your team to explain the decision in terms of what it means for the business rather than the technology.

"We need to refactor the data layer" tells you nothing. Compare it with this: "Right now, generating a single client report takes 45 seconds because of how our data is structured. After this refactor, it'll take under two seconds. That matters because three enterprise prospects told us in demos that the report speed was a dealbreaker." That is a decision you can evaluate, prioritize and fund with confidence.

If your team cannot connect a technical decision to a business outcome, either the work is not important or the team does not understand why it is. You need to know which.

Not every piece of engineering work needs a revenue justification. Some work is about system health, security or reducing the chance of a future outage, and that work should still be explainable. "If we don't fix this, we have a 30% chance of a full outage during peak traffic in Q4" is a business case. "We should fix this because it's messy" is not.

The strongest technical leaders we have worked with make this translation without being asked. They think about business risk and customer impact as well as code quality. That habit is much of what separates a CTO from a tech lead or a senior developer. If you find someone who works that way, keep them.

What this looks like in practice

These tests do not need to be formal interrogations. Make them part of how you handle technical decisions. When someone brings a recommendation, ask what else they considered. When they describe a plan, ask what could go wrong. When they explain the work, ask them to connect it to something the business cares about.

Over time, you will get a sense of which decisions have been thought through. You will notice when estimates are suspiciously precise (real estimates have ranges) and when timelines keep growing without clear explanations, and you will get better at telling "we need to do this" apart from "we want to do this."

None of this requires you to learn a programming language or sit in on code reviews. It relies on skills you already use to run the business: asking pointed questions, reading people and making judgment calls with incomplete information. Technical decisions are business decisions too, and those skills cover most of what you need to evaluate them.

Some decisions need more than these tests, like a choice that would be hard to undo or more technical calls than you have time to check. For those, it helps to have senior judgment on your side. Our guide covers when to hire a fractional CTO and when to skip it.

Five quick questions about where your team's time goes. You'll get the one agent we'd start with, and what it would take off your plate.

Take the quiz

Tell us whatyou’re building.

Senior engineers and fractional CTO leadership, onshore in Irvine. It starts with a conversation.