While reviewing yesterday’s post, I realized my example was wrong. “The customer needs to download historical reports” isn’t the customer’s problem — it’s already a solution. I am already jumping to a solution. This is exactly what I told you not to do.
Which just goes to show — this is an easy mistake to make.
The actual problem is that the customer needs to share historical information with external people.
That could be an Excel file — or maybe a nicely formatted PDF, or even a shareable link with limited access.
The point is that letting the developer know the problem means they have the opportunity to imagine other ideas and potentially make a suggestion that is better or faster to create.
Back to our regularly scheduled programming tomorrow.