This Month
| September 2008 |
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
|
|
1
|
2
|
3
|
4
|
5
|
6
|
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
|
28
|
29
|
30
|
|
Tuesday, September 30

Protoshare - a collaborative way to produce clickable wireframes.
by
Chris Noble
on Tue 30 Sep 2008 23:26 BST
Sometime last year I came across a little article by the Newfangled Web Factory about how they used “Grayscreen Prototypes” - clickable wireframes with some of the elements, such as menus, and text-links live. “That’s a nice idea” I thought, before deciding to leave the mock-ups to the Web developers, working from my specs and wireframes.
Well, now a tool has popped up which promises to anyone capable of creating a wireframe, to turn it into a prototype with enough functionality built in so that a client can experiment with the navigation scheme and get a real feel for how the site works.
It was a commenter to this blog - indeed the only comment in the life of this blog so far - which asked whether I had looked at Protoshare, a relatively new online tool from Site9. I hadn't. But when 100% of your active audience suggests something, it seems churlish not to take a peek.
To get a decent understanding of what Protoshare is all about, it is worth looking at the tutorial videos. It's a slick subscription-based Web tool that allows developers to:
1. Create hierarchical lists of pages (aka site maps) and then: 2. Create wire-frame clickable mock-ups with working menus etc. for each page 3. Set up a collaborative discussion, where developers and clients can discuss and annotate the wireframes.
Overall, I like it. I have some niggles with usability, the pricing model and the support structure, but hopefully these can be ironed out as the product matures. There’s a 30 day free trial - give it a go. Though beware, you have to enter your credit card details and remember to send an e-mail asking to cancel, if you don’t want to be billed.
Being a curmudgeon, I’m going to focus on my dislikes first. One problem with building any drag-and-drop wireframe tool is the constant demand from users for additional drag-and-drop widgets. Some user is always going to want to place a volume-slider, or some such into their mock-up. That user is me. Even so, s it stands, Protoshare’s selection feels a little thin - there are no horizontal or vertical rules, no support for tabbed navigation and no palette of little icons, to let you (say) drop in an RSS feed button. Of course it’s possible to insert your own graphic assets into a wireframe, but who wants to bother with that, for fairly common items.
Similarly, styling of textual elements is a mixed bag. If you create a box to hold rich-text, Protoshare gives you the works - font, size, colour, style can all be selected on a per-word basis. However, if you want to make the text of your bread-crumb trail smaller, or want to decrease the font-size of your navigation bar so that the text doesn’t wrap, you’re on your own. It's true that Protoshare lets you attach custom CSS styles to elements to control all aspects of their look and feel, but it doesn’t give you any CSS tools, just a ‘type your CSS in here’ page. As a lazy IA, I don’t want to bother with code a CSS style to make my text fit on screen.
And while entering the initial page hierarchy for a new site is a joy, why does the software have to make me mouse across to a separate Title box for every single new page? That gets irksome after the twentieth time. The box should be pre-selected as a page is created since the first thing that most people want to do is rename it.

