> 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/prototype-designer-1/designer-skill-tree/website-design-sprint/creating-a-good-sketch.md). # Creating a compelling concept > **Andrej:** \ > This is my approach to create a compelling and self-explanatory concept, even if I lack full clarity of the project. ### **Note-taking** `Suggested Duration: 30 mins` Write down the sprint questions, scan through the inspiration board and write down everything that you think should be part of your concept. Stick to words, or draw simple boxes or outlines. You won't have time to look at details later, so try to write down everything that resonates with you. Write down which screens should be part of your concept (Landing Page, Dashboard, Profile Page etc.), stick to 3 or 4. ### **Crazy 8's** `Suggested Duration: 10 mins` Crazy 8's is a quick exercise to draw some rough sketches of the product. Pick which screen you think will be the most difficult. With each iteration, re-arrange and prioritise the elements based on visual hierarchy. Iterate on the wording of the titles, choosing different words each time, even if you think they might not work. Try to talk to the user, converge to a nice layout by the last screen. ### **Integrate** `Suggested Duration: 60 mins` Use your notes to fill out the screens with content. Make titles bold and dedicate each page to a specific screen. Try to be precise about the wording and use real numbers, even if you think they will be wrong or unrealistic. If you're not sure if something makes sense, write/sketch it anyway. It's better to express an idea wrong than to not express it at all. If you think that some parts of the concept may be hard to understand, briefly explain the benefit of it on a post-it. {% hint style="info" %} **Charlie:** \ On the **Note Taking** there's one trick I've found which helps me to quickly categorise and distill the information on the board in a short space of time: {% endhint %} 1. I quickly decide on the three most important steps the user will take in my concept. E.g. the three screens I'm going to sketch. 2. I take this information from the goals, questions, HMWs and map (I might have a quick look at the research if there's an example which is useful in understanding this. 3. I split a piece of paper into three with these three 'sections' now at the top. 4. This means as I scan the miro, using the process Andrej outlined above, I can quickly drop information, sketches, notes or ideas into each category. {% hint style="info" %} **Charlie:**\ I've found this really helps me process the information quickly and means as I find a new idea or path, I can note it down in the section and move between them. The main advantage is speed getting the notes down, and then the speed to go over these notes again at the sketching stage. For me, it's too much mental capacity to consider all screens at once. {% endhint %} ## Expected Quality Please see the following example from Beefy.Finance to see the quality and level of detail we expect from Product Designers in one hour of sketching: [Beefy.Finance Miro Board](https://miro.com/app/board/o9J_lP2dcWM=/) In this example, the client's sketches are also at a very high standard. ![](/files/-MXqavKROviUXKgtuJas) --- # 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/prototype-designer-1/designer-skill-tree/website-design-sprint/creating-a-good-sketch.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.