I took the train a few times last weekend, and on every trip I saw people playing both and Puzzles & Dragons.
Both are very different in style and mechanics, but at their core they’re both puzzle games.
If we look beyond mobile, millions still play Sudoku, despite the “fad” being close to 10 years old. And countless millions more enjoy filling out the daily crossword puzzle (yes, newspapers still exist).
Why?
Studies have shown the release of dopamine associated with solving a puzzle - the aha moment - clearly there's pleasure in puzzles.
Humans only?
A fascinating new shows how ingrained into our evolutionary makeup this behaviour is.
Research by the Zoological Society of London using a game designed with dice, pipes and holes found that chimpanzees are motivated to complete puzzles even in the absence of external rewards.
“We noticed that the chimps were keen to complete the puzzle regardless of whether or not they received a food reward. This strongly suggests they get similar feelings of satisfaction to humans who often complete brain games for a feel-good rewar.”
- Fay Clark, ZSL researcher
The fun of solving puzzles appears to be wired deep.
Double the pleasure?
So does the pleasure come just on completion of the task? And does it only flow in one direction?
Other has shown the that being in a playful state can help solve puzzles more easily, and interestingly, anticipating solving a puzzle puts the brain into a more open and pleasurable state.
So in addition to the satisfaction of finding a solution to a difficult level in CCS, there is also the sweet anticipation as you start loading up the game and prepare to play.
What does it mean for game designers?
So does that mean we should drop our space battle, shooters or farm games and all switch to Match-3 puzzlers?
No, not really.
But some takeaways I’m thinking about:
What’s your take on puzzle games? I’d love to hear: or
Note - this was a guest for TechInAsia, a great site for APAC startups.
If you’re doing a startup, there’s allure to a big brand partnership.
You might think: close a deal in a couple months and then prestige, validation, press, growth, new opportunities etc…
“If I get this deal we’ll be up in the bright lights!!”
Except it doesn’t usually work that way.
The reality is more like:
Our success and failure
My startup has worked with a few large brands in the past year. One failed draining precious cycles. A couple though turned much better, including a successful collaboration with media giant on new game , launched after months of hard work.
Here are some 8 startup lessons learned:
Lesson #1 - Press is overrated.
If your main goal is “buzz” that will lead to more downloads / users / revenue for your startup, brace for disappointment.
Even a mention in major media such as Tech Crunch translates to only a temporary spike (we’ve seen this). A friend got a top tier celeb to promote his new startup, resulting in far less returning users than he hoped.
We all remember glitzy press launches for projects that end up failing a year later. And those that rose to success without PR. Our new game got only a of editorial pieces but has still grown well despite it.
Whilst press can help for other reasons (eg- fundraising), a partnership is a pretty risky and resource grabbing way to try and achieve those goals.
Press is icing on the cake, rather than the cake itself.
Think about press as a great bonus only - if you don’t get it, no worries, a solid project will still thrive without it.
Lesson #2 - Is your opportunity cost acceptable?
Doing any project with a Fortune 500 company is going to take more time than you expected. Much more time.
Our project took nearly 6 months to deliver, and that’s fast.
Big brands need multiple approvals with different stakeholders, reviews with marketing and legal, endless back and forwards on product etc
If you’re a small startup and think you can create a brand new app for a brand whilst maintaining momentum on your “main” business, think again.
You’ll need to either hire up, rework what you already have, or try to turn your tech into a platform…or accept that THIS is your startup, and that your prior project will have to wait, perhaps forever.
Our project that failed in the end turned out as a good thing for us -whilst famous and adored brand to be associated with, it was turning into a large departure from our existing path (high opportunity cost) without enough strategic benefit.
Lesson #3 - Work with the right advocates
In a big company, it can be easy to find groups who may be interested and engage you in promising discussions that end up stalling.
Before committing lots of time with a group, some good questions to ask:
In our case, we found an innovation products group who had a track record of projects and getting buy in from the different Conde Nast brands, and brands willing to embrace a new project - which got it all started.
Lesson #4 - Define your scope up front
Whilst in lean startup land we work iteratively and adapt, doing this with a brand that changes scope every week is a recipe for chaos at the least.
Small innocent requests - “oh can we add a module to let the customer redeem coupons through the website as well as the app?” can snowball.
Though there are pros and cons, I think it’s better to agree a list of deliverables and put it in writing early.
But how do you get it “right” from the start?
A good way is to either adapt from something that is proven to work (we based the new game on a mechanic from our first game) or do the upfront customer development and planning work to make sure it has as high chance as possible at success.
It’s a tricky one.
Lesson #5 - Harness the supertanker.
Big companies have processes, legacy and move slowly.
Startups are lightweight speedboats, deciding and moving quickly.
So what gives?
The natural instinct may be to try and bend the big company to your way and pace of working. This will lead most likely to frustration. Yours.
Instead, adapt to their way of working and get the big supertanker pointed in the right direction and let it power through.
For example all our normal task planning is through Google Docs. On the other hand, our partner did planning through Excel spreadsheets and a project management system. After a while, we just ran with it, and made sure that ALL the things to make the project succesful were included.
Once they were “locked in” the system, they just got carried through their usual process and happenes. If you focus less on the “how” and more on the “what” you can make the big company ultimately work for you.
Lesson #6 - Get the term sheet in place early
Legal contracts are one of the least enjoyable things a startup CEO has to deal with (after emptying trash and 4am server down emergencies).
Crawling through pages of minutia to spot potentially lethal gotchas doesn’t help you make your app even better.
And you may, like me, suck at it!
I’ve found a couple of ways to lessen the pain:
Lesson #7 - Secure a budget.
Startups think burnrate, but big companies think budgets and headcount.
Are they going to contribute marketing to the project? Then what budget will be spent, by whom and where?
Are they going to be doing part of the work on the project? Then who is allocated and for what percent of their time?
Ensure your project has resources allocated and if not, ask nicely for it. If they are not sure, then request a good number and discuss from there.
Having these in place rather than a “best effort” will increase the chance of making it a success.
Lesson #8 - Does your head and heart align?
Back when we were still doing virtual worlds, we did a collaboration with Weta. As a big fan of Lord of the Rings & King Kong etc I loved this deal!
We would collaborate on a contest to promote their steampunk sci fi brand. The problem? Our audience, mainly women, weren’t into that genre. Despite it being well executed, it didn’t either make our service more sticky nor drum up more buzz for their brand.
The lesson? At the end of the day, only go ahead with a partnership if it really makes sense at both emotional and business level.
If head and heart line up, chances are it’s worth to pursue. Good luck!
What’s been your experience? I’d love to hear: or