Prototyping with data at Nokia

Prototyping with data Matt Biddulph, NokiaToday I’ll be talking about how we do new product development for Ovi at Nokia, by buildingprototypes that use real data as early as possible in the design process.Photo by Joe Shlabotnik - http://ﬂic.kr/p/6DAwoT

Whether youre a new startup looking for investment, or a team at a large company whowants the green light for a new product, nothing convinces like real running code. But howdo you solve the chicken-and-egg problem of filling your early prototype with real data?Traffic Photo by TheTruthAbout - http://flic.kr/p/59kPoKMoney Photo by borman818 - http://flic.kr/p/61LYTT

As experts in processing large datasets and interpreting charts and graphs, we may think ofour data in the same way that a Bloomberg terminal presents financial information. Butinformation visualisation alone does not make a product.http://www.flickr.com/photos/financemuseum/2200062668/

We need to communicate our understanding of the data to the rest of our product team. Weneed to be their eyes and ears in the data - translating human questions into code, and queryresults into human answers.

prototypes are boundary objectsInstead of communicating across disciplines using language from our own specialisms, weshow what we mean in real running code and designs. We prototype as early as possible, sothat we can talk in the language of the product.http://en.wikipedia.org/wiki/Boundary_object - “allow coordination without consensus asthey can allow an actors local understanding to be reframed in the context of a some widercollective activity”http://www.ﬂickr.com/photos/orinrobertjohn/159744546/

no more lorem ipsumBy incorporating analysis and data-science into product design during the prototyping phase,we avoid “lorem ipsum”, the fake text and made-up data that is often used as a placeholderin design sketches. This helps us understand real-world product use and ﬁnd problemsearlier.Photo by R.B. - http://ﬂic.kr/p/8APoN4

data problem 1:how do you use it?

Prototyping has many potential beneﬁts. We use this triangle to think about how to structureour work and make it clear what insights we are looking for in a particular project.

NoveltyPrototyping has many potential beneﬁts. We use this triangle to think about how to structureour work and make it clear what insights we are looking for in a particular project.

Novelty li ty id e FPrototyping has many potential beneﬁts. We use this triangle to think about how to structureour work and make it clear what insights we are looking for in a particular project.

Novelty De li ty sir id e ab F ilit yPrototyping has many potential beneﬁts. We use this triangle to think about how to structureour work and make it clear what insights we are looking for in a particular project.

Novelty De li ty sir id e ab F ilit y“Novelty” is when we are prototyping because we want to know if something is possible.Perhaps we’re prototyping a new kind of algorithm, or a new kind of user experience.

Novelty De li ty sir id e ab F ilit y“Fidelity” is when we are prototyping to get an in-depth feel for the quality of a ﬁnishedproduct, and to see exactly how it should work.

Novelty De li ty sir id e ab F ilit y“Desirability” is when we are prototyping to see if a product is actually something a userwould want. Even if we ﬁnd that a product is undesirable, that is still a positive result as itallows us to “fail fast” and cancel a project before wasting time on fully implementing it.

Novelty De li ty sir id e ab F ilit yMost prototypes are testing a mix of these three factors. But just like the classic “easy/fast/cheap” triangle of software quality, we ﬁnd it’s hard to build a prototype that tests all threepoints of the triangle. This is why we discuss the triangle in advance, so that we know whatwe’re working towards.

helping designers explore dataOne of the ﬁrst things we do when working with a new dataset is create internal toys - “dataexplorers” - to help us understand it.

explorers & data toysFor example, we have been investigating the possibilities of analysing the server logs of OviMaps, our mobile and web mapping app, to create a data-driven view of cities.This is a section of Ovi Maps centred on Los Angeles, California.

LA attention heatmapWe built a tool that could calculate metrics for every grid-square of the map of the world, andpresent heatmaps of that data on a city level. This view shows which map-tiles are viewedmost often in LA using Ovi Maps. It’s calculated from the server logs of our map-tile servers.You could think of it as a map of the attention our users give to each tile of LA.

LA driving heatmapThis is the same area of California, but instead of map-tile attention it shows the relativenumber of cars on the road that are using our navigation features. This gives a wholedifferent view on the city. We can see that it highlights major roads, and it’s much harder tosee where the US coastline occurs. By comparing these two heatmaps we start to understandthe meaning and the potential of these two datasets.

But of course a heatmap alone isn’t a product. This is one of the visualisation sketchesproduced by designer Tom Coates after investigating the data using the heatmap explorer.It’s much closer to something that could go into a real product.

Philip Kromer, InfochimpsFlip Kromer of Infochimps describes this process as “hitting the data with the Insight Stick.”As data scientists, one of our common tasks is to take data from almost any source and applystandard structural techniques to it without worrying too much about the domain of the data.

Dmitriy Ryaboy reminds us that the Insight Stick doesn’t have to be made solely of exciting,complex technologies. With enough data, basic grouping and counting can give massiveinsight.He continues, “I cant tell you how many times Ive seen people get excited about doing K-means and random graph walks only to discover that actually what they want is a group-by,count, and standard deviation.”

