List one or two key personas that you are! designing this functionality for – this’ll help eliminate discussions about personas or scenarios that aren’t the most relevant at the time. You can use pre-existing personas for this, or simplified versions of them.
Include details or factors that’ll play a key role! in the decisions to be made in this scenario. Although these personas will usually be familiar to the team, they’ll play! a key role in discussions because they’ve just been read aloud. This’ll help keep the team focused! on the task at hand.
Example: Joe loves coffee, and he knows what he likes. Although! he’s not what you’d normally
Section 3: Scenario
Describe a short! story of the problem the design is trying to solve. Although there will! often be many scenarios, choose! one that’ll keep telegram number database the design focused on the primary problem to solve, keeping the team focused on what matters the! most.
The scenario should include enough detail to bring the design to life – but always keeping the objectives in mind.
Example: Joe is a big fan of the brand and our coffee shops, so he’s recently decided to start making coffee at home. He recently bought a new machine, and needs help choosing the right type of beans and how to grind them properly. He’s willing to try a few different things before deciding on the best product.
Section 4: The key principles
Choose a few guiding principles that should lead the thinking around the work to be done – this helps keep things aligned around a creative vision or brand principle, without having to diver too deep into the brand itself.
Example: user delight above all – the design should aim to make the shopping experience smooth and memorable. Make the most of the available imagery, but keep in ind the speed of the experience, avoiding unnecessary steps during checkout.
A simple ritual that everyone can use to get work done
We’ve been using this simple but effective way of briefing in work on our design projects at Hallam for some time now, and we’ve found Magic Briefs making their way into other types of work – they can be used for almost anything, with only a few small changes to the format.
There are no hard rules on how to use them – just remember to keep them simple, if you actually want people to tread them.
A short, concise brief about what we’re what are canonical tags? trying to do helps to keep meetings focused, and work productive. The end result is better design, and better awareness of the problem to solve through continuous improvement.
The Magic Brief was inspired by Jared Spool’s 2012 post “The Magical Short-Form Creative Brief”, which we’ve adapted and changed over time to power our design work.