Hills Template
If you don’t know where you’re going, you might not get there.
If you don’t know where you’re going, you might not get there.
When it comes to Design Thinking, we, at the DTTT, refer a lot to IBM Enterprise Design Thinking Courses. This is one of the essential templates every business should familiarise themselves with.
.jpeg)
When it comes to Design Thinking, we, at the DTTT, refer a lot to IBM Enterprise Design Thinking Courses. This is one of the essential templates every business should familiarise themselves with.
If you don’t know where you’re going, you might not get there. Use Hills to clearly state your purpose in terms of user and market value.
When it comes to Design Thinking, we, at the DTTT, refer a lot to IBM Enterprise Design Thinking Courses. This is one of the essential templates every business should familiarise themselves with.
Hills describe something a specific user is enabled to do, not a specific implementation - if you have a challenge or need to find a quick solution to help you boost your productivity, for example. They give teams the creative space they need to come to breakthrough ideas, without the need for detailed requirements. Write Hills at the beginning of a project or initiative, after you’ve identified the real needs of your users.
We suggest 30 to 60 minutes to run this activity. The basic rules are the usual ones when it comes to co-design:
Get the "Who", "What", "Wow" template printed in a large size on a wall or big table or use the digital template on Mural. Prepare large sticky pads and markers for everybody or do a quick run-through on how to use Mural.
Diverge on many ideas for each section and quickly share them with your teammates. Build off of others’ ideas, but focus on quantity over quality and avoid drifting into features or talking about implementation details. Imagine the example is filled in by a vineyard estate.
Build sentences using your ideas for “Who,” “What,” and “Wow.” Draft them quickly and begin to mix and match, until you’ve found a combination that seems to describe your intention for your user.
Get a fresh pair of eyes to read your drafted Hill and give feedback. Remember that your Hills will evolve based on your continued understanding of the problem and your users.
When it comes to Design Thinking, we, at the DTTT, refer a lot to IBM Enterprise Design Thinking Courses. This is one of the essential templates every business should familiarise themselves with.
If you don’t know where you’re going, you might not get there. Use Hills to clearly state your purpose in terms of user and market value.
When it comes to Design Thinking, we, at the DTTT, refer a lot to IBM Enterprise Design Thinking Courses. This is one of the essential templates every business should familiarise themselves with.
Hills describe something a specific user is enabled to do, not a specific implementation - if you have a challenge or need to find a quick solution to help you boost your productivity, for example. They give teams the creative space they need to come to breakthrough ideas, without the need for detailed requirements. Write Hills at the beginning of a project or initiative, after you’ve identified the real needs of your users.
We suggest 30 to 60 minutes to run this activity. The basic rules are the usual ones when it comes to co-design:
Get the "Who", "What", "Wow" template printed in a large size on a wall or big table or use the digital template on Mural. Prepare large sticky pads and markers for everybody or do a quick run-through on how to use Mural.
Diverge on many ideas for each section and quickly share them with your teammates. Build off of others’ ideas, but focus on quantity over quality and avoid drifting into features or talking about implementation details. Imagine the example is filled in by a vineyard estate.
Build sentences using your ideas for “Who,” “What,” and “Wow.” Draft them quickly and begin to mix and match, until you’ve found a combination that seems to describe your intention for your user.
Get a fresh pair of eyes to read your drafted Hill and give feedback. Remember that your Hills will evolve based on your continued understanding of the problem and your users.
.webp)