Hypotheses - TomorrowPartners/tomorrow-web GitHub Wiki

Testable hypotheses to guide design decisions.

We believe that

Showing success stories about how we've solved problems
Showing what it looks like to work with us ("look at how awesome it is to work with us" "we had a great partnership with this client, and we had a lot of fun doing it")

Will get people excited about working with us

We will know that we are right when

We show potential clients our site and they can easily see how we might work together

We believe that

‘Showing our work’ in a way that helps customers ‘connect the dots’ around what we do

Will

Make it clearer to our potential customers how our diverse project background (across sectors) relates to their specific need
Make it clearer to our potential customers that our design strategy experience is a tool that can be applied in many situations
Create a modern and engaging digital experience that communicates Tomorrow’s value across all sectors

We will know we are right when

We show potential clients our site and they can easily see how we solve their need

We believe that

Designing a flexible case study template (for example, something that does not absolutely require the same content, number of images, etc for every case study -- ie, maybe from 200 words to 500 words, with few or many images)

Will lower the barrier to entry for Tomorrow staff to create case studies

We will know we are right when:

Tomorrow staff can update case studies easily and we see a new case study live, on average, every X months

We believe that

Will lower the barrier to entry for Tomorrow staff to create case studies

We will know we are right when

Tomorrow staff can update case studies easily and we see a new case study live, on average, every X months
Tomorrow staff reports that it is relatively easy and part of their normal workflow to create case studies