Posts Tagged ‘experiments’
11th February 14
Posted in Experiments
As Jeremy hinted at last week, we want to make more experiments this year. One of the key things we took away from Robotify is the need for a more modest approach that genuinely allows for speed, failure, mess … experimentation, really.
So for this year, we’ve baked lightness and pace into the process itself in order, we hope, to accelerate learning, but also to have more fun.
Our ambition is to create and release 10 experiments in 2014. We will do this by adopting a ‘hit and run’ approach to the exercise. Each month we’ll pose a new question, and we’ll run a live session to generate and prototype answers. We’ll force ourselves to ship something within 25 days and with a tiny budget – the month’s experiment needs to have sailed before we agree on the next brief.
We might end up with 10 failures, but we’re certainly hoping for 10 pieces of learning, 10 horizons broached, many more new people met and at the very least, to have done something fun with something new, every month for a year.
This new framework means our focus will be on people before machines, behaviours before builds and live development, not drawn out processes. Inspiration might come from platforms, from partners or from people’s imaginative uses of technologies and the web. It could come from anywhere really, as long as it gives us an opportunity to learn.
As well as more experiments, we’re also looking for more involvement from more people. So we’re going to be inviting the whole of BBH and our partner MediaMonks to experiment with us, and a bit later this year, look at how we can go even more open source. For now, we’ll post the question up on the blog before we run the working session and welcome comments and insight. And, as we did with robotify.me, we’ll make the learning process itself transparent, with briefs, ideas, and development being posted in (almost) real time on our new experiments platform.
This new home for Labs experiments is thinky.do. From now on, this is where anyone interested can follow the erratic ballads of Labs experiments, though of course we will point at new thinky.do activities from here and from our twitter every now and again.
If you head there now, you’ll see that we’ve put up our question for the first experiment of the year. It’s all to do with crypto currencies and the creation of value. We’re holding our first live session this afternoon at BBH in London, so expect to hear more very soon.
We’re excited about switching up a gear in experimentation and we’re definitely curious to see what happens. If you’d be interested in joining us for the ride, please drop a note to firstname.lastname@example.org, leave a comment here or at thinky.do.
7th February 14
Posted in robotify.me
Tyrell: Would you … like to be upgraded?
Batty: I had in mind something a little more radical.
Tyrell: What … what seems to be the problem?
Blade Runner, 1982
Robotify.me – what we did, what we learned and what we’re doing now
In December 2012 we launched robotify.me, an experiment to test our hypothesis that seeing social media behaviour visualized could actually influence and change those behaviours. Perhaps, we asked ourselves, data visualisation might reveal surprising nuances of social media behaviour which might otherwise be overlooked?
How would it feel to compare activity – likes, links, retweets, checkins, photos – with the rest of the group’s data? Would the transparency of the visualisation cause any changes in social behaviour? Would inveterate retweeters be shamed into posting more original content? Could we encourage more checking in, more posting of photographs, more liking by visualising the effect that it had on the robot?
Robotify.me was also another opportunity to learn and experiment with process. Could we create a service rather than a campaign? Could we work fast and lean and create a mvp? Could we create a product without a brief, without a client?
A little over a year on, the answers to some of these questions are in. The first thing to say is thanks. Thanks to the team who worked so hard (and gave their time so generously) on robotify.me and thanks to everyone who took part in this project. Thousands of you created robots and we loved seeing the project come to life, reading the tweets, hearing your thoughts and feedback on this thing we’d made.
Much of what we learned is displayed in the infographics accompanying this post and some of our early learnings were incorporated into changes we made live on the robotify site in the early go-live days and weeks. Perhaps our major learning was to do with storytelling – if we wanted people to learn a little about themselves we should, perhaps, have shown more, and told more explicitly. Knowing when to intrigue and when to explain is something we will take with us in the future.
We also learned that when you have a team with demanding day jobs it’s impossible to schedule daily scrums and the focus and scheduling required for an iterative workflow are not easily applied to side projects. When we plan future Labs experiments (and more on that very, very soon) we’ll definitely be thinking about the sorts of projects that lend themselves to a leaner approach. Stretch is good, but restraints will help define scope from the very beginning.
So, we’re going to be pulling down the shutters on this particular garage and disassembling the robotifier, cleaning down the work surfaces and wiping down the whiteboard in preparation for a new swathe of Labs experiments, robotify learnings fresh in our minds. We’ll be keeping the service up in it’s current form for another month, so you can still create a new robot, revisit your robot mirror-self or download and print out your robots for your digital files.
Finally, thanks again for supporting our Robotify.me experiment.
Bleep. And out.
26th April 12
Posted in makings
Author: James Mitchell, Strategist, BBH & BBH Labs
Every once in a while at Labs, we like, no, need to get our hands dirty. Oily, even. We like to make stuff that we can learn from – learn from the making of and learn from the interactions with. Robotify.me is one such experiment. And unlike most of our output, we’re going to share its whole gestation with you. Partly because we’re too excited not to, partly because we want you to shape the product.
Product? Yes. With robotify.me, we want to put a personal digital robot into the hands of every person who wants one.
Of all the companions you could make, why a robot? Why not a plant, an animal, even a pet rock? Because of the line robots walk (or fly), between the artificial and the human. They are not alive, but in the way the act we try to give them life. And this has bearing on the other half of the project.
Since our first aol email addresses, our first Second Life avatars, our geocities and myspace profiles, our first (and second) anonymous twitter accounts and our weavrs, we’ve been talking about the difference between a person, and an online persona. Is there one? We hope robotify will tell us, because the other trick is this: the characteristics and features of your robot will be determined entirely and exclusively by your social network data. So if you post lots of pictures on instagram, your robot might grow a telephoto lens in its belly. If you click lots of odd links, you might develop tank tracks – negotiating rough digital terrain, you see.
That’s the simplest version. Gradually we want to progress to a version with a robot that changes and grows as you do – a living marker of your data journey. We’re even hoping that, over time, robots will be able to interact. Robosociety, if you will. But that’s the nature of the agile process we’re using – aside from the vision, there are lots of assumptions layered on top of each other, and we’d like a willing army of beta pioneers to help slice through these assumptions and get to the robotify.me that you want.
At the same time, we’d like to experiment with a slightly altered way of communicating – so for the 50s radio-style version of the Robotify story, just slip on some headphones and click play.
Hang on. You said something about beta users?
Yes, labs reader. That’s you. We’re making the beta right now – signup at http://signup.robotify.me. If there’s anything you want to see, anything you’ve always wanted to know about your social data, or anything else you think we should look at, let us know below…
28th October 11
Authors: Gabor Szalatnyai (Creative Technology) & James Mitchell (Strategy), BBH London & BBH Labs
Here at Labs, we make a lot of stuff for other people and brands, but, now and then, we like to build experiments – additional stuff we love so much, we take extra time and pull late nights to see it done. We do this because sometimes, we want to test a theory, because we want to test our capabilities, and because we want to make something cool.
But this role is about more than the build. We’ll work iteratively on this, so we’ll be testing and learning as we go. This means you’ll be working with the team to prototype, test, bend and break – modifying and bettering the experiment at every stage. We’ll expect you to have a major impact on the idea itself. You’ll have the freedom to implement any technical solution that solves the problem, to work with the entire team to make sure the thing doesn’t just happen, but happens better.
Why work with us? Because we hope you’ll agree the project is cool, the team is a diverse and interesting one, and the use of data is, as far as we know, something that’s never been tried before. And, at the end of it all, you’ll get to put your name against something very special.
To apply, please send a nice message (with your GitHub username and/or some work) to **email@example.com**, and we’ll have a chat about what we’re trying to build. If you have any more questions, drop them in the comments. Thanks!