Max Obrazchykov’s Post

Trying to Find Impact? 𝙄𝙢𝙥𝙧𝙤𝙫𝙚 𝙋𝙧𝙤𝙙𝙪𝙘𝙩𝙞𝙫𝙞𝙩𝙮 Your team’s productivity is hurting. You just don’t see it yet. Identifying and fixing those are a great way to have impact. Some tips to look for opportunities: 1️⃣ Receiving too many non-actionable alerts? Fix or remove them. 2️⃣ Performing manual tasks too frequently? Automate them. 3️⃣ Shipping bugs frequently due to inadequate testing? Improve test coverage and the release pipeline. 4️⃣ Have an overly complex system that makes trivial changes difficult? Simplify the code and improve the developer guide. 5️⃣ Customers asking repeated questions? Improve your user guide. Got more tips to improve productivity? Share them in the comments. 𝘞𝘢𝘯𝘵 𝘮𝘰𝘳𝘦 𝘵𝘪𝘱𝘴 𝘵𝘰 𝘨𝘳𝘰𝘸? 𝘚𝘶𝘣𝘴𝘤𝘳𝘪𝘣𝘦 𝘵𝘰 𝘮𝘺 𝘯𝘦𝘸𝘴𝘭𝘦𝘵𝘵𝘦𝘳 https://lnkd.in/gkDRPTu8

if you're a developer and work a lot with MVPs for clients, I can guarantee you, you're doing many many, many things wrong. How do I know? I've seen it countless times and have made the mistakes myself. If you want to avoid those mistakes and build solid, useful MVPs for your clients you need to take this course by Jeff Zigman, “The Business CTO” You won't regret it! p.s. Thanks Jeff for making this valuable knowledge available at a fraction of the price it is worth. https://lnkd.in/edk9ZuR6..

4 years back if you had told me I could build products, I would have said "Kya fook ke aya hai bey" Having been a bread-and-butter lawyer for 5 years, Back in 2019 any new technology or product in the market could have only created scepticism in me. Equally fascinated by the build and the functionality I would rather take a step back doubting, how my data would be used. What if the company shuts down? What if there is a data breach? I had so many questions about a product’s build, functionality and it’s working that it led me to leave my law firm job and transition into building software products. Thanks to my critical thinking, I scratched my itch and went on to self-learn the rudimentary fundamentals of what goes behind a website and application. How is data collected, stored, processed and displayed? How to build customer journey and how to improve an existing user’s journey. Today I can design workflows, build designs, and even build products. Thanks to all the no & low-code tools. In 4 years we have built 3 products and served more than 400+ customers. Here are the top 5 skills I believe one requires to break into Product: -Critical thinking -Effective Communication -Understanding & Interpreting DATA -Empathy & user-centric approach -Time Management Tell me what made you make the move into Product? #tellyourstory #productmanagement #productstory #breakintoproduct #productbuilding

📣 "Only the finished product needs documentation." Ever heard of that one? Welcome to another "Myth Buster Monday"! Today, we're tearing down a myth that's as old as my career (JK - it’s older!!). The Old Days Picture this. I'm a newbie technical writer, and the rule is clear: Docs are for GA (General Availability) products only. Beta customers? They're navigating uncharted waters without a compass or a map. Customers would only test products with careful supervision from customer service (back then, there was no such thing as customer success) and in general, had to be convinced with multiple meetings that the upgrade was worthwhile. Fast Forward to 2011 2011 was the year when I joined the open-source revolution. A total game changer and a pivot in mindset. This was the year that changed (for me) from "final product, final docs." to "ongoing product, ongoing docs." In this new philosophy, customers got a beta product that they were willing to test by themselves because they had basic documentation to help them find their way. Think of it like the game Connect the Dots. In this case, the beta documentation is the “dots,” and bit by bit the lines are drawn until the entire image (the product) is there. Because the dots are on the paper, you can understand what the image will be even before you connect the first dot. The Aha Moments * Increased Customer Transparency: We label docs as WIP (Work in Progress / Beta), and suddenly, it's okay for things to be in flux. Customers are more tolerant of smaller changes to documentation. * Incremental Early Testing: We're not just throwing docs into the wild; we're refining them from Day 1, improving them as the product matures. * Customer Insight: Those incremental doc updates? They're like breadcrumbs for our customers, helping them plan for what's next. In addition, they gave us more valuable, actionable feedback, allowing us to change the documentation and the product. In short, what do I think about the "publish early, publish often" mantra? It didn't just change my workflow; it changed my entire outlook. Turning to You Your documentation is a living entity, evolving just like your products. Don't wait for perfection; start the conversation early. Do you publish early, publish often? What do your customers think about it? What insights have you gained? 🤔 Happy documenting, and until next #MythBusterMonday, stay curious and keep questioning! #TechnicalWriting #TechnicalDocumentation #OpenSource #CustomerInsights

