Most software starts with an idea. The useful kind starts with a moment of frustration: something that should be easy and is not, for someone who does not have the time to work around it.
The laptop on the table
Buying a second-hand laptop means trusting a stranger’s description. “Battery like new.” “Never had a problem.” A buyer has no quick way to check any of it, and checking properly means juggling half a dozen tools on a machine that is not yours yet.
That was the problem behind PCVet. Not “build a hardware inspector”, but “help someone decide, in the few minutes they have, whether to hand over their money”.
A good problem tells you what to leave out.
What the problem decides for you
Start from the moment of use and a lot of decisions make themselves:
- It runs from a USB stick, because it runs on someone else’s machine.
- It only reads, because you do not own that machine yet.
- It works offline, because the seller’s Wi-Fi is not yours either.
- The answer is one word — Good, Fair or Avoid — with every lost point explained, because nobody reads a long report standing at a stranger’s desk.
The same question, every time
Every Tevry product goes through the same question before a line of code: whose moment are we fixing? For DiskWarden it is a disk that is full for no visible reason. For Uttor it is a candidate with a few months to prepare for an exam that shapes their career.
Starting with the problem does not make the work smaller. It makes it clearer — and clarity is most of what people need from software.
- PCVet
- Product thinking
Writing from inside Tevry about the things we build.