ideasarehere

August 11, 2010

AEIOU

Filed under: business,creativity,marketing,workflow — Erik Dobberkau @ 00:56

Information itself is useless. What makes information valuable for you are the Vowel Steps:

  • Access (new) information regularly.
  • Evaluate its relevance.
  • Implement it to your routine.
  • Observe. Measure and compare.
  • Undo if it doesn’t work, learn from it and try something different.


August 5, 2010

(Gone) Before Its Time

Filed under: business,internet,marketing,workflow — Erik Dobberkau @ 08:08

As bold the eulogies were when it was announced, they’re even bolder now that Google Wave‘s end as an independent service has been proclaimed. Undoubtedly it’s tool that provided the sought-after curve-jumping, paradigm-shifting innovation which by itself was hard enough for people to wrap their heads around. But I believe what really prevented the breakthrough was a lack of trust. Google still has a major trust problem, and as long as people are suspicious about what’s happening with all their data, a product that deals with such better be trustworthy.

And it’s also worth a look at the marketing startegy that went with it: Google was quite eager to announce it when Wave was still in alpha. And it was a marvel. Then they released the invitation-based beta which still had a lot of glitches and hickups and one year later it was open for public. Which was too late. It’s always easy to be clever in hindsight, but the important thing to point out here is that there was no need whatsoever for Google to tell the public about Wave, because until today there is no competitor. Why hurry? They could easily have waited one more year and make it a finished product.

One more thing. As far as I remember, they didn’t promote it heavily once it was up and running, which wouldn’t have been the worst of ideas. I’m not talking TV here, I’m about press releases for the geeks that want to use this service as  soon as they have someone to do it with. I didn’t use my account because there was no one I was having a project with that would have offered itself to be run on Wave. But if I had, it’d be comforting my sleep a lot had Google told me: “We know there’ve been some issues concerning our security in the last months, but we promise you that your Wave data is 100% safe with us. We use advanced rocket science encryption, so even we don’t know what you’ve been putting in there.” Now you’ve got something to work through the adoption curve.

The majority of users, it seems, is still in the desktop age. This is the domain of Microsoft. Make a document, save it on your hard drive or local network. One application for each purpose. Sifting through 86 emails to find out who said what and when. It’s the classic switching dilemma: As long as their pain is not big enough to see the comfort of the solution, people don’t switch. Because it requires them to take a step back and consider the whole issue. The question is not: “How do I make this work with what I got so far?” but “Looking at both solutions as a whole, which serves my needs best?” That’s the marketing challenge not only Google faces. Only more often than others.

July 25, 2010

The manual that didn’t help

Filed under: business,internet,marketing,workflow — Erik Dobberkau @ 00:15

In his talk during last year’s Business of Software conference, Don Norman mentioned the practical use of mock-ups when you’re designing a user interface.

And unsurprisingly, this also works the other way round when you’re explaining a UI.

The folks at Universal Publishing Production Music obviously didn’t know or think so. They sent an email with 17 paragraphs explaining the menus and structure of their soon-to-be-launched new website, purely verbal. I understand that you might leave away the images when you ship the manual with the software (as the Cupertino guys do), because it’s there, on screen.

But when it’s neither on screen nor in the manual, none of both is of any use, is it?

July 24, 2010

For beta or worse

Filed under: business,internet,IT,marketing,workflow — Erik Dobberkau @ 00:31

The other day, when I posted my insight on that one social network, one comment I got was “Tell that to the customer”.

Here’s what I responded:
“We’re all customers, aren’t we? And what do we appreciate more, trying to find an existing solution that’s already out there (a.k.a. “Check the FAQs” and “search for a tutorial”) or having someone take the time to (find out and) tell us what to do? Of course every customer prefers to have problems solved immediately, but that’s a different aspect of the same issue. Engineers and technicians used to be not very good at interaction with real people (yep, that’s a clichĂ©), that’s why they preferred to keep track of every issue and include it in the manual or FAQ — or, ideally, they would solve the issue in a self-explaining way (not likely, but hey..). And -surprise!- people have not embraced studying manuals cover to cover, because it’s boring, techy stuff! Same problem as before.

Another point: An angry customer is just as good as a happy one, because he gives you two opportunities: You can solve his problem AND make him happy. That’s a reward for everyone involved, isn’t it? :)”

The reply to which was: ” ‘Of course every customer prefers to have problems solved immediately’ – You said it. And so everything else becomes void :-P Welcome to my world!”

This reminded me of one of my favourite drawings. And it’s quite interesting to consider it in the context of software.

