James Ferrandini

Alignment isn’t always easy in product development, but these PM professionals have found the secrets to success. See what they had to say in our new article, and check out their companies’ open roles on Built In! #Hiring #NowHiring

4

Design Systems folks: do you feel you're doing the right work? On Friday I'll be co-hosting the excellent Question with Ben Callahan, where DS practitioners get together for a deep-dive discussion into the topic of the week. This week, we'll be exploring what work you think your team should be doing (and isn't?), and why. All you have to do to get an invite is answer the question! See you Friday! ✨ Answer here: https://bit.ly/3UgkJSc ✨

23

3 Comments

❓ I have a question for product designers ❓ How do you understand that you’ve reached a certain grade or level in your career, such as transitioning to a senior role? Do you rely solely on performance reviews, or are there other ways you evaluate your growth? And what if there’s no formal performance review process? I’m asking because I often get questions about assessing one’s grade or level. So, I’m curious — do you have a similar need or interest in this topic? Let me know your thoughts!

32

30 Comments

1. Cracking the PM Interview 📘 2. Decode and Conquer 📖 3. The Lean Product Playbook 📚 4. Interviewing Users 🧠 5. Product Management’s Sacred Seven 📔 All this knowledge for less than $100! Struggling with interview prep? Practice mock interviews with peers on Candidace.fyi and get the feedback you need! Share your thoughts or experiences in the comments. #ProductManagement #CareerDevelopment #InterviewTips #candidace #pminterview #productmanagement #interviewprep #mockinterviews #datascience

1

Is Detailed Design Anti-Agile? https://lnkd.in/dbpShVPz A CERM Risk Insights article by Howard Wiener, MSIA, CERM. Discover the benefits of agile and detailed design for systems development projects. Learn how it can save time, reduce errors, and increase flexibility.

1

How do you define success for technical documentation? 🤔 Check out the themes that emerged from Write the Docs 2024. Senior Technical Writer Lead Brad Dow shares his key takeaways:📝 🔎 Measuring documentation quality: From user feedback to readability metrics, explore the impact of high-quality documentation. 🔄 OpenAPI adoption stages: Dive into the varying complexities of integrating OpenAPI into documentation workflows. 🚀 Strategic documentation in startups: Learn how to navigate challenges and align documentation with product strategy in startup environments. 🛠️ Applying software engineering principles: Discover how technical writing aligns with software development models. 📚 Sociological considerations: Explore the importance of internal documentation and its impact on organizational functioning. Check out our blog to learn more: https://lnkd.in/gBp2HfV3

13

Documenting product requirements isn't just a step in the process—it's a critical component of successful product development. If you're a product manager striving for excellence, this article is a must-read. It provides a comprehensive, step-by-step guide on how to effectively document product requirements, offering actionable insights and best practices that every product manager should master. Clear and thorough documentation will enhance team alignment and drive your product's success. 🚀 📖 Read the full article here: https://lnkd.in/eRHDqtj6

3

By Ben Labay. "🚀 A customer-data-FIRST process for AB testing documentation 🚀 On our most advanced test reporting setups, we add heatmaps/session-recordings to the end of every test deck. This helps with crafting a comprehensive narrative around your test. Here's a high-level overview of a robust documentation process that ensures clarity and actionable insights: INSIGHT (Problem/Opportunity): Start by identifying the core problem or opportunity. This is where you set the stage for your test by aligning on the business goals and discovered/known customer pain points. PLANNING (Design/Development/etc.): Detailed planning is key. Develop your test hypothesis, plan the design, and prepare development documentation. This phase ensures that all stakeholders are aligned on what the test will accomplish. RESULT (Analysis): After running the test, analyze the results with tools like GA4, Salesforce, and Contentsquare. This analysis phase is where the data tells the story. Document every insight meticulously, ensuring that both quantitative metrics (e.g., $$$) and qualitative customer insights are captured. DECISION (Scorecard): Finally, consolidate the insights into a decision framework. This scorecard should boil down to one key quant metric and a qual customer value insight sentence. It guides the next steps and informs future strategies. (side note, databasing the quant and qual pieces of info across your tests will be gold once you create your own testing GPT or hook up AI to it) This approach not only keeps the process transparent but also ensures that every test is well-documented, with actionable insights ready to drive impactful decisions. 📊💡" By Ben Labay In this week's Speero's best take of the week — where we celebrate and elevate the opinions and takes of experimentation experts.

17

2 Comments

Writing performant user guides doesn't have to be an enigma. We've crunched the numbers and have summarized our findings in a first-ever style guide for user guides. Check it out! https://lnkd.in/er_surjs

6

There’s a subtle difference between “educating” stakeholders and making the impact of your work visible. One of these can help you win promotions, autonomy, and co-conspirators. The other can distract you from your craft at best… or devalue your work at worst. Thought-provoking article from Sara Wachter-Boettcher on how designers can reframe “advocating for design” in a way that avoids burnout and sidesteps the gaslighting.

8

Great advice for both sides of the equation.

5

1 Comment

Many designers still confuse a component library for a design system, but understanding the difference is critical for creating scalable, cohesive products. In this gabble of words I've explored how major companies like Airbnb and IBM do it right? 🧐 #UXDesign #DesignSystems #ComponentLibrary #ProductDesign #DesignVsDevelopment #Collaboration #Figma #DigitalProductDesign #TechDebate #DesignThinking https://lnkd.in/gGmxyKED

2

Top tips when starting a #designsystem! 📚 Document Early: Start documenting your design system from the beginning. Early documentation ensures everyone understands and uses the system effectively, fostering consistency. https://hubs.li/Q02yBVH50

1