<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Think Vitamin - Latest Comments in 20 Steps to Better Wireframing</title><link>http://thinkvitamin.disqus.com/</link><description>A resource for web designers, developers and entrepreneurs</description><atom:link href="https://thinkvitamin.disqus.com/20_steps_to_better_wireframing/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 13 Apr 2009 18:34:24 -0000</lastBuildDate><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-8134323</link><description>&lt;p&gt;Perhaps a print page would be nice. Printed out this article and got about 20 pages of comments.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthew</dc:creator><pubDate>Mon, 13 Apr 2009 18:34:24 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-7997748</link><description>&lt;p&gt;Awesome article. I've started doing wireframes recently at work and this article was certainly a good reading&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">theme park consulting</dc:creator><pubDate>Thu, 09 Apr 2009 01:16:24 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-7897810</link><description>&lt;p&gt;I completely agree about including something about planned/thought of interactivity. In my case (I design a lot of data driven flash-based apps), without describing the interactivity to some extent would sell the idea short. If I'm wireframing or sketching a whole page design and there's some interactivity/widgets that's required to view layers of info, that's included as well. I'll also do smaller sketches of the widgets with a little more detail.&lt;br&gt;&lt;a href="http://www.Start-an-Internet-business.net" rel="nofollow noopener" target="_blank" title="www.Start-an-Internet-business.net"&gt;www.Start-an-Internet-busin...&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jane4455</dc:creator><pubDate>Mon, 06 Apr 2009 07:46:25 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-7786682</link><description>&lt;p&gt;Thanks for the article. I for one find myself rushing the code a bit too much and making mistakes in the process. My last site looks better by slowing things down and doing them right.&lt;br&gt;JasonSt &lt;a href="”" rel="nofollow noopener" target="_blank" title="”"&gt;Men's health issues&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JasonSt</dc:creator><pubDate>Fri, 03 Apr 2009 08:46:22 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-7684266</link><description>&lt;p&gt;I agree with all the points you made except for one: "I think that the wireframe should be a document though rather than something interactive". You are designing something interactive so the wireframe needs to be interactive. In my experience, a HTML/CSS wireframe gives the UX designers, programmers and writers a much better understanding of how the page, section, form, etc. will work. This is especially true in dealing with dynamic navigation or content. Instead of explaining that a user has to select "Y" to get "X" in a written or illustrative form, you can just show it. Doing the upfront HTML work has saved me a lot of time explaining in the long run. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chance Bliss</dc:creator><pubDate>Tue, 31 Mar 2009 15:41:06 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-7462904</link><description>&lt;p&gt;Thanks for the info. This is important for time managers like me.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">com</dc:creator><pubDate>Tue, 24 Mar 2009 03:45:12 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-7216522</link><description>&lt;p&gt;I'm a designer and I absolutely agree that design should not be part of the wireframing process, wireframing helps me show the scope of the project to a customer (as well as giving me a path to follow when I'm designing). Once this is approved any changes become billable, you don't want to create a presentation and take away where the focus should be, at least initially, on usability and the scope of the project.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">LMartian</dc:creator><pubDate>Sat, 14 Mar 2009 14:10:06 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6969185</link><description>&lt;p&gt;And here I am thinking I was in the minority that designs websites on paper before going directly to photoshop. Im going to start wire framing with marker like you did. Its a good idea and looks a lot better then pen chicken scratch lol&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel</dc:creator><pubDate>Fri, 06 Mar 2009 20:10:01 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6949002</link><description>&lt;p&gt;Interesting articles and shows the complexities that need to be covered prior to the coding. impressive read and the points make it easier to understand.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave scott</dc:creator><pubDate>Fri, 06 Mar 2009 13:21:01 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6938571</link><description>&lt;p&gt;If you wish to be associated with a professional sporting tournament, that is, you wish to be a part of live action; you need to purchase valid Tickets to a match. for more information please visit at &lt;a href="http://lextratickets.com/" rel="nofollow noopener" target="_blank" title="http://lextratickets.com/"&gt; Concert Tickets &lt;/a&gt;. you will get your ticket over here without any obstacle.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Linda012</dc:creator><pubDate>Fri, 06 Mar 2009 02:04:46 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6835481</link><description>&lt;p&gt;I love &lt;a href="http://iplotz.com" rel="nofollow noopener" target="_blank" title="iplotz.com"&gt;iplotz.com&lt;/a&gt; better than balsimiq . +1 to iplotz. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ahmad Amran</dc:creator><pubDate>Tue, 03 Mar 2009 05:50:24 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6834749</link><description>&lt;p&gt;it`s true. but in this aplication there are functions of which it is not in visio&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oleg</dc:creator><pubDate>Tue, 03 Mar 2009 04:18:34 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6834714</link><description>&lt;p&gt;understand a structure of project.  make a tree or map of prototype&lt;/p&gt;&lt;p&gt;great article. we are following all points&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oleg</dc:creator><pubDate>Tue, 03 Mar 2009 04:14:56 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6811273</link><description>&lt;p&gt;For people who are total beginners and have never seen wireframes and how they look like, is there any resources or examples? Would really appreciate it if you gurus could point out towards the right direction.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">weboncloud</dc:creator><pubDate>Mon, 02 Mar 2009 21:02:23 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6783877</link><description>&lt;p&gt;I use this to take notes before starting any project&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">vst plugins</dc:creator><pubDate>Mon, 02 Mar 2009 10:24:20 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6783700</link><description>&lt;p&gt;I've always used wireframe to make notes when starting projects&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">vst plugins</dc:creator><pubDate>Mon, 02 Mar 2009 10:15:41 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6737293</link><description>&lt;p&gt;Tim Wright wrote: "I've heard a lot of argument for killing the old fashion wireframe in favor of prototypes to show interaction. Any thoughts on that?"&lt;/p&gt;&lt;p&gt;I guess it depends on what "old fashion wireframe" means. But essentially I would agree. The wireframes we produce are quite sophisticated, sometimes we include things like functional drop down lists and dummy images, but we find it really worthwhile when working on the functional design of a site. I'm sure most clients would appreciate more detailed wireframes.&lt;/p&gt;&lt;p&gt;Kev said: " I started doing wireframes in Illustrator using grey-scale so as not to distract the client with colours etc.  I've moved to using paper wireframes for speed, this also lets others get involved in meetings."&lt;/p&gt;&lt;p&gt;There are many tools for wireframing that are easier than Illustrator! One of the guys who works for me was cursing his Uni lecturer once he discovered how easy it was to create wireframes using MS Publisher (because his Uni lecturer had steered everyone down the Illustrator path). There are two of us working on the functional design for a complex site and Publisher enables us to share documents for modification or re-use of elements. It also allows pages to be saved in MHTML or as a jpeg. Much more efficient than pen and paper. IMHO :)&lt;/p&gt;&lt;p&gt;Of course at the end of the day there's no right or wrong, there's just different ways of approaching the functional design phase.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kevin Howard</dc:creator><pubDate>Sat, 28 Feb 2009 21:40:00 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6725579</link><description>&lt;p&gt;Very informative! I like it.. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">raymondphilippe</dc:creator><pubDate>Sat, 28 Feb 2009 12:59:54 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6720147</link><description>&lt;p&gt;One small (yet critical)  addition to your points, would be to *keep testing* the integrity and flow as a part of the development cycle, and not just a one-time blueprint. &lt;br&gt;Force yourself to go over everything on a weekly(?) basis, as a sanity check.&lt;br&gt;It's very easy to under-estimate the influence small changes in the development can have over the entire user experience.&lt;/p&gt;&lt;p&gt;And sure.. Balsamiq is a great for quick mockups. You can read my impressions of using it here: &lt;a href="http://www.aboutux.com/?p=22" rel="nofollow noopener" target="_blank" title="http://www.aboutux.com/?p=22"&gt;http://www.aboutux.com/?p=22&lt;/a&gt;&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yanay Zohar</dc:creator><pubDate>Sat, 28 Feb 2009 02:03:18 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6719776</link><description>&lt;p&gt;My Site&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jennypauls</dc:creator><pubDate>Sat, 28 Feb 2009 01:13:59 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6677455</link><description>&lt;p&gt;Thanks for the article on wireframing - very informative.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joel McHale</dc:creator><pubDate>Thu, 26 Feb 2009 22:34:16 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6672578</link><description>&lt;p&gt;As some other said, we also use wireframes in the beginning phase of a project.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ally</dc:creator><pubDate>Thu, 26 Feb 2009 18:49:11 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6623348</link><description>&lt;p&gt;Excellent article. Love the "half an hour conversation about the merits of blue" bit....any design elements in wireframes always take the discussion off course. I often use only black and white to create wireframes for my clients specially so they will focus on the functionality.&lt;/p&gt;&lt;p&gt;As a designer/developer I've always found wireframes to be an important step. I do differ with you on the inclusion of ajax and other layout elements. I consider those to be part of the functionality and include them within the wireframes.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">abewallin</dc:creator><pubDate>Wed, 25 Feb 2009 16:44:50 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6616078</link><description>&lt;p&gt;A plan is essential to reach the target you have set because it breaks down several checkpoints to achieve and complete, so in final you reach your goal with better motivation and speed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pauline</dc:creator><pubDate>Wed, 25 Feb 2009 12:42:54 -0000</pubDate></item><item><title>Re: 20 Steps to Better Wireframing</title><link>http://thinkvitamin.com/features/20-steps-to-better-wireframing/#comment-6599264</link><description>&lt;p&gt;I have collected a list of wireframing and prototyping tools you may find useful. See &lt;a href="http://weblogs.asp.net/fmarguerie/archive/2009/02/15/gui-design-and-prototyping-tools.aspx" rel="nofollow noopener" target="_blank" title="http://weblogs.asp.net/fmarguerie/archive/2009/02/15/gui-design-and-prototyping-tools.aspx"&gt;http://weblogs.asp.net/fmar...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fabrice</dc:creator><pubDate>Wed, 25 Feb 2009 08:51:07 -0000</pubDate></item></channel></rss>