On the other hand the collaboration system looks very nicely designed. Pages can have discussions attached to them and those discussions can have draggable push-pins associated with them (as illustrated above) to make it easy to see which part of the page they refer to. Each user can opt in and out of notifications when a discussion is initiated or added to. Alongside the push-pins, ‘specification’ markers can be added. These act as ‘callouts’ giving the developer a place to explain the functionality of a particular page element.
Since this is a Web-hosted application, pricing is per licensed user per month. In effect this makes it a good tool for two groups:
1. An in-house enterprise team, which is developing a new site and may need the system intensively for a month or six, after which the subscription can be jettisoned 2. The dedicated high-end Web development house, which has a number of projects continuously on the go.
It is not particularly attractive to consultants, for whom prototyping is a task that crops up every few months, but stop-start licensers are unlikely to be on Protoshare’s list of top customers.
One area where the company really should move to make improvements, however is support. This is a Web-based tool, built on the premise that collaboration is important, and yet there is little effort to collaborate with customers. At this stage of the product’s life-cycle, I would expect to see a buzzing discussion board with the developers asking for feedback, finding out what the users’ priorities for improvement are and telling the users what developments are coming next. At the very least these online discussions act as a place for users to self-support and share hints and tips. Instead there’s a blog with comments turned off, and a rather thin FAQ. If you have a question, the e-mail form simply promises that a Customer Service representative will get back to you.
Site9’s marcoms team is missing a trick here, with little additional effort they could be collecting data on how to continuously improve their offering, cementing the engagement of their existing user-base and impressing potential visitors with their responsiveness to customers. Perhaps they are just concentrating on super-servicing the super-big accounts, but even they will have "how do I" questions that are often best answered by fellow users.
Post Scriptum. A couple of days after writing this entry Dave DeAngelis, Site9's Director of Product Experience got in touch to say that the company is planning to improve it's Web support in November. He also pointed out that the mouse-averse can tab across to the Title field when naming a page, but likes the suggestion of leaving the page name pre-selected on creation.
Tuesday, September 16

Dropbox in the enterprise? Not just yet.
by
Chris Noble
on Tue 16 Sep 2008 12:36 BST
It's been in invite-only beta since late last year, and I've been playing with it for the last 3 months. But now Dropbox, the "let's make file-syncing and sharing really simple" company has finally announced that it is open for business. The announcement caused quite a stir on blogs and discussion boards, with generally very positive response. But should you use it for business purposes? The idea is deceptively simple. Install the software - available for Mac, Windows and now Linux and it creates an ordinary-looking folder/directory in your home directory called, yes that's right: dropbox. Any files or folders you dump in there can be shared and synced with other drop-box users, or shared via a Web URL with non drop-box users. How does it work? Files in the dropbox are pushed over the Internet to the company's system and placed on Amazon S3-based back-end storage. The system has a variety of uses and what sets it apart is the elegant implementation and attention to detail. At it's most basic the system you to backup some files (2GB storage is free), and to access them when travelling. Alternatively, if you have multiple machines, you can keep the contents of their respective dropboxes in sync, by associating the machines with the same drop-box account. Sharing files is similarly easy and with others comes in a variety of flavours. Any file placed within the Public sub-folder is shareable over the Web by right clicking on the file and selecting 'Copy public link'. For more control, folders can also be shared with selected friends or colleagues by right-clicking and selecting “Share”. This brings up a Web page into which you type the email addresses of who you want to share the folder with. When your colleagues add files to that shared folder, they automatically get downloaded to your machine. 
There are other nice little touches, such as a 'Pictures' folder, which displays in specialised gallery-form when viewed via the Web. Simply dragging photos to a local folder, has to be one of the easiest ways of creating a public photo gallery that I know.The cost? 2Gigs of storage are free, and this can be expanded to 50GB for $9.99/month, or $99.99/year.
The software has immediate applicability to small work-groups or small business collaboration. It is copes in a robust-if-not-brilliant manner if two people try to edit the same shared file simultaneously: Only the first version to fully make it to the server is kept, the other machines get copies of the conflicted file with a suffix, indicating the conflict and the users have to manually fix the conflict before removing the extra copies of the conflicted file. It also implements version control, allowing users to restore previous versions of amended or deleted files. As a way of sharing information in a small group of skunk-works project, it's a very nice solution. But the software isn't really suitable for wider enterprise deployment, mainly due to security and management issues. That actually represents an opportunity for Dropbox. Security and management, not quite there yet.In terms of physical security, there is the obvious concern about letting your valuable data sit around in the cloud. At least, in this case your data isn't held hostage - if Dropbox were to fall under a bus, your data would still exist on your machine. But what about encryption? As it stands, the company's FAQ explains that "All transport of file data and file metadata occurs over SSL. Files are encrypted with AES-256 before being stored on our backend.". Unfortunately (unlikely, online back-up company Mozy, for example) the company does not let you specify your own encryption key, which means that notionally they (and anyone who convinces them that they shoudl cough up your data) could have access to your data). The company says that it "eventually" plans to offer this, and points out quite reasonably that there is nothing to stop you from placing encrypted disk images in the dropbox for additional password protected security. In terms of compliance... well, I'll leave it as an exercise for your imagination to visualise the colour of a compliance offer's face when faced with some software that "allows me to right-click and create a public Web link, though the firewall to a folder on my PC". Who would have thought a human could turn that hue and survive? Some people have also raised issues about the company's terms of service I'm not a lawyer and a cursory glance doesn't reveal much unexpected. But knowing that by putting a file in your drop box you are granting "all other Dropbox users and the public a non-exclusive, non-commercial, worldwide, royalty-free, sublicensable, perpetual and irrevocable right and license to use and exploit Your Files" may cause some people pause for thought.
I'm in two minds as to whether Dropbox has a place in the corporate world. Much of the product's current charm is in it's simplicity and elegance, But the corporate world is going to demand more in the way of management and configurability before unleashing dropbox. Indeed any moderate size company is likely to have at least a fileserver for simple sharing, perhaps even an Exchange, Zimbra or Sharepoint system installed, which will have user roles and policies attached.
The way forwardOne obvious path that Dropbox could take would be to follow the Groove Networks path. Before it was acquired by Microsoft, Groove allowed anyone to download and use its peer-to-peer file-sharing and collaboration tool for free, but then sold an management console that allowed enterprise IT to set policies, user roles etc.
Another would be to take a leaf from Google's book and produce an enterprise appliance: A simple box containing a self-contained dropbox installation which could be attached to a nice big private RAID box would remove most security concerns at a stroke, while providing a solid revenue stream. If the company can retain the stupidly simple ease-of-use while building in the management and perhaps providing an appliance, it could find itself on an winner with medium sized businesses. In the meantime, it is fine to use in small collaborative groups, where compliance isn't an issue and where you are not storing your trade secrets or bank account details. Update: DropBox For Teams is on the way:
Wednesday, September 10

