[ducharmdev]

On a higher level, software development is a process of converting unknowns to knowns. We can't estimate or act upon what we don't know; as we uncover details, we can more accurately gauge level of effort and what the best solution is for the problem at hand.

If they're nontechnical, they may not care about how it's done at all, but they will care about timelines. They may have agreements with others that depend on the product, or may have stakeholders they need to communicate with.

As developers we usually focus on our direct communication with the business owner, but I think it's helpful to imagine the second order communications that will result from how we communicate progress on our technical solutions.

For example, if we convey confidence to get a certain piece done by x date, the founder may in turn pass on that confidence to shareholders. But if we later backtrack after realizing that it will be a bigger lift than expected, the founder may have to walk back those expectations.