[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fEaZeDR8vNLeNJNmja6QyYi-Q3hBw67sbc8gZx5xHLNA":3,"$fy5dZJaftppbxb-gUHSHB19-tcIrsvvk4dwac84DNFqk":15},{"author":4,"tags":11},{"author_id":5,"author_name":6,"author_name_first_letter":7,"article_count":8,"bio":9,"short_bio":9,"slug":10,"image_url":9},28372,"Brian Lawley","B",7,null,"brian-lawley",[12],{"tag_id":13,"tag_name":14,"tag_count":8},23036,"product-management",{"quotes":16,"pagination":163},[17,38,57,81,101,130,144],{"id":18,"quote_text":19,"author_id":5,"source_id":20,"has_image":21,"author":22,"source":23,"quote_tag":24,"commentary":9},705966,"Doing testing with real users (in addition to internal quality testing) can help you avoid the serious embarrassment of a failed product.",2,false,{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[25,30,35],{"id":26,"tag":27},3477982,{"id":28,"tag_name":29},12636,"customers",{"id":31,"tag":32},3477984,{"id":33,"tag_name":34},22921,"testing",{"id":36,"tag":37},3477983,{"id":13,"tag_name":14},{"id":39,"quote_text":40,"author_id":5,"source_id":20,"has_image":21,"author":41,"source":42,"quote_tag":43,"commentary":9},634483,"Engineering-driven companies falsely assume that because they build it, the industry will magically become aware and be willing to buy it.",{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[44,49,54],{"id":45,"tag":46},3274999,{"id":47,"tag_name":48},5455,"industry",{"id":50,"tag":51},3274997,{"id":52,"tag_name":53},9008,"engineering",{"id":55,"tag":56},3275000,{"id":13,"tag_name":14},{"id":58,"quote_text":59,"author_id":5,"source_id":20,"has_image":21,"author":60,"source":61,"quote_tag":62,"commentary":9},601026,"Methodology must be flexible. Companies often don't adopt the materials &amp; methods they were trained on because they aren't flexible enough.",{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[63,68,73,76],{"id":64,"tag":65},3166288,{"id":66,"tag_name":67},4035,"flexibility",{"id":69,"tag":70},3166287,{"id":71,"tag_name":72},9469,"companies",{"id":74,"tag":75},3166290,{"id":13,"tag_name":14},{"id":77,"tag":78},3166289,{"id":79,"tag_name":80},60036,"methodology",{"id":82,"quote_text":83,"author_id":5,"source_id":20,"has_image":21,"author":84,"source":85,"quote_tag":86,"commentary":100},461292,"Not having a specified launch plan and process is one of the biggest pitfalls in the technology market.",{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[87,92,97],{"id":88,"tag":89},2627395,{"id":90,"tag_name":91},1618,"technology",{"id":93,"tag":94},2627392,{"id":95,"tag_name":96},19941,"marketplace",{"id":98,"tag":99},2627393,{"id":13,"tag_name":14},"**The Backstory**\nBrian Lawley, the founder of the 280 Group, a management consulting firm specializing in product portfolio management, likely shared this quote in the context of his work in the technology industry. During the early 2000s, Lawley was immersed in helping companies navigate the complexities of product development and market launch. His expertise was particularly relevant in an era where the pace of technological innovation was accelerating, and the risk of failed product launches was high.\n\n**The Hidden Insight**\nThe quote reveals a counter-intuitive truth: the absence of a launch plan is not merely a lack of preparation, but a deliberate choice with significant consequences. By not having a specified launch plan, companies are, in effect, inviting chaos and uncertainty into their product development process.\n\n**How to Use This**\nTo apply this mindset today, modern professionals and creatives should acknowledge the value of a clear launch plan as a safeguard against the pitfalls of the technology market. By proactively outlining a structured process, they can mitigate the risks associated with product development and increase their chances of successful market entry.",{"id":102,"quote_text":103,"author_id":5,"source_id":20,"has_image":21,"author":104,"source":105,"quote_tag":106,"commentary":9},456820,"After the launch phase, your product is old news. Take advantage of the opportunity to generate interest when your product is new.",{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[107,112,117,122,127],{"id":108,"tag":109},2606392,{"id":110,"tag_name":111},1673,"interest",{"id":113,"tag":114},2606391,{"id":115,"tag_name":116},2130,"ideas",{"id":118,"tag":119},2606395,{"id":120,"tag_name":121},12757,"products",{"id":123,"tag":124},2606393,{"id":125,"tag_name":126},16661,"launch",{"id":128,"tag":129},2606394,{"id":13,"tag_name":14},{"id":131,"quote_text":132,"author_id":5,"source_id":20,"has_image":21,"author":133,"source":134,"quote_tag":135,"commentary":9},134247,"Only move forward with creating a product that will be \"above the bar.",{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[136,141],{"id":137,"tag":138},876063,{"id":139,"tag_name":140},71,"business",{"id":142,"tag":143},876065,{"id":13,"tag_name":14},{"id":145,"quote_text":146,"author_id":5,"source_id":20,"has_image":147,"author":148,"source":149,"quote_tag":150,"commentary":162},134236,"Don't focus all your time and effort on creating the templates &amp; perfecting the documents. Answering key product questions is more critical.",true,{"id":5,"author_name":6,"slug":10,"author_name_first_letter":7,"article_count":8,"image_url":9},{},[151,154,159],{"id":152,"tag":153},876015,{"id":139,"tag_name":140},{"id":155,"tag":156},876014,{"id":157,"tag_name":158},4942,"answers",{"id":160,"tag":161},876017,{"id":13,"tag_name":14},"**The Backstory**\n\nThis enigmatic quote appears to be from Brian Lawley, an influential figure in software development and productivity. Although I couldn't pinpoint the exact origin, it's likely from one of his blog posts or videos where he shares practical advice on project management. During this period, Lawley was actively involved in developing agile methodologies and Lean principles, emphasizing efficiency and customer-centricity.\n\n**The Hidden Insight**\n\nAt first glance, the quote seems to advocate for prioritizing key product questions over documentation. However, upon closer inspection, it reveals a deeper tension between two essential aspects of project development: planning and experimentation. Lawley is warning against over-investing in detailed documentation without concurrently engaging with the actual problem or question at hand.\n\n**How to Use This**\n\nTo apply this mindset today, focus on creating \"Minimum Viable Documentation\" that captures the essence of your project's key product questions. This means producing minimal yet relevant documentation that allows you to explore and refine your understanding of the customer's needs before investing too much time in exhaustive templates or perfecting documents.",{"currentPage":164,"totalPages":164,"totalItems":8,"itemsPerPage":165},1,10]