It's just a rough dammit. Balsamiq to the rescue.
by
Chris Noble
on Wed 10 Sep 2008 21:09 BST
The problem of how to communicate rough design/layout ideas is an old one. How do you find a visual way to communicate the elements that a Web page or application, while making it clear that this is not a finished design?
It's a question that has bedevilled so many designers showing a wireframe to a client or member of their own management team, that it has become an an almost Dilbert-esque cliche. After loudly intoning: "it's a rough - take no notice of the fonts or the colours", they cautiously pop something on the screen, only to find that soon enough the debate turns to - the fonts and colours.
It's too easy to make jokes about pointy-haired bosses at this stage, but the simple truth is, that most wireframes, created in tools such as Photoshop, Visio, even Powerpoint or Omnigraffle (linked because this a personal favourite) have enough polish to override the designer's verbal warnings: The human brain is very bad at ignoring things.
And it is not just non-tech management fall prey to the problem. Designers do too. I've had conversations with Information Architects in the past who have sketched out ideas for a site or interface design, only to find the designer (who is meant to be the expert) has followed the sketch altogether too slavishly.
In 2002 veteran information architecture and user experience designer Dan Brown, came up with the idea of the Page Description Diagram, an attempt to describe, in pure text the hierarchy of elements on a Web page and how they work together. An excellent idea, but one that its rarely seen in the wild.
Which is why Balsamiq mockups, is such a breath of fresh air. This is a specialised graphical tool for mocking up user interfaces and Web pages. It gives you the pre-built wireframe elements, lets you drag, drop and resize and is smart enough to to know that (for example) radio buttons can have two states and to let you simply type in the labels for tab-bars and choose the one that should appear selected. It takes away much of the grunt-work.
Written in Adobe AIR, this is a young app, and it it wasn't the snappiest in the world to begin with. But over the the last couple of months, it's extremely responsive developer Giacomo 'Peldi' Guilizzoni has cranked out the point-revisions in response to an enthusiastic user community posting enhancement ideas and bug notifications on the company's Get Satisfaction page. A one-man-band, Guilizzoni is making himself a text-book case of how to use online tools to interact with your customers.
Mockups isn't perfect - mainly, I suspect because of the quirks in AIR. On Mac OS X OS's native keyboard shortcut don't always work, for example and performance still leaves something to be desired. Nonetheless it is the quickest way that I have found to put an interface together. Moreover, alongside its standalone, desktop version, there versions available as plug-ins for Confluence, JIRA and (in development) Twiki. In other words it slots right into your collaborative workflow system.
But one place where the software scores is the output looks truly rough. And I say that as if it is a good thing - because it is. There is no way that this can be mistaken for anything other than a mock-up. The font even defaults to comic sans, for goodness sake. Some architects/designers might feel that have is that the results look a bit amateurish, indeed they might be a bit embarrassed to put this in-front of a client. Trust me: if you carefully explain the issues and why you are using a tool that enables fast iterations of new layout possible, while also making the rough nature of the layout explicit, they are likely to 'get it'. Indeed the first client I showed it to ended up getting a licence. It is far better to undergo a little bit of pain at the start of the process, rather than endure misunderstandings throughout the project.
Monday, September 8

