Posts

May 04, 09:59 AM

Was enjoying a late night celebratory whisky with a friend late last night at yet another awesome Kreuzberg bar, when the bartender put on the album 'Thirteen Off My Hook' by Dead Moon. Pretty mind-blowing. Check out this review.

Two other cracking tunes from the album are here and here.

Permalink | Leave a comment  »

April 04, 06:08 AM

Liking the photography, vibe and inside Berlin tips of sugarhigh.

Permalink | Leave a comment  »

March 29, 09:33 AM

So my German is still terrible and I wanted to know what my friend Mario was talking about. So I turned to the indispensable Google Translate. Which I noticed now has a button where someone reads the translation out loud!

So in case you don't speak German, here is Google's version of Mario's Facebook status update!

Memo_(1).m4a Listen on Posterous

Permalink | Leave a comment  »

March 27, 12:16 PM

Haha. Just saw this comment on the Youtube video:

Permalink | Leave a comment  »

March 19, 06:56 AM

Check out the launch video.. it is indeed the Tweek team in some pretty damn good acting performances!

Read more about the launch on GigaOM.

Donwload the iPad app [iTunes].

Permalink | Leave a comment  »

March 17, 01:45 PM

A particularly satisfying closing line:

"... given the paucity of fresh ideas in today’s recruitment industry, the job site with no listings may be a concept whose time has come."

Read the whole article.

Permalink | Leave a comment  »

March 14, 07:49 AM

For starters you can create your own rich cultural profile (like the demo one above).

Showing the real you takes a bit of time so grab a coffee or tea or Club Mate ;).

Join the beta and create your rich profile here.

If you're a company interested in applying to the beta, head here.

Permalink | Leave a comment  »

March 12, 09:29 AM

So my friend Carla and I are looking for an apartment in Berlin. This can be such a tedious and difficult process that we decided to try and have a little fun with it.

Also, we know that the best places are not ones advertised on rental sites, they're the ones buried somewhere in your social networks.

Inspired by (and ever so gently mocking) Kickstarter, we came up with...

... HausStarter!

(check it out, if only to laugh at the 'rewards' we came up with.. although they are genuine!)

Permalink | Leave a comment  »

Recent tracks

  • Keeping Warm by {u'mbid': u'8f0e0596-5a39-4bd5-9dfa-f2b12030ffdc', u'#text': u'We Were Promised Jetpacks'}
    10 months ago
  • Quiet Little Voices by {u'mbid': u'8f0e0596-5a39-4bd5-9dfa-f2b12030ffdc', u'#text': u'We Were Promised Jetpacks'}
    10 months ago
  • Laughing With a Mouth of Blood by {u'mbid': u'5334edc0-5faf-4ca5-b1df-000de3e1f752', u'#text': u'St. Vincent'}
    10 months ago
  • Fragile Bird - Radio Edit by {u'mbid': u'b1003bf1-25b8-41f4-a783-36060f987913', u'#text': u'City and Colour'}
    10 months ago
  • Calgary by {u'mbid': u'437a0e49-c6ae-42f6-a6c1-84f25ed366bc', u'#text': u'Bon Iver'}
    10 months ago
  • You're No Good by {u'mbid': u'ef52c079-9d84-4409-b7c2-24902dfdec1b', u'#text': u'About Group'}
    10 months ago
  • You're No Good by {u'mbid': u'ef52c079-9d84-4409-b7c2-24902dfdec1b', u'#text': u'About Group'}
    10 months ago
  • Sweet Disposition by {u'mbid': u'bb6eaced-69dd-4636-829f-9f987acc4fc3', u'#text': u'The Temper Trap'}
    10 months ago
  • Taken by {u'mbid': u'a458b4a4-bba1-4733-a920-cbf4b2295417', u'#text': u'The Waifs'}
    10 months ago
  • Conquest by {u'mbid': u'a83ec79e-bcbf-4872-92e5-8c7ca1bb8ff2', u'#text': u"Tapes 'N Tapes"}
    10 months ago

Top tracks

Posts

May 24, 08:00 PM

