> For the complete documentation index, see [llms.txt](https://playbooks.equalexperts.com/advice-process/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/advice-process/background/adoption-pains.md). # Adoption Pains ## It isn't all Sweetness & Light Adopting a management system like the Advice Process doesn’t happen overnight. Even within EE, where we have intelligent, free-thinking people, there were many bumps in the road. The main problems we encountered were around the transition of power, permission seeking and dealing with the tyranny of structurelessness. ### Dealing with Uncertainty A side effect of the Advice Process is that power and control is distributed widely throughout the company. This transition can be particularly difficult for those used to making decisions on behalf of others. Passing decision-making onto others brings uncertainty and feelings of lack of control, which may be uncomfortable for some. Over time, most people adjust to this new way of working, but if it completely goes against your grain, EE may not be the right fit for you. ### Permission Seeking The counter side to managers letting go is team members defaulting to the reflex of permission seeking. If you are the one who is being asked “for permission” then try not to just make a call but rather use this as a teachable opportunity. Ask questions about the problem, who are experts in the area, who might be affected and help them think about measuring the outcomes and reflecting on the learning. Basically, give them the tools and help them understand how to use them. ### Drawing the Line Another regular bump in the road we encounter is drawing the line between decisions that are small, fast or low-risk enough to incorporate in our everyday work versus those that benefit from the investment, transparency and consultation of using the Advice Process. The same conflict occurs when faced with decisions that are larger, but fall within one’s existing responsibilities. Using the Advice Process doesn’t come for free, so the benefits its usage brings need to be weighed up against the cost. Often we’ll apply the principles of the Advice Process (e.g. soliciting advice, enumerating the costs and success metrics), without formally writing up and publishing the decision. This is a blurred line that we still haven’t got totally right and can generate some confusion; something we continue to 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/advice-process/background/adoption-pains.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.