Why this Blog will never be popular.
by
Chris Noble
on Mon 08 Sep 2008 10:16 BST
This then, is the first entry in the pun-tastically named Information Overlode, blog. And you, dear reader have stumbled upon it. So what's it all about? First, I spend my working life talking to organisations about the benefits of using appropriate technology to communicate with customers, partners and employees, so not having a blog is is almost something of a faux pas. On the other hand, having a blog just for the sake of it, with no rhyme or reason is an even worse error. So like all good blog authors should, I had to consider whether this prospective blog would serve any purpose and whether it would be sustainable.
Initially then, I'll be using this blog as primarily a place for me to talk to myself and refine my thinking. As I come across useful tools, novel developments or interesting topics, I'll use this space to note, digest or analyse them. Hopefully, along the way some of these posts will be helpful to others. "But surely", you are saying to yourself "Chris really wants this blog to be monster success with thousands of visitors and commentors every week". It would be nice wouldn't it? It is also entirely unrealistic. And it may be instructive to examine why: This blog will break three key rules which are necessary for business or tech blogs to thrive:
1. Keep it focused, serve a well-defined community.
The best corporate blogs serve a well defined purpose and/or a well defined community. The community might be existing customers, in the case of a product support blog. The purpose could be to shape opinion about the company and engage interest in the case of a CEO's blog, but they are well focused. Which leads us to the relate point 2. Make it best-of-breed Best of breed? Isn't that a tall order for most people?
Not really. If you are the Acme company selling Widget X, it tremendously easy for a blog to be best-of-breed. You simply make it the place where customers and potential customers learn about developments, support issues and the vision of future development. If you are feeling daring, you can even use the comments sections to back-and-forth with customers about their feelings with regards to your fabulous widget. Of course, by definition, disgruntled punters are likely to be over-represented. But with astute and intelligent handling, it is possible to publicly re-gruntle (most of) them.
3. Blog regularly You might think that the use of RSS, Atom etc. Had obviated the need to blog regularly. But no. Most people do not currently use feeds. If you're waiting for me to give you some nice sound figures on the absolute numbers or proportion of Web users who use feeds, you are going to be disappointed. A quick browse around suggests a lack of solid research out there. But the figures that I have seen make me more than comfortable with saying that most do not. Ergo your committed readers will only find your blog entries by regularly browsing to your site and if you regularly disappoint them by slacking off the updates visits will slowly dwindle. Initially this blog will assuredly break all three rules. I hope it will contain interesting and valuable items, but it won't be focussed on a particular community or be strongly themed. It won't be best-of-breed in the terms outlined above, and I certainly expect a hiatus or two (or three) in the publishing schedule.
So "Welcome" and make sure that, when setting up your corporate blog you do as I say, not as I do.
|
|