As one of the new recruits to the many, I thought I would introduce myself with a wee snap shot of what I have been up to in my first 2 months in the city.

 

Hello,

I  thought I'd introduce myself: I'm the new Service Designer at Made by Many.
I thought that perhaps you'd like to know what makes me a little different from the rest of the many, what makes me tick, why I'm here in the first place.

I like designing for people, with people. I love spotting details, space for opportunities and the intricate ways in which individual people move through and use a service.

Instead of telling you what projects I've been involved in and what I've been working on I thought I would share how I do it. It's usually with pen and paper (shock, I know).  I like drawing as it gves you time to think, understand the structures you are working with and the individual stories to take into consideration.
So here's a sample of bits and pieces I have been working on and explorations around this giant city I now call home, enjoy!

May 14, 08:00 PM

For the last few months, we've been working with Skype to create a new service proposition for small businesses. Today, we're launching in private beta. If you’re an entrepreneur, or working in a small business that’s looking to grow, Skype in the workspace is a place to meet potential partners, suppliers, or customers anywhere in the world. You can promote your service, send messages, talk, or meet face-to-face over Skype. And it's free. 

As with Skype in the classroom, we've designed the service in collaboration with potential users, working to solve the problems you've told us about.

And now, we’re looking for a limited number of participants to try the service and help us test, push, and stretch Skype in the workplace to its limits. Are you game?

Once you’ve joined, we’ll look to you for feedback to help us better shape our community. And as we improve the experience, we’ll open it up to more users.

We can't give away too much right now as we are still in private beta, but we are really excited about  Skype in the workplace . So, if you'd like to be part of the beta community, request an invite here
May 03, 08:00 PM

Since I joined Made by Many on March 5th as a Service Design intern, I have been involved in various interesting situations and conversations. They have propelled me into taking some time to reflect where I was before I started, to where I am now. For many reasons I feel I've been quite fortunate so far, and here I tell you why. 

Where it started

About a year and a half ago, I began reading "The Art of Innovation", by Tom Kelley, general manager of IDEO. As a student at Hyper Island, offering a strategic focus on digital advertising, my mind slowly began drifting towards fascination by IDEO's 'human' and user-led projects - it was my first encounter with an innovation company. My contributions to the OpenIDEO platform began as a way to start learning and develop my passion for designing better solutions to social problems. This book, as well as attending a lecture by the great Bruce Mau in Stockholm, was my embarkation into a journey knowing that this was the kind of field I wanted to work in. I immediately began craving for the human insights and experiences of projects, those being values I cherish. At the Bruce Mau talk I was first introduced to the concept of ‘Experience Design’, enlightening me to the fact that our whole life is a designed experience, this is true from the transport routes we use to everyday objects like the envelope, which has already been designed for us. And the best thing of it all is that we are living in a revolution of possibility:

“When we don’t apply design to ecologies that support us, we fail” Bruce Mau.

He basically was saying that we have to create the future we want to live in. His wise words remain engraved in my head today.

The importance of prototyping

Chapter 6 of The Art of Innovation is called: "Prototyping is the Shorthand of Innovation". It makes clear that there is no substitute for building things enough to try them out. The aim is to make mistakes & discoveries before you have the answers. One of the examples used is that of Amazon, started by Jeff Bezos: after quitting his Wall Street job to pursue his imagined company, his aim was to get it functional and get it out in the world. Function preceded style and editorial content. The first Amazon.com was low on graphics and animation. It loaded fast and excelled at the basics - easy to find and buy books. Very much what Made by Many practices and preaches, as Tim mentions in this blog post, about the first version of Picle app:

"We deliberately built less, because the leaner you are the easier it is to change."

Prototyping at Made by Many

Well, it seems my day dreaming about IDEO-and-Bruce-Mau-ways-of- doing-things kind of turned into reality! I’ve felt that at Made by Many we work surprisingly similarly to what I've read about IDEO, however with a dedicated approach to Agile & Lean Startup principles: "work quickly, waste little, respond to change and release working software as often as possible". One major difference I notice here at MxM is that very often they share their iterative processes (successes & failures) of working with products and services very openly. Something I haven’t really come across from other service design companies. It really seems that MxM ‘walk the talk’. I'm quite certain this is a big factor that will continue accelerating my learning process here as an intern. 

