<?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 Jonathan Lampron on Medium]]></title>
        <description><![CDATA[Stories by Jonathan Lampron on Medium]]></description>
        <link>https://medium.com/@JLampron?source=rss-5d35f9c4573a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zT9rS3UcUG-0I7BKdrFF2A.jpeg</url>
            <title>Stories by Jonathan Lampron on Medium</title>
            <link>https://medium.com/@JLampron?source=rss-5d35f9c4573a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:55:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@JLampron/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[Kleverbeast]]></title>
            <link>https://medium.com/@JLampron/photoshow-by-kleverbeast-47048cc0d6ca?source=rss-5d35f9c4573a------2</link>
            <guid isPermaLink="false">https://medium.com/p/47048cc0d6ca</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jonathan Lampron]]></dc:creator>
            <pubDate>Tue, 12 Jan 2016 21:05:14 GMT</pubDate>
            <atom:updated>2016-01-19T23:15:23.421Z</atom:updated>
            <content:encoded><![CDATA[<h4>The one with the failed startup</h4><p>At the end of 2012, I was finishing up the first semester of my middler year at Northeastern, looking to find my next co-op. I was working part time at PayPal as an extension of my first co-op and knew I wanted a change. One day, I received a call from Kleverbeast, a very early stage startup in New York City offering me an internship position that I immediately took. This began one the weirdest, most challenging, and fun work experiences of my life. When I look back and try to place this experience in the context of my career in general, I realize that the value of my design output from Kleverbeast pales in comparison to the personal growth I had there. I’ll try to summarize the three most important things below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BDURO5u8UFHNYdnnVRicLA.png" /><figcaption>Iterations of Our Product, PhotoShow</figcaption></figure><h4>It’s Never Not Your Job</h4><p>At Kleverbeast, there were simply too few people to be able to say “that’s not my job.” As a result, I was forced to become a flexible and reliable team member. Being flexible taught me how to collaborate with others in a meaningful way. It was great to work with an iOS developer and learn how to import assets into a project because I would then able to that knowledge to inform my designs. By sitting in on financial or roadmapping conversation with the CEO, I learned to keep my designs modular so that the one “killer feature” we needed to add before the next pitch meeting didn’t implode the overall design. I learned how to pitch a product, set up a research lab, model for product photos, make a cappuccino, etc… Any time I had to do something that “wasn’t my job” was a valuable learning experience. (Even that one time I had to make a Jeopardy! template in Keynote for my boss’s friend’s birthday party.)</p><h4>No Plan Survives First Contact With The Enemy</h4><p>No matter how smart I thought a design was, user testing (enemy may be to harsh of a word) proved it to be full of flaws. I learned to have firm beliefs, loosely held. Everything I did was right, until it wasn’t and then I would move on from there. Listening to users talk candidly about what ideas of mine were confusing, incomplete, or just plain idiotic was a humbling experience that had a tremendous impact on me. It taught me to design with a purpose, but be open to criticism. It also taught me that the user is (almost) always right — after hearing what they had to say about certain choices I made, I was left wondering how I could have ever thought it was a good idea. Now I actively seek out feedback from anyone who is unfortunate enough to walk by my desk when I am deep into a design problem.</p><h4>Design to Understand, Not Solve</h4><p>Having this constant feedback loop also cued me into a secret: you don’t always have to know why you are making certain decisions. Up to this point, my process would be to plan everything out in my head, start sketching, nit pick all the designs, end up erasing everything, and then struggle to create something, anything, in Photoshop. With the time constraints at Kleverbeast, that simply wasn’t a viable workflow. I started challenging myself to make 10 sketches in 5 minutes. I switched from a pencil to a pen which freed me from the eraser. My notebook was full of ugly, lopsided sketches that were extremely valuable and could actually inform my design process. The less I thought, the better decisions I made. It became clear that my subconscious had been assimilating everything I had learned as a designer, and was just waiting to be plugged into the process. Now I let that part of my mind drive the early stages of my design process, and use the more analytical part of my brain to pull out the valuable decisions that are worth ideating on.</p><p>I left Kleverbeast, which never materialized into a finished product, to complete my education, and found that I was a totally new person in class. Confident and not afraid to fail or look dumb. I truly consider it to be a milestone in my design life, no matter how stressful it was at the time.</p><p>Thank you for reading this, hopefully you found it worth while. If you would like to get in touch with me with any questions or feedback, my email is <a href="/service/mailto:%20jonathanlampron@gmail.com">JonathanLampron@gmail.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47048cc0d6ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FoodPrint: Responsible Eating]]></title>
            <link>https://medium.com/@JLampron/foodprint-responsible-eating-39f151916c70?source=rss-5d35f9c4573a------2</link>
            <guid isPermaLink="false">https://medium.com/p/39f151916c70</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jonathan Lampron]]></dc:creator>
            <pubDate>Sun, 10 Jan 2016 21:13:44 GMT</pubDate>
            <atom:updated>2016-01-11T21:03:38.008Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making the world better, one taco at a time</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vuNZBv0M_HsbbWI0fONxuA.jpeg" /><figcaption>Seriously, yum.</figcaption></figure><p>The prompt behind the exercise was to create an app that had a positive impact on the environment. I wanted to create something that was informative, convenient, and useful. The result was FoodPrint. FoodPrint is an app that allows people to plan meals for the week and see the carbon footprint produced. Users can change certain ingredients in a recipe to see what impact that has. (Chicken for example, has a lower carbon footprint than beef.) Once the user has their meals planned, they can get an itemized list of all the ingredients to check off while at the supermarket.</p><h4>Planning</h4><p>It was crucial to me that the product I made had a lot of utility. I figured that the best way to get people to actually make changes is to frame it in a way that makes their life easier. To help focus on what exactly I wanted to do, the first thing I did was create a user profile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*FE1xfwJ61r1X0gJBxc_PiQ@2x.png" /></figure><p>Bev, busy schoolteacher and mother of two, became the prototypical (and hypothetical) user of FoodPrint. She certainly wants to be environmentally conscious but finds it hard to do the right research with her busy life. She does most of the shopping for her family, so the onus to plan healthy meals for the family is on her. Bev is used to using the computer and the internet in her classroom, but when she is home she prefers her iPad for the mobility and ease of use. Based on this, it was clear that for her to adopt a new product, it would have to improve her day-to-day significantly without adding any additional burden.</p><h4>App Overview</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*XN64Q1Fk56MsY5CAbgTLvg@2x.png" /></figure><p>When FoodPrint first starts up, the user sees a series of statistics that drive home the point that yes, what you eat does matter. After that screen, users are sent to the week view. From this screen users can see what is planned for the week, and what the environmental impact is. It is in the part of the app that users can dive in to each day, choose their recipe, and mess around with the components. This is the main part of the app, but there is also a monthly calendar view and a shopping list component.</p><p>The main way that information is coded is via color. Every food item in the app is coded either green (low carbon footprint), yellow (medium carbon footprint), or red (high carbon footprint). For ingredients, this is their specific number and recipes are a combination of all ingredients. This color system makes it easy to, at glance, understand where on the spectrum an ingredient or recipe falls and how environmentally friendly a day or week is.</p><h4>Week View</h4><p>The week view gives the user a high level look at the meals for week. I wanted this screen to be information dense, but easily scannable. The upper part of the screen focuses on the individual meals, color coded based on their carbon footprint. I found during user testing that people were not sure what the colors meant, so during the refinement process a key was added to the navigation that surfaced that information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iGPXzLKZCPF9_yliPi8nhw@2x.png" /><figcaption>Week View Progression</figcaption></figure><p>Underneath the meals is a bar graph that gives more insight to the individual meals. I thought that this would animate when changes were made, providing visual feedback that delights while also showing progression. I also ended up adding a discrete readout of the carbon footprint of the week after some testing revealed users would want that information.</p><p>One thing that I knew from the beginning was that goal setting was going to be a big part of this app. When users have a concrete goal, they are likely to push themselves to reach it. The final piece of this screen provides that goal, while also giving some statistics that are grounded in the real world. There is a circle that fills up as you add ingredients that require more fossil fuel. As that circle fills, it outgrows its bounds meant to represent the national average. My thought was that if people saw that bound, they would work to keep their circle inside of it. The other stats, car miles and lightbulbs left on, are meant to ground this information in a way that is relatable. (20 car miles is easier to contextualize than 1kg of CO2)</p><h4>Day View</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phYt1DiTdexMeye25b_dCQ@2x.png" /><figcaption>Day View Progression</figcaption></figure><p>The day view is where most of the interaction happens. Once the user has chosen the recipe they want for that day, they can edit the (color-coded) ingredients in each recipe and watch the carbon footprint update below in a simple bar graph, repeated from the week view. The recipe is always viewable on the top of the screen, so there is always context.</p><p>I wanted to make sure that users could easily move from day to day, so I added controls for that on the left and right hand sides of the screen. Originally, this section was a collection of floating modals. As I worked through it, and ran user testing, I found that people needed a more grounded interface.</p><h4>Conclusion</h4><p>Overall, I consider the output of this exercise to be a high-fidelity wireframe. The main thing I wanted to practice was feature ideation and refinement. I enjoyed going through the user persona exercise and doing a lot of testing throughout the process. Moving forward, I would focus on cleaning up the interface and further refining some of the interactions and navigation throughout the product. You can see the InVision prototype here: <a href="https://projects.invisionapp.com/share/6TKTRKGX#/screens">https://projects.invisionapp.com/share/6TKTRKGX#/screens</a></p><p>Many icons downloaded through <a href="http://thenounproject.com/">The Noun Project</a> and are presented without changes:<br><a href="http://thenounproject.com/term/hamburger/153/">Hamburger</a> — <a href="http://thenounproject.com/edward/">Edward Boatman </a><br><a href="http://thenounproject.com/term/meat/25544/">Meat</a> — <a href="http://thenounproject.com/term/meat/25544/">Christopher T. Howlett</a><br><a href="http://thenounproject.com/term/meat/25544/">Meat</a> — <a href="http://thenounproject.com/nsteve/">Nithin Viswanathan</a><br><a href="http://thenounproject.com/term/meat/25544/">Cheese</a> — <a href="http://thenounproject.com/term/meat/25544/">Shirley Wu</a></p><p>Thanks for taking the time to read this case study. If you would like to get in touch with me with any questions or feedback, my email is <a href="/service/mailto:%20jonathanlampron@gmail.com">JonathanLampron@gmail.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39f151916c70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Local Social App]]></title>
            <link>https://medium.com/@JLampron/local-social-app-42ec9bf4492?source=rss-5d35f9c4573a------2</link>
            <guid isPermaLink="false">https://medium.com/p/42ec9bf4492</guid>
            <dc:creator><![CDATA[Jonathan Lampron]]></dc:creator>
            <pubDate>Sun, 10 Jan 2016 17:38:17 GMT</pubDate>
            <atom:updated>2016-01-19T23:15:57.393Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s all good in the hood</h4><p>As a visual design exercise, I reworked some screens from a location based app that pulls in social media from a nearby, trending, or user-defined area. The functionality is all based on an existing app. I specifically wanted to explore information hierarchy, fluid transitions between states, and a dark color palette.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*V4aPkd7ipdOU_0yZBxIlrQ.png" /><figcaption>Mocks of Different Sections of the App</figcaption></figure><p>One of my main goals was to make sure that relevant information was always available to the user. The main metaphor of the app is a feed. The feed is a collection of posts and each feed is tied to a geographic area. The main pillars of the app are different feed, made up of posts tied to a specific geographic area. These areas could be user defined, trending, maintained by another user, or nearby. I tried to make sure that on a post, users could easily see who created that post, and, more importantly, where that post was coming from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PdgtDl3730LD44osPCog1Q.png" /><figcaption>Example of a Post</figcaption></figure><p>It was also important to differentiate posts by content type while keeping a clear design system. Since this app pulls in content from other social media sites, there is no creation element, only curation, it was important to make sure the user knows where it came from. This goes a long way in creating trust between the user and the product, as well as setting the correct expectation for where the user will go when they tap on the post.</p><p>Around the time I was working on this, Apple introduced the “screen edge swipe” into iOS and I really wanted to incorporate that in the navigation of this app. Working first in pen and paper, I defined the different interactions. Then I translated these decisions into After Effects. (Unfortunately, prototyping tools were not yet enjoying the prominence that they are now.) You can see how it works in the video below.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffast.wistia.net%2Fembed%2Fiframe%2F87oxpg75rd%3Ftwitter%3Dtrue&amp;src_secure=1&amp;url=https%3A%2F%2Fjonathanlampron.wistia.com%2Fmedias%2F87oxpg75rd&amp;image=https%3A%2F%2Fembed-ssl.wistia.com%2Fdeliveries%2F2b9f69cf291dfb4df21bc94b839b86b286675977.jpg%3Fimage_crop_resized%3D960x540&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=wistia" width="960" height="540" frameborder="0" scrolling="no"><a href="https://medium.com/media/3b6e35625c590a6c949e7648bb785e77/href">https://medium.com/media/3b6e35625c590a6c949e7648bb785e77/href</a></iframe><p>Thanks for taking the time to read this. If you would like to get in touch with me with any questions or feedback, my email is <a href="/service/mailto:%20jonathanlampron@gmail.com">JonathanLampron@gmail.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42ec9bf4492" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing the New Q]]></title>
            <link>https://medium.com/@JLampron/designing-the-new-q-af7b43295351?source=rss-5d35f9c4573a------2</link>
            <guid isPermaLink="false">https://medium.com/p/af7b43295351</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Jonathan Lampron]]></dc:creator>
            <pubDate>Fri, 08 Jan 2016 20:41:24 GMT</pubDate>
            <atom:updated>2016-01-12T20:32:52.251Z</atom:updated>
            <content:encoded><![CDATA[<h4>A new look for a legacy product</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fBE2w_VoGP-64iS23J6q3g.png" /><figcaption>Don’t worry. I cleaned up the layers after I took this screenshot.</figcaption></figure><p>QuitNet is a social networking site all about connecting people who are trying to quit smoking. It is a serious task, with serious implications, so we have to weigh all our decisions very carefully. There are times when it feels as though it would be more fun to work on a more whimsical project with an established design language, but most of the time I just feel grateful that I get to be a part of shaping the future of a product that has already helped so many people, and adds thousands of users a month.</p><p>Recently, I started thinking about what QuitNet could do better and how the design could be updated to reinforce the main pillars of our app. I ended up making many changes, but the main ones, and my thinking behind them, are outlined below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3awM1KSXfp9o66OAm1PqHg.png" /><figcaption>The New Q</figcaption></figure><h4>The Feed</h4><p>The feed is the main component of QuitNet. It is where people go when they have questions, are seeking advice, or just need to vent about what makes quitting smoking so damn hard. QuitNet, like all MeYou Health products, is built on the philosophy that social interactions help people stay motivated and achieve their well-being goals. Knowing the stakes, I set out to create a feed that felt readable, interactive, and valuable.</p><p>I started this process researching how other social media sites designed their feeds. After looking at many different sites, I found that there were two main design patterns. The first, employed by products such as Twitter and Instagram is to have one continuous feed, without much separation between posts. Each piece of content feels light and ephemeral because it is a small part of a much larger group. As a result, these sites feel very entertaining.</p><p>The second design pattern, employed by products such as Facebook, LinkedIn, and, ultimately, this version of QuitNet, is to have each post exist on the same plane, but in it’s own container. Each piece of content essentially becomes its own “card.” Each card, in turn, has a weight to it, and the piece of content feels more valuable since it is separated from all the others. Social interaction feels more impactful and significant. This style of feed creates a nice design language that can be carried through throughout the product. I can design a card as a module, and know that it has a place. We can create cards that appear in the feed that aren’t posts — a call to action to encourage someone that is craving, nudges to add a profile picture, updates about new features, etc… — without breaking the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jRoNs9BC1F9jRAzMbmpPbA.png" /><figcaption>An Example of a Post</figcaption></figure><p>Another benefit of this style of feed is that it creates a lot of opportunity for motion, due to the depth of the product. After looking through Google’s Material Design guidelines, I became acutely aware of how depth and motion can work together to not only delight the user, but also reinforce hierarchy of information. When hovering over a post, it moves closer to the user, indicating it can be interacted with. When clicked on, the other posts disappear and the comments on that post slide out from underneath. Since the “New Post” module is modeled off the same metaphor as posts in the feed, there is an easy visual transition from reading to creating to have created. All of this is afforded by the new visual metaphor of cards.</p><h4>The Action Column</h4><p>A consistent piece of feedback I would get about QuitNet is that it can be difficult to figure out what the primary action is. Our main feedback loop is reading posts and interacting with users, but there are other actions a user can take that have value in supporting a successful quit. The problem is that these actions are all surfaced in a linear way. You log in, are prompted to take the pledge, and then asked how your quit is going. Once you get to that point you are in the end of a funnel and your momentum is halted. In an attempt to surface more information to the user and create a non-linear way to interact with QuitNet, I added a secondary column that can prompt the user to take different actions, give them more information, and promote exploring the product a little more. The actions available in the default version of this column are taking a daily pledge not to smoke, seeing friends’ activity, and getting an overview of your quit status. I chose these as they represent three very important pillars of our product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acy9Zp9r_K5iobhaQXcxww.png" /><figcaption>The Pledge Module for the Action Column</figcaption></figure><p>The daily pledge my not be our main feedback loop, but it is potentially our most important. By pledging, people add themselves to a chain of people that have also pledged that day and get encouragement from other users to keep that pledge. Friends’ Activity allows people to keep up to date on how the people they have specifically chosen to follow are doing in their quit. This allows us to bring in a little of the entertainment value of a Twitter like feed, while getting to keep our interaction-heavy main feed. It even has an indicator alerting the user to if a friend posts about having a craving. Finally, the Quit Status brings to the forefront all the progress that the user has made and the real impact of their hard work in staying quit. These stats are great motivators for our users.</p><p>Having a dedicated space for actions also allows us to to try out new features easily such as an emergency craving button, commonly asked questions, quit tip of the day, etc., without having to figure out where to stick these new features and how to get users to notice them. Overall, it provides much more flexibility for us to try out new features.</p><h4>Keeping it Friendly</h4><p>When creating this new, sleeker, version of QuitNet, it was important for me to keep in mind what makes the current QuitNet successful. Of course, the main thing is the wonderful community we have, but there has also been a lot of thought put into the current design to create an inviting, warm environment. Where other sites choose to keep a neutral design so as not to impact the content, we try to add elements and colors that create an friendly and comforting backdrop that adds a lightness to the otherwise difficult task at hand.</p><p>One of the main elements I wanted to keep in this new version of QuitNet was the tan background. After trying background colors of varying hues and saturation, most end up feeling very cold. Our users come to the site to discuss difficult, annoying, and mainly negative things — and that’s ok! They need a place to vent and unload this stuff, and we are happy to be that place. That being said, a monochromatic blue background, for example, would read as being sterile and reinforce the negativity of the site. The yellow background puts the user in a happier place, and posts that could turn the site into a pit of despair become a little bit lighter to create a sense of camaraderie and unity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*da2PWt49zHs1c5-i-CDkSQ.png" /><figcaption>Putting It All Together</figcaption></figure><p>We also like to use fun visual element to highlight celebratory moments. On certain days of their quit, we add hats to users’ avatars across the site to let everyone know that they have reached a new milestone. We also give a user who is celebrating a milestone a different prompt for posting. For example, at three months quit, we ask people what they are doing with all the money they have saved from quitting. To indicate that the user’s post is a special milestone post, we put confetti behind it on the feed. Both of these things not only encourage people to come to the site on milestone days, but also provide a sense of progression and reward that reinforce their quit.</p><h4>Looking ahead</h4><p>This redesign mostly focused on the feed of QuitNet. I believe that the new visual language will have value throughout the Q, and help unlock the potential of areas that are currently lacking such as the profile view and messages. There is also plenty of work that needs to be done to translate this design to mobile. I am excited to see how users will react to these new changes. Our users tend to be optimistic about change, but since our audience tends to skew in a non-tech savvy direction, it can sometimes be tough to accurately anticipate all their needs. Luckily, they are not shy when it comes to telling us where we make mistakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytH92niACRfOvN_SP-dm7w.png" /><figcaption>Feed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ufsGO9znCdVeINjalOnoYg.png" /><figcaption>Post</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NzFlV7dTiRhzneXJDn1n-w.png" /><figcaption>Mobile</figcaption></figure><p>Thanks for taking the time to read this case study. If you would like to get in touch with me with any questions or feedback, my email is <a href="/service/mailto:%20jonathanlampron@gmail.com">JonathanLampron@gmail.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af7b43295351" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>