No Words – just beautiful …
As a social experiment (and because i had to reset my phone) i decided not to put any social networking applications on it.
I see people everyday, walking around so engrossed on the little world in their hand that they forget that there is a real world with real walking talking people in, all around them.
They sit in front of the tv, looking at their phone, they sit in restaurants with friends and love ones, looking at their phone. They eat, pkking at their phone.
So i figure, lets not look at our phone, don’t get me wrong i still have SN on my laptops and tablet, but my ill not be a 24/7 to my SN profiles, let see how this goes.
Youth and the internet
We all hear the parents of gifted youth excitedly telling everyone who will listen how their marvelous child already knows how to use the family Ipad, born in to the technology age their parents are amazed that their toddlers know more than they, isn’t it wonderful, talented children already ahead of the curve.
And yet we also here how kids get lost in the technology wrong, a teens foolish tweets lose her the job of youth crime commissioner fake ids luring children out to who knows where, the dubious sexting and almost as disturbing ‘ selfie’ habit.
I’m a parent who is a more than a little clued up on the tech, the web and this brave new world, and guys let me assure you your little darlings don’t have a clue. Worse, you know less.
Sure they know what buttons to press, they know which app does what and how to use it, but are you sure they are aware how they use their knew toys. take a look around, the evidence is against it.
Don’t be glib, explain to your kids that the internet is not a playground, its a tool and like any other it has a cutting edge, educate yourself so that you may educate others and learn the tools that are out there so that you can protect what is yours.
Hands up if you have a Facebook account, (or for that matter twitter or Google or another ‘free’ service) now hands up if you were one of the throng that howled with pain when Facebook changed its interface or bought Instagram or did anything else that you felt affronted by as a user, a customer.
How dare they they change your service without consulting you, after all its yours, right? Simple put, your wrong. In a discussion I had with my new boss at Felinesoft, if you use these ‘free’ service that that you, your details, your pictures activity checkins, likes and even pokes are all traded by Facebook.
You are a product, you are what the Facebooks of this world trade on, not the customer.
Remember that the next time you feel the need to post a picture of yourself in your pants drinking a glowing pink drink with an umbrella poolside at some summer party you don’t remember attending.
Don’t say we didn’t warn you
Reading Robert Scoble ‘s friend feed conversation list, he posted a notice that got some traffic regarding the use of twitter as a conversations tool
His argument was that twitter was not and should not be used as a tool for conversations, but more for ‘announcements’. Now his argument is not without merit, if you follow many followers or take your eye of your twitter app for a second then you can quickly lose the conversation thread, however he seems to be implying that you should not use twitter in this way, full stop. Problem with that is his argument suggests that there is a set if rules for using twitter and these should be followed by all users, this is wrong, for twitter and all other products or services being developed. There are no rules there are however behavious patterns that define how users adapt a service to their needs, and its this that makes the web(2.0?).
If twitter or any service is to survive then it has to evolve, just like people.
Argument is as follows:
As you build a site( for site you can substitute webapp /service /product/whatever but I’ll use app for ease of use) you have an idea of the users that you need to talk to. If your smart you talk to these users and ask them what they want, try to use this to identify what they actually need and design a solution that fits this need, you of course test it with representatives of these users and make adaptations to the site before go live.
On go-live you are confident you have a successful site in the making and sit back, update content maybe add functionality in later phases of the site as per the development roadmap and generally watch the site grow.
Trouble is the users evolve, they mature in their use of your site , their needs develop as they get comfortable they develop new ways of using the what you have delivered in ways you never considered, and, if you don’t adapt to these needs then your site will whither and die, and your visitors find a new site that fits their new behaviour better.
you need to monitor how your users try to *abuse* the functionality you have supplied and adapt the site to make it easier for them to achieve their new activity.
This is <tech-volution /> (yes i made this up)
So back to the original point, and Roberts assumption that Twitter is to say that twitter is not for conversations, this is a mistake and I’m afraid, wrong, if this where true then no-one would use twitter for conversations, the problems with using the service in this way would make it unusable, in the same way as you don’t use a fork to eat soup.
Twitter may not be ideal for conversations , it may be tricky but its not wrong, and it would not surprise me to hear that the folks at twitter are planning spend some of their $50 million to release new features for the service that allows threading for conversations, that is if tweetdeck or twhirl (insert twitter client here) don’t get there first,
In a recent discussion / interview with a member of the Eduserv research group (previously known as (Eduserv foundation) which focused on a study soon to be proposed into CSM and HEI, I was asked to define the ‘user requirements’ for content management system project.
Users.., what are ‘users’ when discussing CMS requirements, and are they the same as website users?
In a traditional sense users are often regarded as the ‘users’ of a website, UX professionals talk about user testing and user centered design processes, but when it comes to CMS the user can be seen as the ‘site; user or the CMS user, each with very different needs and thus differing impacts on your requirements exercise. It’s important therefore to make sure that you are talking about the same ‘audience’ and that you accurately address their needs.
Site users, (visitors) need to be able to find information quickly and need navigation accessible content, they may ‘use’ the functions of the site in the process of finding content but referring to them as users (in the CMS context) clutters the message. Navigation, clarity, language findability structure and design make for the site visitors experience.
The needs of the CMS user however is concerned with editing interfaces, categorization and linking, they need workflow and accessibility checkers, they need to know who did what when and how, the kind of stuff that CMS (WCMS) should do well.
Most of the time the description of the feature needed will be itself explanatory. However you should never allow ambiguity and assumption into your requirements study. (Similarly words such as ‘solution’ ‘system’ and ‘service’ should also be avoided in this context.
“The solution should be accessible to users with disability”…means what exactly?
Then we get to audiences, now these are different again. An audience, in this instance, could be defined as category or group of users (or visitors) who share characteristics, interests or experience levels.
Parents, teaches and students are all audience types, as a parent I am a visitor to my boys school website. The teacher’s who create the site with their CMS is a CMS User,
Users, visitors and Audiences are therefore interlinked, but have differing views of the solution you are defining, if you are going to meet these needs you need to make sure that you and your project sponsor / customer have a shared understanding of these differences and needs to avoid the ambiguities and, even worse assumptions that add risk to your project.