Connecting the dots

Nonetheless, at this stage I find myself putting into perspective many things I read in The Art of Innovation, very happily, in the Service Design team at Made by Many. Quite early on, during my interview phase I emphasized that I really wanted a mentor during my internship here, as I feel this would be a great way to support my learning. My wish was kindly granted and Paul Sims who leads the Service Design practice at MxM has been closely following my journey since day 1. One of the first things I noticed and learned with Paul is how he so clearly and easily dissects a Service problem through the users eyes, simultaneously clearing the way for articulations of what the solutions could be - always using diagrams. We’ve been evaluating my process here with a bi-monthly feedback session - the first one was a couple weeks ago.

The first reflection session questions and a look back at my internship objectives set out in week 1.

I am working on interesting projects and hoping my analysis has a small influence on them. That's why I feel lucky: to have found a company that allows me to put to practice a lot of service and product design issues for the first time. It's been very interesting to connect the dots in  my journey  since I became passionate about innovation up until now - where I'm prototyping in real-life, with real innovation projects. 

One thing I am really curious to witness here at MxM is how ideation for new client projects occurs. All projects I’ve been thrown into have already been ‘idealized’ and their creative direction is pretty much defined. Ideation is a really fun but also challenging process, something we really get a lot of training at Hyper Island about. Therefore I’m incredibly interested in experiencing the purely creative stamina of the great minds here, as MxM focuses a lot on sharing their processes, like their iterations within agile methodology.

Made by Many's beautiful office entrance. And of course special mention of  Strategy Dog, our office dog who provides us with so much entertainment.

Working on Picle

For the last few weeks I’ve been working on designing user journeys for the future updates of Picle app. We’ve been working through small iterations and releasing a few updates every two weeks, based on feedback gathered from users. Although I have not accompanied the evolution of Picle from pre-launch to launch as a Minimum Viable Product, until today, it is still at a stage needing prioritizing and testing. I am particularly interested in asking/observing how current users use Picle and what they dislike about it, something I have started to do this week. How could we make the experience of the 50,000 + users of Picle better? That is really exciting I think, as there is so much room for imagination when using Picle, and that seems to be part of this journey: learning through the lens of the user.

The 'Picle app wall' in the office, where we initially began to map out the future road map for Picle.

One of my most important learnings when working on future user flows, has been that I sometimes over complicate the steps involved, instead of breaking the problem down into parts, and working to simplify as much as possible. I also need to keep the user  in mind more often when designing these user journeys.  The people I’ve been working with at Made by Many and in particular within the Picle team - Alex, Adam and Will - have been really great at helping me grasp this concept.

May 03, 08:00 PM

Apologies for the radio silence on how Picle has been developing since the last release. The reason for this is that we have been wrestling internally over what Picle actually is. It sounds rather existential, but by watching how people use Picle and feedback to us, we have had to ask some deeper questions than 'How can we get more people using the app?'.

 

Here is a panaromic shot of some sketches, printouts and timeline up in the Picle den. 

Firstly  to help inform our decisions we focused on the things we have received the most feedback about. 

 
 
Player - Consumption of content 
Communities - Finding other users and sharing your content. 
 
We then explored 3 different scenarios for what Picle could evolve into. 
 
1. Optimise mobile so there is an Instagram like stream.
This would be mobile focused only and we would leave the web service.
 
2. Focus on Picleapp.com 
A webservice where you can upload and view picles on the web. More like You Tube.
 
3. Develop Picle to be a Broadcast Utility 
So the user can capture, upload and share to the world as .mov files
 
Whilst weighing these up and debating the pros and cons of each we also have to take into consideration that we are developing in a lean way and we also have to ship our client work. It would be lovely to dedicate all of our resources on getting all of the above optimised, but we must priorities and choose what features are achievable. As Tim mentioned in this post
 
Let's be really honest - we're a small product innovation and service design company with clients. Our model is to help clients make their own product and services and we're not set up to launch and operate our own.
    
