· Comma Labs team
Day one: whose problem is being solved?
Most projects that arrive from a search for a software company in Ankara have already described their solution too early. But the aim of the first session is not to approve screens — it is to understand why the user is leaving the current method behind.
The user, the decision-maker, and the person using the system every day may not be the same. Without seeing the expectations of these three roles separately, no solid product decision comes out.
The first week: surfacing the invisible work
Moving a file in a process, confirming something over the phone, updating an Excel sheet, or checking a permission can be skipped in the first telling. Yet the real cost of a system is often hidden in these small steps.
That is why we do not limit the flow to the happy path. What happens if it gets cancelled, who fills in data that arrives incomplete, which record changes if the user wants to go back? These questions build the backbone of the product.
The first month: choosing what to measure
Whether the first release is good should be judged not by feel but by signals chosen in advance. The number of completed requests, the rate of faulty records, or the time it takes to finish a task can be chosen according to the product's purpose.
When these metrics are clear, new feature requests can be prioritized more soundly too. Not every good idea has to be built right away.