<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ike Breed on Medium]]></title>
        <description><![CDATA[Stories by Ike Breed on Medium]]></description>
        <link>https://medium.com/@ieks?source=rss-1ad5896c6b94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2sk81APFdHUFJtJdYD6oLQ.jpeg</url>
            <title>Stories by Ike Breed on Medium</title>
            <link>https://medium.com/@ieks?source=rss-1ad5896c6b94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:11:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ieks/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Wireframe testing: follow a use case]]></title>
            <link>https://medium.com/@ieks/wireframe-testing-follow-a-use-case-7247a6e0434?source=rss-1ad5896c6b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/7247a6e0434</guid>
            <dc:creator><![CDATA[Ike Breed]]></dc:creator>
            <pubDate>Wed, 02 Oct 2013 21:13:43 GMT</pubDate>
            <atom:updated>2013-10-03T06:05:33.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L--Mx94rClhI5jmB.jpeg" /></figure><h4>Creating context with the right content</h4><p>When developing a new website, it is advisable to involve the end user early in the process. You do not want to lose time and energy developing something that does not properly work for the user. Letting end users use your product in an early stage will therefore potentially save cost.</p><p>An observation when testing wireframes is that participants forget that they are testing a non-finished website relatively easy. However, this can also be a pitfall. So what to keep in mind when testing wireframes? And what should you be aware of when interpreting the results?</p><h4>Tell a consistent story</h4><p>Telling a consistent story is a matter of details—the right details. When testing an order flow and the price of a product is raised from one page to another, participants will address this as well. When prices are unrealistic, this will be noticed as well by the participants. The price of a product is in most cases a decision factor when buying a product, and therefore an element on the page that grabs the attention.</p><h4>“What is this, Italian? Should I read this?”</h4><p>Participants are not necessarily familiar with lorem ipsum, but also a mixture between different languages for copy and labels — e.g. a wireframe that contains copy in both English and the native language of the participant — can complicate things. While reading or scanning a page, familiar words will be automatically processed. When only part of the page contains the real content, this part will automatically receive more attention—influencing the test results.</p><h4>A (too) logical path</h4><p>Wireframes are a good way to determine whether a flow on a website is experienced as a logical flow, but there is the risk of putting too much energy in the details of only a part of the page. Consequently, that part of the page will get more attention. What is tested, then, is not whether people can find something on the page but if they spot the parts that are different from the rest of the page. Therefore, the level of detail that is put into call-to-action elements on the page, e.g. buttons, should be the same for all buttons — not only the one the user needs in the flow being tested.</p><h4>Conclusion: context and content</h4><p>In sum, it is important to tell a clear story in your wireframes, a use case. The more a participant can empathize with this story, the better the feedback will be. The use case should therefore be the starting point when the wireframe is made. The right content is an important aspect of the use case: rather use content from the (current) live website than using dummy content like lorem ipsum. And give the different call-to-action elements the same level of detail — not just the buttons that are essential to the logical flow of the use case.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7247a6e0434" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>