Note: I apologise in advance for this being an infomercial for Box. I assure you that was not my intent when I started writing this post.
A few weeks ago (Oct 10 – 12) my new colleague (I’ll explain later), Greg, and I were at BoxWorks in San Francisco. For those of you who don’t know, BoxWorks is Box’s annual conference, and a must-attend event for those interested in content management, especially cloud first content management. A topic that came up more than once was OpenText’s purchase of Documentum. Specifically, what it means for Documentum customers, and what they are thinking. I’ll give you a hint; https://www.youtube.com/watch?v=7FPELc1wEvk.
Let me just say that Aaron Levie owes Mark Barrenechea a great bottle of Scotch, a bouquet of roses, and a hand-written thank you note. If OpenText hadn’t bought Documentum I doubt you’d hear of so many Documentum customers getting ready to bail, and taking a serious look at Box as a viable replacement.
More recently, we had a couple of very relevant and telling conversations; the first was with a Box customer looking to get off Documentum; the second was with Box. I also had a conversation at last year’s BoxWorks event with someone in a highly regulated industry. Their company is a sizeable Box customer and is, reluctantly I think, still required to use Documentum for some of their more regulated content. I’m fairly certain that they’d prefer not to have to rely on Documentum. For what it’s worth, I had this conversation prior to the closing of OpenText’s purchase of Documentum, but we all knew it was coming.
This is just me being long-winded in telling you that I have decided to join e-Wave Solutions (the Greg I mentioned is Managing Partner). We’re a small company headquartered in Calgary, Alberta, Canada. In a nutshell, we bi-directionally integrate content management systems with SAP. Greg invited me down to BoxWorks, we had some interesting conversations, I got excited, Greg got excited, and we literally shook hands on a deal on the flight home.
Anyways, I digress a little … where I’m actually going with this post is that there is going to be an evolution of Box within client organizations. It won’t simply be spread and sprawl, like we see with so many ECM implementations that begin life in one department and eventually spread throughout most of the organization. Certainly this will happen with Box, but with the added advantage of (easily) encompassing the extended enterprise (i.e.: external stakeholders).
No, the evolution of which I speak is about starting as a relatively simple content management implementation and evolving into actual business solutions. Yes, legacy ECM platforms are certainly capable of this as well, but most haven’t gone down that path for one reason or another.
For Box customers this evolution is going to happen one of two ways, or, more likely, in a hybrid manner. Customers are going to sign up for Box to solve some pretty simple content management and collaboration uses cases. Once they have this initial set of use cases sorted out, they are going to get a visit from their friendly neighbourhood Box representative and be shown “the art of the possible” (I really, really hate that phrase!). Once they see what can be done with Box and its myriad integrations, they are going to start crafting solutions that solve business use cases.
As much as Box, paired with some of its available integrations can do, it can’t do everything. And this is where that second type of solution evolution comes in, and it’s called Box Platform.
I’m fairly convinced that organizations wanting to have content centric business solutions are going to need to build applications that tie together disparate repositories with business logic. Today, a basic premise of Box is that all your content is in one place; that’s not realistic, nor will it ever be. Even legacy ECM platforms relied on Business Process Management Systems (BPMS) to tie together content and logic from multiple systems in order to deliver business solutions, rather than content management solutions.
A client that I have spoken with intends to use their content management system (CMS) for loan origination. That’s cool, but, other than the content, there is nothing in the CMS that helps with loan origination. The business logic is in an ERP tool and the content is spread across multiple repositories, one of which is Box. Currently, they really have no way to tie everything together in order to deliver an elegant, functional, efficient solution to their users and clients. However, once they go down the Box Platform path, and they will even if they don’t yet know it, they will have the tools necessary to build an end-to-end solution for loan origination.
Think about all the different content centric / reliant use cases that every organization has that they use every day. Think about their desire to go mobile and go to the cloud with as much as they can. That’s when the beauty and the magic that something like Box Platform happen; it allows organizations to build content centric applications that transcend technical, geographic, and organizational boundaries. A little over two years ago, when Box Platform initially became available, I was pretty excited (as you can tell if you read this); there is no reason for me to change my mind. Box customers looking for solutions beyond content management and collaboration are going to evolve into Box Platform customers. When that happens the potential impact of Box products such as Relay, Skills, and Graph (all announced at BoxWorks, all coming soon) is going to be even more important than it is today.
Two key changes from last year really made me happy:
- Box’s enterprise customers (at least the ones on the panel during the analyst event) are calling Box content management (advanced content management, even);
- Box is unequivocally stating that Platform is the base upon which the Box application is built – they weren’t so clear about that last year.
On a personal level, the first of those makes me the happiest because, along with Cheryl McKinnon of Forrester (my reaction to Box’s inclusion in the Forrest Wave), I was the first analyst / person-who-should-know type that came out and unabashedly called Box an Enterprise Content Management vendor. Here’s my post from June 2015 when I first called Box ECM (you can also get to the whitepaper I wrote on the topic via that post). Whatever. I’m just happy and gratified that Box is finally being seen as what they are. I’m guessing they’re pretty pleased about it as well.
Remember in this post I included a footnote stating that BoxWorks could be a better Information Management / Governance conference than the AIIM conference (I didn’t even mention that records management conference or organization)? Yeah, nothing took place at BoxWorks that made me change my mind.
On to my thoughts about the conference happenings … I’m not going to recap all the announcements; they’re available on the Box site over here and elsewhere on the web and on Box’s site. There were a bunch of announcements about making Box more usable, intuitive, and user friendly, but they didn’t tell me that Box Capture for Android is coming. Box Desktop, Files, and Notes are much needed improvements that are coming, and will make for a much better user (yeah, I said “user”) experience.
If I’ve got this all right, Box Platform can serve up Relay (workflow) and Governance (governance), as well as versioning and all the other mundane content management stuff as a service. While that’s very cool and all, what I really find exciting is that there is a growing ecosystem of partners / developers that include companies like Cognizant, as well as in-house IT shops, ISV’s, and small niche / boutique app developers. The potential implications are pretty cool for all the stakeholders. For example – during his session at the analyst event, Jeetu Patel (heads up Platform and Strategy for Box and is a really nice guy) mentioned that: A – all companies are becoming digital companies (glad he gave up using all companies are becoming SW companies), and; 2 – there’s no templates for digital transformation (I am summarizing). So it seems that there is an opportunity for Box to do for digital transformation on an industry basis what SAP did for ERP on an industry basis. Between in-built capabilities and partnerships, Box has the beginnings of being able to build content-centric digital transformation on-ramps / roadmaps / whateveryouwanttocallthem. The Perkins+Will demo was really cool and a harbinger of what is possible.
What’s really cool and significant is that, if the implementation gets done properly, that whole thing about putting governance in the background and letting users just focus on their jobs will actually happen.
There’s also some other stuff happening with Platform and the application that, if done correctly, could make the whole auto-classification thing a reality. There are other ECM providers that have been working on it for years, to very little uptake. What’s happening, I believe, is that Box is trying to solve the same problems, but in a different way.
One of the product managers told me something to the effect that she was talking to her team and they were telling her they knew nothing about Information Management or Governance. She responded by telling them that they were actually delivering it. There’s a whole bunch more detail, but that’s actually a very cool story. It’s possible because Platform takes care of it in the back end.
Regardless of the size of a company, if they operate in a regulated industry they have to comply with the relevant regulations and legislation. At the same time, if you’re one of the smaller players you likely need to do more with less and can’t afford dedicated compliance solutions. Where Box fits is that they don’t know how to do it the legacy way, and this is a very good thing.
During the customer panel at the analyst session, one of the customers, in a highly regulated industry, was lamenting that they could not use Box for some of their controlled documents. The issue is that Box brings out new stuff too fast and the regulators and legislators simply cannot keep pace. That just sucks.
I asked Aaron Levie something along the lines of “do you think that current legislation and regulations hamper your ability to innovate?” I liked that he acknowledged that it’s the customers, not Box, that are actually being hampered. Box’s approach is to innovate to the spirit of the legislation or regulation, rather than to the letter. I.e.: they’ll satisfy the what, but the how may look a little different.
Odds ‘n’ Enns
- One of the most interesting, to me, integrations I saw at the conference had to do with SAP (apparently you don’t pronounce it “sap”). There’s this company based in Calgary, Alberta, Canada that effectively does for Box-SAP what OpenText Extended ECM does for OT-SAP. I don’t know a ton about it yet, but it is something I will be looking into and getting more familiar with. The fact that the folks at e-Wave Solutions have put effort into building a Box-SAP integration in addition to their Filenet-SAP integration (I think I have that right) is significant. They’re not just chucking up content that’s relevant to stuff happening in SAP. No, they’re doing it in an intelligent way that leverages / manages metadata and preserves the integrity of the “records”. That’s kinda cool. Like I said, I’ll be looking into this a bit more.
- One of the really good things about being an analyst at an event like BoxWorks is that you get one-on-one time with some key people at Box. The normal scenario is the analyst asks questions and the company person answers them. What I love about the people at Box is that we both get to ask questions and have an open, frank discussion.
- Thanks to the Box Governance Product Marketing people (thanks, Veena!!!) for inviting me to share some of my thoughts on Box Governance.
- Thanks to Aaron Levie for taking the time to come and chat with us analysts. I’m a bit of a sceptic at times, and I sometimes wonder if certain tech CEO’s are putting on a show for analysts, the press, prospects, etc. After sitting less than thirty feet from him and being able to look into his eyes, I’m pretty certain that Aaron Levie truly believes in what he and the rest of Box are doing.
- Lastly, a huge thank you to Joely, Signe, and Megan for making the analyst day and, especially, the analyst dinner truly excellent. The whole idea of going to a chef’s residence and having a home made meal in a more intimate setting … loved it.
- That pic is what greeted us as we walked into the chef’s home. There were leftovers.
The one thing that I didn’t hear anything about is a service organization that can make it (all this next generation ECMness) happen (Box Shuttle aside). I still believe that without the right services capabilities, things will not progress as smoothly as they could. Overall I’m pleased about Box’s progress over the last 12 months. You could even say I’m optimistic and excited for what they can achieve and change about ECM in the future. The recently announced OpenText acquisition of Dell EMC ECD (ya know, Documentum and LEAP) just made Box a more attractive option for ECM buyers. As one industry analyst type mentioned, it’s a changing of the guard in the ECM space. Among others, Box is leading the charge. Not to say I told ya so, but I told ya so.
What follows in this post is pure fantasy and speculation, directly out of my head. Or not.
Over the past few weeks I’ve been talking to vendors and some end user types about Information-Governance-as-a-Service (IGaaS). Forget for a moment that no one vendor does all aspects of IG, or that there’s not even a universally accepted definition of IG. Focus instead on the lighter touch that’s required today when so many enterprise tools are required to have a consumer experience about them. Also think about Content-as-a-Service (CaaS, defined here) and what that means for building the apps needed to work with, manage, and govern content.
To save time, let’s get the fawning out of the way:
- Box – I am unashamedly and unabashedly a fan;
- Egnyte – see Box. I’m not getting into what Egnyte announced in this blog as there are plenty of great summaries around the web, including Egnyte’s site;
- GlassIG – more quietly, but see Egnyte.
Pay attention to all three of those companies if you are remotely interested in Information Governance and/or Management. There are other companies that I think are pretty damn good, but when it comes to managing and governing content in cloud or hybrid environments, these are my three. Oracle Web Center Content would be my go to for on-premises ECM (w/some nascent cloud capabilities like file syncing).
When I mentioned to someone at Egnyte a while back that if they added governance to what they already had they could absolutely kill things, I wasn’t thinking about what came out in Egnyte Protect, announced earlier yesterday (June 7,2016). I was thinking more about things that the AIIM and ARMA crowds, especially ARMA, would consider governance. You know, stuff like retention management, legal holds, classification … all that records management-y goodness.
So, even though I was a little, initially, underwhelmed with what Egnyte did release, I sat back and thought that it’s not necessarily a bad thing. What was released is good and what’s coming up is good. Without getting too deep into the weeds, let me paint a little picture for you …
Let’s pretend, for the sake of discussion, that my organization just went out and procured Box as a content management platform. Let’s also pretend that I’ve got stuff stored in SharePoint and network drives, and that in addition to the standard security stuff, I also have to deal with internal policies and external regulatory requirements, a lawsuit or two, some retention requirements, …, you know, a bunch of IG stuff. Let’s also pretend that I want to monitor who’s doing what with content to determine its effectiveness. In other words, let’s say I need to manage and govern content like it’s 1999, but my content isn’t all paper or in one convenient spot that’s on my infrastructure. My point is, the what of what we need to do hasn’t really changed all that much; why, and especially how, have. Ideally, I want to, as much as possible, centralize policies and controls. Enter my IG Mirepoix (yeah, I just made that up) …
In order to meet the requirements outlined above, one could go to each of the individual repositories and do what’s necessary, hoping that things stay in sync and no one ever forgets to do anything in any of the repositories. Even if all that happened, there’s still nothing in place to handle any of the records management, legal hold, and discovery functionality needed. Note to self – go buy more software that needs to be installed, configured, and maintained. Or …
Deploy Egnyte Protect to handle my security and analytics across all the in-scope repositories; deploy GlassIG to handle the records management and related functions. The fact that two tools are needed is not an issue as the tools will be used by different roles in the organization.
I know mega-suites were all the rage for a while, but look what happened. I like the approach outlined above because it’s a best of breed approach. Each tool gets used for the stuff it’s best at. There are areas of overlap between Egnyte Protect and Box, and between GlassIG and Egnyte Protect, but it’s using the three tools as complementary technologies that, I believe, provides the greatest overall value to organizations.
Yesterday (May 30, 2016) I read this article which contends that Box, Dropbox, and others are not content management platforms. I was considering not linking to the article and just putting up screen shots of the main points, but I decided on the link instead. The article is nothing but FUD (Fear, Uncertainty, Doubt) being spread by an on-premises content management provider (props for dropping Gartner, Forrester, and AIIM names though). As a bit of a refresher on where I stand, you might want to read this whitepaper I wrote last year (sponsored by Box, 12 pages long). By the way, I tried to post a comment to the article, but it seems the site’s not taking comments (mine had a couple links).
Without further ado I’ll get into the counter arguments to the author’s “five reasons why cloud file sharing platforms can’t touch document management software platforms from an enterprise functionality standpoint” …
- Security at all costs – If the author had written something about data residency I would have bought it, probably. However, the author goes on about a bunch of FUD, and does nothing to dispel it. The author also illustrates her lack of knowledge, not only of security issues, but also of the capabilities of the cloud players. She implies that many think that on-premises security is better, which we know isn’t the case. Major hacks and leaks have come primarily from on-premises data centres.
- Document storage and beyond – uhm, just plain wrong. Sure, it may take a combination of tools to achieve the same level of functionality that one could achieve with a traditional, legacy suite such as OpenText, Filenet, or Documentum, but is that really a bad thing? Haven’t we already accepted that the whole ECM world is actually changing and the way forward is platforms, integrations, and API’s? I have. Has someone forgotten the abysmal success rate of traditional ECM deployments?
- Not yet ready for primetime – What? This is 2016, technology is changing and advancing more rapidly than ever. No one has a 10+ year window any more to demonstrate anything. Those traditional ECM players you mention are precisely the reason people and organizations are going to the cloud. Traditional ECM platforms are old and out of date. Yes, some are making changes, re-architecting, and adding CLOUD -FREAKIN’-CAPABILITIES-DAMMIT!!!
- Migration issues – Really? You really want to go there? How ‘bout migrating from OpenText to SharePoint? Or from Documentum to Filenet? Or from what you’re selling to anything else? Or from file shares to whatever the hell you want to name? Migration sucks. Always has sucked. Always will suck. Cloud or on-premises makes no friggin’ difference.
- Performance concerns – hahahahahahahahahahahahahahahahaha!!! Ha. That’s cute.
- It’s ON-PREMISES for ***** sake!
Now I’m just angry and irritated. I need a drink.
I’m not saying that everyone should move everything to the cloud, but at the very least think a bit and don’t buy into the nonsense spouted by some people who may have something to gain by spreading FUD. The fact is that managing content in the cloud, whether via cloud capabilities of legacy vendors or via the “new” vendors, is perfectly viable. The key is to know what your requirements are before choosing a technology.
So Box came out and announced Box Governance this week. For those of you thinking that Box is just one of the surfeit of file sharing providers on the planet, think again. Box has been steadfast in stating that they are providing content management and this week’s announcement is further proof of that.
Box Governance provides three important capabilities: 1) Retention Management; 2) Content Security Policies (really should have something about “sensitive information” in the name); 3) Defensible eDiscovery. While having these capabilities available is in and of itself a major step forward, it’s also important to note that organizations that choose to deploy Box can now claim compliance with a number of government and industry regulations and standards (e.g.: PII, FINRA, SOX, SEC 17a-4). However, the most important thing about this announcement, in my opinion, is that it serves to remove additional barriers to including Box in the conversation when talking about Enterprise Content Management vendors (pay attention Gartner, Forrester, IDC, et al). Coupled with Box’s Enterprise Key Management (my post on the topic) announcement earlier this year, organizations relying on FUD (Fear, Uncertainty, Doubt) to exclude Box from consideration are losing rationale for doing so. Security and information governance are what separates true managed content from just another shared drive, and Box has them. Bleat all you want about cloud not being secure and cloud content repositories being unmanaged messes, it’s not working anymore.
Since BoxWorks last September (my thoughts) Box has made a number of feature additions, announcements, integrations, and alliances that are moving it closer to being able to deliver the right balance of System of Record and System of Engagement. At this point it’s still a little ugly and cumbersome for administrators to configure the backend to deliver the various governance, workflow, and security bits to work properly, but that’s what the team at Box Consulting is paid to help with. Those paid to worry about security, legal, regulatory, and audit have less to worry about now than a few months ago. From a content consumer/contributor perspective it’s all pretty slick and that’s what it’s all about.
It’s no coincidence that a white paper I wrote for Digital Clarity Group was released yesterday. The paper is about the next generation of ECM (#ECMnext) and how Enterprise File Sync and Share (EFSS) platforms will provide it. We’d (Box, DCG, me) love to get your thoughts on the paper. Feel free to reach out to any of us (you can reach me via email at email@example.com as I am no longer with DCG) to rant or rave. There’s no data collection, fees, marketing gates or other intrusive nonsense to get the paper, so download The Next Generation of Enterprise Content Management to your heart’s content.
Regardless of what you’ve been hearing, Enterprise Content Management (ECM) is not dead. For years ECM has been harangued as being overly cumbersome, overly expensive, overly difficult, and underwhelming when it came to delivering benefits. That’s all about to change…
The manner in which ECM is delivered is going to change. Taking a cue from what consumers have come to expect in terms of the technology they use for personal reasons, a subset of Enterprise File Sync and Share (EFSS) vendors, led by Box, are emerging as purveyors of ECMnext – the next generation of Enterprise Content Management platforms. The focus is on how and why people create, consume, and share content, supported by a foundation that provides the security and governance required in today’s digital business environment.
This whitepaper explores the short-comings of legacy ECM platforms, and how ECMnext vendors can step up and deliver what we’ve wanted out of ECM all along. While there’s still a ways to go for ECMnext platforms to be able to completely replace legacy ECM platforms, the basic building blocks are in place and the roadmaps are pointing in the right direction.
You can download the whitepaper directly from here.
If you need a little more evidence that ECM is changing, take a look at Box’s announcement about their governance functionality: Introducing Box Governance – Delivering Control and Compliance in the Cloud.
This year the annual AIIM Conference was held in San Diego, California; way better than last year’s location which was really a few hotels sitting on reclaimed swamp land or something. And it was great to reconnect with people and meet some new folks and blah, blah, blah ….
Overall I found this year’s event much better than last year’s. This could be because: A) I had no responsibilities as a speaker or representative of any company in any form; B) The content was just way more compelling to me. Either way the AIIM crew, led by Georgina Clelland (recently promoted to VP of something at AIIM, deservedly so), deserves huge congratulations. If I’m not dead or incapacitated I fully intend to be at the 2016 conference in New Orleans, Louisiana.
On to the good stuff …
I have to say that I was pretty dismayed, though completely unsurprised, that most people and organizations still view managing information from the risk / compliance side of the ledger. Even one of the vendors I spoke to understood that their tools could do so much more if they were employed for insight and analytics, rather than for responding and defending against discovery and compliance issues. During the conference AIIM ran an informal, unscientific survey about organizational priorities; the results are over there <-.
Information Governance seemed to be a hot topic this year, with at least a couple of roundtables and one panel discussion dedicated to it. Good news, right? Sort of. Between the sessions I attended and discussions I had, no one offered up a definition of Information Governance. In fact, one of the IG vendors went so far as to say that they don’t do IG, they’re merely a small part of it. For the record, this is the same vendor that opined their tool could be used for value as well as risk. Regardless of the lack of a cohesive definition (just shows that what the IGI, I, and others have said is true) it was apparent that IG is an important topic.
Enterprise File Sync and Share (aka The mmppfff Problem)
You don’t think that file syncing and sharing is important or disruptive? I don’t know how many sessions at the conference covered the topic, but I attended three:
- ECM is Not Doomed for Failure (Lubor Ptacek, OpenText)
- Use Cases: How Enterprise File Sync & Share Powers Digital Business Today (Oracle hosted roundtable)
- File Sync & Share – The Future of ECM? (Alan Pelz-Sharpe, 451 Research, keynote, I mean KEYNOTE!!!)
While Lubor’s session was not explicitly about EFSS, it doesn’t take a genius to figure out where things are headed. Actually, you could say that we’re already there, but just not in a very polished way. In his session, Alan pointed out that, while working for some client or other, he and his team stopped counting once they’d reached 130 EFSS vendors.
EFSS is a big deal. No, it won’t kill ECM; depending on the vendor, it will BE ECM. Don’t believe me? Think about ECM vendors coming out with their own EFSS offerings. Some because it’s the future, some because it’s the only way to defend against the likes of some of our favourite EFFS players (130+? Holy Carp!)
Bits and Pisces
Lane Severson and I chatting about big data, analytics, data scientists (that kinda stuff) – if your data scientist type people don’t understand your business and context, they’re not worth it.
The guys in the corner from a three-letter ECM vendor now flogging an EFSS solution – if you can’t answer the simple questions, why are you here? Seriously. Why?
You know who you are – a roundtable session is not where you talk about your product for 20+ minutes to the point the AIIM monitor person has to step in and tell you to give everyone else a turn. That said, once you stopped talking it turned into a pretty good session.
Surprised but not by the absence of some of the EFSS players. You should have been there; I think it would have worked out better than last year.
Panel moderators should be like hockey referees; we don’t know they’re there until a fight breaks out.
Last month Box announced their Enterprise Key Management thing. Today they announced their acquisition of Subspace, and are part of ACE (really important app standard). I sometimes marvel at the progress that the industry that pays my bills is making, and then this kind of shit shows up in my mailbox (the Canada Post version, not the Outlook one) …
In case you were wondering, mobile access is not supported and it’s recommended that you use IE or Safari.
On February 10, 2015 Box announced the beta release of Enterprise Key Management (EKM). Put simply, EKM addresses cloud security concerns by giving customers control over the encryption keys used to access content stored on Box. It’s add-on functionality, at an additional cost, that’s going to remove one of the barriers to cloud adoption. This is a very, very good thing.
For those customers that have been dithering about whether or not to move content to the cloud because of security concerns, EKM ought to alleviate those concerns. Of course, those customers will have to be willing to commit to Amazon Web Services (AWS) if they want to avail themselves of EKM. However, it’s a beta folks and I’d bet that Box is actively working on other options.
With this announcement there’s a bunch of organizations that, all of a sudden, have no excuses left. That’s not to say that organizations should put everything into the cloud; they shouldn’t. There’s tons of content that organizations deal with on a day-to-day basis that makes absolutely no sense to move to Box. Take a look at transactional data that’s generated by utilities, communications providers, and financial companies; there’s nothing to be gained, yet, by moving all those transactions into Box. However, those same organizations, along with most others, deal with tons of content that is perfectly suitable due to its purpose in business processes. Think about loan/mortgage applications, cell phone contracts, and applications for utility services; all of these could easily be moved to the cloud. And now (well, when EKM gets to general release) it can be done with just that little bit extra assurance of security. Which brings me to another point, which I’ve made before …
Organizations are going to have a mixed bag of content repositories for the foreseeable future. Once EKM goes to general availability I’d love to have a bar chat about which is more secure; Box, on-premises, or the hosted private data centre. Based on what I know about some orgs I’ve worked with, I’d rather they put their content in Box, with or without EKM. I digress …
My point is that hybrid is a reality and that everyone involved in managing content (vendors, customers, regulators, legislators) is going to have to figure out how best to deal with access, security, collaboration, and everything else that goes into managing content as an asset. Part of that is understanding that not all content is created equal and can be treated the same. For me the end game has to be putting the users at the center and not forcing them into Cirque de Soleil-like contortions to gain access to the content they need to execute the task at hand. If Box’s track record is anything to go by, I’m optimistic that they haven’t lost sight of ease of use with the EKM beta.
The title of Aaron Levie’s (Box CEO) post announcing EKM is Breaking the Last Barrier to Cloud Adoption with Box Enterprise Key Management (and I thought I liked long titles). Uhm, no. Hell, EKM won’t even break down the last legitimate barrier. There is still a lot of Fear, Uncertainty, and Doubt (FUD) to overcome in getting organizations to move to the cloud (not a legitimate barrier). Organizations worry about data sovereignty, sometimes legitimately. Some contexts just don’t lend themselves to a smooth cloud experience (from twitter this am, via Laurence Hart “Some agencies require govt clearance to have access to encryption keys and/or be US citizen. Box can’t do that for workforce” – he’s not wrong. Laurence expands on the quote in this post.).
If I were Box I’d handle the above like this:
- FUD – time, tide, and attrition are your friend – patience, Grasshopper.
- Legitimate data sovereignty issues – influence and wait for legislation; partner up to build/lease/coopt some friggin’ data centres.
- Illegitimate data sovereignty issues – see FUD
- The point that Laurence brought up – don’t sweat it. You can’t play there now anyways.
Box’s announcement about Enterprise Key Management is significant, and it’s a really good thing. However, it’s not the last hurdle and I’d bet money they know that. But it does take away one excuse that that ditherers and FUDders have been hanging on to.
And for those of you who are about to bring up AWS outages – IT’S A BETA!!!