The simplicity/complexity tradeoff is one that many ELN teams struggle with and is the underlying reason for most ELN project failures.

In an interesting post from Jack Vinson (a fellow CENSA alumni) lays out to three simple truths of failure from a post on the IT Failures Blog which in turn was inspired by Dilbert:

  • Complicated plans don’t work.
  • “Spraying energy into the vortex of failure” doesn’t work.
  • Your boss really doesn’t care.

The first is the most important in my opinion; and it is directly relevant to ELN projects. In my experience the more time a product takes to implement, and the greater the change in working practices required, the less chance there is of the project achieving the hoped-for Return on Investment. Which in my mind is a failure, even if you do manage to roll the application out and torture the users with it (aren’t we here to make life better for the end users?).

I’d broaden the last point to no one really cares about the ELN project – they care about its potential to impact their lives in a positive or negative way. If they really cared they’d be on the Project Team! This is a broader varient of my Toaster Analogy which when it comes up in Workshops often gets that kind of embarrassed “Yeah, that’s very true but it makes us comfortable so let’s move on” laugh.

There’s enough material around to show that complexity causes massive problems. There’s enough public literature around to show that IT projects often fail to meet their goals (and you only have to wonder what really goes on in private because who likes washing dirty laundry in public?).

Which is why I am mystified to see complexity still worshipped, with project teams brandishing their laundry list of features (all mandatory) and vendors explaining with great pride their multi-week implementation process. When questioned, people seem to honestly believe it has to be this hard!

Why can’t we find the quickest, simplest way to achieve the outcome we seek? Why are project managers so rarely rewarded for paring down the list of requirements to the essentials, shortening the project timescales, reducing risk, and slashing the budget? Why is it that products that “Just work” are somehow “Not powerful enough”?

I suspect the underlying reason (once you get beyond organisational politics and vendor sports) it is because geeks see value in intrinsic complexity. Which is fair enough – until that complexity meets the real world of people, budgets, and other projects.

Amphora are quite happy worshipping at the temple of “Less is more” because we believe that’s the best way to serve our customers. Seems that this view isn’t shared by everyone but that’s fine – the trend is in our favour. In this economy we all need to renew our focus on adding the most value for the least cost.

Oh, here’s Dilbert:
Dilbert.com

 

This is a good story on the problems of proprietary file formats, which has a happy ending but only through what appears to be days of effort and some Open Source tools.

I really don’t know why customers put up with vendors shipping undocumented private file formats. It just locks up your data.

Purchasing should be requiring Open File Formats for any piece of software that is purchased – it should be an absolute corporate mandate. Sadly the purchasing playbook has yet to get a section on probably one of the most business-critical aspects of scientific computing.

 

Almost all “Electronic Laboratory Notebook” vendors assume you are deploying onto reasonably-recent Windows PCs, which might be the case if you are focusing on Big Pharma (which most vendors were) but isn’t true when you start working with Academic Labs and Biotechs.

As a general rule Apple MacOS X, Linux are second class citizens in the ELN world and it is all the salesperson can do to stifle a laugh when you mention those “other platforms”. The iPad and Android equivalents don’t even get a look in!

I’ve felt this situation is increasingly unsustainable – not only is Apple’s Macintosh experiencing a resurgence, but we’re quite possibly on the cusp of a tablet-drive revolution.

An interesting blog post from the CTO at the UK’s Department for Work and Pensions wonders if their current Windows desktop refresh might not be their last.

Personally, I think it likely this is the last version of Windows anyone ever widely deploys, though.

The reason? I think they’ll be fewer workloads that actually require a heavy deskop stack. Today, of course, we have all this legacy that’s coupled to the desktop, but in a decade, I really doubt that will be the case. Most stuff will arrive via the browser.

Talking with our larger Enterprise customers, it appears their Windows Desktop infrastructure is increasingly cumbersome and it is very hard to innovate in such a complex environment. In the smaller Biotechs there’s a real push to avoid cumbersome IT generally and there’s ready adoption of web and Cloud technologies, as well as additional platforms such as Macs and iPads.

The article makes a good long term point which ELN project teams should urgently consider:

