Tips, Tricks and Requirements for Your Studio Submission
Here are some thoughts to consider for a successful submission.

FIRST OF ALL
Don’t be afraid!
Help us explore your vision and experiences of Legal Design.
Things we ENCOURAGE
CONTENT
- Real use case (not invented,not fictional). Does not have to be in use yet or not anymore, but should contain the story of use case journey which is implemented in the respective organization.
- Remember we need waivers from every player involved!
- use cases with business, non-profit or educational background
- a2j and public sector use cases
- impact-related client work
- Articulating a defined problem statement
- A good description of the methodology to solve the problem, e.g. user research and analysis of insights (interviews, focus groups, questionnaires etc), prototyping and testing
- Providing an Impact analysis of the outcome
- Telling us a compelling story
- Making your content enjoyable and easy/interesting to read
- If you use AI for your entry, explain which tool you used, why you picked this tool and how you checked for e.g. accuracy, copyright, security issues and human-centricity of the output
- Explain how AI empowered you to get deeper/further with the design process
FORMATTING
- Image Resolution: min 1280×720 pixels, no larger than 2 MB per image (format: .jpg, .png or .svg)
- send all images separately
- transparent or white background for illustrations
- Solid structure of content: 3 to 6 chapters outlining problem statement or challenge / methodology / result / impact assessment
- Executive summary / Intro section
Things NOT to do
CONTENT
- Submitting a marketing deck or a marketing story just selling a service or a product
- Applying only a limited, poor or no design process or methodology
- Using only AI to produce your content – we can tell! (or at least we think so…)
- Being generic. Please be specific!
FORMATTING
- Excel-Graphs
- Images larger than 2MB per image
- Only a slide deck without an accompanying text document
- Only a PDF without an accompanying text document (reason: makes editing for us easier and reduces a lot of back and forth)