20 years ago, handling computers was not very straightforward. You had to learn a set of commands to tell the machine what to do, which in itself was awkward enough to keep the majority of people away from it. Unless, of course, your computer’s brand contained a fruit. There was little convenience in using these gray boxes, and the once who used them were in majority expert enough to find workarounds in case something caused an error, like “Oh, this field requires only digits to be entered, and I entered letters, so it didn’t store them.”.

The first major shift happened when software became more accessible by graphical user interfaces (GUI). The upside for the software companies was they could sell more because there were more customers because of the improved convenience. The downside was that the more people used software, the less experienced they were. Thus manuals grew ever larger, and programmers had to implement more error handling and feedback mechanisms to tell the users what to do when the software didn’t deliver what the user thought it should.

The second major shift happened when computers became ubiquitous. Now software designers had to deal with the whole range of users from absolute newbies to experts who had been using their software since version 1.0. The analogy here is the VCR. Every household had at least one, but even in the 90s, when VCRs were sophisticated as they could be, only a small fraction of people would know how to set the time. It just wasn’t straightforward. It’s like comparing Microsoft to Apple to Linux. Every company or project has it’s own approach of how things should be, and some people favor one over another because it matches their expectation.

Nevertheless, it’s still software which has been made by people who do not always consider or who can’t anticipate every way a user will use their product. This is a given which also applies to custom designed software. People do not know everything they want their software to do, because they don’t care about what happens under the hood. What they do care about is the look of the GUI, and ideally, error handling and feedback functions that do not make them feel stupid.

Another thing that users in general have little concept of is “beta”, meaning “it should work, but there will be some glitches that we have to figure out yet”. Which is why most beta versions are free, because no one can expect you to pay for a product that doesn’t work. Or can they?

Zynga’s very popular game Farmville is labeled as beta ever since its release one year ago, spreading like wildfire with more than 70,000,000 players worldwide. Like other games, this one has a virtual currency allowing you to buy stuff in the game. One way to increase your amount of virtual currency is to buy it with real money. And what happens (quite predictably) is that people are confusing things: The game is free and still in beta, so you can’t expect it to work perfectly. But what you buy should be yours no matter what. This explosive combination detonates every once in a while. It’s technically okay when the game crashes, but not when items they bought disappear. But people do not distinguish between the two. Their posture is: “I pay for this, so I can expect it to work.” Which is not quite the case. What’s worse though is that they a) keep on playing no matter what, and b) they complain to the public, but not to Zynga. This is not changing anything, it’s just whining.

One more thing before I’m trying to wrap this up: Software design is also about fashion. It doesn’t matter if the latest trend or technique adds any value to your project, but you better brace yourself that your customer will ask for it — just because they can! They pick up something somewhere, and they will ask you just to look smart themselves, impress their peers, whatever.

So what do we make of all of this? You have to embrace a number of things:

  • Whatever approach you take, one size will not fit all. There will always be someone screwing up, and that’s when your phone rings.
  • Be careful about customer’s expectations. There’s a large shift as soon as money is involved.
  • People hardly call when everything is alright. That’s when you should call to ask for improvements and the like.
  • Expect your customers to be human, not tech experts. This also implies that they will react as humans do, meaning they will be angry when they call you in case something fails. That’s ok. You have the opportunity to solve their problem AND lighten their mood. Give them a hug.

May 12, 2010

Innovation!

Filed under: business,marketing,media,workflow — Erik Dobberkau @ 15:27

Listening to Guy Kawasaki’s presention on innovation (which is an interesting lesson in and of itself), I got a cool idea which I tried to find an existing solution for on the web, but there’s no easy-to-find result. So I’m sharing it here, for free.

There should be a microphone headset with an incorporated mute switch or noise gate, so in case you need to sniff, cough or produce other kinds of unpleasant noise that you don’t want to be amplified over the PA or recorded on the video, you — the one who’s wearing it and knows when the incident is about to happen — can just mute it out.
BUT what would make it really great would be if the button were part of a presentation remote that works with both Mac and PC and has all the other cool stuff. But only what we really really need, ok?
So if you’re a microphone manufacturer and don’t want to make the handheld device, please integrate a bluetooth or whatever-works-interface so someone else can make the counterpart.

What else would be cool (in case you’ve already recorded a presentation and want to clean it up afterwards — audio-wise): A plugin or function in your audio software that lets you define a sound (like the noise print in a noise removal plugin) which then marks all the spots in your recording where the software thinks this noise occurs (with adjustable tolerance and so forth), so you have just to check whether the predicted sounds are the ones you want to get rid of and remove them.

Should any of these solutions already be available, I’d be happy if you dropped me a line. Otherwise I recommend you to run with it!

April 19, 2010

Take care of the time

Filed under: creativity,personal,workflow — Erik Dobberkau @ 06:00

