It’s this time of the year again! It’s the BIG BOWL GAME DAY! Tonight the New England Patriots will fight against Seattle Seahawks. While we at Pidoco are still placing our bets and discussing which company will place the most awesome ad, we also noticed some similarities between creating a prototype and playing the perfect match. Wait, you think football and prototyping don’t have anything in common? Think again because as a “prototyper” you can learn a lot from it. Here are our Top 5!
1. Tactical creativity
Whether it’s matching day or the day you start creating a prototype, you need to have an idea of what you are going to do and what the final result should look like. So you start scribbling down your ideas for a prototype. This will help you to get a clearer structure of your prototype and its content. Whether a greenhorn or an expert, you, your product manager or whoever is in charge have to find out if there are already competitors out there and what their products’ core features are like. From that, you can chart out your strengths and figure out how to improve potential weaknesses.
Develop a creative tactic
The coaches Bill Belichick of the New England Patriots and Pete Carroll of the Seattle Seahawks can, of course, draw back on a very long NFL career; nevertheless they have to do their homework as well and do what every coach has to do: find the strengths and weaknesses of their teams, train players to improve their skills, build up strong offensive and defensive lines, encourage the players and of course, finally create the perfect tactic for the final matching day by monitoring every little step of the opponent.
Whether you start from scratch or are already an experienced superstar, all the creativity and tactics are important, but you need to be able to adapt to suddenly arising chances and maybe even rebounds. It’s an ongoing iterative process.
2. Collaborative sportsmanship
Best results can only be achieved when working together. That’s nothing new, but something really important. Of course, you need a coach, a quarterback or a designer, product manager etc. to strive forward, but creating a competitive product is like building a strong backfield – it only becomes a bastion if you really work together.
Collaborate with your team members
When prototyping you can try sharing your prototype with others to get feedback or work on solutions collaboratively in real-time. So, you see … whether you are part of the Patriots or the Seahawks or of an app development team, it’s all about exchanging ideas and talking about strategy, tactics and all the many details.
3. Impressive interactions
Rather than coming along with fancy details, especially early prototypes can fully rely on simplicity, simple colors, simple structures and even placeholders instead of detailed content. Nevertheless this doesn’t mean that you have to leave out important, unique core elements. In prototypes you might create a simple black and white wireframe, but since especially mobile applications are about interactions, touch gestures or screen transitions, exactly those interactions shouldn’t be ignored. So with only a few clicks, add interactions to an element (e.g. a swipe gesture), define corresponding system reactions (e.g. a pop-up opens) and voilà, you breathe new life into your simple prototype and impress without much effort.
Bet on interactivity
It’s the same with a football match. Honestly, we all know this and have seen quite a lot of those matches: They didn’t look that nice and mainly showed very simple maneuvers or “impressed” with rather unspectacular moves over quite a long time. But there are those moments, when the crazy snap frenzy suddenly starts and e.g. Tom Brady or Russell Wilson see their chance, get the ball from the center, immediately plan a spectacular move, outmaneuver the opponents defense or pitch the ball backwards to a running back or even crazier run the ball themselves and serve a nice quarterback sneak. A perfect way to describe an action-reaction-chain consisting of “only” a few moves!
Football matches are not only about tactics, collaborating and interacting. Of course they are just as much about entertainment! Certainly, the teams will present themselves in the best possible way and will work extremely hard to finally get the Vince Lombardi Trophy. However, the Super Sunday, especially for the viewers, is also about being entertained by the expensive commercials excelling themselves, and of course by the music acts appearing during pre-game or halftime ceremonies. It’s all about having the perfect night, fun and the perfect presentation of everyone’s skills.
The same applies for your prototype. Once you are done with all the preparations and ready to present it to the decision makers it’s often all about top or flop. So you need to impress. And you can easily do this by simulating your prototype on the device it should finally be used on. Let’s say, you created a prototype to be used on a tablet, well simply simulate it on one! Even better: if you built a location-based service app, you could embed a map into your prototype and set the interaction such that e. g. a pop-up window appears on the screen once you have reached a specific spot. So why not invite your audience for a stroll around the city and they will certainly be impressed by your new LBS app. Or add some music for instance to add to the entertainment.
5. Result-oriented discussions
To be honest, the more people are involved, the more opinions rise up. Sometimes this can be really awkward and it’s not always easy to deal with it, especially if you don’t or can’t agree on something. As a prototyper collaborating with various people you are certainly familiar with discussions about things like the size of a button, the position of an image or even the shade of green. But especially when simulating your prototype, everybody can get a realistic impression of the final result and you can steer discussions by focussing your prototype on the most critical aspects of the project. Sometimes less is more, and eventually the perfect position and size are found. You can take this even further: why not invite test users to work with your prototype and ask for their feedback and the experience they had? The aim should be clear: result-oriented discussions will definitely help you create a better product.
Taking home the Vince Lombardi Trophy is THE goal for the New England Patriots and Seattle Seahawks on Sunday. We can all guess how many discussions on tactics, analyses etc. this involves.
Discuss the results (Photo by Johntex, 2005. under the terms of the GNU Free Documentation License Version1.2)
No matter which move is made, which player makes the deciding touchdown, everything will be strictly monitored and heavily commented on especially by the fans. We are all quite good at that, aren’t we? But even if we root for the same team, it doesn’t necessarily mean that we have the same opinion, and we can certainly support different tactics or know more effective moves.
Probably, the only way to avoid discussions is to be around people sharing your thoughts. But in this case, whether you are the coach, a team member, the prototyper, the product manager or the viewer etc. a vivid and constructive weighing of all options, what-ifs or (missed) chances and opportunities would disappear – and with them also the praise and celebration. Wouldn’t this be boring?
Finally, who will win tonight? Well, we are still undecided, but to make your choice a little easier, here are some facts on the finalists …
The finalist check: New England Patriots vs. Seattle Seahawks.
What do you think which team will win? Let us know on Twitter, Facebook or Google+.