One Laptop Per Child (OLPC) announced their 2010 expected delivery machine. With a price tag of $75 there will soon be no reason for the 1st world not to be able to get PC’s in the hands of every 3rd world child.
Photo thanks to OLPC on Flickr.com
One of our Saasu customers optimises Web 2.0 in it’s original meaning. He uses 88miles.net for tracking time on projects against customers and uses Saasu.com for his accounting ledger, tax and so on. 88miles and Saasu’s API’s have a little chat during the day keeping all his stuff in line, like a couple of fax machines having a banter. bidi bidi bidi beeeeep bidi bidi bidi —– Don’t you love that, it’s not humans having to do it!
What the customer actually has is a virtual application. Two distinct applications developing and enhancing separately but operating as one. Very cool.
Portfolio managers use tools to optimise placement of investments. It’s all about rigour and hard maths. So to should we optimise how we spend our time. It’s all too easy to concentrate on money, it’s in your face day in and day out, but people forget to act on the well known truth that time is money. You cannot separate the two.
Myles Eftos of Madpilot Productions built the 88miles.net connector, so a hat tip to the mad pilot. Check out his blog he shoots from the hip which is just how I like it.
Well at 4:30pm today Aust EST it was official. Vodafone wins the iPhone deal.
Do I have to accidentally drop my Blackberry?
Do I divorce my Blackberry and go for the younger more nubile SaaS enabled iPhone?
Might wait a while, let all the cool kids go first.
If I was in Jack Dorsey and Biz Stones I would be monetising their Twitter asset fast, damn fast. Sell it, open it up, whatever it takes. I think they aren’t far away from being standardised out of their current business model unless they can quickly fix their scale problems.
Driven by reliability issues on the Twitter platform, a plethora of conversation emerged this week. Bloggers and tech commentators are turning their conversation to workarounds. It’s as though the conversations and connections in Twitter have become bigger than Twitter itself. The conversation is alive and it wants to fix itself.
One example is Techcrunch’s coverage by Chris Saad of Dataportability.org. His workaround is micro bloggers using tools that are certified as compliant with a microblogging standard (posts of 140 characters and no titles). Users install complaint software on their own servers like you would blog software. He expects this to emerge from the opensource arena.
Personally I disagree, Twitter is successful because it’s easy. Easy to get started, easy to play, easy to have fun. I don’t want to install an app on a server to use a Twitter like product. I love the SaaS Twitter engine and the ecosystem of desktop and websites that have evolved around it.
It’s much like blogging where it’s just a small hassle managing a blog on a server. However, it’s still a hassle. I’d rather someone take care of that for me. My attitude to Chris’s self hosted microblogging application is the same - you’re taking my time away!
Twitter is most at risk from 3rd party application builders who have built desktop apps for Twitter. They are well positioned to build into emerging microblogging engines and thus becoming the microblogging feed readers. In much the same way RSS Readers cover many blog platforms. To do this standards are needed.
So there’s three pieces to the microblogging picture:
I expect one ‘rough’ standard across many platforms the way RSS has evolved. After all who seriously owns a 140 character field limit? How can you protect that?
Twitter the nuclear option
Stilgherrian points to a great read. I particularly loved this quote describing the potency of Twitter….”This newest of new things has only just started to rise up and flex its muscles. The street, ever watchful, will find new uses for it, uses that corporations, governments and institutions of every stripe will find incredibly distasteful, chaotic, and impossible to manage.”
Frasers Broadway
Grant Young points to this amazing (looking) bit of Green architecture. I have to agree with Grant that the various artists impressions always leave me a little skeptical. I’ll track the detail on their website with interest. Draping plants over balconies never seem to last long. Why? Because humans let them die. Let’s hope the building has systems for managing humans lack of plant care.
Microsoft Live Labs Photosynth
Photosynth is getting a run in CSI NY episode “Behold the Future”. CBS’s trailer is out but I don’t think the episode has aired yet. I first checked out the Photosynth technology mid last year when it was soft launched via the Microsoft labs blog. It’s worth a look through the tech preview on the Photosynth website - stuff of the future.
Microsoft says it has a strategy to take on Google without Yahoo. See the Wall Street Journal story or the CNET story for details.
I don’t think this is over, it’s normal to put some flushing press out there to make the seller feel a little regretful and uncomfortable.
Google is moving fast, time is against Yahoo and Microsoft. Every day that passes saw further options for Microsoft to take as an alternative strategy and possibly a cheaper strategy.
The deal is never good if both parties don’t feel a little discomfort - Yahoo was wanting a mega win. The Yahoo board should have read the shareholders intent and acted on it.
The press highlights all the problems with the deal and the analysts carve it up leaving juicy excuses lying around for Microsoft to justify not paying a higher price.
There’s plenty of frustration amongst social media commentators about the steadfast attitude of many enterprises towards the adoption of social tools. More specifically, accepting the philosophy of Enterprise 2.0.
Ross Dawson of Future Exploration Networks and Stephen Collins of AcidLabs amongst others have often commented in detail on this topic. They have pointed to some great successes and I also hear their frustrations. There is language, thinking and approaches around social tools that simply don’t fit into the corporate culture of old. Barriers need to be broken down to give people free open access to these tools, sometimes rules need to be put in place and even some situations call for access to be restricted during work hours. There isn’t a clear and general solution for all enterprises be they large or small.
I’m an advocate for open access for enterprise knowledge workers, as we do in Saasu. We’ve even built connections to social platforms from our online accounting web finance engine. We are building Enterprise 2.0 capabilities into our products and services. However I also hear the frustration of business owners and management teams who believe they are losing productivity due to Facebook and Myspace.
The main factor causing slow adoption by enterprises is productivity fear. Decades of workhorse enterprise culture has left management in fear of productivity declines from social tools. Just as SMS, Instant Messaging systems were perceived to be slowing productivity so are social networks at this early stage of their technology cycle.
Naturally they jump to no access for anyone. Well, they are totally justified to have this fear, but not to apply it to everyone unilaterally. If in managing the flow of information in tools like Facebook can only be served by blocking certain users and allowing others then that’s justified but far from ideal. Many roles in organisations may not be well served by these tools until either a self managing culture or a social communication workflow system is firmly in place that understands or controls acceptable versus unacceptable use.
I talked about restricting access to social tools some time ago in my post about Facebook in the workplace. I’ve witnessed first hand productivity costs in an enterprise environment. I still advocate restrictions and policy around access based on a role by role basis. Access to social networks should be no different to any other communications or knowledge tools used to generate productivity. Any approach to this which is not analytical and scientific in it’s assessment is simply decision making based on poor business intelligence.
Even in the Saasu business we are careful what each new system is that we adopt. It’s not about a free for all, an unequivocal license to explore for all employees. That’s nice, but an analogy springs to mind. If all the scientists choose to go out into the field because it’s fun then none of the lab work gets done.
Most importantly I’m committed to scientific rigor on the adoption of any tool in an enterprise. Anecdotal, emotional and social benefits are all important but what do the numbers also say about the social tool being employed. This is where enterprises should look at the usefulness in numbers and not just jump to conclusions. There is no substitute for at least some rough scientific checks being applied to any system, business or otherwise.
Many managers witness staff spending time working their personal Brand in Facebook. Plain and simple it often about entertainment, events and niche interest groups. So a manager in that situation adds that anecdotal evidence to their bag of reasons and moves on. That evidence is then pulled out of the bag when a decision is being made to block a tool or if thought leaders like Ross or Stephen happen to be giving advise and encouragement on adoption. The argument no doubt becomes tough in the face of this. My approach would be to:
The reality is that some jobs simply become less productive while others benefit. The job specs for a production line worker, retirement home salesperson or waste removal person probably don’t call for it. However, there is an argument that even people in those roles gain job satisfaction, get better communication with colleagues and possibly better access to management when using social platforms.
Knowledge workers should always be given access to platforms. I’ll leave it to Ross and Stephen to communicate this. Read their blogs, they are the experts.
One of Australia’s top IT Journo’s brad Howarth wrote Saasu up in his lastest Dynamic Business article on Automating Businesses. I’m a product person and often struggle trying to write how I feel about our product (I’m confident I’m not alone). Brad just seems to have the knack of communicating it without all the ‘tech’.
Many SaaS applications also feature in-built connections to other SaaS tools, quickly creating a web of interconnected applications that can automatically send data among themselves.
It was strange for me moving from a trading environment to the software as a service industry (SaaS). One of the biggest differences I noticed straight away was how sparse web pages were. Even the early web tools like online banking and broking portals were so inefficiently designed. They failed to optimise screen real estate and forced users to scroll, mouse, search, yada yada yada.
Traders Reuters/Bloomberg terminals and their spreadsheets were nearly always set to the smallest font size you could find (or read). You would use efficient fonts like Arial Narrow to try and squeeze a few more prices into the screens that surrounded you. You didn’t have the luxury of whitespace (actually it was blackspace). The vast majority of traders went for black background designs. This was interesting in itself.
In a way I miss that, it was extremely time and information efficient. It was also easier on the eyes and clearer for the mind. You had all your information laid out in front of you. It can be likened to ‘chess boarding’ your desk with all your paperwork so that you would know exactly where everything is and be able to grab it instantly.
You could see the markets and the world events unfold in realtime. You could be efficient, no transition costs, such as the need to navigate a clumsy mouse, tab through browsers, scroll down screens, drag and drop or refresh web content. Screen real estate was prime real estate. No cares for font-type, white space pixel counts and the finest navigation effects. Just jam it in was the approach so you don’t have to do a single thing except read it.
It dawned on me when I first came into the web applications space that financial markets traders had actually evolved their own designs. The result was quite different to web applications as we know them. Here’s some of my observations.
Traders designed and built their own screens
Traders designed their screen themselves, or ex-traders working for Bloomberg or Reuters helped them. Extremely user centric design, they got exactly what they wanted. There was no lost-in-translation, lost-in-budget or lost-in-design-ego issues to contend with.
Traders built their screens like engineers and not like designers would
Traders are generally left brain logical types which could be described as ‘engineering like’. So their screens were very matrix like. Information was given the best screen real estate if it was the most financially sensitive. Really important financials received the mega-font treatment.
Traders were bad designers, but did it matter?
Web designers and now usability designers tend to come from right-brain imaginative and creative backgrounds (in my experience). The traders didn’t care much for good looking screens. This wasn’t a male thing. There were plenty of female traders in the organisations I worked for and it made no difference. Design extended to font colour and that was it. A non-black background was an outlier in this crowd. Traders seemed to naturally design for screen real estate optimisation and minimal navigation choices (no navigation), so there was an element of design in usability.
I thought I’d write this post to highlight something which has influenced keeping features a click or two away in our Saasu application. It has been extended further in our next Saasu.com release with the new one-click menu.
Photo credit: Matt Seppings
Full RSS Blog Feed
Saasu.com | Blog | RSS Feed