<?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 Alex Pour on Medium]]></title>
        <description><![CDATA[Stories by Alex Pour on Medium]]></description>
        <link>https://medium.com/@alexpour?source=rss-a87f84d2952a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*w_jtyGtb4moLTgwj6SKfNg.jpeg</url>
            <title>Stories by Alex Pour on Medium</title>
            <link>https://medium.com/@alexpour?source=rss-a87f84d2952a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:29:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexpour/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[I Don’t Know How to Be Productive]]></title>
            <link>https://medium.com/@alexpour/i-dont-know-how-to-be-productive-7a3584c9574a?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a3584c9574a</guid>
            <category><![CDATA[efficiency]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[to-do-list]]></category>
            <category><![CDATA[hustle]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Sun, 09 Sep 2018 20:06:45 GMT</pubDate>
            <atom:updated>2018-09-09T21:18:09.059Z</atom:updated>
            <content:encoded><![CDATA[<p>Today is Sunday the 9th of September, 2018. The day before my first holiday this year. I am sitting here looking at my todo list, I have just noted down something that I am exciting to do. And I realised something that has prompted me to write this short, off topic blog post.</p><h3>What did I realise?</h3><p>Far too often, I think of something that I want/need to do, note it down and then arrange to do it in some magical future scenario. A scenario in which I have spare time and the motivation to do it. Basically assigning work to my future self.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*bs3evGJ658QG4o5qTkxEaw@2x.jpeg" /></figure><p>However, when I get to that magical date, I very rarely have the time or motivation to complete that task. I also have no commitment to my past self that set the task, because my present self is waaay more convincing than my past self.</p><blockquote>This made me think about how life would look if my present self worked for my future self.</blockquote><p>If my goal was to complete tasks, so my future self didn’t have to do them. This future self, could be me at 6pm that day, me on the weekend or me on holiday.</p><h3>What does this look like in practice.</h3><p>Instead of setting loads of tasks for a future date and then picking which of those tasks to do when I sit down to work. I plan to start each day by reviewing my done list from the previous day.</p><p>This should help me focus on how far I have come, instead of how far I have to go.</p><p>I also like the idea of starting the day by looking at what I said I would do, but didn’t. I imagine it will put me in a motivated mindset. One where I want to do better than I did yesterday.</p><p>Once I have reviewed yesterdays work, I’ll set my todo list for just the day ahead. Making sure to be realistic with how much I take on.</p><p>Selecting my tasks at the beginning of the day, means I can choose what I want to get done with a level head. Rather than choosing to work on the wrong things in the moment.</p><h3>Summary</h3><p>Tomorrow is the first day of my holiday. It is also the first day I plan to try this method. If all goes according to plan, I will write a follow up.</p><p>Thanks for reading,</p><p>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a3584c9574a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know How to Learn Soft Skills]]></title>
            <link>https://medium.com/@alexpour/i-dont-know-how-to-learn-soft-skills-5d02366acbfc?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d02366acbfc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 19:33:41 GMT</pubDate>
            <atom:updated>2018-09-03T19:33:41.689Z</atom:updated>
            <content:encoded><![CDATA[<p>Ok this is going to be a shorter, more off topic post. I have been focussing on improving my ability as a Product Designer and have been neglecting learning and improving soft skills.</p><p>When I first joined my company, I warned my team that when I’m head down solutioning, I completely miss social cues and become very ‘to the point’. Making some conversations painfully awkward or even coming across as rude.</p><p>So, over the past few months I have started to be more conscious of learning soft skills. Below is a list of recently adopted behaviours and the benefits and lessons that have come along with them.</p><h3>What are soft skills?</h3><p>Soft skills are the skills that help us navigate our environment, work well with others, perform well and achieve our goals.</p><p>They help us to think critically, solve problems, resolve conflict and interact effectively. Through a combination of people skills, social skills, communication skills, character traits, attitudes, career attribute, social intelligence and emotional intelligence.</p><p>We develop soft skills through experience. Focus, structure and repetition help us hone those skills.</p><h3>Communication</h3><p>Not that I’m not interested or socially awkward, it’s just that when I have something I want to ask or do, it’s all I can think about and it often ends with me awkwardly navigating the start of a conversation.</p><p>Creating time for communication has proven to be invaluable. It has improved my working relationships and made working with others effortless. I often ask people for coffee during the day and ask them how things are going.</p><p>Everyone needs to vent and feel like they are being listened to. So when I talk to people on these coffee breaks, I don’t tell them what they should do, or tell them about my similar experiences. I just listen.</p><p>If I can give advice or offer a different point of view, of course I will. But the idea is to let them talk themselves through to a solution or resolve.</p><h3>Seeking feedback</h3><p>I think it’s important to make it clear that people can give me honest, unsolicited feedback. We have a culture where you can book a 1:1 or go for a coffee and give someone completely honest feedback.</p><p>We’ll talk it out and both parties will give their perspective and then move forward with no resentment or bitterness. I value this so much!</p><p>But something I have been trying to do more is to seek out feedback. This can be at the end of a project or</p><h3>Have confidence in your ability</h3><p>I often get overwhelmed when starting out a particularly complex project. “Am I good enough to be doing this?” is an all too familiar thought.</p><p>I have since learned to trust in the process. It’s worked so many times before, so why do I doubt it this time? I now head into new challenges with the confidence that I my process will result in a solution.</p><p>I also communicate the value of each stage of the process to my team. Making them aware of what I am doing, how much time it’s likely to take and the value we get from it.</p><h3>Leadership</h3><p>Being that I’m the only designer at my company, it is important to have a clear vision of where things are headed. But the tricky part, is getting the rest of the company onboard.</p><p>Not long after I joined I was tasked with redesigning our core product. An application form that previously, had a lovely, colourful image in the background.</p><p>My proposed redesign, did away with this image as a way of making things more accessible. Everyone kept talking about how bland it looked and saying they preferred the old version.</p><p>So I booked a meeting with our CEO and the PM for that product. In the meeting I ran them through the reasoning behind most major decisions. Presenting facts to back up each decision.</p><p>A couple of weeks later I was speaking with our CEO and he mentioned that he much preferred my version to the old product. It wasn’t an overnight change, but my meeting definitely helped to get everyone on board with the change.</p><h3>Learn to listen</h3><p>I realised that I had 2 really bad traits when talking to people. It wasn’t until my colleague who doesn’t do these things showed up, that I realised what I was doing.</p><p>Firstly, when someone was talking I used to be formulating a response in my head. Meaning after a certain point I wasn’t really paying attention, but trying to remember my response.</p><p>This would result in me sometimes only addressing the first half of what they had said and losing track of what we were really talking about.</p><p>The second thing I would do, was finish other people’s sentences once I thought I knew what they were going to say. I think I probably did it as a way of confirming to them that we were on the same page. As well as trying to move the conversation along.</p><p>Now I’ve learned to listening to what people are saying with all my attention. And then think of a response once they have finished.</p><p>The differences I have noticed are, most of my responses now are questions whereas before they were usually statements. Secondly, conversations seem to go a lot slower, but are packed with much more information.</p><h3>Be adaptable</h3><p>Being able to adapt to changes quickly is something I’ve had to learn quickly at my current job. My previous jobs were all green field project that I work on in my spare time.</p><p>Meaning there was no firm deadline and always plenty of time to adapt. With my current job, no two days are the same. One day we can be planning what the next 6 months looks like. The next, we are reacting to something completely unforeseen.</p><p>Positioning myself in a way that lets me adapt easily, means that these surprises rarely catch me off guard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d02366acbfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know How to Become a Senior Product Designer]]></title>
            <link>https://medium.com/@alexpour/i-dont-know-how-to-become-a-senior-product-designer-35cd6254abc?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/35cd6254abc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Mon, 03 Sep 2018 19:18:16 GMT</pubDate>
            <atom:updated>2018-09-03T19:20:05.048Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGSzMhPG59KTJQoF2167dg.jpeg" /></figure><p>I’m currently hired as a Mid-Weight Product Designer. However, when interviewing other Mid-Weight designers it became apparent to me that I’m somewhere in the top end of the Mid-Weight bracket.</p><p>In fact, I’m probably a senior. At least for what my company needs. However, as the sole designer at my company, it can be hard demonstrate when you’re doing everything including design delivery.</p><p>So I decided to set myself a checklist of things I need to demonstrate in order to move up to a senior level.</p><h3>As I understand each level of seniority</h3><h4>Junior Product Designer</h4><p>Someone who focuses solely on solving the problem at hand. They have a granular view of the product and pay attention to the details more than the big picture.</p><p>They think about their users in general terms rather than specifics and can explain the reasoning behind their decisions.</p><p>A Junior Product Designer utilise online resources for inspiration and advice and is always looking to pick up and develop new skills.</p><h4>Mid-Weight Product Designer</h4><p>Someone who can assume the user’s point of view and can design with them in mind.</p><p>They know how to write user stories, map user flows and perform other commonly used UX methodologies. One of which is how to test their designs online and onsite.</p><p>They communicate confidently and efficiently and understand and work towards the business goals.</p><p>Design starts with research and exploration before producing prototypes in order to validate assumptions.</p><h4>Senior Product Designer</h4><p>Someone who is now in a position where they can stray away from rules and convention when called for.</p><p>They know how to create and maintain an enjoyable experience and have earned the trust of others through consistent high quality of delivery.</p><p>They still constantly look to improve themselves and their abilities, but also look to improve internal processes.</p><p>They highlight problems through research and observation and then come up with, test and deliver solutions.</p><p>They also use their knowledge and experience to help other designers with their own work.</p><h3>The Challenge</h3><p>Being the sole designer means that I am doing all design related tasks. From high level strategy to putting together high fidelity screens.</p><p>This puts me in a position where I am limited on the time that I can spend doing more senior level tasks. So I have highlighted some things that I need to adopt, continue and or demonstrate within my company.</p><h4>Manage projects alone</h4><p>Although developer resource is allocated by PMs, I have been making a point to deliver data driven solutions to problems that aren’t widely known or talked about.</p><p>This means discovering and defining problems our users are having, through the use of data analysis, interviews and user testing. Then, coming up with a tested solution which includes written tickets with assets attached.</p><p>When required I should be able to demonstrate the value of the solution to the business and get the work prioritised by the PMs.</p><h4>Rapid prototyping &amp; data informed design</h4><p>Something I’ve learned over the past few years is the difference in efficiency between trying to figure out all the problems up front and rapidly prototyping. Testing prototypes with 5 users after coming up with an initial solution usually highlights 80% of the problems.</p><p>It also gives me data to backup my decisions which helps to gain the trust of my colleagues and the company. This data can also be used to measure the effectiveness of my solutions.</p><h4>Holistic View of product</h4><p>When exploring design solutions I make sure to think about how it affects everything. How it fits in with other products, the lifecycle of the product and the user’s relationship with the product.</p><p>Before I joined there was no real overview of our product and as a result, decisions were often made out of context. Resulting in a disorientating user experience.</p><p>Upon joining I put together flowcharts of all of our products. Showing all journeys and decisions along the way. I also included the user’s emotional state.</p><h4>Trust the in process</h4><p>I often get overwhelmed when starting out a particularly complex project. “Am I good enough to be doing this?” is an all too familiar thought.</p><p>I have since learned to trust in the process. It’s worked so many times before, so why should I doubt it this time? I now head into new challenges with the confidence that I my process will result in a solution.</p><h4>Own the design</h4><p>We don’t have a front end dev. We also deliver extremely quickly, which means that adding small things solely to make the user experience a bit nicer, are often left out.</p><p>At first this really annoyed me, but I got to a point where I stopped pushing for these things because I knew what the answer would be. However, I’m now in a position where I’m fighting to get them in.</p><p>It comes back to data at the end of the day. If I can prove it, it’s not a problem. But the change that happened was my ownership of the design. I take sole responsibility for everything design related, which means, I have committed to delivery things I am proud of.</p><h4>Understand the business and market</h4><p>Understanding the market and the job we do for our users is something that I am starting to double down on. Up until now, I only had a basic knowledge.</p><p>I thought I knew why people used our product and our place in the market. However, since then I have taken a step back and started to find out what our users actual motivations are.</p><p>Speaking to users is the only way to truly understand why they are using our product and the effect it has on their lives. As well as finding out user needs and requirements.</p><p>Personas that are kept up to date, are a great way of distilling the information gained through these interviews. It allows the product team to actually build features that our users want.</p><h4>Design as a pillar of Product</h4><p>Since joining, I have outlined and implemented a design process where before there was none. It’s a thorough design process that can also be scaled back to deliver quickly.</p><p>I have communicated the value of each stage of the process to my team. Making them aware of what I am doing, how much time it’s likely to take and the value we get from it.</p><h4>Demonstrate forward thinking</h4><p>Something I’ve always done is think about where our product is headed and what I need to do in order to be prepared for when the change eventually does come.</p><p>This can be things like thinking about how multiple products sit within our site and how we can keep a consistent navigation across all products.</p><p>I enjoy doing this kind of thinking in my spare time and look forward to the times when I can present these ideas as fully tested solutions at the point we need them.</p><h4>Don’t accept solutions without defined problems</h4><p>A number of people in the company with a decent amount of product experience, like to jump straight to solutioning without fully understanding the problem from the user’s perspective.</p><p>At first I wasn’t confident enough to challenge this and often ended up delivering what they had asked for. Once I noticed I was doing this, I called myself out on it.</p><p>So now when someone comes to me with a solution, I take the time to backtrack and fully understand the problem we are trying to solve.</p><p>Sometimes I come up with the same solution, but more often than not, I come up with a different solution that is easy to implement and a better user experience. AKA my job.</p><h4>Fight Design’s Corner</h4><p>As I mentioned, design doesn’t yet play a major role in our company. So I learned to compromise early and not fight too hard for the design.</p><p>This was an awful position to adopt. Now I always speak up for design and the integrity of the user experience. If I don’t who will? I am still learning to do this, but it was a much needed switch in the right direction.</p><p>With tight deadlines and limited resource, it can be an uphill battle. But I have seen how it snowballs out of control if it’s not done. To the point where we’re delivering things that I’m not proud of.</p><p>Thanks for reading,</p><p>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35cd6254abc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know How to Conduct Stakeholder Interviews]]></title>
            <link>https://medium.com/@alexpour/i-dont-know-how-to-conduct-stakeholder-interviews-a748609946dc?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a748609946dc</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Mon, 27 Aug 2018 17:45:03 GMT</pubDate>
            <atom:updated>2018-09-10T19:39:35.651Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K2OH4K5ZkXp50iL2_xpgfw.jpeg" /></figure><p>When I started my job I didn’t even know what a stakeholder interview was, let alone how to conduct one. But looking back, I did unknowingly (and inefficiently) conduct plenty of stakeholder interviews out of necessity.</p><p>Once I realised how important this step of the discovery process was, I started to research how to improve the way in which I executed it. Below I have put together a brief overview of how I now conduct stakeholder interviews.</p><h3>What are stakeholder interviews?</h3><p>Let’s start with who Stakeholders are. A Stakeholder is anyone who has a stake in the success of your solution. For me it’s usually the business, the Dev team, Operations, CS or sometimes Marketing.</p><p>Because stakeholders largely define the success of a solution, it is important to work with them to clearly define the goals of the project as well as what success looks like. I also use this process to reveal hidden assumptions and getting insight into the business goals, user needs and technical constraints.</p><h4>Business Goals</h4><p>What the business wants to achieve in a specific time period and what they define as success.</p><h4>User Needs</h4><p>What the current beliefs are about the user and any data to back it up. (Any assumptions are noted down as hypothesise to validate.)</p><h4>Technical Constraints</h4><p>What the limitations are based on time, money or technology. This usually come from the dev team and or PM.</p><h3>Ask questions ahead of time</h3><p>When I book in a meeting with a stakeholder, I also send through an overview of the interview questions. This gives the Stakeholder a chance to think about their answers and also gather data to back up their points.</p><p>Helping to gets the most out of the interview, as the stakeholder isn’t caught off guard by probing questions and can put forward a well thought out case.</p><h3>Define Goals</h3><p>Firstly, I make sure we are on the same page and understand what we are trying to achieve. I find that clarify and confirming what seem like obvious questions, often highlights differences in understanding and unspecified requirements.</p><p>Next I work on defining what success looks like to the stakeholder. I make sure to keep them updated with what success looks like if my exploration shows that a different outcome would be better suited. I take it upon myself to make sure they are up to on what we are aiming towards.</p><h3>Insight</h3><p>I gather insight into the problem we are trying to solve as well as the users you are trying to solve it for. The person I am interviewing often has unique insight into this specific area that I may only have a high level view of.</p><p>The stakeholder can also offer insight into what will make a solution successful or what is technically possible.</p><h3>ASS-U-ME</h3><p>It is important not to assume what the stakeholder is trying to say. Just as it is important not to ask leading questions. Having to repeat a question or sit in silence for a while as they think of an answer is far better than misunderstanding what they mean.</p><p>Something I used to do frequently, was finish other people’s sentences once I thought I knew what they were going to say. I think I probably did it as a way of confirming to them that we were on the same page. As well as trying to move the conversation along.</p><p>More often than not, I’d be giving them an answer without letting them come to their own. Since realising this, I have learned to stay quiet and listen. Then repeat back what I have understood them to mean.</p><h3>Don’t solution</h3><p>During the interview, I focus on gathering requirements and highlighting issues. Very often they will want to skip right ahead to what solution they think will solve their problem.</p><p>I always try to steer the conversation away from specific solutions and more towards what they want to achieve and what success looks like. Until I define the problem and back it up with data, there’s no point in thinking about a solution.</p><h3>List of issues</h3><p>I note down a detailed list of issues the stakeholder raises and get them to prioritise them, based on which issue they would most like to solve.</p><p>When the Stakeholder talks about a problem they want to solve, I always ask for data to back up that this is indeed an issue. Rather than just a hypothesis or a result of another issue.</p><p>This also helps me measure the effectiveness of my solutions as I can compare data from before and after the solution was implemented. Showing whether the solution has achieved the desired result.</p><p>It’s also helpful to find out the current state and the desired state and the value that the difference makes, now and over time. This lets me think about what the cost of the problem might be and can help prioritise the solution.</p><h3>Is this a valuable use of time?</h3><p>Sometimes it’s good to challenge the stakeholder on whether this is a valuable use of time and resource. The cost of not solving the problem might cost less than investing in solving the problem.</p><h3>Share your notes with PMs and Stakeholders</h3><p>Once I have written up my notes from the interviews, I put together a summary and email it to the stakeholders and the Product Manager. This gives everyone a chance to correct me on things I have misunderstood or left out.</p><p>I also update the document over the course of the project, keeping everyone up to date with any changes. This ensures that when requirements or definitions of success change, everyone is aware and know what to expect at the sprint review.</p><p><em>Thanks for listening,<br>Alex</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a748609946dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know How to Make Time for Personal Projects]]></title>
            <link>https://medium.com/@alexpour/making-time-for-personal-projects-edad1b418791?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/edad1b418791</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[side-project]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 08:26:27 GMT</pubDate>
            <atom:updated>2018-09-10T19:40:17.773Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NB0gT6H4bzWiFoHCjRtLxw.jpeg" /></figure><p>My career as a Product Designer started out by working on a number of side projects. I would wake up early (like 4am early), go to a cafe to do a couple hours of work before heading to my job. Then come home and work some more until around 10/11pm.</p><p>Now that I work full-time as a Product Designer, with a 1.5 hour commute each way, I find it increasingly difficult to make time to work on any side projects. So I have created a list of a couple of tips that help me make time to work on my side project.</p><h3><strong>Side Projects</strong></h3><p>Firstly, a side project shouldn’t be additional work for the sake of it. It should be something you are passionate about. Something you can learn and try new things doing, that you can’t or don’t have time to do in your day job.</p><p><a href="https://tinytracker.co/">My current side project</a> started as a problem that we wanted to solve. Once we started, it turned into something that we loved working on and couldn’t wait to use at our own companies.</p><h3><strong>Differentiate between relaxation and work</strong></h3><p>I make sure to distinguish between working on my side project and relaxing. There is no multitasking. Putting YouTube on in the background and trying to do some work doesn’t work. Trust me!</p><p>As well as making a distinction between my time, I try to distinguish between environments. If I relax and work in the same place, the lines between productivity and procrastination quickly become blurred. Associating a place or room with work, means that if I’m in that space, I am working and nothing else.</p><h3>Have a schedule</h3><blockquote>It’s easier to make time than it is to find time.</blockquote><p>Creating a schedule around working on my project allows me to still have time to relax and unwind without feeling like I’m ignoring work that needs to be done.</p><p>When creating a schedule I try to be realistic and set aside enough time to relax and sleep. Setting aside 3 hours for work each day would end up burning me out and putting me off working on my project entirely.</p><p>Setting my phone to do not disturb and putting headphones in helps me make the most of my allotted time. That being said, if I’m setting aside a couple hours to work, I make sure to take frequent breaks.</p><h3><strong>Accountability</strong></h3><p>Working with someone has a number of benefits, most notably making it easier and more enjoyable.</p><p>It also creates accountability, making it harder to convince myself that I’ll do the work later or twice as much the next day. Having someone who is relying on me to do my part, helps to motivate me to sit down and do the work I need to do.</p><h3><strong>Create a To-Do list</strong></h3><p>Having a list of things that need to be done, means I’m never in a position where I don’t know what to do next.</p><p>Similarly, splitting tasks into smaller tasks, means that I can do as little or as much as I want. Without being daunted by huge tasks or feeling like I’m leaving something unfinished.</p><p>I spend the last 15 minutes of each session planning out the first tasks of my next session. This helps me know exactly what I’ll be starting on as soon as I get home.</p><p>Tackling a small task that requires little cognitive exertion, is a great way to start off a work session. It allows me to get something checked off the to-do list without spending too much effort. It also helps me get into work mode, without being put off by the amount that I have to do.</p><h3><strong>Set low expectations for yourself</strong></h3><p>Setting low expectations for yourself sounds like a bad idea. But in practice, it’s the key to working consistently. Telling myself that I need to do a certain amount of work usually ends in achieving lots, but still feeling like I’ve fallen short.</p><p>Going into a session wanting to achieve one small thing and seeing where I end up, makes me feel more productive as I always end up doing more than I set out to do.</p><p>Things often come up and cut my work sessions short. Achieving what I set out to do in the first 30 minutes, means that I can cut my session short without feeling guilty or like I’m neglecting work that needs to be done.</p><h3><strong>Create a habit</strong></h3><p>Creating a habit to work on my side project is probably the most valuable tip. Once it becomes a habit, I don’t have to use any tricks to get myself started. It’s just what I do at that time, on those days.</p><blockquote>When creating a habit, start small and prioritise consistency over output.</blockquote><p>When I say start small I mean it. The first couple of days I scheduled 15–30 minutes to sit at my desk and think about my project. I was creating the habit that at this time, on this day, I am focussed on my project.</p><p>Starting out by setting myself 3 hour sessions to complete a tonne of work, quickly burnt me out and left me feeling unmotivated and stressed.</p><h3>Conclusion</h3><p>Working on a side project should be fun and enjoyable. It shouldn’t be added stress or guilt, that you’re not getting things done.</p><p>Creating a consistent habit and schedule with a mixture or work and relaxation, will get you a lot further than going all out.</p><p>Thanks for reading,</p><p>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edad1b418791" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know How to Manage Designing Multiple Products]]></title>
            <link>https://medium.com/@alexpour/how-to-manage-designing-for-multiple-products-44dc39d78211?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/44dc39d78211</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 07:14:21 GMT</pubDate>
            <atom:updated>2018-09-10T19:40:51.775Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zM4iQKSm6ZrG75AfHlWIDA.jpeg" /></figure><p>Being the only designer in a multi-product company gets overwhelming at times. Especially when you have multiple Product Managers trying to make sure their thing gets done over everything else on your plate.</p><p>Initially I was completely frozen by the sheer number of things to do. I would end up switching back and forth between tasks, trying to make sure I was making equal progress across them.</p><p>Very quickly I realised that what I was doing, wasn’t working. So, as I normally do when I have a problem, I turned to my friends and the internet. I have put together a list of a few things that have helped me manage the design of multiple products at the same time.</p><h3><strong>Prioritise</strong></h3><p>Numero uno, is to prioritise. When I have multiple deadlines it can be hard to focus on one thing. Just as easily, I can end up focusing on the wrong thing. So it’s important to figure out what the most important tasks are.</p><p>I now engage all of the Product Managers in a dialogue. Challenge them on the deliverables and deadlines they have set. Work out what will happen if I don’t deliver on certain tasks, or whether they really need high fidelity screens at this stage.</p><p>I’m also selective about which meetings I attend. Far too often I would will find myself in an hour long meeting that I really didn’t need to be in. Now I take my laptop into meetings so I can work if I’m not involved in the current discussion. I also leave meetings if I know that there is no reason to be in them.</p><p>Finally, I have started attending weekly, meetings biweekly. If I miss anything important, it’s usually brought to my attention. Most things are discussed in the next meeting to some extent anyway.</p><h3><strong>Time management</strong></h3><p>I often felt like I was neglecting one task by working on another. This resulted in me switching back and forth between the two and not committing to either.</p><p>So I’ve started to section time to work on a specific task, there is no multitasking. I’ll book a 2 hour slot in my calendar to work on one specific task. No interruptions, no meetings, no multitasking.</p><p><strong>Do not disturb</strong>. I can’t tell you how often I used to get tapped on the shoulder and taken right out of the problem I was working on. When you have multiple Product Managers coming and talking to you, this very quickly becomes a problem. Putting headphones in and or finding a quiet place in the office usually solves this problem.</p><h3><strong>Push back</strong></h3><p>I find it difficult to stop myself from jumping in to solution mode when someone comes to me with a problem. I like to be helpful and it often resulted in me becoming overwhelmed and working weekends. But it’s important not to take on too much.</p><p>Now when people come to me with a request I put it on my todo list. This assures them that I have heard them and will get around to doing it as soon as I can. It also tells them roughly how much is on my plate and gives them the opportunity to try and prioritise it above other items on the list.</p><h3><strong>Create a buffer</strong></h3><p>Other things come up, they always do. So I try to create time for the unexpected. Whether it’s an urgent task from the CEO or an unexpected sick period. If I’m already stretched too thin, I’ll have nothing extra to give.</p><p>This doesn’t mean that I accomplishing less. If nothing comes up, I just carry on and deliver a bit earlier that anticipated. It’s far better than not delivering on time.</p><h3><strong>Leave on time</strong></h3><p>I used to work an extra hour or two every day, trying to cram in every bit of productivity that I could. I would end up neglecting the gym and often eating not so healthy lunches at my desk.</p><p>This left me feeling burnt out in the evenings and on weekends. I would end up spending my entire weekends recuperating and before I knew it, I was back at work on Monday.</p><p>Now I schedule what time I leave the office in my calendar. Unless something urgent comes up, I leave at that time. This sometimes means I have to reschedule a meeting for the following day, or responding to an email first thing the next morning.</p><h3>Summary</h3><p>Before I learnt these things, I was stressed and never had time to relax. Everything felt last minute and rushed. Since learning these few things, I have been able to manage multiple products much more efficiently.</p><p>It has also given me more time to work on my own projects, in and out of work. For instance, writing. I am not good at writing, but now I make time for it. Nothing interrupts it and I don’t feel like it’s time spent away from anything else I ‘should’ be doing.</p><p>Thanks for reading,<br>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44dc39d78211" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know the Difference Between a Product Designer and a UX/UI Designer]]></title>
            <link>https://medium.com/@alexpour/when-i-tell-people-im-a-product-designer-i-get-confused-faces-people-either-think-the-term-refers-eda90ba216c0?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/eda90ba216c0</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Mon, 30 Jul 2018 06:06:30 GMT</pubDate>
            <atom:updated>2018-09-10T19:41:25.789Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpvKv5LxolZg08uRnA5xYg.jpeg" /></figure><p>When I tell people I’m a Product Designer I’m often met with confused faces. People either think the term refers solely to someone who designs physical products, or they think it’s just a fancy term for a UX/UI Designer.</p><p>In those situations I struggle to explain exactly what it is that differentiates a Product Designer from a UX/UI Design. So I’ve put together a little overview to explain what I understand the difference to be.</p><h3>What is a product Designer?</h3><p>A Product Designer is similar to a Product Manager. However, they focus more on the user’s needs as well as the value and experience that the user gets from the product. They understand the objectives and constraints of the business and design around them.</p><blockquote>What do our users want to solve and how can we help them solve it?</blockquote><h4>Responsibilities</h4><ul><li>Discover and define our user’s problems</li><li>Come up with solutions</li><li>Oversee the design of the entire product</li><li>Know where they want the product to be in 6 months</li><li>Demonstrate UX values visually</li></ul><h3>What is a UX Designer?</h3><p>A UX Designer is responsible for improving the usability and accessibility of a product to create an enjoyable experience for the user. They conduct user research and user tests in order to highlight and solve problems that the user may face when interacting with the product.</p><blockquote>What problems might the user face when trying to solve their problem using our solution?</blockquote><h4>Responsibilities</h4><ul><li>Concerned with the feel of the product</li><li>Highlight and solve potential user problems</li><li>Validating hypotheses through testing</li><li>User research</li><li>Personas</li><li>Scenarios &amp; Storyboards</li><li>Flowcharts</li><li>Wireframing</li><li>Prototyping</li><li>User Testing</li></ul><h3>What is a UI Designer?</h3><p>A UI Designer thinks about the elements that make up the graphical interface (buttons, typography, navigation, icons etc.) and how the user interacts with them. Making the interface as intuitive, efficient and easy to use as possible.</p><blockquote>How can we make our solution easy and enjoyable to use?</blockquote><h4>Responsibilities</h4><ul><li>Concerned with the look of the product</li><li>Represent the UXer’s finding in their designs</li><li>Ensure the user can see what they need to</li><li>Design elements such as buttons etc.</li><li>Maintain high discoverability</li><li>Simplicity</li><li>Layout and Hierarchy</li><li>Minimise actions</li><li>Grouping relevant information and controls</li><li>System feedback loading etc.</li><li>Reducing cognitive load (field masks)</li><li>Consistent and reusable patterns/behaviour</li><li>Brand consistency</li></ul><h3>Summary</h3><p>This is of course a very simplified way of looking at it. There will always be overlap between to three roles and different companies will have different ideas and expectations of what each role should do.</p><p>This was put together to help me explain the difference to friends and colleagues and is my opinion and understanding of the topic.</p><p>Thanks for reading,<br>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eda90ba216c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know What UX Writing is]]></title>
            <link>https://medium.com/@alexpour/ux-writing-b740176f51af?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b740176f51af</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-writer]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Sun, 22 Jul 2018 20:45:36 GMT</pubDate>
            <atom:updated>2018-09-10T19:41:49.686Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5IMcR-LE6ETfXpZ12QVfA.jpeg" /></figure><p>I could take a guess as to what exactly a UX Writer does, but I don’t actually know. I have been seeing the term ‘UX Writer’ pop up more frequently and every company seems to be hiring them at the moment. So I’ve decided to do a little digging to find out what exactly the role does.</p><p>From my research I understand that the role of a UX Writer is to:</p><blockquote>write copy in a way that tells the user exactly what they need to know, while taking into account the their needs and emotions, as well as the company’s tone of voice.</blockquote><h3>Writing for the user</h3><p>One of my goals when joining my company, was to remove as much of the stress, uncertainty and confusion from our user’s experience as possible. Being that we are a fintech company and our users usually come to us in financial distress, the last thing I wanted was for our product to add to that stress or make our users feel confused or worried.</p><p>Prior to my joining the copy had been written by a number of people. There was no real consideration for the user’s needs, emotional state or knowledge about finances. Copy was often an afterthought once things had been designed and there was no consistency in the way we spoke to our users.</p><p>Some places the copy was jokey and bloated, adding frustration to already annoying sections of the product, like an error message on the password reset journey. Other times it was overly formal and technical, to the point where we were basically explaining what goes on in the back end.</p><p>Being fairly new to the company, I wasn’t sure what the company’s tone of voice was. There was nothing definitive written down and depending on who you asked, you would received a different answer.</p><h3>Tone of Voice</h3><blockquote>Every brand has a voice (what they say) and a tone of voice (how they say it). While a company’s voice should remain consistent throughout, the tone of that voice should take into account the user’s emotional state as well as the context in which the user reads it.</blockquote><p>I booked a meeting with the product team in order to define what the company’s tone of voice actually was. Unsurprisingly, going into that meeting, we all had different ideas of what it should be. However, by the end of the meeting we were very much in agreement.</p><p>Once I had the tone of voice, which was basically a list of words with an agreed priority of which were most important, I turned it into a guideline. I added descriptions to each word explaining what it meant in practice, making it tangible rather than just a fluffy word that had no real application.</p><h3>Testing</h3><p>Initially the guidelines had to be tested, myself and one of the previous copy writers tested variants of the the same messages with a number of users. He wrote from his head, thinking about how best to phrase the sentence, I wrote using the guidelines I had created.</p><p>The results were mixed, some places his copy prevailed, others mine was preferred and in some instances we learned things that neither of us had thought about. Everything we learned was and continues to be fed back into the guidelines.</p><p>And that’s the point – without starting, you have nothing to build on. I never thought I was writing the definitive guide on how to talk to our users. I just wanted to create a foundation on which to build.</p><h3>Summary</h3><p>Overall, spending time on copy during prototyping now means that user testing is more reliable, as thinking about copy early on means that the interface itself didn’t have to do all the heavy lifting of the products usability.</p><p>It also means that we have a consistent way of speaking to our users which is beneficial for 2 reasons. One, it helps us write quickly and 2, it means that the user recognised us through the way that we speak to them, meaning that a serious message comes across as serious right from the offset.</p><p>The guidelines that I created were also transferred to the marketing team, meaning that the users are spoken to right from first contact, through to the last, in a consistent manner that aligns with our company’s tone of voice and goals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b740176f51af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Don’t Know How to Write a Blog]]></title>
            <link>https://medium.com/@alexpour/my-first-blog-post-bb0c8e0ee702?source=rss-a87f84d2952a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb0c8e0ee702</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Alex Pour]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 20:08:46 GMT</pubDate>
            <atom:updated>2018-09-10T19:48:53.605Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*pkEDcYuaCpVgSZEenJnO2Q.jpeg" /></figure><p>Hi, my name is Alex, I’m a <a href="http://www.alexpour.com/">Product Designer</a>, <a href="http://www.tinytracker.co/">Co-Founder</a> and now blogger. I’m about to turn 27 and around this time I like to think about the things I want to achieve over the next year. One thing that I have wanted to do for a long time but have been putting off, is to write a blog.</p><p>I like writing and really want to get better at it, but until very recently I had always told myself that I had nothing of any value to add; there’s always someone who knows more and or could do a better job of explaining the things I have to talk about.</p><p>However, while thinking about this idea of writing a blog, I had a thought that entirely changed my perspective:</p><blockquote>The value that you add through what you say and do is, at the very least, your unique perspective based on your personal experiences.</blockquote><p>With this new outlook, I feel like writing a blog post each week is a more than achievable goal. Especially as I have an hour and a half commute to and from work, in which to write it.</p><p>So, I am committing to writing at least one blog posts each week over the next year. I will be mainly be writing about Product Design but I might add in the occasional post talking about this journey and things I learn along the way. I hope you’ll join me on this journey.</p><p>Thanks,<br>Alex</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb0c8e0ee702" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>