We decided that focusing on just 1 of the above directions isn't the best way to use our resources, it is in fact a mixture of 1 & 2. 
The reasoning for this is that building a stream a la Instagram for the iPhone is quite a large undertaking and not the best use of our limited time and resources. We also know that with the app we have a creeping technical debt as we are adding new features onto what is essentially a prototype base. This means that we will have to do a re-write of the app fairly soon and building something of that size within the app would rack up lot more debt that we will have to deal with later. And if we were just to focus the web service, it would mean that the difficulty of sharing, finding others and the UX of the app would not be resolved.  
 
The web service's player is something that we have had a lot of feedback for. As we don't have a stream on the app yet the web service is the platform to consume the content created by other users. In order to make that consumption of content better we will be working on improving the playback for the player. There is work going on in the back to improve the gapless playback and experience that I can't show yet, but here is one of the designs we have sketched up that will improve the experience. 
 
 
To address the feedback we have received about communities we looked at what sharing currently means on the app. At the moment a user can share to Twitter, Youtube and email, but cannot find other users on the web service or app. We created this story to articulate the user's journey   
 
'As a user I want to create a log in and connect my account through Facebook + Twitter connect, or through email.'
 
Lots of sites and apps are doing this in lots of different (and there is another blogpost in the pipeline about that). The pictures below show a prototype of how we are re-working the user journey on the app so that you can find other people through Twitter and Facebook. 
 
 
These new features will enable people to find out who else is using Picle, as I have mentioned before the ability for people to discover and share is absolutely key to the experience of Picle. 
 
So that is a much distilled update from the discussions we have been having here about Picle, as ever if you have feedback don't hesitate to get in touch with us on the usual social media channels. Or if you want to email do get in touch with Ana at ana@madebymany.co.uk.     
April 26, 08:00 PM

Time for a new mural in the office, based on a famous Edward McKnight Kauffer poster design from 1919.

New office mural

The previous mural of a catherine wheel

 

First coat of white paint. Should have bought some undercoat

 

Three coats later and the catherine wheel is not giving up easily

 

(5 coats later) Transferring the new design on to the white wall

 

Design transferred. Masking out the areas where white meets yellow before painting the first colour

 

First coat of yellow

 

Three coats of yellow applied, masking added for the next colour: grey

 

Grey done. Masking applied for the final colour: black

 

Moments before the tape is removed to reveal crisp, sharp lines

 

Done.

April 19, 08:00 PM

 

So this isn't an actual Smiths lyric, but this bastardised version has been rattling around in my head while thinking about the whole Instagram + Facebook thing over the last week. In trying to figure out how I feel about it I keep returning to a couple of ideas. 

Primarily, the fragility of my relationship with services that I've grown to depend on. Somewhat crazily, I started to consider photo sharing as a kind of human right. Ok, I am not by any means saying it's on a par with access to clean water or safety from repression, but it's become an essential part of my daily life and something I derive a great deal of wellbeing from. Instagram has become the first social digital experience that I consider to be a connection between not just my friends and co-workers, but also a way of sharing with my family. This isn't the case with twitter where a. my family wouldn't have any idea what the hell I was talking about b. Would be bemused by relentless stream of techie links and in-jokes c. horror at the impotent fury with which I lead my daily existence. Whereas, Facebook is somewhere you actively avoid connecting with your mother. She might just see you as you really are.

Instagram is not just another social network, it's a core part of my lifestyle. In the same way as accessing a library, mailing a letter or buying a newspaper.  This brings me to my next point which is a critique of contemporary entrepreneurship. Whilst I greatly admire the ability of folk to get off their backsides and change the world, the problem I have is not being confident the services I love will be the same tomorrow. Now, I *completely* believe it when Mark Z states that they will care for IG like a new born kitten.
 
We think the fact that Instagram is connected to other services beyond Facebook is an important part of the experience. We plan on keeping features like the ability to post to other social networks, the ability to not share your Instagrams on Facebook if you want, and the ability to have followers and follow people separately from your friends on Facebook.
 
SO kind. Also fascinated about Facebook's process of buying IG
 
