> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/inceptions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbooks.equalexperts.com/inceptions/introduction/why-run-an-inception.md). # Why run an inception? **BETTER OUTCOMES.** We’re passionate about building great software. Collectively, the contributors to this playbook have some 500 years of software delivery experience. But starting something new always has its challenges. We’ve experienced pain: both when things go pear-shaped and also when things work out. The common root causes? Misaligned values and expectations, overlooked risks, missed dependencies and unsophisticated approaches to managing uncertainty and complexity. > ### ***Technology initiatives, if done in the right way, can be successful and fun.*** It’s particularly frustrating when that pain could easily have been avoided. The complex interplay of people, processes and technology will always bring change, uncertainty and unknowns. By acknowledging and addressing these factors early, we can reduce the risks we’re exposed to, and create safe spaces to experiment and learn together. This is why we run inceptions. They systematically address the issues that threaten to derail delivery, by reducing risk, creating alignment, building trust and providing us with the best possible starting point. Of course, knowing why you might want to run an inception is not the same as being able to run an effective one! This is where this playbook comes in. We believe it’s possible to distil the essence of an inception into a blueprint. This document is that blueprint. By taking away some of the complexity and providing ideas to riff off and make your own, this playbook aims to support beginners and experts alike. Over the pages that follow, you’ll find the tools to build better foundations for the initiatives you work on. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://playbooks.equalexperts.com/inceptions/introduction/why-run-an-inception.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.