From a strategic point of view, if you’re designing the future technology estate of a large organisation, that last thing it makes sense to do in this kind of context is build stuff that depends on a desktop stack. Furthermore, decoupling legacy from the desktop stack also has to be on the agenda, because you just can’t count on that stack being relevent in 10 years time.

Most ELN products on the market are tightly linked into the Windows ecosystem, even to the extent that one vendor just trumpeted the re-launch of their ELN which is now completely based on SharePoint!

My feeling is that organisations looking for an ELN which is going to last for more than 2 years should consider a situation where there are more than just Windows Desktop PCs in their IT infrastructure – not an unreasonable consideration, but one that needs thinking about up front rather than purchasing a product that locks you in to a dying ecosystem. The Windows PC isn’t going to be replaced but it won’t be the only way you’ll want to access your ELN, and whatever you select needs to be able to work with whatever you might adopt. That such lightweight “thin” solutions are easier to deploy than a thick client just icing on the cake.

(update: this story has been picked up in The Register)

 

“Simplicity is the ultimate sophistication.”—Leonardo Da Vinci

A good Electronic Lab Notebook takes careful design; the foundation of this is what does, and more importantly what it doesn’t do. This is really hard, as evidenced by the complexity that can creep in to products as you add feature after feature. Apple’s success is built upon design and the fact that better-resourced competitors can’t keep up shows just how difficult it is to get design into your corporate DNA.

I’ve always felt that ELNs are particularly susceptible to “Kitchen-sink” tendencies; the term is so badly defined, and the potential use cases so broad that you can easily find yourself needing to add more and more functions until you end up with an unholy mess which then:

  • Requires a lot of consulting to customise the application to fit the needs of any group of scientists
  • Is complex to master, requiring quite extensive training time

In PatentSafe we’ve taken a different approach – less is more. Our aim is to allow our users to use any application as part of the ELN experience, and we’ve come up with a handful of basic concepts which can be mastered in lass than 15 minutes and allow the user to use all their existing applications and work processes unchanged.

I’d to claim this is as a result of an amazing design philosophy but in truth it is a product of where we started. Most ELN companies started either in big Pharma (or were swiftly pointed in that direction by their VCs). Amphora in contrast started out working with Kodak and then into companies such as DuPont, PPG and J&J – doing really very large deployments (100′s to 1,000′s of users). When you’re rolling out that many seats especially into the very diverse research environments of chemical companies, you have to keep things ruthlessly streamlined and build on what’s there, because it is just physically impossible to customise the ELN for each group.

When we started to work with Biotechs this experience really paid off:

  • Biotechs don’t have the resources to pay for a long consulting engagement and lots of software
  • Biotechs will often change their entire business over a period of years; if their ELN was overly customised it would be hard to prevent it becoming a business-threatening impediment to change

It is interesting that Biotechs really have a lot more in common with diverse Chemical companies when looked at this way; most people seem to think Biotech is just little Pharma, but nothing could be further from the case when you are deploying IT.

Less-is-more is also helping us as we move into additional devices such as the iPad. PatentSafe is device-, application-, and discipline-agnostic, so the iPad just fits right in.

When we first started out I was always worried that we would need to add a lot more functionality to the core product to meet market demand. It turns out that resisting this was one of the best decisions we made as a company – we now have a product that can be dropped in almost anywhere and used immediately, which is dramatically different from the alternatives (so much so that people often think we’re lying when we say no consulting and 15 minute training time!).

I can’t help but feel that our market-leading presence is down to what we decide not to do, instead choosing to work with what’s out there. I’d like to think that what we’ve done is technically excellent, and PatentSafe has a number of very powerful features. But it is the features we chose not to implement which make PatentSafe so quick and easy to use, and able to stand the test of time as our customers’ business change.

(this post was inspired by “Simplicity isn’t that Simple” on 52 Weeks of UX blog.

 

Here’s a nice article on one of the HBR Blogs about the differences between larger and smaller companies. Although Amphora is no longer a “Small” company by most definitions I’d like to think we’ve managed to keep the qualities of a small company – we’re certainly able to be a lot more agile and responsive than some, and retain a pretty healthy culture internally.

© 2011 elnblog.com Suffusion theme by Sayontan Sinha
This website uses a Hackadelic PlugIn, Hackadelic Sliding Notes 1.6.5.