This one Zuck did alone, taking just three days for solo negotiations with Systrom.
 
boom! 
 
However, I also know that I'd be concerned if the fair-trade single-estate coffee I buy from my local independent hipster coffee house became a Nestle property. It isn't necessarily a bad thing, they can scale and reach massive new audiences etc etc, it's just not really the thing for me and I can't begrudge the owners of IG either. Who wouldn't love a billion dollars? 
 
The thing is, IG created an amazing sharing utility that caught on, but they didn't make IG the thing it is today, we did, by relentlessly demo-ing and nagging people to get on it. It's the first service I've used that created a real sense of service envy from non-iphone users. The crux is - as we become more and more reliant on our devices to mediate connections we lose touch with the artefacts created and shared. Images are often the most treasured of all. I have been trying to imagine my mother telling me she has entrusted the family albums to Big Yellow.
 
So in the light of the boom in Collaborative Consumption, I have a question that goes a step further. Should we be handing over our treasure to folk looking for a speed-boat-full-of-cash exit from services we have entrusted with our collective memory? This got me thinking about a proposition, something really simple - like Instagram - but that realigns the rockstar entrepreneur approach. When dealing with our 'common wealth' we need to change the nature of how this content is managed and handled… or maybe What would John Lewis do?
 

The crowd is the entrepreneur

 
 
Kickstarter is proof that crowdfunding works. Likewise, AirBnB is evidence that we don't need a lot of complexity to start sharing the things we own. Services like Whipcar and Zopa show peer-to-peer lending can get the glacially slow worlds of insurance and banking to support innovation. If an insurance document can be generated on the fly, seconds before you get in a stranger's car, then could a user become a part owner in a organisation simply by signing up or using micro-investment? I am talking about the idea of 'mutual' organisations. It's been around for a long time along with Friendly Societies, all precursors to the concept of the welfare state. Apply the same sort of disruptive innovation to this and we could see organisations being created in seconds owned by possibly massive communities.
 
A mutual exists with the purpose of raising funds from its membership or customers (collectively called its members), which can then be used to provide common services to all members of the organization or society. A mutual is therefore owned by, and run for the benefit of, its members - it has no external shareholders to pay in the form of dividends, and as such does not usually seek to maximize and make large profits or capital gains.
 
As users of the service we are all partners, it makes being a product advocate much more palatable. 
 

Me We Us data

 
Part of the vulnerability in the deals we make with social networks is that free-ness is paid for by a loss of control. We hand over our data as a down payment on access to the services. There isn't anything inherently bad about this if you're happy to play along. Except that maybe you aren't so happy when the new owners of your treasure start to exercise the rights stored up in the t&c's you blindly accepted. For instance, this is a fairly famous slice t&c.
 
For content that is covered by intellectual property rights, like photos and videos (IP content), you specifically give us the following permission, subject to your privacy and application settings: you grant us a non-exclusive, transferable, sub-licensable, royalty-free, worldwide license to use any IP content that you post on or in connection with Facebook (IP License). This IP License ends when you delete your IP content or your account unless your content has been shared with others, and they have not deleted it.
 
With the emphasis on *deleted* the idea of making it easy to move your data is antithetical for obvious reasons. The solution then is to not get into the data storage game. What then if our data is stored for as long as it's needed and it's made a core part of the proposition? Then our service could hold on to images for what is probably the natural sharing lifecycle. 
 
 
It's your data so the service would naturally support it being moved right along to your favorite flavour of data store via an API. Public or private. I have used Flickr for years (badly) but I've been using the brilliant IFTTT to back up Instagrams for a while. The options are there, from DropBox to iCloud. Sensibly the service would provide it's own storage (perhaps for a bit of £$) and maintain links to everyones archives for folk wanting to rummage about in dusty drawers. As a grid of APIs evolves we are going to start seeing folk building their own sharing communities in a no-code way. Apple are patenting some of the ideas now... yikes!
 

A blueprint

