I hoped you noticed that in literally every one of these examples, the winning solutions didn’t come from users or sales; rather great products require an intense collaboration with design and engineering to solve real problems for our users and customers, in ways that meet the needs of your business. In each of these examples, the users had no idea the solution they fell in love with was actually possible.
Absolutely love this article. The stories. The people. The clarity.
I’ve been researching different approaches to understanding and prioritising product features and the concept of demand validation really stands out.
Demand validation is a testing methodology that ties in with lean principals to figure out ways to answer the question “do people want to use this?”
“Is this product usable?” is answered by usability testing. “Do people want to use this?” is not.
The core idea centres around running tests against prototypes of ideas long before any pixel perfect design work or coding has begun.
There are claims that on average, 50% of the work a product/delivery team completes is notused because customers were asked “would you use this?” in UX testing. The waste happens because there was a gap between customers saying “yes I would use that” (hypothetically) vs. customers actually committing to use it once launched.
Demand validation introduces a cost question. The theory is that until you make saying “yes” cost something to a test respondent, their answer is meaningless.
Once you make it cost something, respondents start to analyse the trade offs they’re going to have to make which then validates that they mean what they say.
If customers are excited to give you either time, reputation or money as a result of testing a prototype – build that feature.
It’s an interesting approach to an old problem in which you can’t guarantee demand for your product. It helps a team understand and prioritise features with high probability to achieving market success. Maybe worth a try?
I’ve been running the company-wide hack at Hooroo for the last year or so and I thought I’d share how they happen. There isn’t a lot of great info on the web on the topic of running Hack Days and where there is, everyone is doing things slightly differently. I’ll let this serve as a contribution to that pile of disparate info for others use how they please.
It’s also my last day at Hooroo tomorrow so this serves as a guide for those who’re carrying the Hooroo Hack torch into the future!
The big takeaway is that the key to a great hack day is the prep that gets put in leading up to the event. If the prep happens then the participants, theme, location etc all fall in to place.
1) Pick a date. This is the first and most important step. We try get 6-8 weeks ahead of ourselves with this. Get an all-day 2 day invite sent out and into everyone’s calendars so there’s few excuses for not being there. This also buys 6-8 weeks to prep which allows for a nice relaxed build up.
2) Decide on a theme. It pays to list 3 or 4 theme ideas and involve a few people for feedback and a decision. You may need to take some time to mull over a popular candidate or to gather a few more ideas – make sure you don’t rush as the theme of the hack is critical to it’s success. Previous themes of Hooroo Hack include:
Pitch anything that helps Hooroo customers, helps raise awareness of the Hooroo brand, or helps Hooroo suppliers.
Pitch something our competitors are not doing.
Pitch something that makes coming to work at Hooroo more awesome.
A good theme is one that folks can get their heads around pretty quickly, is relatively broad in terms of scope and creates a lot of discussion (usually about how good or bad of a theme it is). The idea of having no theme for the next hack has been discussed a lot – it’s always something worth considering and no doubt you’ll get feedback on whether it’s a good idea or not.
3) Create teams. Because Hooroo is only a small crew (30 employees), pre-determined hack teams with a even mix of members from the various Hooroo groups goes down well. It means folks don’t have to self gather and manage, no one misses out and the barrier to entry is lowered due to the extent of “being told what to do”.
It’s fun to pick a team name “theme” and also setting up distribution groups with team names in our Google apps admin makes it super easy for team members to communicate leading up to, and during, the day. I imagine private Slack channels will also be used in a big way now that we’ve adopted it company-wide. Past team name themes include:
Colours: Green, Black, Red, Blue
Phonetic alphabet spelling of “HACK”: Hotel, Alpha, Charlie, Kilo
Property amenities: WiFi, Breakfast, Shuttle, Valet
4) Plan team spaces. It’s critical that each team has their own space to hack together, uninterrupted over the 2 days. The spaces we’ve used in the past are:
Hooroo board room: Easy to sort out as we manage the room.
A shared meeting room close by: If it requires a booking, best to get on it as soon as the Hack date is set.
Main Hooroo showcase open area: Set up a whiteboard and a use few projector screens as walls and suddenly there’s a tidy little area for use.
Hooroo quiet rooms: By opening up the doors of the 2 Hooroo quiet rooms and using a whiteboard on wheels to block off the area, you create a nice spot for a team to set up.
5) Share Hack details. This is fairly straightforward but requires a bit of prep. Essentially it’s a slide deck at our company Friday showcase that recaps last Hooroo Hack, reminds everyone why we do Hooroo Hack, what the next Hack theme is and details some timelines between that day and the Hack kick off.
There are some steps that can be completed immediately following the sharing of the above info:
Create, print and put up some Hooroo Hack posters: Our design team are always a big help with this and love putting these posters together. It’s great to see them around the office advertising the upcoming Hooroo Hack teams, theme, dates etc.
Send out a 9am “Hack kick off” calendar invite to get Day 1 of the Hack going. This is a great reminder for folks closer to the time and is also a timely chance to repeat the slides used at showcase.
Set up a “Hack pitches & voting” calendar invite for the arvo of Day 2 of the Hack. This can also be shared with external folks who may like to attend the pitches and vote for a winner.
Send out a Hooroo Hack prize giving calendar invite to follow the preso’s and voting and book a nice space at a bar of your choosing.
Decide on a voting method. Our voting boxes work a treat and someone usually brings in coloured poker chips so each team can be identified and can’t get away with voting for themselves.
6) Kick off the Hack. Pretty straight forward. After setting up the team areas first thing in the morning, get everyone together and get things going. Take a random draw to allocate teams to rooms and the order of pitches. Remind teams they need to put an A3 pitch poster together to be next to their voting box and that they need to be ready to present at the decided time the following day. Recap how voting will work and where prize giving and drinks will happen in the arvo.
7) Hack. The best part!
8) Pitches. Set up the Hooroo Showcase area for the pitches. One team may have to finish early to help with this. Follow the order identified the previous day. Hand voting tokens to team members after they have finished their pitches.
9) Voting. Have everyone vote and then help clean up their team areas before heading out to the pub. The rule of 2 votes per person and not voting for your own team has worked pretty well.
10) Count votes. Most votes wins. Make sure teams haven’t voted for themselves. Take notes of best pitch poster and best pitch for announcement at the pub later.
11) Head to the pub. Announce winners and give the trophy.
12) Get the trophy engraved. Usually takes about a week and costs $20. It’s great to capture the winning team’s idea and the date of month/year of the hack for posterity.
13) Collect feedback. A quick email in the week following Hack to make sure everyones ideas and suggestions are captured.
14) Start thinking about next Hack.
Here’s a video from Hooroo Hack #2 back in June 2014. Excuse the audio track. Mike turned this around quick smart at the time and didn’t have many options.
Here’s another video of outtakes where the folks at Hooroo give progress updates on how Hooroo Hack #3 is going for them and their teams.
Every post you share, every friend you make and every link you follow is tracked, recorded and converted into data. Advertisers buy your data so they can show you more ads. You are the product that’s bought and sold.
We believe there is a better way. We believe in audacity. We believe in beauty, simplicity and transparency. We believe that the people who make things and the people who use them should be in partnership.
We believe a social network can be a tool for empowerment. Not a tool to deceive, coerce and manipulate — but a place to connect, create and celebrate life.
1. Have we documented the basics, down to the tiniest detail, including the software and product design, and all trademark and patent applications?
2. Are we using technology to create an atmosphere of transparency and clarity around critical decisions related to product design, business development, marketing strategy and more?
3. Are we recording customer interactions in a way that will deliver insight to future iterations of the team? If the sales department turned over, would its new leaders be able to maintain key relationships?
4. Have we created systems that stakeholders (investors, large customers, strategic partners) could tap into for insights into the business?
5. Is our culture one in which all employees are empowered to take decisive action, or one in which only the founders can drive advancement?
6. Are we building on employee strengths as we grow our team? Are new hires complementary extensions of the existing staff?
7. Have we created a network of partners, technology providers, installers and others who can become part of our growth framework?
“The priority has always been, first and foremost, to feature the work and the designer,” Cederholm explains. “We’ve intentionally kept the UI agnostic (monochrome, Helvetica type, simple glyphs) so that the variety of work being shared takes the spotlight and isn’t overshadowed by Dribbble’s brand.
“Over time, many of the features we’ve added have been a direct reaction to how the community chose to use the site. Rebounds, for instance, were being done by members simply linking their shot in the comments. We noticed that and built a UI around that to support what was going on.”
With an approach like that I can only imagine greater success in the future.