There’s a saying that goes “Take care of the dimes and the dollars take care of themselves”. No need to explain, it’s a no-brainer. But what I was thinking the other day is that we tend to pay little attention to our dimes of time. Email here, Facebook there, just a little peek over to Twitter, and hey, I could check out if there’s someone new I know on LinkedIn. Have a smoke. Repeat. Do this often enough in a single day and it’s two hours or more gone. And I mean gone. Dead time.

But we’re pretty good at finding excuses afterwards to justify what we did, right? So, if they’re only half as reasonable as we pretend (already getting nervous here?), make a list, a plan for tomorrow, on which you write down everything you do including all these “filler” activities (you can have multiple instances of the same item, because you’re at least checking your inbox twice a day) and for each item on this list, write a good reason for executing this activity with the given amount of time.
Like this: “9.00 a.m.: Check private email, supposed to take 1 minute, will be 10, because I’ll spontaneously decide that more than one particular email will be so subjectively important that I can’t reply later.” If you don’t feel any pain when you’re writing this and going through it afterwards, really nothing it all, I recommend you hand it to your boss, she can certainly help.

The challenge is to replace these bridging activities with ones that create value. You were clever enough to discover your old ones, I’m pretty certain you’ll find some new and useful ones too.

March 28, 2010

Needful software (II)

Filed under: business,IT,workflow — Erik Dobberkau @ 18:27

A project management software for Mac that is compatible to MS Project and offers the same features, only better. And which can be fully integrated with iWork. And MS Office. Filemaker too (just in case the one person who needs it shows up). Plus Google Docs — and Google Wave, of course (no pun intended — there’s quite little buzz about it recently, or is it just me?)

Can you make it? Pretty please?

Needful software (I)

Filed under: IT,workflow — Erik Dobberkau @ 17:32

I’ve been using computers for about 20 years now and never had any issues in terms of violating file system limitations. One reason certainly was that I never ran the risk of having too long/deep folder structures because there wasn’t that much data. This of course changes when you have a constellation where you have a desktop workstation and a notebook for working remotely, and use the desktop PC to store your backups as well. You can pretty easy end up with a folder structure that has more than 255 characters (including filename and extension). What happens next is your computer crashing without warning every time the automatic indexing hits the folder. I only discovered it because I tried to move all the data to a Linux-based NAS (which has an ext-3 file system with almost the same limitations as NTFS on Windows). For some reasons Windows doesn’t give a warning when you put a folder structure of critical length into another folder but has no problem telling you thereafter taht it cannot do anything because it’s broken.

The core question is: How do we organize data? What’s most annoying about the classic folder concept is that it only allows for one context in which data can be represented, but technically, it doesn’t matter. The file system itself is nothing but a giant database where a string variable points to a physical area of your hard drive. Some more information that is stored there: file size, file type (extension), creation date, modification date.

I’d like someone to come up with a piece of software that hooks in at this very basic level and gives me whatever contextualization of the data I like, say, by last modification date, document type and a number of tags I have entered. Or the other way round, with a single click, not going through the whole procedure again. It’s all built in, but not being used. To be clear: I don’t want a search tool, what I’m asking for is a flexible explorer (hint: if you’ree finished making it, flexplorer.com is already taken — by a Cayman Island Domain Troll of course. Flexplorer-xp or winflexplorer are still up for grabs).

March 26, 2010

Common mistake

Filed under: business,marketing,workflow — Erik Dobberkau @ 07:18

There seems to be an expectation, even by people who usually think progressive, that the new should adapt to the old. It could be means of collaboration like software or a new colleague joining your team, somehow there’s a ubiquous, subliminal sense of “embrace the status quo first and then -maybe- you can share your thoughts”. Opportunity killed in less than a second. This doesn’t mean I suggest doing the opposite — it doesn’t make sense either when you overthrow everything just for the sake of overthrowing, you’ll never get to work.

What makes sense indeed is to seriously consider that adaptions of the old can cause a much larger progress in general, even if it requires more effort — which is quite likely since it’s been around and running in the same groove. Of course this is safe, but it slows down the pace. What do you need more to keep up? That is the question. The businesses and people who are open to this and have developed a culture of being able to adapt quickly are the ones that outperform the stubborn ones.

March 17, 2010

3D for you and me

Filed under: creativity,video,workflow — Erik Dobberkau @ 11:38

FX makers idustrial revolution have posted a tutorial (sorry, they seem to have taken it down in early 2012) on how to create 3D video using Apple’s Motion and Final Cut Pro with a plugin called Stereo 3D Toolbox, made by DP Tim Dashwood. Tim also has a series of tutorials for 3D editing and compositing on his site. Terrific! [Update: Tim’s place has moved to dashwood3d.com.]

« Newer Posts — Older Posts »

Powered by WordPress