Sure, it's a naive idea, hard to fund, no VC chasing and no new billionaires. It's a fantasy. But it's something that I would use and support and share and nag other folk to join and get involved. I reckon that counts for a lot, after all it's mine, right?  Like the occupy movement, maybe it's an idea of it's time. I'm in if you are… @saulpims
 
 
 
April 11, 08:00 PM

Toot toot! Picle 1.0.3 is in the app store. It isn't the overhauled socially integrated version that I wrote about previously, but it does include something that we have had a lot of requests for, converting picles into movies. There are also new notification screens for uploading stories and the uploading of individual Picles has had some improvement tweeks made. 

 

To convert your Picles into MP4, create your Picle or story and then tap edit in the top right hand corner.

Then tap the share button in the bottom left.

This will bring up your options, then tap make into movie. 

Processing...

Then just tap to save it to your camera roll. 

Once tapped you will be notified that the movie is now in your camera roll. 

From the Camera Roll open up the movie and tap on the share options and you can Email, Message or Send to YouTube. 

And here is my first Picle as a YouTube video. 

We are working on a more seamless sharing experience for a later release, but for now we have managed to create a new feature that users really wanted. We really hope that you enjoy using this new feature and as ever please do let us know  if you have any feedback or feature requests. 

April 09, 08:00 PM

Instagram, I loved you.

You were my first real relationship after Twitter, and right now I feel angry and bitter about you turning your back on all the good stuff we had going. I feel shut out by you, and I can't bear the thought of you and Facebook, you know... 'together'... 

I don't know how I can keep all this hurting inside of me...

Obviously, I will get over this... I will, really. 

You're only an app after all - but that's the thing, and this is why I worry about you... you're more than an app: you are an extraordinary community, and that's what I fell in love with.

We all knew you weren't the best app ever - that was never the point with you. You connected me with my nearest and dearest, and we shared our lives, fears, loves, cats... pork...  in such a simple and wonderful way. I saw the world through their eyes. 

So, Facebook say they're going to respect you. That's good. I hope they do. But they've spent a lot of money, and they're going to want something more than just 'hanging out' with you if you know what I mean...

I wish you luck. I really do. It's great for the IG team - although surely you guys had a chance to really fuck with Facebook. It feels like we just got started. It's been really brilliant and I've enjoyed every second we've enjoyed together... but I'm out.

Goodbye my darling!

April 04, 08:00 PM

Tim took time out from SxSW to answer questions on Picle, its future developments, walking around in underwear and other things to look forward to. 

 
Thanks very much to Relax in the Air and MC Casal for the interview and kind words. 
April 03, 08:00 PM

Last night I went along to the first Ad Hoc enquiries. It's a new approach to doing an event. Someone is invited to present on a topic within the broad sphere of innovation in the public sector, a diverse mix of people are selected to come along, have supper and frankly discuss and critique the topic of the day.

 
Last night's topic was "imaginative, liberating technology" and it centred around a case study on Patchwork  presented by Ian Drysdale.

 

A quick explanation of what Patchwork is

Patchwork is a simple service that allows social workers to see contact details for other social workers working with the same family and when they last visited them. So far it's been trialed with two Local Authorities.

It's often very difficult for case workers to easily find out who else has been working with a family using existing systems. They can spend hours tracking down contact details and phoning round. This means that care isn't joined up and that it's harder to manage good working relationships with the families.  Unsurprisingly research shows that the better the relationship between families and social workers, the more likely you are to safeguard the well-being of the children.
 
In summary then, Patchwork uses technology to provide an effective solution to a known problem which in turn contributes towards achieving a much greater goal. It's great to see local government experimenting in this way, especially in an area which as as sensitive as social care.
 
There was a fair amount of debate about Patchwork's process, aims and success last night. Given the theme of the evening was "imaginative, liberating technology", much of the conversation revolved around two points - are we investing too much in technology as the agent of change and is this service really an example of "disruptive innovation"? 
 
There were a lot of diverse points of view and challenging comments but a few things stuck in my head, which I think have relevancy to anyone interested in innovation.
 

Can user needs drive disruptive innovation?

Last night one of the key themes was whether you can innovate when working within a system. If you think the status quo is fundamentally wrong but your design is driven by the needs of those working in that system, will you not end up being constricted by the very system you want to challenge?
 
