Great article, it would be interested to know if other people have a different take on this especially in a freelance context?
Thanks for reading. I'd also be interested in hearing how freelancers think about this.
Thanks for sharing Charlie. Even as a seasoned designer with a fair few years in the game there were some useful takeaways from this article. Always learning...
Well written too.
Thanks for reading!
My university professor always hated the structure of "building up to the big reveal", and perhaps that's left me biased, but I think I agree.
Instead of putting the viewer/client in a position where they're slowly building expectations as to what they think the solution should be, which you'll inevitably never align with 100%, I find it better to be upfront about the proposed solution.
Obviously first define the problem you're trying to solve, but why not go right to the solution after that. You can explain how your particular design solves that problem, and then go on to address what other options you explored that didn't work for particular reasons, or what shortcomings the particular design might have in order to focus the feedback a bit more, rather than asking for open questions before people have a concrete design to help ground some of the more abstract thinking.
I see that. Holding off on the design here obviously isn't meant to be dramatic. More so, it's meant to make sure that as many points can be agreed upon and understood before discussing the design just to keep the conversation from wandering off into 'what ifs'.
The fear I have about putting the design right up front is ignoring the work that went into the product/design decisions. I think constraining the conversation to limited feedback is likely to be more productive, assuming the designer has a good understanding of what feedback they need to move forward.
Thanks for reading.
Thanks for checking this out!