Fluxon’s Post

Launch Week - Day 5 🚀📅 Examples are an incredible way to explore a product. I find myself navigating to examples first and then working my way back up to top-level messaging and docs when first learning about a product. We built out an example framework early on at Dopt, and they've been amazing at showcasing how Dopt can help you build best-in-class product onboarding and education experiences. Recently, we've come back at our examples with fresh eyes and added some awesome improvements, like: 🧑💻 Forkable CodeSandbox environments 🗄️ Filter by category, like technology or component 🌅 Flow previews to better understand how the example is powered by Dopt Check them out here https://lnkd.in/gtMnq-Hf

On my way to ProductCon in London by Product School! 🚀Thrilled to be joining an event with top product leaders from leading tech companies. Ready to soak up all the insights and tactics on developing the next-gen software products. If you are also attending would be great to say hello! 👋 #ProductCon #London #ProductLeadership #productmanagement

I’m thrilled to share my first Medium post with you all. Check out my journey and insights from HerTechTrail. Special thanks to Nsisong Uko Ann Ezeogu, CSPO and all my coaches for their guidance and support. #HerTechTrail #ProductManagement #Journey #Learning #MediumPost #TechCommunity #HerTechTrailCohort9

Reviewing my product from early 2022 as a student who participated in a hackathon and won 1st place, I realize I've failed in key areas. 🏆 Let me explain how: 1. Lack of Proper Market Research: I relied on self-assumptions without conducting thorough market research. 2.Neglecting Backend Operations: There's no seamless backend operation; relying on a single person to upload new videos is inefficient and leads to a growing number of video files, impacting the storage system. 3. Addressing Temporary Pain Points: The project only addresses temporary issues without proper long-term planning. 🤔 To improve as a product manager 1. Conduct thorough market research 🌐 to replace assumptions with data-driven insights. 2. Strengthen backend operations ⚙️ for seamless video uploads, ensuring scalability for a growing file system. 3. Address long-term challenges by implementing strategic planning 📊 to solve lasting pain points.

Attending Online the Product School event #productcon Joe Futty: Changing the paradigm from "Users are tasked to learn how to use our systems." to "system that understands the users in their natural language". Fabrice des Mazery "Get the skin in the game, the stakeholders don't need to "understand" they need to live it." know and respect "Your own level of risk tolerance" "Product teams and stakeholders should act like owners by taking responsibility for the effective use of resources and seeking maximum returns of the investments" #productcon #productmanagement

#Day16 of the #3week_product_build_challenge was all about Rework You know that feeling when the developer completes building everything after a many days of efforts and then the tester comes up with a few bugs due to which now the developer has to again redo everything from scratch with a different approach? That's exactly what happened today with me Starting off from where I let off yesterday, I was very confident that I'll be done by today afternoon, which I almost was. I had a basic structure of the overall app ready by late afternoon. But during testing, I found 2 key issues - 1. Some buttons could not accommodate a few MCQ answers due to it's length constraints, which meant that I had to change the fundamental design of the overall app 2. The database structure that I had was a bit inefficient, trying to strike a balance between the amount of work needed (Time) vs No.of updates that can be done for free (Cost) vs the knowledge of knowing what to do when (Expertise). I got stuck in many places without a path forward and again had to start things from scratch (a couple of times). This was when I truly understood the power of Hands-on learning. While I spent a good amount of time trying to understand everything about the app yesterday, there were many scenarios which I couldn't handle or know what to do next. Seeing those tutorial videos at that point was a complete eye-opener for me, I started understanding and learning things from a different lens all together. Going by the trajectory of it, I've planned to remove the game development from the product roadmap and instead I'm planning on just getting everything done with the basic functionalities and position it as the Duolingo of Product management. Let me know what you guys think! Checkout my Youtube video where I deep-dived into my explorations today (https://lnkd.in/gpFvvR3F) Checkout my Notion if you wish to follow my build journey closely (https://lnkd.in/gpq3zgqm)

Filled with anticipation, this marks the first step in our journey to developing more useful tools.

#Day11 of the #3week_product_build_challenge was all about MVP relaunch and it failed, again. So I completed reworking on all the aspects of my MVP, completed it and did all the preps needed for the relaunch with all the hype, and all I heard were the crickets :) 4 of them signed up for the MVP evaluation session I had, 2 backed out, 2 newly joined and I had to rush the session due to multiple reasons and at the end of the day, there was no way for me to evaluate the MVP. This gave me a couple of lessons 1. Don't do something just to try and prove a point (like MVP need not be a digital product). While it definitely need not be and I stand by it, I feel like I tried to force fit that thought too much into my MVP 2. Always ask the questions "What's in it for them?" before you ask someone to try something - everyone is busy with their own work, you need to clearly define why should they do this, instead of continuing with their tasks 3. It's always better to have some sort of traction present before you launch something and some sort of virality within the product that'll help continue the traction after the launch So what's next? It's Day-11 already, and I just have 10 more days to complete my challenge. So I plan to go on extreme-agile and have 2-3 day sprints with continuous releases instead of the initial idea of launching the beta by this week and the final product only by next week. At the end of the day, until launch, it's only about testing the hypotheses and making sure the need is there. I'm not sure if it'll work, but I also don't plan on shying away from giving it a shot Let me know what you guys think :) Checkout my Youtube video where I deep-dived into my explorations today (https://lnkd.in/gsvvMnTH) Checkout my Notion if you wish to follow my build journey closely (https://lnkd.in/gpq3zgqm)

Fear of failure holding you back? Turn it around at the Boost event 👊 Our event "Embrace Failure to Boost Success" is happening 𝗧𝗛𝗜𝗦 Saturday, June 22nd at 10 a.m. at Critical TechWorks in Porto! ⏳ We have 𝟱 𝗱𝗮𝘆𝘀 𝗹𝗲𝗳𝘁 to the big day and only a few free spots to dive into: ➡️ Interactive sessions with product leaders sharing their biggest flops. ➡️ Learn how industry giants overcame product failures. ➡️ Psychologist-led workshop on harnessing failure for growth. ➡️ Network with fellow PMs and build tools to crush setbacks. Plus, when you join Boost, you'll be entered into a draw for one ticket to join PRODUCTIZED in October! Register in the link in the comments 👇 #productmanagement #failureisfuel #porto #Boost

📢 Missed our webinar on Technical Product Strategy for New Product Development? Don't worry, we've got you covered! 🚀 ✨ For those who missed the live session, we’ve outlined some highlights from Daniel’s presentation. Follow the link to gain valuable insights on how to build a successful technical product strategy for new products. If you’re a startup or small business, you won’t want to miss this: https://bit.ly/479dfVq