Why We Start Every Project With the Problem, Not the Tech Stack
By FishIT PK Team · October 10, 2026
Most software projects go wrong before a single line of code is written — not because of a bad technology choice, but because of a rushed understanding of the problem.
The pattern we see most often
A business knows something isn't working. Maybe it's a manual process eating hours every week, or a customer experience that keeps causing complaints. The instinct is to jump straight to "we need an app for that" — before anyone has clearly written down what "that" actually is.
Why we slow down first
Before we open an editor, we ask questions like:
- Who exactly experiences this problem, and how often?
- What are they doing today as a workaround?
- What would actually change if this problem disappeared?
These answers shape everything — the features we prioritize, the platform we build for, and sometimes even whether custom software is the right answer at all.
The result
Projects scoped this way tend to ship faster, cost less to maintain, and actually get used — because they were built around a real, specific problem instead of a guess.
If you're facing a problem you think technology could solve, let's talk about it before we talk about the tech stack.