It is a phrase I use on a daily basis, because I find it so important to everything.

You have to make people care: to fill out a form, visit a website, give their details to you, make that event, try that new activity.

I see it as a scale of: not caring, which leads into a caring cutover point which leads into people caring.

If people don’t care about this thing you are doing, then they won’t interact.

If they do, they will.

To me, it is as simple as that.

But making them care can be hard.

You have to really understand them to know what will make them care.

Today, I saw a new website launched to the Electorial Commission trying to get people to register to vote.

http://www.thecommentator.com/article/3258/electoral_commission_spends_55_000_on_ice_cream_scoops_and_cats

I struggle to see how this makes people care about registering to vote.

If people don’t care, they won’t do.

Make them care.

Looking back at my twitter history (mainly links to GIFs and frivolous comments) and delicious (nothing of substance) I turned to my Readability list (just articles).

I’ve done posts in the past (https://paulrandall.com/2010/01/23/condensed-type-1/ and https://paulrandall.com/2012/04/25/linkspiration/) that collate what I have consumed over the week, and I think it is much better way of documenting what is going on, because otherwise I just forget!

I watched a talk by Gavin Strange (@jamfactory) http://vimeo.com/61248847 where he had a page full of things that interested/inpired him recently. Braun watches, old sticker packets and wicked-awesome camera rigs. I’d like to play with creating one of these a week/month as a visual representation for the things that I have consumed.

“My job at the time involved an incredibly simple transaction: I traded my time for a set hourly wage. They asked nothing more.

Turns out, this was a big problem. I didn’t want to put in only the minimum required hours, nor, did I feel the need to vacate my chair at the exact moment the buzzer rang. I was looking to turn the position into something bigger. I wanted to get my hands dirty and make things; to learn everything I could; to imagine how we could make that place the very best it could be. I wanted to feel like I was a part of something.

But that, generally, isn’t how jobs work. I was a simple cog, and they don’t ask cogs to do bigger things.”

http://www.ideasonideas.com/2012/09/so-you-want-a-creative-job/

According to Wikipedia, they are:

small piece(s) of data sent from a website and stored in a user’s web browser while a user is browsing a website. When the user browses the same website in the future, the data stored in the cookie can be retrieved by the website to notify the website of the user’s previous activity.

But why call them cookies?

Well, nobody seems to know – at least there is a lot of debate about it.

So if we were tasked with rebranding cookies, so that they had a little more meaning what would the alternatives be?

How about a reference stub or just stub.

The part of a check, receipt, ticket, or other document torn off and kept as a record.

If you were tasked with renaming cookies, what would you call them? Leave a comment, or tweet with the hastag #newnameforcookies

When synced with my phone or iPad I can pick up my ‘to read’ list in a nice readable format.

My only problem, I queued up too many articles. With near 200 articles to read, where do you start?

This happens a lot. You start a new service with the best of intentions – use it too much and find you are back to square one with too much information (I decided to stop catching up on my RSS feeds after it reached 1000+).

The solution? This weekend I deleted, skim-read and perused over 100 to get my list back down to 40ish. Much more manageable.

But it’ll happen again, that’s a given. So is there a solution to the problem? Here are a couple of suggestions.

• Group 1-3 minute articles in a ‘Quick reads‘ section
• Articles 10 minutes or more go into ‘Long reads‘
• Articles from the same website get grouped ‘Related reads‘
• ‘Favourite reads‘ is a previously saved article. If you re-read an article you enjoyed you are likely to stay on the service and read something similar in your unread queue.

I guess this is all down to using the product more; creating a richer experience so that the list doesn’t get large again, because I use it more often.

Otherwise it’ll be like my RSS feeds. After 1000+ I’ll stop looking.

But as soon as you let the client call the shots, you are a pixel pusher, bowing to the whims of a client.

Thing is, if you don’t tell them, they won’t know (what not to do). Laying out the rules early will avoid things like this being said:

• I’ll know it when I see it.
• I think we’re nearly there.
• I showed it to my son/daughter and they suggested…
• I’m not feeling it yet.

You get the point.

The thing is, the design process should be a collaborative one, just make sure you lay out what work the client should be doing.

Clients know their business better than you do.
You know design better they they do.

With this quick understanding, make sure that the client makes the business decisions, and you make the design decisions.

There’s a good reason for it; It gives you the opportunity to demonstrate how you solved the problem. You would be marked on the working out, and not just the final answer.

It’s the same with design work, if you can’t describe how (and more importantly why) things are done a particular way, then the client should (quite rightly) think of it as just a guess.

Being able to do this successfully is probably the most important skill to learn in client services, because without this, you risk a client reject or dismiss good ideas, simply because they can’t see how you worked out the answer.

1. Write a post called Ideas of March.
2. Write about why you like blogs.
3. If you don’t already blog regularly, pledge to blog more the rest of the month.
4. Share your thoughts on Twitter with the #ideasofmarch hashtag.

Point 1, done.

Why I like blogs, and blogging

I believe that writing about something helps you to understand it in a different way; in much the same way having to give a presentation or explaining a topic to someone means articulating the topic.

This skills is vital for any professional.

If there is one thing I have learnt whilst being a designer, it is that articulating yourself well makes you a better designer. Explaining designs to a client, boss, or colleague is key. In the past I wouldn’t have been able to describe why I created something the way I did; I felt (wrongly) that talking about it was art bollocks and not necessary.

Describing a design is as important as designing it well.

What I wasn’t aware of was all the thoughts that went through my head whilst creating a design. A client can’t see this, and so you have to articulate yourself to describe your design process. With the client aware of all the decisions made, they are more likely to ‘buy in’ to your work, as they’ve been taken on the same journey.

Back to this blog…

Never thinking of myself as a writer, my blog includes things that I want to explore in more detail. Blogging allows me to collect my thoughts and put it out there, primarily for myself, and secondly for anyone who is interested.

But my blog has never been an advert for myself. If there is one thing I have learnt from my website it is that the most lovingly crafted posts fall by the wayside in favour of posts that were created on a whim, but I don’t write for traffic, and neither should you. Don’t go for the cheap shot of a red-top headline when your content deserves better.

Writing more

In my professional career, i’ve set myself a few goals. Some of which have happened already, like being featured in .net magazine but to have my writing published somehow is still on the list, waiting to be ticked off.

A few people I follow on Twitter have wrote books. Their tweets during the writing phase make it sound like a kind of literary torture, but having your work in print, being able to buy it in the shops, and being in Amazon must be quite a cool feeling.

Don’t just say it then, do it!

In the coming months, lots of things will be changing for me, and I hope to be able to delve deeper into the process of designing, in particular for the web. It’s an exciting time with lots of innovations to come and I want blogging to become an integrated part of my work.

So I’m not going to get hung up on the design of my site (yes, it is the default WordPress theme at the moment) because people will hopefully be reading these posts on Readability, Instapaper, or an RSS reader, but I do hope to develop my site to include more development work, code examples, snippets and other tools in the near future.

Now it’s your turn…

If this post, or the Ideas of March concept has spurred you on to write your own, let me know in the comments and I’ll make sure I link to it.

As it turned out, sharing was not broken. Sharing was working fine and dandy, Google just wasn’t part of it. People were sharing all around us and seemed quite happy. A user exodus from Facebook never materialized. I couldn’t even get my own teenage daughter to look at Google+ twice, “social isn’t a product,” she told me after I gave her a demo, “social is people and the people are on Facebook.” Google was the rich kid who, after having discovered he wasn’t invited to the party, built his own party in retaliation. The fact that no one came to Google’s party became the elephant in the room.

I think this ex-Googler has it spot on: You can’t force people to use your stuff. How many of us have a Google account? And how many times did we use Google Wave, or Google+?

Giving Google some credit, they saw Google Wave was a complete flop and scrapped it; something Kevin Rose’s company Milk did today with Oink. Having only launched 3 months ago, they have decided to shut the service down for good.

Scrapping things takes guts (and a ton of money) but ultimately admitting you are wrong and moving on is a better thing to do then leaving it to turn into a ghost town.

On 23rd February the first ever Responsive Summit takes place in London. Thinkers and do-ers in the field of responsive web design get around a table to discuss how to make this easier for all of us.

http://responsivesummit.com/

This I can guarantee will enhance how we build sites in the coming years. Some of the questions I have are:

How we can serve up the right images for the right device?

Because of the responsive nature, images usually have to be created larger to compensate. I am wary of this because there have been discussions about increased page bloat and serving up multiple versions.

Further reading:

• http://www.alistapart.com/articles/responsive-images-how-they-almost-worked-and-what-we-need/

Is there still a place for ‘mobile’ versions of websites?

With the emergence of responsive and adaptive designs, do ‘mobile’ versions still have a place on the web?

How do we ‘sell’ responsive design to clients?

This is of course, down to the agencies and salespeople themselves. High profile responsive sites, such as http://bostonglobe.com/ have helped, but clients still need to be educated. That is our job.

There is, naturally a slightly higher cost to designing responsive sites, but this is minimal and when compared to separate desktop and mobile versions is usually a lot more cost effective.

How do we present responsive designs to the client?

Designs are typically served up in visual format, most proabably created in Photoshop or Illustrator first. Is there a good way of presenting these to the client whilst conveying the concept? Which leads on to…

Are we going to abandon Photoshop?

Is Photoshop even the right tool to design nowadays. With frameworks and tools available to create demos relatively quickly will this be the standard in the coming years?

Should we still be designing in pixels?

With the emergence of the retina display iPad and multiple resolution devices, have pixels had their day? Has the concept of pixel-perfect designs gone in favour of percentage and em-based designs?

Any other questions?

You can submit your own questions before the discussion takes place on the 23^rd Feb by going to the website http://responsivesummit.com/.