> For the complete documentation index, see [llms.txt](https://multi-ocean-strategy.designcriticalthinking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multi-ocean-strategy.designcriticalthinking.com/oceans/yellow-ocean-blitz-scaling.md). # Yellow Ocean – Blitz-scaling ## **Description** A warm ocean with an abrupt change pattern ## **Features** Rich only in primary resources (it can hinder the development of more fragile resources). Few islands, but growing Port Cities with an appetite for en bulk trading and investing in scalable products/services. Water evaporates at an abnormally high rate due to its temperature, but it's warm currents of the Yellow Ocean are fast-moving and swift which, for agile players, is a powerful asset. ## **Typical behaviour** You need to move fast and efficiently. Mismanagement of resources is costly and can shut down your operations overnight. Blitzscaling friendly It favours quantity over quality since the main objective of the players is to sell at scale. There is little to no customer loyalty. If you cannot continue to scale, there is no sustainable value in your brand. Innovation is more incremental than radical - hype and high consumption are prioritized. Vulnerable to pirate attacks and extremely difficult to navigate rough waters for those inexperienced. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://multi-ocean-strategy.designcriticalthinking.com/oceans/yellow-ocean-blitz-scaling.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.