“With enough d ata you can er patterns and facts discov le counting that you using simp iscover in small data cant d ophisticated statistical using s and ML app roaches.” rasing Peter Novig on Quora paraph –Dmitriy Ryaboy http://b.qr.ae/ijdb 2GDmitriy Ryaboy reminds us that the Insight Stick doesn’t have to be made solely of exciting,complex technologies. With enough data, basic grouping and counting can give massiveinsight.He continues, “I cant tell you how many times Ive seen people get excited about doing K-means and random graph walks only to discover that actually what they want is a group-by,count, and standard deviation.”

questions and answersOnce you start to understand what the data is made of, it’s great to get into a fast cycle ofquestions and answers between designers and developers. This is where familiarity with bothyour software tools and the data itself becomes critical. It’s important to focus on creativethinking around the potential products that come from the data, and not get caught up intechnology.

“Listen to the data.”“Rather than burntime debatingpossible scenarios -work together to ndthe real answers.” —Pete Skomoroch, LinkedIn http://qr.ae/vYLr

When we started to explore the city data, we wanted ways of communicating the “feel” of acity using everyday language and products. Tom Coates asked, “can we calculate a Starbucksindex? A metric that indicates how many Starbucks cafes there are per square mile?”Using Apache Pig, I was able to answer that question with a few lines of script and a ten-minute Hadoop job. Quick answers like this mean that the creative process isn’t interruptedby the constraints of the technology.

“Products that arebuilt from data areoften constrainedin ways you didntinitially expect.” —Pete Skomoroch, LinkedIn http://qr.ae/vYLr

from explorers to products

LinkedIn’s Maps product - http://inmaps.linkedinlabs.com - is a lovely example of acompany using its core data, some smart algorithms and info-visualisation to communicateproduct possibilities. Posted on their LinkedIn Labs site, this isn’t a mainstream consumerproduct, but has done a great job of building buzz in the geek segment of their audience.The real challenge is to take great data-processing like this and use it to power a feature onthe main LinkedIn site that doesn’t confuse normal people with dots-and-arrows overload.

data problem 2:where do you get it?

nding itIf your company already has large datasets that you can use to create new products, how doyou ﬁnd it? It might be a dataset they’ve licensed from a partner. It might be the logs of anexisting product that can be analysed to extract user activity. It might be buried in abusiness-reporting data warehouse.

At Nokia in Berlin we’ve been working hard to improve our understanding of what data wealready own. Josh Devins, who is in charge of data gathering and analytics, started simple bycreating a data matrix on a wiki. Each line lists a source of data - an appserver log, a mysqldatabase, a partner datadump - and catalogues attributes such as “is it timestamped? does ithave user IDs? how frequently is it collected? what date did we start collecting it? who is theresponsible team? can I ﬁnd it on the Hadoop ﬁlesystem yet?”

faking itIf you’re working on a new product, you need a way to envisage what it’s going to feel likewhen it’s got a million users and the data is ﬂowing through it. In this case, you probablydon’t have the datasets you need already available in your organisation.

In this case, we turn to open web APIs and datasets. Working on an app with a social graph?Create dummy users from a crawl of the Facebook or Twitter social graph APIs. Need to ﬁll itwith fake user content? Use real blog posts via RSS feeds to seed the CMS.http://www.blogperfume.com/new-27-circular-social-media-icons-in-3-sizes/

When we worked on a prototype of improving a mobile photo gallery with social and dataintelligence features, we realised that the demo would be more powerful if it was full of yourown pictures. So we made a prototype that starts by asking you to log into your Flickraccount, and then populates itself with your own photos.

“just because the ‘grain’ isn’t always as obvious as with wood doesn’t mean it’s not there, it just takes different skills to nd it.” —Dan Catt, The GuardianEverything we’ve talked about in this presentation brings a data way of thinking to existingprocesses and skills. Working with real data takes practice and experience.

“We threw out custom non- hadoop code that was faster.” —Jay Kreps, LinkedInThink about how you use your data-processing tools when you prototype. Don’t let themslow you down. Optimise for creativity and speed, not technical perfection.http://www.ﬂickr.com/photos/russss/3630698158/

summing up...all points of the triangle helped by dataknow what data is available to you, inside and outside your teamuse real data to unite design and tech, contextualise prototypes, answer questions, ﬁndproblems early

Novelty De li ty sir id e abF ilit y

Novelty real data helps all points of the triangle ty De eli sirFid ab ilit y

look for analoguesin existing datasets

explore thedata together

Thank you @mattb | matthew.bidduph@nokia.comPlease email me if this is the kind of work you’d like to be doing.Photo by Joe Shlabotnik - http://ﬂic.kr/p/6DAwoT

Noki a is hirin g! Thank you @mattb | matthew.bidduph@nokia.comPlease email me if this is the kind of work you’d like to be doing.Photo by Joe Shlabotnik - http://ﬂic.kr/p/6DAwoT

http://uxground.blogspot.com	14
http://lanyrd.com	10
http://twitter.com	2
http://tumblr.iamdanw.com	2
http://www.mongodb.org	1
https://twitter.com	1
http://paper.li	1

Prototyping with data at Nokia

by Matt Biddulph on Feb 23, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

7 Embeds 31

Statistics

Prototyping with data at Nokia — Presentation Transcript