Pull Requests: Shift Left, Please: A two-part dive on pull requests and their efficacy, including a few thoughts on assessing their actual cost vs value. Lots of bold claims, as well. https://lnkd.in/eCK7-ejN

Here is a sample case study on how bad technology choices can cripple your product and reputation My client John (not a real name) led a SaaS company. They chose a new backend framework. The dev team thought the framework was cool. But it was hard to work with it, and debug, and full of unexpected bugs. Every product demo felt risky. No matter how hard they tried, the software had issues. Clients saw these problems. The company's reputation suffered. Then John reached out to me for help. We decided on a plan. Shift to a more reliable technology. One I had worked with before. Even though I'm not a big fan of replacing a key technology, the pain was too big. However, this had to be carefully planned. We didn't want to disrupt anything. While we fixed the backend, John's demos went on. - We still used the old technology while working on the new thing - We used a stable front end (the UI). Clients saw the potential rather than the problems. A few weeks later, everything changed: - The software was stable - The team was able to add new features faster In 14 months, a big corporation company bought the product. John's story is common. Many CEOs and CTOs face similar challenges. But with the right help, things can change. If your software isn’t reaching its potential, let's talk. Together, we can find a solution. Contact me and let's get started.

Check out our new “Developer Thriving White Paper Series” to discover the four factors that drive software developer performance and satisfaction, and learn recommendations you can immediately put into practice with your team.

🔥 Discovered: Our Game-Changer for Flawless Software Projects! 🔥 Have you ever felt like you're drowning in software issues, missed deadlines, and unexpected costs? Let me share a piece of my journey. Watch John's story and it mirrored many of the challenges projects faced. But there's a twist. 🎥 In this video, we would like to describe how a "Solution Review" turned things around by: * Highlighting weaknesses in the tech team's approach. * Identifying hidden technical debts. * Bringing clarity over documentation, access, and code quality. Share this with those who have issues with their software. They will be grateful for the solution. I would appreciate it if you could assist me by letting me know how clear the service offered in this video is. P.S. To request the service, please follow the link in the first comment. 📌 #SoftwareDevelopment #SolutionReview #TechInsights #ProjectManagement #TechChallenges #TechnicalDebt #CodeQuality #Documentation #SoftwareSolutions #ProjectSuccess

Do you write use cases? Or, even if you perhaps don't write them, do you THINK in use cases? A structured use case approach helps you: ✅ Think critically about the end-to-end flow of how a user interacts with a software system. ✅ Avoid developing a mess of user stories with conflicting or overlapping requirements. ✅ Helps you ask really smart questions that uncover gaps BEFORE the software is ready for testing. Learn more about use cases in this video - it's still one of our most-viewed videos month in and month out, so I know that a lot of people are looking for more information on this technique. https://lnkd.in/dP6U9Gq #UseCases #SoftwareRequirements #SoftwareProjects

Day 32: Business Requirements Document (BRD) - A Pillar of Product Development In today's #90DaysOfProductManagement Challenge, let’s delve into the critical topic of Business Requirements Document (BRD). What exactly is a BRD? It's a comprehensive document that outlines high-level business needs and expectations for a project or product, serving as a foundational guide for development teams. Who Creates a BRD? Typically, a BRD is crafted by business analysts or experienced project managers in collaboration with key stakeholders, including product managers. This collaborative effort involves gathering and analyzing business requirements through various elicitation techniques. The benefits of a BRD to a product manager include: 1. Clarity of Business Objectives: The BRD clearly articulates the business objectives, helping the product manager understand the broader goals and vision of the project. 2. Alignment with Stakeholder Needs: By involving stakeholders in the creation of the BRD, it ensures that their needs and expectations are documented, providing a foundation for product development that aligns with these requirements. 3. Foundation for Product Development: The BRD serves as a foundational document for the development team, outlining the high-level features, functionalities, and constraints that need to be considered during the product development process. 4. Risk Identification and Mitigation: Through the analysis of business requirements, potential risks and challenges can be identified early in the project lifecycle, allowing the product manager to proactively address these issues. 5. Communication Tool: The BRD serves as a communication tool between business stakeholders and the development team. It helps in fostering a common understanding of what needs to be achieved. 6. Scope Definition: The document helps in defining the scope of the project, specifying what is included and excluded, which is crucial for managing stakeholder expectations and preventing scope creep. 7. Decision Support: During the project, the BRD can serve as a reference point for decision-making, providing a documented rationale for various aspects of the product.   Components of a BRD: The attached BRD showcases key components, using the TechieKiddie App as a case study. https://lnkd.in/duPTC_Pt In summary, mastering the art of creating or interpreting a well-crafted BRD is a pivotal skill for a product manager. It serves as the cornerstone for successful product development, offering clarity, alignment, and a clear roadmap for the entire project team. Embracing this skill is the key to building products that seamlessly align with your business objectives. #brd #productmanagement #businessanalysis #productguide #wtfc24 #womenintech #womenintechafrica #womentechstersfellowship