> For the complete documentation index, see [llms.txt](https://docs.deepwork.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwork.studio/teams-departments/deep-work-studio/roles/logo-designer/workflow.md). # Workflow ## Project Onboarding When you begin a new project, you will receive an overview from the Workshop Facilitator regarding visual direction for the logo. ## Review Styleboard & Create Rough Drafts Use this information and the client's styleboard to make sure the logo drafts fit the typeface, size, and colors determined in the Alignment Workshop. ## Attend Review Workshop 1 Attend the first section of the first Review Workshop. During this portion of the Review Workshop, you will have the opportunity to receive feedback on your logo drafts. This feedback will let you know if you are on the same page and act as an anchor that can be referenced during the creation process. It can also be referenced if the client's preferences change. ## First Iteration Use the client's feedback about the drafts to create a first iteration of the logo for the project. You can always reference the Figma board that will be shared by the Product Designer. Paste a screenshot of the first iteration of the logo under the moodboard in Miro. ## Send Final Iteration to Creative Director The Creative director will ensure the iteration fits in with the rest of the website design and the desires of the client. They will provide feedback on what to improve. With this information, iterate and submit for approval until the logo is complete. ## Attend Review Workshop 2 & Create Final Iteration During the first section of Review Workshop 2, you will receive feedback from the client regarding your first iterations. Use this information to create a new iteration that will be presented at the Final Presentation. ## Attend Final Presentation At the Final Presentation Workshop, you will have the opportunity to spend 5-10 minutes presenting your final iteration. Once you have received the client's approval, send the finished product to the Creative Director who will ensure it reaches the client in the Project Completion stage. See the Final Presentation page for more information: {% content-ref url="/pages/JGm6pEU4DtxfqZzAmUru" %} [Final Presentation](/teams-departments/deep-work-studio/roles/workshop-facilitator/facilitator-skill-tree/final-presentation.md) {% endcontent-ref %} --- # 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://docs.deepwork.studio/teams-departments/deep-work-studio/roles/logo-designer/workflow.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.