Understanding what the client needs

Clients describe solutions. Your job is to find the real problem.

A client often comes with a solution in mind: "We need an app", "Add a WhatsApp button", "Make it like that website". Behind every request is a problem they want gone. If you build the solution without finding the problem, you may build the wrong thing perfectly.

Questions that find the real need

  • What happens today, step by step, without the software?
  • What goes wrong or takes too long?
  • Who will use it: owner, staff, customers? On phone or computer?
  • How will you know it worked? (fewer missed calls, faster billing...)
  • What must it connect to: payment, SMS, Tally, an existing website?
  • What is the deadline, and why that date?

After the call, write the requirements back to the client in simple points and ask them to confirm. A requirement is clear when a tester could check it: "Patient gets an SMS reminder 2 hours before the appointment" is testable; "good reminders" is not.

๐ŸŽญ What would you do?

A clinic owner says: "Patients keep missing appointments. Build us a mobile app."

๐Ÿ”ฌ Try it: the clinic that asked for the wrong thing โ†’

โ† A project from enquiry to supportEstimates, scope and change requests โ†’