<?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 Ravi Teja Vempati on Medium]]></title>
        <description><![CDATA[Stories by Ravi Teja Vempati on Medium]]></description>
        <link>https://medium.com/@ravitejavempati?source=rss-c1296349e31d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*gWFafajTWwR5oCi3.jpg</url>
            <title>Stories by Ravi Teja Vempati on Medium</title>
            <link>https://medium.com/@ravitejavempati?source=rss-c1296349e31d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 06:44:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ravitejavempati/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[My first UX sales pitch!]]></title>
            <link>https://medium.com/@ravitejavempati/my-first-ux-sales-pitch-1c9dc29a373?source=rss-c1296349e31d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c9dc29a373</guid>
            <dc:creator><![CDATA[Ravi Teja Vempati]]></dc:creator>
            <pubDate>Mon, 01 Sep 2014 00:52:28 GMT</pubDate>
            <atom:updated>2014-09-12T14:29:41.862Z</atom:updated>
            <content:encoded><![CDATA[<h3>Our first UX sales pitch!</h3><p><strong><em>“I want my son’s picture on the front page of the website” </em></strong><em>Says Mark, Owner of the restaurant</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/1*R5T9ULNXfenwEinHFdE_gw.jpeg" /><figcaption>Did you sign your name on the Columbo’s chair yet?</figcaption></figure><p>Later did we realize that his son is 39 years old. We immediately knew what had to be left out while analyzing the interviews. In your experience, you must have seen hundreds of projects with hip clients, cutting edge technologies and arrive at a shiny, perfect app or a website.</p><p>No, this is not such kind of a story. This is the story of 4 graduate students who had to make their first sales pitch, work as a team and come up with a final product. No prior experience. <em>Only theory.. Would it be enough?</em></p><p>We had 5 days to find a website or an app of a local business and convince the client to re-do <em>or</em> do it from scratch using UX methodologies. I remember thinking BBC Top gear Jeremy’s words, <em>“How hard can it be?”</em> We were obviously, naive and foolish.</p><p>We approached several restaurants and businesses who appeared to have minimal online presence. There was one small problem. None of us had any idea how to pitch to a client. So, we did what any clueless person would do. We called and tried to set up an appointment.</p><p>Here’s how our first couple of conversations went:<br><strong>Us:</strong> “<em>Hello! We are Clemson University researchers and we would like to work with you to develop your website. We have a great idea and tools that can help you gain a lot of customer base. Can we set up a meeting to talk about it?<br></em><strong>Other side:</strong> <em>I don’t feel that is necessary. I already have a website for people to see what I do.</em> <em>What’s wrong with the one that I have?<br></em><strong>Us:</strong><em> umm.. umm.. (Panicking)! It does not conform to all the standards. It is not easy for people to use. — </em>Oops<em>.<br></em><strong>Other side:</strong><em> Who are you to tell me that?!” — </em>We lost a couple of people that way — We learnt it the hard way</p><p>It was gold digging. We searched for every business, restaurant, whatever there is… Among all the mud. We found a gold mine. And this is what it looked like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gLINiMfw1ORax6MhGojH7w.jpeg" /><figcaption>As you see, there’s a lot of noise in the website</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6ieXwfhVzU7B5ZZFcgw85g.jpeg" /></figure><p>All we now had to do was to convince the reluctant manager to re-do his website. <strong><em>Change in strategy:</em></strong> We went to the restaurant and talked in-person to the client and presented him our idea and the benefits of working with us. We explained him the importance of a website and updating information in this growing world of technology. We showed him statistics proving that most of his customers are college students and that they are among the ones who use technology the most. — <em>“Is it not important to cater to their needs?”</em> — Bang on Target!!</p><h3>Talking to strangers</h3><p>Before we hit the streets to find our pizza lovers, We brainstormed and came up with a list of questions to begin the interviews. We were able to use these questions and follow up depending on their answers.</p><p>We wanted to know about our users. We asked them to tell us a bit about themselves. Here’s an expanded list of some of the points that we used to ask questions:</p><p><em>“1. How and where do they access the websites from?<br>2. Do they order pizza online? If so, how often?<br>3. What are their concerns when ordering something online, let alone a pizza<br>4. If they had any frustrations during their previous ordering experiences<br>5. Likes or dislikes about the current system<br>6. If they have ever been to Columbo’s pizzeria? what makes it unique from a customer perspective?”</em></p><p>Well.. The interviews went well, but standing and talking about something that users do is not as good as them showing you how they do it. To get access to that, we went to the library and were able to observe users using the competitors websites and the <em>gold mine (old website) </em>while thinking out loud.</p><p>When your product is something that everyone uses, you find your users all around you. But, you have to approach them for information, not to sell anything. So, presentation is important. We included a clipboard and ID card to appear as researchers. Blending in with the environment is equally important.</p><p>We approached them at the restaurant, downtown, library saying this:</p><p><em>“Hey! I’m Ravi. I’m a researcher and I’d love to ask you a couple of questions about a website for a restaurant.”</em></p><p>Well.. Being in the college town helped. We were able to get information from all age groups including the client. We asked the client on what he wanted his website to portray and got some insights from it.</p><h3>Data conversion for insights</h3><p>We have all the raw data now. <em>What do we do with it?</em><br>We analyzed each and every sentence that we got from the users. Ignored their advice on how to do it. Instead, concentrated on the reason for their frustrations.</p><p>While analyzing, we used the following guidelines to convert the raw data into proper need statements (insight statements).</p><p>“<em>1. Express the need in terms of what the product has to do, not in terms of how it might do it.<br>2. Express the need as specifically as the raw data.<br>3. Express the need as an attribute of the product.</em>”</p><p>Doing this ensured that the need statements are not solutions for the problem and users’ needs are interpreted directly without any alterations.</p><p><a href="https://drive.google.com/file/d/0B_oQQF9VNlICdW1fM1AtbHlkQ2s/edit?usp=sharing">Click here to view an example of our insights</a></p><h4>Affinity diagrams:</h4><p>Once we had our insights, we went back to the users asking them to rate each insight on a scale of 1–5 with 1 being unimportant and 5 being highly important. The result: We had our priorities set straight. We knew what we could not ignore and what immediately needed our attention</p><h3>Personas and use cases</h3><p>We used the information that we got from the interviews and gave them a whole new shape. We also gave them a name, a character and a role in the society of design. They were a snapshot of our users. We included a fictional name, photograph, job titles and responsibilities, demographics, goals and tasks with our product and their environment.</p><p>Here. Take a look at one of the characters in our movie.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*9VXxEDNIvYIeSYhnwX36Nw.jpeg" /><figcaption>One of our persona</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*o5JcZL0ugP5rfWVG8X_CXw.jpeg" /><figcaption>Use cases</figcaption></figure><h3>Competitive analysis</h3><p>We used the need statements and converted them to metrics. These metrics were used to calibrate the performance of a website. This gave us an idea of how lacking our website is in terms of performance. <strong><em>What do you need to do in order to improve?</em></strong><em> — </em>Set targets. Yes! That’s what we did!</p><p>We set target specifications at 2 levels.<br><strong>Level 1: </strong><em>Marginal target specifications</em> — These are the specifications that are higher than the competitors performance. It takes reasonable amount of time and effort for the team to achieve these. But it is doable!</p><p><strong>Level 2:</strong> <em>Ideal target specifications</em> — These are the maximum performance figures that the team can possibly achieve (Yes. We considered our limits).</p><h3>Concepts</h3><p>We used our needs and came up with as many concepts as we could. We placed the concepts on the walls of a conference room and started discussing each concept in detail. We noted the parts that we liked and disliked in each concept. We then voted for each concept and eliminated them one after the other.</p><p>It wasn&#39;t feasible for us to test each and every concept with the users. There were just too many. Voting among the team members seemed to be a plausible solution for that.</p><h3>Sketching</h3><p>I’ll cut it short now. Not much is needed to be told about sketching and wireframing. Here are the sketches of the final concept that I drew. We also did a wireframe of the same, my teammate did it, so I’m not publishing it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pblAaphI9RHQWyrJXBCUfg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tF_i-ki1ad5ng7prT3R5cg.jpeg" /><figcaption>Final concept sketches</figcaption></figure><h3>Usability evaluation</h3><p>We now had both low and high fidelity prototypes to test with the users. But before we went out, to set up a stall and found our mistakes, we did a small usability evaluation with methods such as task analyses and heuristic evaluation.</p><p>For task analysis — we took the use cases, broke down each task in to very minute steps. We recorded everything the user need to know in order to operate the website and also found <em>potential </em>problems for the users.</p><p>Heuristic evaluation was not so effective since we did it on a prototype. We should have done it at the end. Given another chance, I would do it at the end of user testing phase, so that I can ensure that the system is ready to be implemented.</p><h3>User testing</h3><p>We did user testing in 2 phases. One — With the prototypes before implementation. Two — During implementation.</p><p>We got a script ready and set out with all the weapons (tools — prototypes and stuff. Nothing harmful!). We went to the restaurant, library, also set up a stall in front of the library for a day to test with the users. We tested the prototypes with 28 participants and recorded all the problems.</p><p>At users setting — you can gain a lot of information through that. You’ll know the distractions they face, their environment, see how your website or app is working in that conditions. <strong><em>At one instance</em></strong>, one of our users was interrupted by a phone call in the middle of the test. The task was to buy a pizza, and she was not able to utilize the coupons while ordering since they were hidden in the drop down menu. So, to solve the problem we brought coupons on the main menu. And the <strong>RESULT: Not that user alone, everybody went right to that page!</strong></p><p>At the stall — We humans are curious. When there’s a group of people watching something. We want to go there. We want to take a peek and see what’s going on. We had more than our target number of users come and test our prototypes. It was beneficial for collecting the info for the survey at the end.</p><h4>Making:</h4><p>We made the website page by page and iterated until our target specifications were met.<br>Here are our iterations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R4IPF_4z0puEj_StMzbLSg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SaIm3PxymnqMSolryGt0oA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VVR9YBxUcmPp3GOu59t3tg.png" /><figcaption>Iteration 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SubRp1ch7lZ8gII3TMe9_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uc52zQDkrBxWT0JWdHoCVA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FC2shjHYfQL9NTbKVKgEkQ.png" /><figcaption>Iteration 2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RRHLKae7B79cLU4sEbem1g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvCs54FCc9mexwt7BlJx9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5aUD_VgAancepztlGr22cA.png" /><figcaption>Iteration 3</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VMWnPGioyU9KM0WGui6gCQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-pRovkGx4_rdTtaQLDpQkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hYVQjvRsVM4aqWkZkI8Zxg.png" /><figcaption>Iteration 4</figcaption></figure><p>AND, here’s the <a href="http://www.columbospizzeriaclemson.com/">final product.</a></p><p><em>Thanks for getting to end of the article guys, you have done what 80% of those reading this weren&#39;t able to do.</em></p><p><em>I don’t only talk, I listen too.. I want to hear from you. How do you do things? How would you have done this project? Any flaws with this process? . You can comment here or you can write to me directly at </em><strong><em>rvempat@g.clemson.edu</em></strong><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c9dc29a373" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>