Ok, I have a few thoughts on this but I'm going to start by re-iterating that I'm in favour of user-centred innovation. If you're creating a service, I think putting users needs first works.
 
Understanding user needs doesn't just mean giving people what they say they want. You have to be endlessly creative to find ways to understand what peoples' underlying needs and motivations are - that's why this process is hard. And then you have to collide your own expertise together with that understanding to develop new approaches and propositions.
 
People might be surprised by what you come up with, but if you have understood their needs well then they'll get it and, crucially, want to use it. You can innovate alone in your creative cave all you like but there's just no point if the people you are making things for won't want to use it.
 
You need to consider everyones' needs to be able to design a service well. In this case, that means children, their families, social workers, the Council and also those who have a more indirect relationship to the delivery of the service. But when you design that service you will probably find you have to carefully balance those needs with each other, and end up making some tough decisions about your priorities. At this point, I think it's helpful to always question whether the decisions you are making help you achieve your overall vision.
 
If you want to create change in a system, you need to gain the trust of the people working inside it. This means making compromises and sometimes taking smaller steps so you can show people they don't have to be afraid. You can be far more disruptive when you're working outside the system, but in the case of something like social care this is very difficult to do. 
 
Yesterday we dicussed the best possible way to innovate within a system. Where possible, work with the mavericks - identify the people who are already innovating and are most open to trying new things, help them and then lead others by their example.
 

The role of technology 

As Dustin O'Hara said:
 
we're at the point where our knowledge is being rewritten from prose to code
The tools and technologies we use in our lives now play a far greater role in how we do things than before. Ian told us an annecdote about how social workers often tailor what they ask families to the questions they have to fill out when they write it up later in the system. The technology they are using determines how they do their job, not vice versa.
 
Today we change the platforms and applications we use more and more frequently. The decisions that are made by those of us who design and develop these platforms and apps has a huge impact on how people will use them. We can embed existing behaviours or open up routes to new ones and we need to be hyper-aware of that.
 
I'm not going to go all Marshall McLuhan about it, but it's naive to think that organisations can innovate now without having technologists in the room. You want people embedded in your working culture who get this stuff or it's going to be done wrong.
 
It reminds me of an old post by James - the concept is the execution.
 
The part played by technology is of course just one piece of a much wider picture but it is an increasingly vital one, especially as 'digital services' expand beyond web and mobile. The number of digital touchpoints is proliferating in everything that we do.
 

Being innovative = lots of experiments in pursuit of a greater vision

 
Last night, someone criticised Patchwork for being "just a CRM" and Ian responded that it was acutally so much simpler than a traditional CRM, and that's what makes it special.
 
I was reminded of something we talk about a lot here - how small solutions to small problems can be much more effective than grand ideas. Innovating is often about starting lots of small experiments with many different approaches to the same problem. An environment that fosters that kind of behaviour is far more likely to come across ideas which disrupt the status quo. 
 
It helps to have a unifying vision that holds these experiments together, an overarching goal you are working towards. I came across a comment from Dave Morin lately which summed this up for me:
 
When the first version [of Path] did not work entirely, it became imperative to unlock the things that were working and become a more true version of the original vision. You must stay in the problem long enough.
I also think you need to leave a healthy amount of what Conor calls "hackable space" in the service you develop so that users can bend it to their own needs and desires. Often this is where unexpected innovation occurs. 
 
Lastly, I'm not sure who said it last night, but Patchwork definitely feels like a "yes and…" solution. The aims of the team behind it are much more ambitious than the initial service might lead you to believe. It's not the final answer to a problem but a gateway to new approaches. 
 
I know I'm biased on this side of the debate, and I really enjoyed having a critical discussion with people at Ad Hoc who have very different perspectives.
 
Huge respect to Ian for being so open about the process behind developing Patchwork, and to the team who continue to take Patchwork forward. Hope you don't mind me using you as such as extensive case study in this post, it wouldn't have made much sense without the context.
abcdefghijklmnopqrstuvwxyz abcdefghijklmnopqrstuvwxyz