3 ms·

I wouldn't write off project managers' appreciation for interactive prototypes... Although I would agree that they often (but, ime, not always) appreciate an e

I wouldn't write off project managers' appreciation for interactive prototypes... Although I would agree that they often (but, ime, not always) appreciate an export (eg pdf) that can be signed off and stored. We've had some project managers who were almost the most enthusiastic team member about interactive prototypes because they were the most effective (and understandable) thing to demonstrate/give to customers. (To your general point though, I entirely agree, I wouldn't use QT Designer for this role -- and I'm also quite a fan of pencil, because it feels intentionally plain/bland.)

kagamine 10y ago
I think we agree, but prototypes and demos are not the same thing. A wireframe can be a prototype, with buttons linking from one page to another to demonstrate workflow, a prototype would be built to a near-finished specification and close to an alpha/beta. I feel like I'm being a pedantic a-hole in this thread, but the terminology of UX/IxD and the process seems like one of the more misunderstood aspects of building software and as a lot of developers (in my experience) want to either dismiss the process as unnecessary (they don't need to be told what to do) or they want to take on the process themselves (experienced coder, of course I can analyse and plan a user interface). I'll stop now before I start ranting.