<?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 Sarah Faber on Medium]]></title>
        <description><![CDATA[Stories by Sarah Faber on Medium]]></description>
        <link>https://medium.com/@sarah.faber?source=rss-a103a25b7121------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KzYXmi-ea4Ui9tgeGlX5Jw.jpeg</url>
            <title>Stories by Sarah Faber on Medium</title>
            <link>https://medium.com/@sarah.faber?source=rss-a103a25b7121------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:25:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sarah.faber/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[22 Random Lessons From the Last 22 Months in Product]]></title>
            <link>https://medium.com/@sarah.faber/22-random-lessons-from-the-last-22-months-in-product-dfdbe8aae40d?source=rss-a103a25b7121------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfdbe8aae40d</guid>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[product-engineering]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[empowered-teams]]></category>
            <dc:creator><![CDATA[Sarah Faber]]></dc:creator>
            <pubDate>Sun, 20 Jul 2025 11:15:46 GMT</pubDate>
            <atom:updated>2025-07-20T11:28:22.220Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0EjR9mmHWu3P7FJ3dv_NAg.jpeg" /></figure><p>Some of the following lessons came from high-fives, others from facepalms. Most were somewhere in between. No grand conclusions here, just 22 honest takeaways from 22 months of building, learning, failing, and laughing with a team I’m lucky to work with.</p><p><strong>1. Although sometimes frustrating, not being a domain expert helps simplify complexity.</strong></p><p>I used to worry about not being a domain expert — now I’ve learned to value it. Asking “Why?” more often helps me dumb things down early, strip away complexity, and translate needs into scalable, agnostic flows.</p><p><strong>2. Don’t underestimate celebrating micro-wins.</strong></p><p>You never know who on your team is doubting themselves that day. One small celebration can shift a person’s day — or week. Compound enough of positive mindsets and you’ll feel it in your team’s health.</p><p><strong>3. Never get too busy for micro-interactions.</strong></p><p>I’ll never stop believing in the ROI of micro-interactions, even though they’re often the first things to go when time gets tight. A small shoutout, a thoughtful check-in, a genuine thank you, or a kind ask for help — it pays off.</p><p><strong>4. Negative micro-moments leave bigger scars than you think.</strong></p><p>Closely tied to point 3. Too many “Don’t have time to answer this properly, they’ll manage” moments will cut the team’s trust eventually.</p><p><strong>5. It’s okay to be friends with your colleagues.</strong></p><p>I used to be afraid of it. But after nearly six years of work, I’m starting to realize how much of our lives we spend at work. Letting relationships evolve into real friendships has made the day-to-day more joyful — and turns out, it can work without crossing any lines.</p><p><strong>6. Fast teammates need fast feedback.</strong></p><p>Simple but good reminder: Stay responsive if you want to keep momentum alive.</p><p><strong>7. The ripple effect of underperforming members is real</strong></p><p>Old lesson, relearned several times this year. Don’t underestimate the <em>exponential</em> impact of underperforming members. Don’t wait to protect your team from that impact.</p><p><strong>8. A high-performing team feels almost surreal.</strong></p><p>You know when you are surrounded by high-performers. Things just <em>work</em>. Problems are energizing, and you don’t need to over-process everything. It’s rare, and it’s magical.</p><p><strong>9. Empowered teams aren’t a myth. They’re just rare.</strong></p><p>This is the first time I’ve truly been part of one. Ownership is real, trust is mutual, and it’s wildly satisfying.</p><p><strong>10. Product engineers are a real thing.</strong></p><p>I honestly can’t imagine doing product without product-minded engineers anymore. When devs truly think product, it changes everything — the collaboration, the quality, the energy.</p><p><strong>11. QA becomes fun when creative freedom is welcome.</strong></p><p>I often reflect on what moments can uplift devs. This one is to uplift <em>me</em>. When engineers feel safe enough to add polish or throw in a thoughtful “nice-to-have,” QA becomes a space for delight — not just bugs.</p><p><strong>12. The “no rules” rule only works when people care.</strong></p><p>If the team is mature and aligned, minimal process doesn’t mean chaos but speed and trust.</p><p><strong>13. Always — Clear is kind.</strong></p><p>Again, put in the effort to be clear in your communication. Vagueness is exhausting. Don’t hide behind soft language. And yes — proofread your messages.</p><p><strong>14. Psychological safety looks like laughing over a critical bug — and then fixing it immediately.</strong></p><p>A good way to check the level of your team’s psychological safety: how do they react when critical bugs occur? Do they stay calm? Maybe even giggle quickly about the miss, but keep focused enough to fix it. Sounds ideal to me.</p><p><strong>15. Leadership should leave a little ambiguity in the vision.</strong></p><p>Too much clarity can kill ambition. Too little clarity can make teams spiral. The right amount of ambiguity keeps teams curious, aligned, and motivated.</p><p><strong>16. Shielding your engineers is important — but so is exposure.</strong></p><p>PMs often try to protect devs from the real chaos. But hiding too much leads to disconnection. Share some of the raw context, even if it’s messy. I’ve found it helpful to delegate some of that exposure to specific roles (like dev leads) who can handle it.</p><p><strong>17. When the week feels chaotic, do the small things well.</strong></p><p>Make your bed. Do the dishes. Write your Friday wrap-up. Prep your Monday’s first To Dos. These small rituals ground you when everything else feels messy.</p><p><strong>18. Sometimes your job is to commit to leadership — even if you disagree.</strong></p><p>You’re there to challenge, align, and sometimes just commit. Knowing when to do which is a subtle but important skill. (Also inspired by: <a href="https://www.youtube.com/watch?v=xm5QAzAlqEY">How to build a team that can “take a punch”</a> — Hilary Gridley)</p><p><strong>19. Procrastinating on a small, annoying task? Your team might be your solution.</strong></p><p>If something feels heavy, someone else might love that kind of task. Ask around. Use your team. You’re not alone.</p><p><strong>20. Realizing your company isn’t that product-led is humbling — but freeing.</strong></p><p>Realising product doesn’t always shift the numbers can make you question the purpose of your daily efforts. However, you can also use it to reduce pressure on yourself and focus on what <em>can</em> be done. (Also inspired by: <a href="https://www.youtube.com/watch?v=8TpakBfsmcQ">From ChatGPT to Instagram to Uber: The quiet architect behind the world’s most popular products</a>)</p><p><strong>21. You’ll find this in all of my reflections: Don’t cut 1:1s.</strong></p><p>No explanation needed.</p><p><strong>22. Reflect, or forget.</strong></p><p>No explanation needed.</p><p>No rulebook, just reflections. Here’s to the next chapter and the lessons it’ll bring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*sBmoiMvsuKmk2KjjXP_Uhw.jpeg" /><figcaption>Some of the amazing people I get to work with at the moment</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfdbe8aae40d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Begin again: Insights from my latest onboarding]]></title>
            <link>https://medium.com/@sarah.faber/begin-again-insights-from-my-latest-onboarding-2a3de8a93321?source=rss-a103a25b7121------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a3de8a93321</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ambivert]]></category>
            <category><![CDATA[onboarding-process]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Sarah Faber]]></dc:creator>
            <pubDate>Mon, 06 May 2024 12:49:00 GMT</pubDate>
            <atom:updated>2024-05-07T13:17:25.140Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ten onboarding highlights in the eyes of an ambivert PM</h4><p>Mastering the onboarding of a new Product Manager is tough. Of my three onboarding experiences over the past three years, the latest perfectly matched my expectations and profile. Let’s dive into what made this onboarding successful.</p><p>To put my personal highlights in perspective, I wanted to share a snapshot of how I work and learn best.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbphnvjXCaAYpmjhMwmFEg.png" /></figure><h4>10 Onboarding Highlights</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jf4hPZnVD8rpRAWL8kwqDg.png" /></figure><h4>1. Meeting key stakeholders during a 30-minute exchange</h4><p>My first week was filled with a rapid-fire series of 30-minute sessions with key stakeholders. The events were shared with me in advance, allowing me to think ahead and absorb the primarily theoretical exchange faster. Apart from understanding the big picture, the greatest benefit of this approach was that I met all the key team members before I needed them, which empowered me to own my first cross-functional tasks early on.</p><p>Example: A session with an underwriter taking me through the basics of the insurance business and the underwriting flows at the company.</p><h4>2. Getting to my first win within the first 2 weeks</h4><p>By the end of week two, I got to validate a complex yet not urgent feature. Having the space to explore solutions, demonstrate my problem-solving skills, and communicate effectively with my product team and managers without the rush was a crucial step. This early small win built trust with my team and established me as a point of contact for developers and other stakeholders. Ultimately, the feature was prioritized for the upcoming sprint, marking a satisfying start.</p><p>Example: A point of friction outside of the golden path that was mostly related to design debt and made the UX more coherent.</p><h4>3. Having room to breathe, connect, and laugh during a few social activities — but not too many</h4><p>As an ambivert, the first weeks in an open-space can be very exhausting and socialising after work requires energy that I personally did not have. So while I truly appreciated the considerate touches like welcome breakfasts and lunches, I was relieved that social events were limited and there was no pressure to attend other social gatherings.</p><h4>4. Owning the first cross-functional challenges</h4><p>By my second month, I started owning my first medium to low impact cross-functional product problem statements. This allowed me to explore other functions in the company, understand their wishes, constraints and frustrations and therefore deliver more value later on.</p><p>Example: Automating a manual process that involved tasks from more than three different teams.</p><h4><strong>5. 1:1s — of course</strong></h4><p>I think it goes without saying why 1:1s were crucial to my experience but they need to be listed here. I used 1:1s with my manager, the CPO and my PM buddy to help shape the onboarding so it responded even more to my needs to learn faster. While our 1:1s do not have a specific structure, I made sure to prepare a few points regarding my experience in advance to get the most out of them.</p><h4>6. Processing information with repetitive tasks</h4><p>We all know the small manual tasks that simply do not deserve developer time to get automated. While they tend to be tiresome, I think they are a great onboarding lever. It allowed me to touch upon many edge cases of the product and deepen my understanding of the product’s strengths and weaknesses. I think it is important to only start doing these once you already have a solid foundation of the product and business, otherwise you do not gain enough insights from them.</p><p>Example: Modifying automatically generated documents manually.</p><h4>7. Making room for the first important mistake</h4><p>A few weeks in, I made a significant mistake by overlooking an important QA step. To give you an idea of what I’m talking about, I authorized the release of a feature while our sales team was demoing the platform, unaware of the update. As this incident caused frustration it greatly accelerated my learning and strengthened my relationships with my team and manager, as we had to work together to resolve the issue. The ability to make such mistakes — and learn from them — was made possible by my manager’s foresight in allowing room for error. Although mistakes can be daunting early on, the timing here turned out to be “just right”.</p><h4>8. Owning first uncomfortable public product exchanges</h4><p>This was a challenging part of my onboarding. I started responding to bug reports or product related questions in slack channels of +50 members. The pressure to demonstrate my knowledge in real-time, while tracking down product flows that I was still unfamiliar with, was uncomfortable. What made the task easier was having a fellow PM as a buddy on my side. They were ready to assist whenever I got blocked, making this high-pressure situation a bit more manageable. Despite the discomfort, this experience was crucial. It rapidly deepened my understanding of the product and its technical details, allowing me to more effectively plan and enhance future features.</p><h4>9. Running first user feedback sessions</h4><p>By the time I conducted my first user feedback sessions, I felt incredibly empowered. There’s something uniquely satisfying about hearing users discuss your product when you fully grasp their perspectives, understand the specifics of their use cases, and decode their language. These sessions not only offered tremendous learning opportunities but also boosted my motivation by reminding me why I do what I do. The timing couldn’t have been better — I was well-prepared to categorize feedback, pinpoint users’ needs, and confidently discuss the product, which allowed me to effectively share these insights with my team.</p><h4>10. Updating new and existing feature documentation</h4><p>Teaching is often said to be one of the best ways to learn quickly, and this certainly held true during my onboarding, when I had to update our internal documentation on existing features. Writing concise articles on a feature’s purpose and technicalities was a great task to measure of how much I had actually grasped and where I still needed to dig a bit deeper.</p><p>That wraps up the highlights of my onboarding experience. I was fortunate to have a team that provided excellent framework and support but I also tried to remind myself that the speed and effectiveness of onboarding can be greatly enhanced by actively reflecting on and sharing my learnings right from the start (<a href="https://medium.com/@sarah.faber/your-perspective-matters-no-matter-your-level-of-experience-b8b647eefc03">How to share your thoughts in the very beginning</a>).</p><p>Why do I consider my onboarding a success? Beyond the motivation to continue thriving in this environment, I measure my progress by a straightforward principle: ‘As a PM, my primary role is to deliver the most user value in the least possible time.’ Given the skills and knowledge I’ve acquired through these key moments, I feel well-prepared to continuously improve on this front, marking my onboarding experience as a definite success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a3de8a93321" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your perspective matters, no matter your level of experience]]></title>
            <link>https://medium.com/@sarah.faber/your-perspective-matters-no-matter-your-level-of-experience-b8b647eefc03?source=rss-a103a25b7121------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8b647eefc03</guid>
            <category><![CDATA[first-job]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[feedback-culture]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <dc:creator><![CDATA[Sarah Faber]]></dc:creator>
            <pubDate>Tue, 28 Dec 2021 13:47:06 GMT</pubDate>
            <atom:updated>2021-12-28T15:42:41.326Z</atom:updated>
            <content:encoded><![CDATA[<p>How to value, document and bring up your questions and concerns during your first weeks at a new job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*hVIR7KK-3cb_j6mt0NkBzA.jpeg" /><figcaption>Young Woman Before An Aquarium (Jeune fille devant un aquarium)— Henri Matisse</figcaption></figure><p>Our Podcast guest on Teams At Work, Ryan Donovan, CTO at Hootsuite, correctly said, “The job to learn how to build new relationships as a leader will never be done. New generations entering the workplace look at things differently, and we as leaders need to keep listening and adapting accordingly.” 2021 has been an exciting year for my career start in Product Management, and Ryan has encouraged me to summarise one of the key take-aways that I would like to share with my peers and anyone who is starting at a new team.</p><blockquote>Who am I to judge the working styles of experienced managers?</blockquote><p>My first weeks at Bunch were everything new members dream of when they want to get on top of things quickly. The trust I was given from the start made me discover new behaviours, vocabularies, smart principles and adjustments of popular processes. I was spoiled with new learnings. While I was endlessly grateful for the steep learning curve, I of course didn’t feel aligned with 100% of what I was observing and struggled to figure out where to put my thoughts.</p><p>To give you an example, I had just studied various theories at university on how we should stop celebrating workaholics and focus more on mental health in organisations. I also kept debating with peers that it will become more and more difficult to acquire talent from our generation without providing clarity on healthy working principles from the start. At the same time, I saw the team working extremely long days, being online late at night, and reading messages in the weekend. I noticed that it stressed me out and that I didn’t want to adopt these styles. I didn’t feel comfortable sharing how I felt about it right away because I kept telling myself, “Who am I, as an entry-level PM to judge the working styles of experienced managers.” Today, I would encourage myself to value the impressions instead of judging them.</p><h3>What to do with your impressions on the first days</h3><h4>Observe don’t Reverse</h4><p>Meanwhile, I have onboarded new team members myself and I have experienced what it feels like when a new joiner suggests turning a process upside down because of flaws they have spotted. Suggesting significant changes at the very start risks being counter-productive because one often doesn’t have enough data on why a process is a certain way. While feelings can hardly ever be evaluated as right or wrong, there is often an optimal time and space to suggest improvements that benefits you as a team member and the manager. And that perfect time usually isn’t the first day for various reasons.</p><h4>Let your journal be your gossip partner</h4><p>You’ll likely need to vent within the first days and weeks of your new job. And sometimes, expressing your feelings is all you need to reflect upon happenings with a clear mindset. I would suggest making your journal your best friend. Don’t watch your words, be as dramatic as you want and share everything you feel. This makes you feel heard, and you don’t risk sharing intuitive thoughts too early. But again, you must document them.</p><p>I would follow the good old saying to sleep over it if you have the opportunity. Sometimes a 15-minute screen-free break already helps me see things from a different perspective.</p><h4>Analyse your impressions and evaluate your confidence</h4><p>Read your impressions and focus on the language you use. Evaluate how much background information you have and how much energy it costs you. Focus on formulating questions around interpretations which are based on little background knowledge and come with high frustration and prioritise them for your next chat with your manager.</p><h4>Gain clarity in your next 1:1 — Don’t wait too long</h4><p>Now comes the crucial part. After listening to yourself, giving it time and reflections, don’t hold back with sharing your thoughts. Make sure to schedule time for it in your next 1:1 with the responsible team member.</p><h4>Use a feedback framework to share your thoughts</h4><p>Try to avoid to spill your thoughts and questions messily. Make it easy for your manager or team member to pick up on your concerns by using structure. I really like using the Situation, Behaviour, Impact feedback model which focuses on your feelings and guarantees that you don’t make false accusations.</p><p>Example:</p><ul><li><strong>Situation</strong>: When I receive messages late at night</li><li><strong>Behaviour</strong>: and you don’t indicate whether it is urgent or not</li><li><strong>Impact</strong>: it makes me feel stressed about work</li></ul><h4>Lastly, follow-up on improvement, if your manager doesn’t do it</h4><p>I am extremely lucky to have an excellent listener as a manager who cultivates a learning organisation and an environment where it is easy to speak up. This environment has proven to be successful several times. For example, as more members started feeling stressed, the company quickly introduced new experiments. Next to a monthly paid day off, the team has agreed on no meetings past a specific time, two mindful mornings per week, and is continuously investing time in everyone’s mental health. Everything turned out great for me, and yet I wish I had documented my first impressions more to now be able to understand new joiners better on topics that still need improvement.</p><p>No matter how much experience you have compared to your team, your thoughts will likely reflect those of other new joiners and that alone makes them valuable to the team. You teach the team what it is like to work with people of your personality, your generation, your identity and more. See it as a superpower that you need to learn how to make use of, and you can contribute to the company’s success right from the start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8b647eefc03" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>