Timeline for Best way to deliver "mockup tool kit" to engineering team?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2012 at 0:14 | comment | added | Rahul | Look, I mean no offence with my advice. I'm just telling you what I think you should do (since you asked). It's cool if you don't want to do anything with it. :-) But just because I think you should do things differently doesn't mean I'm insulting your work ethic or intelligence - I'm just disagreeing with you. If you want to let it drop here that's fine; if you want to continue talking, feel free to drop by the chat. | |
| Mar 7, 2012 at 23:50 | comment | added | dennislees | It seems as though I'm not accepting your sage advice and you are insulting my work ethic, or intelligence, to compensate. I do want to change this system, but even if I didn't, it would't make your suggestions any more realistic. Those two concepts are unrelated. If you were my colleague we wouldn't be having this conversation, because you'd have some understanding of the existing culture and its limitations. So please, accept my thanks for your input so far, hear me when I say that it's sound but not appropriate, and let's let this go. | |
| Mar 7, 2012 at 21:09 | comment | added | Rahul | Have you considered that I am in fact answering your question, just not the way you wanted me to? I'm sorry that it's not what you want to hear, but if you were my colleague this is what I would tell you. I wouldn't just tell you what you want to hear because that's more convenient. I don't intend to point out flaws, I'm just pointing out that the solution to your problem isn't a "mockup toolkit", it's better communication with your team. It's only unrealistic if you decide that you don't want to put in the effort of solving the problem. | |
| Mar 7, 2012 at 18:44 | comment | added | dennislees | The question was "Best way to deliver...?" Not "What are the flaws in my philosophy?". You're answer was great, just not what I was asking for; maybe a little bit idealistic, and certainly not realistic given the real-world limitations I face. I have a plan and I'm looking for way to deliver it. Hence wording of the question. Thanks. | |
| Mar 7, 2012 at 15:58 | comment | added | Rahul | That's why I recommended the engineers write the HTML, not the product owners. Further your responsibility as the UX person is to help them not overcomplicate things by communicating better with them, not by giving them Twitter Bootstrap. If you've already decided what the solution is (throw Bootstrap bitmaps at them), then why did you come here and ask a question about it? | |
| Mar 7, 2012 at 15:45 | comment | added | dennislees | Thanks for the input, but I'm not exactly sure why it's being upvoted. "Just make them write the html/css themselves" is not a reasonable suggestion in this case; some product owners have are not code-savvy in the slightest. Also, the whole point of using the Bootstrap elements is to be restrictive. These people are not UI designers, and they're also prone to overcomplicate processes. So by limiting the options, I keep things simple and looking good. I understand that the process needs to change, but that's a multi-year project. This is a damage-limitation step I can put in place within weeks. | |
| Mar 7, 2012 at 10:27 | history | answered | Rahul | CC BY-SA 3.0 |