<?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 Josephine Palberg on Medium]]></title>
        <description><![CDATA[Stories by Josephine Palberg on Medium]]></description>
        <link>https://medium.com/@josephine.keil?source=rss-50a967e2a070------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uUmUAKEuii5z_X5ikQMfhg.png</url>
            <title>Stories by Josephine Palberg on Medium</title>
            <link>https://medium.com/@josephine.keil?source=rss-50a967e2a070------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:53:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@josephine.keil/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[No Time? No Problem. Just…]]></title>
            <link>https://medium.com/@josephine.keil/no-time-no-problem-just-45537c749783?source=rss-50a967e2a070------2</link>
            <guid isPermaLink="false">https://medium.com/p/45537c749783</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lovable]]></category>
            <category><![CDATA[product-vision]]></category>
            <category><![CDATA[efficiency]]></category>
            <dc:creator><![CDATA[Josephine Palberg]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 13:15:17 GMT</pubDate>
            <atom:updated>2025-11-13T12:56:09.070Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tcUaClSJGe2Z1kEBD8NHPQ.png" /><figcaption>source: <a href="https://lovable.dev/brand">https://lovable.dev/brand</a></figcaption></figure><p>As a Product Manager with a UX background, I love turning early-stage ideas into something tangible. I’m comfortable creating wireframes, mapping user journeys, and building quick, interactive prototypes to validate assumptions in user interviews.</p><p>But as powerful as that skill set is, it comes with one major drawback: <strong>time</strong>. Depending on complexity, building a testable prototype sometimes costs me a full workday, often even more. And with a calendar full of roadmap discussions, alignment calls, and stakeholder updates, I mostly end up asking myself:<br> <em>Is this idea worth all the effort?</em></p><p>Then I tried <a href="https://lovable.dev/"><strong>Lovable</strong></a> and everything changed.<br>Suddenly, I could go from idea to clickable prototype in minutes. Usable flows. Shareable concepts. Testable results.<br>Here are three ways Lovable already made a difference in my work:</p><h3>1. Validating hypotheses without losing momentum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkqJwAMbXAgqgYjWKz9HrQ.png" /><figcaption>Screenshot taken from Lovable.dev</figcaption></figure><p>At <a href="https://www.linkedin.com/company/staffomatic/posts/?feedView=all">Staffomatic</a>, we spent the past weeks analysing a key funnel. After mapping pain points, interview insights and funnel data, we had a list of hypotheses to test.<br>But building a prototype for even one of them? Hours I didn’t have.</p><p>So I tried something new: I wrote a short prompt with context, added UI references and style guide files and let Lovable do the work.<br><strong>Two minutes later, I had a working prototype.</strong> Not perfect, but testable.</p><p>Same day, we ran a user session. The feedback was clear and constructive, even though the design wasn’t fully on-brand.</p><blockquote><strong><em>What I learned:</em></strong><em> Quick prototypes lower the barrier to testing ideas. And that makes product discovery more lightweight, faster, and ultimately more focused and impactful</em>.</blockquote><h3>2. Bringing people into product conversations, even without product roles</h3><p>Inspired by a <a href="https://www.linkedin.com/posts/nickeyskarstad_build-with-ai-pm-prototyping-workshop-activity-7344008715647270912-_Ccy?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAABwX2wIBo-NREiy9_wVR9HX2ppLpNQbN8K4">post from Duolingo’s Product Director Nickey Skarstad</a>, I ran a <strong>Lovable mini-workshop</strong> at our company-wide AI session.<br>Anyone, Sales, Support, Devs, even our founders could join.</p><p>I prepped a FigJam board with:</p><ul><li>Upload instructions for design files and UI references</li><li>Four real hypotheses from our previous funnel analysis</li><li>Simple tips on working with Lovable’s free version</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17AHSkuu-OIS9_LE1tlTuw.png" /><figcaption>Template for our Lovable mini workshop, created with Figjam</figcaption></figure><p>After a brief intro, people formed small teams and picked a hypothesis-idea to prototype. They had <strong>15 minutes to create</strong> and <strong>10 minutes to present </strong>their results. And yes we ran out of time. But what we saw was honestly impressive: <strong>four truly inspiring prototypes</strong> that amazed everyone in the room. All participants were impressed by the results and clearly had a lot of fun creating them.</p><p>One prototype, built by a Sales colleague and our CEO, really stood out.<br>What impressed us most wasn’t the visual polish it was the <strong>depth of the concept</strong>. Neither of them had any design experience, but they brought in <strong>a ton of sales expertise that sparked ideas</strong> we are excited to take further.</p><blockquote><strong><em>What I learned:</em></strong><em> When people outside the product team can turn their ideas into something visual, it unlocks new perspectives and much better conversations.</em></blockquote><h3>3. Making our product vision more tangible</h3><p>We have a new product vision, since the beginning of the year. And we repeat it every Monday during our weekly kickoff but I started wondering:<br> <em>Does everyone picture the same thing?</em></p><p>A quick survey showed mixed responses, some had a clear picture, others none at all. So I mapped the current vs. a future product state and identified key features to bring the vision to life.</p><p>That’s where Lovable came in again. I initially tried putting every idea into one big prototype, but quickly realised that was way too chaotic. So I broke it down into smaller flows, each focusing on one aspect of the vision.</p><p>In one afternoon (roughly 4 working hours), I built <strong>9 simple prototypes, </strong>each zooming in on one idea we might want to explore further.<br>They weren’t perfect, but they gave shape to what our vision could look like and helped me learn whether others saw it the same way, or had ideas to take it even to the next level.</p><blockquote><strong><em>What I learned:</em></strong><em> A shared vision gets stronger when people can actually see it. And Lovable helps turn abstract ideas into something we can point to and talk about.</em></blockquote><h3>Final Thoughts</h3><p>I don’t see Lovable as a replacement for designers or developers, but as a powerful tool to speed up exploration, foster clarity, and spark better conversations across teams and disciplines.</p><p>It’s especially useful when you:</p><ul><li>Need to <strong>test fast</strong>, but can’t build</li><li>Want to <strong>align your team</strong>, but don’t have time for polished decks</li><li>Are looking to <strong>make your vision tangible</strong>, but don’t want to start build everything manually.</li></ul><p><strong>I spent 22€ on a one-month Pro account and got:</strong></p><ul><li>9 prototypes for our product vision</li><li>4 cross-functional team prototypes</li><li>more feedback than I ever expected in just a few days<br> and I still have 20 credits left for the rest of the month</li></ul><p>Most importantly, I saved time and opened the door for others to contribute visually in a way they hadn’t before.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45537c749783" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we show (and miss) Appreciation at Work]]></title>
            <link>https://medium.com/@josephine.keil/how-we-show-and-miss-appreciation-at-work-1fdbb37319d7?source=rss-50a967e2a070------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fdbb37319d7</guid>
            <category><![CDATA[love-language]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[recognition]]></category>
            <category><![CDATA[appreciation]]></category>
            <category><![CDATA[positive-thinking]]></category>
            <dc:creator><![CDATA[Josephine Palberg]]></dc:creator>
            <pubDate>Mon, 10 Feb 2025 08:07:19 GMT</pubDate>
            <atom:updated>2025-11-13T13:19:52.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-oxKRnUamZJFqXH3_LXDRQ.jpeg" /><figcaption><a href="https://www.freepik.com/">Designed by Freepik</a> | Creator: <a href="https://de.freepik.com/autor/wayhomestudio">wayhomestudio</a></figcaption></figure><p>We often talk about appreciation at work, but do we truly understand how it is perceived by our colleagues? Inspired by the concept of the five love languages, I recently gave a workshop on how these communication styles can be applied in the workplace. Through an interactive survey and discussion, we explored how different forms of appreciation resonate with individuals and how we can use this knowledge to foster a more positive work culture.</p><h3>Survey Results: A Shift in Perception</h3><p>Before revealing the topic of my workshop, the majority of participants responded that they had either not experienced any appreciation at work over the past 3 days or had noticed it only once or twice. However, after the workshop and exploring different ways in which appreciation manifests, responses shifted. While some still felt unappreciated, most participants now identified moments of recognition they had initially overlooked. Many moved their responses up to “3–5 times” or even “more than 5 times.”</p><p>This shift highlights an important insight: <strong>Appreciation isn’t always about grand gestures.</strong> Often, <strong>it happens in subtle ways, </strong>through a quick thank-you message, a colleague stepping in to help, or simply being invited into a discussion. The key takeaway? Appreciation is more common than we think, but we may not always recognize it in the form we expect.</p><p>It’s important to note that this survey was conducted with a small group (10 participants), meaning the results are not representative but rather offer a small sample of individual experiences and perceptions.</p><h3>The Origin and Application of Love Languages</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*7sMc-4wO-8xgS08bYan1wQ.png" /><figcaption>By Nicole Marino | Source: <a href="https://www.fochtfamilypractice.com/blog/2023/2/1/love-languages-a-give-and-take-with-couples">https://www.fochtfamilypractice.com/blog/2023/2/1/love-languages-a-give-and-take-with-couples</a></figcaption></figure><p>The concept of Love Languages was first introduced by Dr. Gary Chapman in his book <a href="https://www.amazon.de/Five-Love-Languages-Chapman-Gary/dp/8179928268"><strong><em>The Five Love Languages</em></strong></a>. Originally developed to help couples improve their relationships by understanding how they and their partners express and receive love, the framework has since been applied to various interpersonal contexts, including friendships, families, and, the workplace. The five Love Languages: Words of Affirmation, Acts of Service, Receiving Gifts, Quality Time, and Physical Touch — can serve as a useful tool to better understand and express appreciation in professional settings.</p><p>The application of these concepts in professional settings has been extensively explored in <a href="https://www.appreciationatwork.com/5-languages-appreciation-workplace-improve-employee-engagement/"><strong><em>The 5 Languages of Appreciation in the Workplace</em></strong></a> by Dr. Paul White and Dr. Gary Chapman. Their work highlights how different forms of appreciation impact workplace relationships and team dynamics. Dr. White’s company, <em>Appreciation at Work</em>, provides research-based tools and resources to help organizations build positive workplace cultures through meaningful recognition. For more insights, visit <a href="http://www.appreciationatwork.com/">www.appreciationatwork.com</a>.</p><p>If you’re curious to discover your own Love Language, there are several providers offering free tests. However, most of them require payment to unlock the full results. If you’d rather avoid that, you can use this <a href="https://nbcgutah.com/wp-content/uploads/2017/09/5.LoveLanguageTest.pdf">free self-assessment PDF</a>, which takes only a few moments longer to evaluate your results.</p><h3>Reinterpreting Love Languages in a Work Context</h3><p>In my workshop, we explored how the five love languages can be adapted to the workplace. The following examples are based on our discussions, participant insights, and my own observations in a professional setting.</p><p><strong>Words of Affirmation</strong></p><ul><li>Public or private verbal recognition</li><li>Written messages (emails, Slack, or personal notes)</li><li>Emojis and positive reactions in meetings</li><li>Simple greetings or check-ins to acknowledge others’ presence</li></ul><p><em>Example: A manager taking a moment in a team meeting to highlight a colleague’s great work on a project.</em></p><p><strong>Acts of Service</strong></p><ul><li>Offering support with tasks</li><li>Taking over responsibilities when needed</li><li>Small helpful actions (e.g., “Can I grab you a coffee?” or emptying the office dishwasher)</li><li>Active participation in meetings and being engaged</li></ul><p><em>Example: A team member voluntarily covering for a colleague who is overwhelmed with deadlines.</em></p><p><strong>Receiving Gifts</strong></p><p>This category sparked an interesting debate about salary. Some participants argued that salary should not be classified as appreciation since it is contractually agreed upon, while bonuses were seen as a form of appreciation under “gifts.”</p><ul><li>Bonuses or performance-based rewards</li><li>Surprise treats, team lunches, or small thoughtful gestures</li><li>A well-designed and comfortable workspace</li><li>Extra time off as recognition</li></ul><p><em>Example: A team lead bringing in coffee for the team after a tough week to show appreciation for their effort.</em></p><p><strong>Quality Time</strong></p><ul><li>Making time to collaborate on tasks</li><li>Attending meetings on time and being fully present</li><li>Shared lunch breaks or team bonding activities</li><li>Preparing for discussions and practicing open communication</li></ul><p><em>Example: A leader setting aside time for a 1:1 check-in to discuss a colleague’s career development goals.</em></p><p><strong>Physical Touch</strong></p><p>This was the least emphasized category, as physical interactions in a professional setting can be sensitive and depend heavily on personal boundaries. However, we identified three small gestures that could work:</p><ul><li>Eye contact to signal active listening and engagement</li><li>A pat on the shoulder (if appropriate and welcomed)</li><li>Hugs — but only when explicitly welcomed (e.g., after asking, “Would you like a hug?”)</li></ul><p><em>Example: A reassuring pat on the back after a successful presentation (if appropriate within the individual and the company culture).</em></p><h3>Key Takeaways and Next Steps</h3><p>The biggest learning from this session was that <strong>appreciation is often expressed in many ways, but not everyone interprets it the same. </strong>By understanding our colleagues’ preferred “appreciation language,” we can build stronger, more positive relationships at work.</p><p>I encourage teams to openly discuss how they perceive appreciation and incorporate these insights into their workplace culture. Try asking in your next 1:1 or team meeting: “How do you like to be appreciated at work?” You might be surprised by the answers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fdbb37319d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I landed a new job in four weeks after being laid off]]></title>
            <link>https://medium.com/@josephine.keil/how-i-landed-a-new-job-in-four-weeks-after-being-laid-off-b14e44f350c2?source=rss-50a967e2a070------2</link>
            <guid isPermaLink="false">https://medium.com/p/b14e44f350c2</guid>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[notion]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[google-docs]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Josephine Palberg]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 08:05:13 GMT</pubDate>
            <atom:updated>2025-02-11T06:24:08.917Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8HTGmROS4VrraFpjUX3OKw.jpeg" /><figcaption>picture by <a href="https://pixabay.com/de/users/jenregnier-7438086/">Jennifer Regnier Photography</a> | source: <a href="https://pixabay.com/de/photos/feier-geburtstag-hochzeit-liebe-3301738/">https://pixabay.com/de/photos/feier-geburtstag-hochzeit-liebe-3301738/</a></figcaption></figure><p>In August 2024, I faced an unexpected layoff due to economic reasons. It was a surprise but also an opportunity to reshape my career path. Within just four weeks, I signed a new job contract.</p><p>How did I manage that? Through clear steps, helpful tools, and a bit of support from my network. Here’s my story – and the tips that might help you too.</p><h3>Step 1: Building visibility on LinkedIn</h3><p>When I found out about my unexpected job loss in August, I decided to share it openly on LinkedIn. I posted about the situation and made it clear that I was looking for new opportunities, including what kind of role I was aiming for and when I would be available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLHFTUyuQEIgDxOCxTGyow.png" /><figcaption>Screenshot LinkedIn 07.01.2025 | source: Linkedin.com</figcaption></figure><p>The post generated (at least for me) impressive visibility: 3299 people reached (by 856 direct LinkedIn followers and contacts only)</p><p>One thing I really want to emphasize is that <strong>there is absolutely no shame in sharing your job search status on LinkedIn</strong> – whether it’s through a post <strong>or using the “Open to Work” badge</strong>. For me, both of these actions were incredibly helpful in getting noticed by hiring managers and recruiters. In fact, this transparency led to 7 direct contacts with hiring managers and recruiters within the first two days of my job search. In the following days, I already had my first interview and continued receiving messages from several different companies.</p><p>By being open about my situation, I gained valuable support and increased my visibility, which helped me find a new job much faster than I had expected in the beginning. So if you ever find yourself in a similar position, don’t hesitate to be open about your job search – it can make all the difference.</p><h3>Step 2: Staying organized with Notion</h3><p>As my job search progressed, I quickly realized I needed a system to keep track of everything. That’s when I discovered Notion, which turned out to be a game-changer. I used a pre-built template for a job application Kanban board, which allowed me to get started right away with only minor adjustments. This setup made it much easier to track my progress and keep all relevant information in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFEoXBgfJ1Ua0_9ld_jbaw.png" /><figcaption>Screenshot Notion Job Application Tracker Template 07.01.2025 | source: <a href="https://www.notion.so/Job-Application-Tracker">https://www.notion.so/Job-Application-Tracker</a></figcaption></figure><p>• Kanban board for tracking applications: I personalized the board, based on my needs.</p><p>• Centralized notes: I kept questions, salary discussions, and other details in each application’s “ticket”.</p><p>•	Job ad backups: To avoid losing access to job postings that might go offline, I copied the full text of each ad into Notion.</p><p>This setup helped me keep everything organized and reduced the stress of managing multiple applications on different platforms like LinkedIn, Google Jobs, StepStone, Indeed, GoodJobs, Xing, and Instaffo (German job market).</p><h3>Step 3: Crafting Resumes and Cover Letters with Google Docs and ChatGPT</h3><p>Writing personalized applications was one of the most time-consuming parts of my job search. When I finally found my old CV, I ran into formatting issues because it used fonts not installed on my new device. Rather than fixing it, I saw it as an opportunity for a fresh start. A new job deserved a new CV, and using the built-in templates in Google Docs made the process efficient and enjoyable with its well-designed, easy-to-customize options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wo_TdoVpCWc6Kuuks7KnjQ.png" /><figcaption>Screenshot Google docs Templates gallery 07.01.2025 | source: <a href="https://docs.google.com/">https://docs.google.com</a></figcaption></figure><p>I also appreciated how straightforward it was to edit these templates, which saved me a lot of time in the long run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HtyO5NEuP2C09QIB8ZCGHw.png" /><figcaption>Screenshot Google docs Resume Template 07.01.2025 | source: <a href="https://docs.google.com/">https://docs.google.com</a></figcaption></figure><p>To streamline the cover letter process, I first put considerable thought into crafting a general version that truly reflected who I am, what I value in a job, and the kind of employer and product I wanted to work with. This document served as the foundation for all my applications. I then used ChatGPT as a tool to refine my letter for each specific job, but the content was always shaped by my own words and values. ChatGPT helped with structuring and fine-tuning the text, but it was important to me that the applications remained authentically mine, with ChatGPT acting purely as an assistant to bring my ideas into the right form.</p><p>One key learning from this process was that ChatGPT can be an incredibly powerful tool to streamline and speed up processes, but it’s crucial to review the output carefully to ensure that your original intentions are fully communicated. <strong>ChatGPT should not be viewed as a replacement for your own work; rather, it should serve as a support tool</strong>, helping you structure your thoughts and enhance your writing. At the end of the day, it’s still up to you to ensure that the result aligns with your true message.</p><h3>Conclusion</h3><p>After four intense weeks, here’s what I accomplished:</p><p>•	25 job applications</p><p>•	25 responses</p><p>•	8 direct rejections</p><p>•	14 interviews and team meetings</p><p>•	1 offer, which turned out to be the one I wanted</p><p>My Takeaway: <strong>An unexpected layoff can be daunting, but it’s also an opportunity.</strong> The right combination of visibility, organization, and helpful tools like LinkedIn, Notion, Google Docs, and ChatGPT can save time and increase chances of success.</p><p>More importantly, they allowed me to make the most of what could have been a stressful time, giving me the freedom to not only focus on finding the right job but also to invest in my personal growth, spend quality time with loved ones, and enjoy life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b14e44f350c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Co-Pilot to Pilot: My Journey from UX Design to Product Management]]></title>
            <link>https://medium.com/@josephine.keil/from-co-pilot-to-pilot-my-journey-from-ux-design-to-product-management-5af1a04c0827?source=rss-50a967e2a070------2</link>
            <guid isPermaLink="false">https://medium.com/p/5af1a04c0827</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[carreer-change]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[carreer]]></category>
            <dc:creator><![CDATA[Josephine Palberg]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 09:24:28 GMT</pubDate>
            <atom:updated>2024-10-16T09:28:13.522Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mOe8Twcacs_aEUhTOp7lGg.jpeg" /><figcaption>picture by <a href="https://www.pexels.com/de-de/@cottonbro/">cottonbro studio</a>, source: <a href="https://www.pexels.com/de-de/foto/anzug-madchen-gelb-sitzung-9656756/">https://www.pexels.com/de-de/foto/anzug-madchen-gelb-sitzung-9656756/</a></figcaption></figure><p>As a UX designer, I often felt like the co-pilot of an airplane. I helped set the course, corrected the path when needed, and ensured we had a smooth journey for our passengers — the users. But at some point, I realized that I didn’t just want to help steer; I wanted to decide where we were flying in the first place. That was the moment when I knew I wanted to make the shift into product management.</p><p>Now, as a pilot, I realized that this job is about so much more than just deciding on the destination. It’s about understanding the airplane itself, navigating the weather, and managing the resources while flying, … I’m sure you get the point.</p><p>Product management surprised me in ways I didn’t expect, but I wouldn’t want to switch back. It’s a role that constantly challenges me, but it also offers immense joy and fulfillment. I hope my journey can provide insights for others looking to make a similar transition.</p><h3>Why I decided to switch to Product Management</h3><p>I spent about six years working as a designer. I started in graphic design and transitioned toward UX design. Switching from UX design to product management wasn’t just about taking on more responsibility — it was about thinking on a larger scale. As a designer, I focused deeply on the user’s immediate experience, crafting solutions based on their needs and feedback. But in product management, I found myself juggling multiple layers: aligning with business goals, managing stakeholders, ensuring technical feasibility, and constantly balancing short-term wins with long-term strategy. It was a challenge to move from purely user-centered thinking to making decisions that also prioritized the company’s success and market demands.</p><p>In my new role, I had to build a deeper understanding of the product’s technical constraints, learn how to communicate with engineers, and oversee the bigger picture, including roadmap planning, KPIs, and competitor analysis. All of these aspects made the transition both challenging and rewarding.</p><p>Here’s why I decided to make the switch:</p><ol><li><strong>I aspired to take the lead in shaping product strategy</strong>, making strategic decisions that influence the product’s direction and success.</li><li>I believed <strong>my background in UX provides a strong foundation for making informed product decisions</strong>, enabling me to strike the best possible balance between enhancing customer experience and achieving business objectives.</li><li><strong>The design job market was shifting, and I wasn’t adapting to it.</strong> There was a growing demand for UX/UI roles, but my strengths lay in the conceptual side of things.</li><li><strong>I wanted to earn more money in the long term.</strong> There’s still significantly more earning potential in product management.</li><li><strong>I was tired of keeping my portfolio updated.</strong> It felt like a never-ending cycle of case studies, constantly proving my abilities during every application process.</li></ol><h3>Challenges in the transition</h3><p>One of the most significant challenges during my transition was demonstrating my value as a product manager. I applied internally for two roles and externally for about 10 to 15 positions. However, most applications didn’t result in an interview invitation, and the few responses I received culminated in a case study where I didn’t leave the best impression, looking back on it now.</p><p>Additionally, I faced challenges related to understanding common salary ranges for product management roles, which made it difficult for me to articulate my salary expectations during interviews. In many cases, I also wasn’t entirely sure what recruiters valued most. Questions like which skills to highlight and which specific examples would best demonstrate my limited prior experience often left me feeling uncertain.</p><p>A few years and learnings later, I can share the following insights:</p><ol><li><strong>Salary Expectations</strong>: Research is key. There are many websites that provide salary ranges for different roles, considering factors like company size, seniority, industry, and location. I also highly recommend speaking with other product managers about their salary experiences. These conversations can give you a more realistic idea of what to expect and help you feel more confident during negotiations.</li><li><strong>What Recruiters Look For</strong>: While I can’t tell with 100% certainty what every recruiter values, I discovered that it was helpful to describe specific situations where I had already carried out product management tasks. Don’t just focus on the positive experiences — share examples of conflicts or challenges and how you resolved it and learned from them. From my experience, recruiters want to see that you can handle difficult situations and find solutions when things get tough.</li></ol><h3>Starting small</h3><p>Luckily, there was one internal people manager who recognized my potential, gave me a vote of confidence, and supported my development. I am still incredibly grateful for the opportunity he provided me and for the guidance that helped steer my career in the right direction.</p><p>When I started my new position, I began collecting new experiences step by step, initially without a dedicated team to support me. Month by month, new team members joined, which turned out to be a fortunate situation. This incremental growth gave me the time to deeply understand the new product, its market, and the surrounding customer base.</p><p>My people manager and I held two weekly meetings — one focused on project updates and another dedicated entirely to coaching. Additionally, I was fortunate to have a mentor who had been a product manager for a while. At first, we met biweekly, and as I gained more confidence and experience, the meetings became less frequent. I even had the chance to shadow him during planning sessions, where I learned about the frameworks he used regularly.</p><p>After a year, I was promoted, and in the following year, I had the opportunity to take on a second team and additional projects.</p><h3>The power of specialist in your team and supportive product peers</h3><p>Initially, I lacked a solid understanding of technical feasibility and didn’t know how to build or interpret data dashboards. However, by consistently collaborating with my tech lead and our data analyst, I gradually became more comfortable making data-driven decisions and trusting my own judgment.</p><p>In our product cluster, we had regular exchanges between product managers. I quickly learned who had which skills and strengths, allowing me to ask for help more intentionally. To my surprise, my peers were always open and willing to share their knowledge and offer support. This gave me additional sources to acquire knowledge and learn from the experiences of others, expanding my understanding beyond my immediate team.</p><p>The biggest lesson I learned was this: <strong>Observe closely and ask questions, try things out yourself. Finally, review your results with an expert and learn from their feedback. </strong>This process helped me progress much faster than I ever expected.</p><h3>Tools, books, and podcasts that helped me along the way</h3><p>Here are some resources that have been especially beneficial during my transition into product management and up to now:</p><p><strong>Getting Things Done</strong> framework: Helped me organize my to-dos and prioritize effectively, allowing me to focus on what’s most important.</p><p><strong>LinkedIn</strong>: I follow posts from people, groups and companies I felt I could learn from:</p><ul><li>People: <a href="https://www.linkedin.com/in/alexwang2911/">Alex Wang</a>, <a href="https://www.linkedin.com/in/nireyal/">Nir Eyal</a>, <a href="https://www.linkedin.com/in/donnorman/">Don Norman</a>, <a href="https://www.linkedin.com/in/stephanie-leue/">Stephanie Leue</a>, <a href="https://www.linkedin.com/in/elenaverna/">Elena Verna</a>, <a href="https://www.linkedin.com/in/melissajeanperri/">Melissa Perri</a>, <a href="https://www.linkedin.com/in/pascalbornet/">Pascal Bornet</a></li><li>Groups &amp; Companies: <a href="https://www.linkedin.com/company/nielsen-norman-group/posts/?feedView=all">Nielson Norman Group</a>, <a href="https://www.linkedin.com/company/interaction-design-org-foundation/posts/?feedView=all">IxDF — Interaction Design Foundation</a>, <a href="https://www.linkedin.com/company/mind-the-product/posts/?feedView=all">Mind the Product</a>, <a href="https://www.linkedin.com/school/product-school/posts/?feedView=all">Product School</a></li></ul><p><strong>Learning Apps</strong>:</p><ul><li><a href="https://brilliant.org/"><em>Brilliant</em></a>: This app helped me enhance my skills in interpreting data, and it offers a wide range of topics, including Math, Computer Science, Programming &amp; AI, and Science &amp; Engineering.</li><li><a href="https://www.udemy.com/"><em>Udemy</em></a><em> &amp; </em><a href="https://www.coursera.org/"><em>Coursera</em></a>: These are excellent platforms for courses on nearly every topic. I personally used them to deepen my understanding of business fundamentals and product strategy development.</li><li><a href="https://www.audible.de/"><em>Audible</em></a><em> &amp; </em><a href="https://www.spotify.com/"><em>Spotify</em></a>: I enjoyed listening to books and podcasts during my commutes or workouts, making the most of my time while gaining new insights.</li></ul><p><strong>Books I recommend</strong>:</p><ul><li><a href="https://www.amazon.com/Articulating-Design-Decisions-Communicate-Stakeholders/dp/1492079227/ref=as_li_ss_tl?_encoding=UTF8&amp;psc=1&amp;refRID=N0KEWQPFW3DEVY8T46VT&amp;linkCode=sl1&amp;tag=tomgreevercom-20&amp;linkId=5dc9ca21c74c2831bd4c223caa54f60b&amp;language=en_US"><em>Articulating Design Decisions</em></a> by Tom Greever</li><li><a href="https://www.askyourdeveloper.com/"><em>Ask Your Developer</em></a> by Jeff Lawson</li><li><a href="https://www.producttalk.org/2021/05/continuous-discovery-habits/"><em>Continuous Discovery Habits</em></a> by Teresa Torres</li><li><a href="https://susancain.net/book/quiet/"><em>Quiet</em></a> by Susan Cain</li><li><a href="https://erinmeyer.com/books/the-culture-map/"><em>The Culture Map</em></a> by Erin Meyer</li><li><a href="https://en.dt-toolbook.com/"><em>The Design Thinking Toolbox</em></a> by Michael Lewrick, Patrick Link, Larry Leifer</li><li><a href="https://productschool.com/resources/ebooks/the-product-book"><em>The Product Book: How to become a great Product Manager</em></a> by Carlos Gonzalez de Villaumbrosia, Josh Anon</li></ul><p><strong>Podcasts</strong>:</p><ul><li><a href="https://www.produxlabs.com/product-thinking"><em>Product Thinking</em></a> by Melissa Perri</li><li><a href="https://www.mindtheproduct.com/the-product-experience/"><em>The Product Experience</em></a> by Mind the Product</li></ul><h3>My long-term goals in Product Management</h3><p>When I look back at the past 2.5 years of my journey, I’m proud of the new challenges and responsibilities I’ve taken on in my role, which have helped me grow into the Product Manager I am today. As I look to the future, my long-term goals in product management focus on three key areas:</p><ul><li><strong>Continue building effective products</strong> that strike the right balance between user needs and business objectives.</li><li><strong>Lifelong learning.</strong> Technologies and markets are constantly evolving, and there will always be new trends and frameworks to explore. I plan to continue experimenting with innovative ideas, learning from others, and embracing growth through challenging situations.</li><li><strong>Fostering growth in others.</strong> Whether they are product managers, designers, developers or … I firmly believe that individuals from diverse backgrounds bring essential perspectives to our community. If someone is eager to drive a product, willing to learn from challenges, and unafraid to ask for help, I am confident they can thrive as a product manager. Helping people unlock their full potential is something I find incredibly fulfilling, and I would love to practice this even more in the future.</li></ul><h3>Closing thoughts: The Pilot’s journey</h3><p>The journey has taught me that being a product manager is like being both the pilot and co-pilot simultaneously. You’re guiding the direction, but you’re also constantly learning from your surroundings, your crew, and unexpected challenges in the air. It takes time, experience, and a lot of reflection to keep improving. But with the right mindset and willingness to grow, I believe anyone can become an excellent product manager.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5af1a04c0827" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Overcomplicating It! Why You Should Start Small with User Journey Maps]]></title>
            <link>https://medium.com/@josephine.keil/stop-overcomplicating-it-why-you-should-start-small-with-user-journey-maps-246536a42f65?source=rss-50a967e2a070------2</link>
            <guid isPermaLink="false">https://medium.com/p/246536a42f65</guid>
            <category><![CDATA[user-journey-mapping]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[simplicity]]></category>
            <dc:creator><![CDATA[Josephine Palberg]]></dc:creator>
            <pubDate>Tue, 17 Sep 2024 09:16:51 GMT</pubDate>
            <atom:updated>2024-09-17T09:16:51.443Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQsPCorMUoSiCV-wZofWmw.jpeg" /><figcaption>My journey discovering User Journey Maps</figcaption></figure><p>The first time I encountered User Journey Maps was during my time as a UX designer. Back then, I was fascinated by the potential of this framework to visualize the entire user experience. However, I also found it intimidating at first — these maps often looked like complex, multi-layered documents that demanded a lot of time and effort. As I transitioned into my role as a product manager, the pressure of limited time made it easy to see why some might shy away from using them.</p><p>But over time, I discovered that User Journey Maps don’t have to be overwhelming. In fact, they can start small and simple, allowing you to build iteratively as more insights come in. This approach not only makes them manageable but also turns them into a powerful tool for improving both user experience and product development.</p><h3>How I started: From Excitement to Uncertainty</h3><p>When I first came across User Journey Maps, I was genuinely excited about the framework. The potential to capture the entire user experience was thrilling, and I couldn’t wait to dive in. However, that initial excitement quickly gave way to a mix of overwhelm and uncertainty. The complexity of the maps seemed daunting, and I felt unsure about how to begin.</p><p>Before I started building my first map, I looked at examples online. They were impressive but also complex and time-consuming. I saw massive visualizations that mapped out every touch point, user goal, pain point, emotions and interaction. It seemed like creating one would take weeks to months, and in a fast-paced product environment, I just didn’t have that kind of time.</p><p>Additionally, I got the feeling that I needed to test my assumptions before presenting them to stakeholders or my team. This added another layer of pressure and made the task seem even more challenging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xo9j1iVL31nyUURAiO4jfg.jpeg" /><figcaption>From excitement to intimidation before mapping the first user experience</figcaption></figure><h3>How I Simplified My Approach</h3><p>As I started using User Journey Maps, I discovered that the complexity I initially perceived was optional. You don’t need to create a fully detailed map from the start. Instead, I began by focusing on a few key touch points in the user journey and gradually expanded the map as I gathered more data and insights.</p><p>Starting small wasn’t just more manageable — it proved to be more effective. By concentrating on essential stages of the user journey, I could address pain points and refine the map incrementally. This iterative approach allowed me to engage continuously with my team and stakeholders, facilitating direct discussions and challenge assumptions.</p><p>The ongoing dialogue made the User Journey Map a powerful tool for fostering interdisciplinary exchange and collaboration. Regular updates ensured that everyone stayed aligned and engaged, making the process more dynamic and collaborative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sSlvFU-_ZuiYyIJeLT4Z1w.jpeg" /><figcaption>Surprised by how simplification enhanced my experience with the framework</figcaption></figure><h3>The Benefits I’ve Seen from Starting Small</h3><p>Starting small has had several benefits for me, and it’s completely changed how I view User Journey Maps.</p><p><strong>1. It Reduced My Stress:</strong><br>The pressure to create a perfect, all-encompassing map disappeared once I realized that I didn’t need to do everything at once. By breaking the journey into smaller phases, I could focus on what mattered most at any given time, without feeling overwhelmed.</p><p><strong>2. It Gave Me Quick Wins:</strong><br>Even a simple map brought immediate value. By mapping out a specific phase, I could quickly identify where users were struggling and address those pain points right away. This allowed me to see results faster and make impactful changes without having to wait for a fully detailed map.</p><p><strong>3. It Allowed Me to Iterate Naturally:</strong><br>What started as a basic map grew organically over time. As I gathered more data and insights — whether from user interviews, analytics, or feedback — I was able to update and expand the map. It became a living document that evolved along with the product, allowing me to refine and improve the user journey continuously.</p><p><strong>4. It Strengthened Interdisciplinary Collaboration:</strong><br>Working on User Journey Maps wasn’t a solo effort. By involving different team members and stakeholders, I was able to strengthen interdisciplinary collaboration. This collective approach not only improved the map itself but also enhanced our overall team dynamics and alignment.</p><h3>Iterating Over Time: How My Maps Evolved</h3><p>What really made this approach work for me was the ability to iterate. My User Journey Maps were never static; they grew and changed as my understanding of the user evolved. After mapping out a specific phase like onboarding, I would layer in new data, like user feedback or behavioral insights, over time. This helped me stay flexible and up to date.</p><p>One of the best parts of this iterative process was how easy it became to collaborate with my team and stakeholders. Instead of trying to explain abstract pain points, I could simply show them the map and demonstrate where users were getting stuck. It made communication so much clearer and more effective. I often used tools like Miro or FigJam to create these maps, but even simple tools like Excel work just fine when you are in the early stages of the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_ss-ay5gcHlLWFWRiaqyA.jpeg" /><figcaption>Continuous use of User Journey Maps made me feel like a pro</figcaption></figure><h3>Conclusion: Don’t Let the Complexity Scare You — Start Small</h3><p>If there’s one piece of advice I could give to anyone feeling intimidated by User Journey Maps, it’s this: start small. Don’t feel like you need to have a massive, perfect map from day one. Focus on one phase, identify key pain points, and build from there. You’ll be surprised at how quickly the map grows and how much insight you can gain even from a basic version.</p><p>User Journey Maps don’t have to be overwhelming or time-consuming. By taking an iterative approach, I’ve found them to be one of the most valuable tools for improving the user experience, guiding product decisions, and ensuring team alignment. So let go of the pressure for perfection — <strong><em>just start</em></strong> <strong><em>small</em></strong> and watch how much easier your product journey becomes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=246536a42f65" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>