<?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 Anastasia Melnichenko on Medium]]></title>
        <description><![CDATA[Stories by Anastasia Melnichenko on Medium]]></description>
        <link>https://medium.com/@magenpie?source=rss-ee8c89ae1451------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PEVt_xjSwilY-e66NLKEag.jpeg</url>
            <title>Stories by Anastasia Melnichenko on Medium</title>
            <link>https://medium.com/@magenpie?source=rss-ee8c89ae1451------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:28:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@magenpie/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[What it was like to start as a product designer at Alan]]></title>
            <link>https://medium.com/alan/what-it-was-like-to-start-as-a-product-designer-at-alan-e8dea8c11900?source=rss-ee8c89ae1451------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8dea8c11900</guid>
            <category><![CDATA[design-methodology]]></category>
            <category><![CDATA[new-job]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design-skills]]></category>
            <dc:creator><![CDATA[Anastasia Melnichenko]]></dc:creator>
            <pubDate>Sat, 17 Oct 2020 08:57:36 GMT</pubDate>
            <atom:updated>2020-10-17T08:57:36.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*llM0gMX5p-y4B-SO" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Half a year ago I joined Alan as a product designer, and it’s been a very exciting time full of new learnings. But it was also quite bewildering since <em>everything was so completely different</em> from what I was used to!</p><p>I was coming from a startup about the same size and age as Alan where the way of working was pretty classic. My days consisted of a few meetings: stand-ups, team syncs, presentations and design reviews. Between these meetings, I would do actual design work: sketching, producing wireframes and prototypes, and polishing the final UI.</p><h4><strong>Back to school?</strong></h4><p>My first days at Alan looked nothing like that. My calendar was empty and I spent my entire day at my desk in the library-quiet office. My primary activities were now reading and writing (spoken discussions that would normally happen in a meeting were now replaced by written ones). It is more tiring than listening and speaking, and it makes you retain more information. By the end of the first few days, my head felt heavy with all the new knowledge, and I felt exhausted. It felt like I was working on my university thesis again.</p><h4><strong>Am I still a designer?</strong></h4><p>I wasn’t producing anything other than written discussions I was leading or participating in. This felt strange, I saw my role as a designer in producing visual solutions to problems that were normally defined by a product manager. Now I was doing the problem definition part myself. Ultimately this overhauled my understanding of what it meant to be a designer, and the way I worked. Design is often referred to as problem solving. But in fact it starts much earlier — with identifying and shaping the problem that needs to be solved. I no longer took over problems shaped by someone else without agreeing or fully understanding them — I did it myself, and it informed and enhanced my work greatly.</p><h4><strong>Going beyond design skills</strong></h4><p>Having the scope of my responsibilities expanded beyond visual problem solving to owning a project from an early stage put me out of my comfort zone at first. Adapting to my new role brought a lot of things into play. It made me exercise skills I have as a designer but didn’t get to use very often before: , like analytical thinking, decision making and risk taking, prioritising and saying no. The last one taught me a lot, making me realise that what you decide not to do can be as important as what you do. Keeping things lean and mean isn’t easy, but having a first-hand understanding of the problem means you no longer design solutions “just in case”. For me it meant that when I did get to producing a final solution, I no longer spent hours to achieve something workable — it often offered itself naturally.</p><p>This approach allowed me to take on projects I’d never dare work on due to their complexity — from working on invoicing and payment management to data visualisation.</p><h4><strong>Writing helps design</strong></h4><p>Another newly introduced aspect of my job was writing. It’s certainly not something I got to do a lot before. At first it was tough — normally the visual part of my work would be the centre of attention. All the “homework” leading up to it didn’t matter much so I wasn’t used to documenting it. With writing though, all the work I was used to doing behind the scenes — the analysing, reasoning and decision making that went into designing, became visible. Discussing a design proposal with others, getting them to comment on and challenge it became so much easier. All the feedback was centralised, meaning I no longer had to have the same discussion with various stakeholders at different times.<strong> </strong><em>Ultimately the part of my job that was previously invisible became central to everything.</em></p><h4><strong>Growing as a designer helped me grow as a person</strong></h4><p>All of the professional learnings rubbed off on me as a person too.</p><p>Being in an environment where I am entrusted to own a project and make the right decisions taught me to trust myself more. As a result, I am much less of a procrastinator as I am not held back by doubt and I understand that I don’t need all the answers to act. Learning to manage a large volume of work and address complex projects taught me to prioritise better. I no longer spread myself thin because I know how to choose where and when to invest my time and attention. As with designing, I stopped doing things “just in case”.</p><p>Switching to the written way of working put me in charge of organising my day, and allowed me to understand my productivity patterns better. My meeting-free calendar (meetings are replaced by written discussions) allowed me to figure out how to manage my time in the best way possible, when to go into an uninterrupted, focused productivity mode, and when to take it easy — do some reading or clean my Figma files for instance. It also taught me to know my limits, draw boundaries, and know when to disconnect and recharge.</p><p>Overall, the past 6 months haven’t all been easy — learning never is — but in the end, I’m a little faster to react, a little sharper in my judgments, a little more calm and deliberate, and a lot more excited for more things to come!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8dea8c11900" width="1" height="1" alt=""><hr><p><a href="https://medium.com/alan/what-it-was-like-to-start-as-a-product-designer-at-alan-e8dea8c11900">What it was like to start as a product designer at Alan</a> was originally published in <a href="https://medium.com/alan">Alan Product and Technical Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>