the diagnosis before prescription framing is really good — jumping straight to wireframes without validating the problem is such an easy trap to fall into, especially when you're excited about a project. the bit about bridging 'pretty screens' to 'business ROI' in the proposal language is something i need to be better at. this is the kind of post that actually makes me want to rework my proposal template
I've found that explicitly listing what is not included in the scope has saved me from more headaches than anything else. Does anyone else include a specific 'Out of Scope' section in their design proposals, or do you handle scope creep differently?
Tiffany Spark
Web designer in London. Clean code, good design, strong coffee.
love how you broke this down. the section on setting scope expectations before you even touch wireframes is spot on, that is where so many projects go sideways.