<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Notes &#187; Design</title>
	<atom:link href="http://valka.info/notes/category/design/feed/" rel="self" type="application/rss+xml" />
	<link>http://valka.info/notes</link>
	<description>Notebook of a front-end Web design &#38; development dude</description>
	<lastBuildDate>Thu, 12 Aug 2010 16:00:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Notes on Pain Free Design Sign Off</title>
		<link>http://valka.info/notes/2010/05/notes-on-pain-free-design-sign-off/</link>
		<comments>http://valka.info/notes/2010/05/notes-on-pain-free-design-sign-off/#comments</comments>
		<pubDate>Tue, 25 May 2010 07:51:23 +0000</pubDate>
		<dc:creator>Ondřej Válka</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://valka.info/notes/?p=228</guid>
		<description><![CDATA[Great talk named Pain Free Design Sign Off on handling Web site design process and clients and by Paul Boag at SXSW. Full length video is available via Boagworld.

Client knows his users and business. Ask him about it.
Client should like the web site.
Confrontation to collaboration.
Client searches for problems, designer finds the solutions.
Do have a strong [...]]]></description>
			<content:encoded><![CDATA[<p>Great talk named <a href="http://my.sxsw.com/events/event/623">Pain Free Design Sign Off</a> on handling Web site design process and clients and by <em>Paul Boag</em> at SXSW. Full length <a href="http://boagworld.com/random/pain-free">video is available</a> via Boagworld.</p>
<ul>
<li>Client knows his users and business. Ask him about it.</li>
<li>Client <em>should</em> like the web site.</li>
<li>Confrontation to collaboration.</li>
<li>Client searches for problems, designer finds the solutions.</li>
<li>Do have a strong methodology.</li>
<li>Include client early and often.</li>
<li>Educate the client why do you work in such a way.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://valka.info/notes/2010/05/notes-on-pain-free-design-sign-off/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Everyday prototyping</title>
		<link>http://valka.info/notes/2010/01/everyday-prototyping/</link>
		<comments>http://valka.info/notes/2010/01/everyday-prototyping/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 00:38:18 +0000</pubDate>
		<dc:creator>Ondřej Válka</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://valka.info/notes/?p=93</guid>
		<description><![CDATA[Prototyping is a must. No matter what business you deal with, prototyping should be a welcome guest that helps you figure out the right decisions in quick-and-dirty way. Today I&#8217;d like to reveal my prototyping techniques, related not only to Web sites.
Wearable mockup
 Designing a T-shirt for signály.cz I have to find out which size [...]]]></description>
			<content:encoded><![CDATA[<p>Prototyping is a must. No matter what business you deal with, prototyping should be a welcome guest that helps you figure out the right decisions in quick-and-dirty way. Today I&#8217;d like to reveal my prototyping techniques, related not only to Web sites.</p>
<h4>Wearable mockup</h4>
<p><img class="alignright size-full wp-image-126" title="prototyp-blog" src="http://valka.info/notes/wp-content/uploads/prototyp-blog.jpg" alt="T-shirt mockup" width="300" height="200" /> Designing a T-shirt for <a href="http://www.signaly.cz/">signály.cz</a> I have to find out which size of the illustration would fit best. A paper cutout (based on a quick sketch) together with an old blue T-shirt allowed me to show the final product to the client without touching a mouse/keyboard.</p>
<p>All the equipment I used was a pen, a paper, a scissors, a T-shirt and a half-assed mobile phone camera. Having finished the phone call with the client I was able to create an almost final design solution <em>in half an hour.</em></p>
<h4>From paper to computer screen</h4>
<p><em>The text was originally published at <a href="http://wireframes.linowski.ca/2009/11/paper-prototype-cutouts/">Wireframes magazine</a>. Thanks Jakub!</em></p>
<p>A part of a school project was to create a paper mockup. Having considered all the problems I’m going to resolve I’ve made a list of proper goals:</p>
<ul>
<li>I have to create a paper prototype of an audio/video manager app. I already have the creative brief and the technical brief.</li>
<li>The prototype should contain all the screens and dialogue boxes of the app. It should be compact, easy to store, portable all-in-one solution.</li>
<li>It should provide quick and fancy user testing.</li>
</ul>
<p>I wanted to have the whole app in a single notebook. Because the app would have a single window interface, the solution had crossed my mind immediately.</p>
<p>The result with all its benefits you can see below.</p>
<p><img class="aligncenter size-full wp-image-129" alt="Audio/video manager app mockup" src="http://valka.info/notes/wp-content/uploads/cutouts-blog.jpg" width="700" height="233" /></p>
<p><em>See all the <a href="http://www.flickr.com/photos/34791101@N07/sets/72157622773498276/detail/">cutouts photos at Flickr</a>.</em></p>
<ul>
<li>A page = a screen. Using such solution provides you with a lot of space around every screen. Put down some thoughts, notes and explanations.</li>
<li>The main frame of the app can serve as a stencil when drawing new screens. Speeds ups the drawing process and keeps the notebook full of drawings clean and consistent.</li>
<li>In addition, the space around every screen serves as a place for pop-up windows, dialog boxes and other elements made from post-it papers.</li>
<li>The main frame stencil can hide all the stuff around a screen and turns a set of described wireframes into a testable prototype in a moment.</li>
</ul>
<p>Take such prototype anywhere, create new screens in a bus or train, test with your mates during a coffee break and finally archive it next to your past prototypes. Worth trying, isn’t it?</p>
<p><em>Keep your eyes on <a href="http://wireframes.tumblr.com/">I ♥ wireframes</a>&mdash;a popular wireframes showcase.</em></p>
<h4>Off the wall prototype</h4>
<p>Since <a href="http://www.signaly.cz/">signály.cz</a> is a Christian organization, we wanted to have our very own cross. We&#8217;re a non-profit organization, so the design solution has to be low-cost and easy to produce.</p>
<p>Using 2 <em>moodboards</em> I&#8217;ve suggested a solution, but it would have been complicated to be produced and also quite different from our corporate design too.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/moodboards.jpg" width="700" height="233" alt="Moodboards" class="aligncenter size-full wp-image-153" /></p>
<p>Together with a couple of friends we&#8217;ve designed a cross that perfectly goes along with our design style. A few sketches came in handy.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/cross-mockups.jpg" alt="" title="cross-mockups" width="700" height="230" class="aligncenter size-full wp-image-155" /></p>
<p>Final production process included a paper prototype of the cross. In 15 minutes we joined some blank papers to show the final shape.</p>
<p>The cross was hand-crafted together with a few skillful friends of mine. Thank you, guys&mdash;the result was amazing.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/cross.jpg" alt="Cross" width="700" height="230" class="aligncenter size-full wp-image-157" /></p>
<h4>The good, the bad and the ugly sketchbook</h4>
<p>I can&#8217;t remember how many times a day a open one of my sketchbooks to draw a design concept or put down an inspiring idea.</p>
<p>Actually, I have <em>3&nbsp;sketchbooks.</em> The fat one is A4 format where I put every single possible sketch: wireframes, banner proposals, sketches etc.</p>
<p>The big one is A4 format too, suitable for text notes. While reading books or articles I put down notes, diagrams etc.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/sketchbooks.jpg" alt="sketchbooks" width="700" height="230" class="aligncenter size-full wp-image-160" /></p>
<p><em>Don&#8217;t miss great Flickr group <a href="http://www.flickr.com/groups/uxsketches/">User Experience Sketches</a>.</em></p>
<p>The little one is a pocket-size notebook that I try to take with me everywhere. The ideas and concepts I&#8217;d like to remember but I haven&#8217;t time to carry out now I keep here. Such notebook could one serve as a springboard when searching for ideas.</p>
<h4>Show must go on</h4>
<p>Now it&#8217;s your turn. Show off your projects!</p>
]]></content:encoded>
			<wfw:commentRss>http://valka.info/notes/2010/01/everyday-prototyping/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Web site design process techniques</title>
		<link>http://valka.info/notes/2010/01/web-site-design-process-techniques/</link>
		<comments>http://valka.info/notes/2010/01/web-site-design-process-techniques/#comments</comments>
		<pubDate>Sat, 02 Jan 2010 21:10:03 +0000</pubDate>
		<dc:creator>Ondřej Válka</dc:creator>
				<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://valka.info/notes/?p=43</guid>
		<description><![CDATA[Working on my bachelor thesis—redesign of a community Web site signaly.cz—I have collected a bunch of methods and techniques I should learn, apply and finally mention in my work. Here are some &#8220;mind maps&#8221; describing what every Web designer should know.
Be aware of the fact, that this is just a list of Web site design [...]]]></description>
			<content:encoded><![CDATA[<p>Working on my bachelor thesis—redesign of a community Web site <a href="http://www.signaly.cz/">signaly.cz</a>—I have collected a bunch of methods and techniques I should learn, apply and finally mention in my work. Here are some &#8220;mind maps&#8221; describing what every Web designer should know.</p>
<p>Be aware of the fact, that <em>this is just a list</em> of Web site design process techniques. It could serve as a springboard for intermediate Web site designers. Try to:</p>
<ul>
<li>Read it.</li>
<li>Check the Resources section in the end of the article.</li>
<li>Study all the books and articles—I drew on just these resources.</li>
</ul>
<h4>Step 1: Briefs</h4>
<p>Get a client brief from you business partner. Than form a creative brief and technical brief. Finally, try to figure out idea brief(s).</p>
<p><img src="http://valka.info/notes/wp-content/uploads/synopsis-briefs.png" alt="Briefs" width="438" height="500" /></p>
<h4>Step 2: Research</h4>
<p>Here is a huddle of methods that can be performed during the design part of process.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/synopsis-research.png" alt="Reserarch methods and techniques" width="438" height="519" /></p>
<h4>Step 3: Ideas</h4>
<p>Organize a strictly moderated idea session or try one of these utilities.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/synopsis-ideas.png" alt="Ideas part utilities" width="438" height="471" /></p>
<h4>Step 4: Deliverables</h4>
<p>Having collected all the necessary pieces of information, start creating deliverables—documents, that are useful in some way and describe the final design process product.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/synopsis-deliverables.png" alt="Deliverables" width="438" height="487" /></p>
<h4>Tools</h4>
<p>This utilities could be applied in any part of the design process. Try to figure out, if they are useful to you.</p>
<p><img src="http://valka.info/notes/wp-content/uploads/synopsis-tools.png" alt="Web site design process tools" width="438" height="532" /></p>
<h4>Resources</h4>
<p>All the books and articles mentioned down there are stuffed with knowledge, describe techniques mentioned above and will help you with understanding them.</p>
<ul>
<li>Book <a href="http://www.amazon.com/Communicating-Design-Developing-Documentation-Planning/dp/0321392353/">Communicating Design: Developing Web Site Documentation for Design and Planning</a> describes the deliverables.</li>
<li><a href="http://erskinelabs.com/post/the-process-toolbox-part-one-project-backbone/">The Process Toolbox</a> is a transcript of <a href="http://www.colly.com/">Simon Collison</a>&#8217;s talk at <a href="http://www.vivabit.com/atmedia2009/">@media 2009</a> conference.</li>
<li><a href="http://www.markboulton.co.uk/">Mark Boulton</a>&#8217;s book called <a href="http://fivesimplesteps.co.uk/">A Practical Guide to Designing for the Web</a> describes number of techniques mentioned.</li>
<li><a href="http://www.ixda.org/">Interaction Design Association</a>, a network dedicated interaction design.</li>
<li><a href="https://gettingreal.37signals.com/">Getting Real</a>, a book by <a href="http://37signals.com/">37signals</a> focused on building Web applications.</li>
<li><a href="http://delicious.com/ondrejvalka/UI">delicious.com/ondrejvalka/UI</a> shelters bunch of another links related to the topic.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://valka.info/notes/2010/01/web-site-design-process-techniques/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
