Note: this post contains links to every craft brewery in British Columbia and Alberta that I could find. Sadly, I have yet to sample all of their wares.
Anyone who’s been paying attention lately, or who has met me in person, knows that I’m fairly passionate about Information Management and Craft Beer. Depending on the day, my passion for one is slightly higher than my passion for the other. What does one have to do with the other? I’m glad you asked. Please bear with me, this may take a while. Three things happened that resulted in a new vision for me:
- In late June at a networking event in Calgary I met Chris. Chris is one of the co-founders of Caravel Craft Brewery in Calgary. Over a couple pints of IPA from Last Best Brewing, Chris and I started chatting about beer. It turns out that we both love beer, though he knows a ton more about it than I do. My expertise is limited to knowing what I do and don’t like.
- A few weeks later, just prior to the Calgary Stampede, I saw a feature on CBC News about craft beer being shut out of official Stampede events because one of the Big Beer companies had the beer contract. One of the guys from Tool Shed Brewing was talking about how there is more than enough space and thirsty Stampeders for all to benefit. And, what better place and time to showcase all the wonderful Alberta craft beer producers.
- A snarky comment about whether a tour of Village Brewery could be used to make money led to a “why not” moment. I took the picture in this post during that tour, by the way. I also ate a cascade hop pellet – that was a mistake.
So far I’ve been able to find 156 craft brewers in British Columbia and Alberta. Starting with Alberta, I decided that I was going to reach out to all of them and pitch my services to them. I mean, they have a fair bit of paperwork to deal with, right? They produce alcoholic beverages which means much governmental regulation stuff to deal with. They use big shiny equipment which means maintenance and safety stuff. They do stuff which means various types of operating procedures. I’m betting that there is a lot of paper to deal with in a craft brewery and I want to help brewers get rid of it as much as possible. Basically, I want the brewers to be able to concentrate on brewing great craft beer, not pushing paper around.
So I wrote to all the breweries in Alberta telling them what I wanted to do and why. The first response I got was a phone call from the CEO of a brewery located in Calgary. The dude called within 15 minutes of my email and we chatted for about 20 minutes. However, he wanted to chat about craft brewery specific ERP (there is such a thing) rather than content management. So now I’ve got to go and reach out to a bunch of brewery management software vendors, mobile app developers, and consultants to see if we can collaborate (I think we can).
There is a market there, but information management / governance is not the springboard (something I’ve said for some time now, frankly). It’s going to rely on solving the immediate challenges the brewers have and moving on from there. I’m not saying IM and IG aren’t important, they’re just not the immediate need.
So what does the above have to do with the Cloud? Well, a lot, actually.
One of the really cool things I’ve noticed about the craft beer community is that it’s, well, a community as much as it is an industry, maybe more. Despite being competitors, craft brewers collaborate, a lot. Not only do they get together and jointly concoct sudsy, hoppy wonderbeers, they invite others to have guest taps and share brewing facilities to help each other out.
Now, if I look at many of the companies involved in cloud content related stuff, I notice the same thing. Perhaps not with the same level of artistry and fun, but it’s there. If you look at companies like Google, Dropbox, Egnyte, Microsoft, Box, Splunk, GlassIG, …. etc., you’ll notice the level of collaboration and cooperation that exists. In fact, it’s this very collaboration and cooperation that’s going to allow many of these companies to be the core set of cloud technologies that make up the next generation of Information Management and Governance solutions. Craft brewers being what they are, I suspect that cloud apps are going to be of far more interest to them than on-premises solutions.
In the same way that craft brewers experiment with techniques and ingredients, cloud vendors experiment with features, functions, methods, and requirements. Just as brewers have an openness about them, cloud vendors (the good ones) do as well. The end result in both cases is better end products for all. This Brews Brothers collaboration from Parallel 49 Brewing was pretty cool for beer fans; cloud vendors are seemingly announcing new collaborations every week that are pretty cool for those of us interested in managing and governing content.
156 BC and AB Craft Brewers
Information governance (IG) is all the rules, regulations, legislation, standards, and policies with which organizations need to comply when they create, share, and use information. Governance is mandated internally and externally. (PHIGs IMC Inc – 2014)
The above graphic, courtesy of the Information Governance Initiative, presents facets of Information Governance. I don’t agree that everything in the graphic belongs under IG, but it does illustrate how all encompassing and complicated IG is.
With cloud content management, collaboration, and storage offerings becoming more and more accepted, IG needs to adapt. No longer can organizations govern and manage information as if it’s paper or as if it’s stored in on-premises, silo’d repositories. Vendors and their clients have rethought how to work with information; users have come to expect great experiences when working with information in the course of their daily jobs; now we need to rethink how we govern and manage information.
We’re at a point where the whole IG profession must change. It’s not just about the people practising the profession adapting, it’s also about how we actually execute that needs to change. Coming out of a couple conferences a while back I put my thoughts down. Read them for a little more insight, if you wish. I’m convinced that we’re at a point where, together, we can make a huge impact on how IG gets done, and actually get adopted by information workers. At 10am PDT on June 29th Box’s Jessica Fain and I will be chatting about How to Succeed at Information Governance in the Cloud; join us and join in on the discussion – we’d love to get your thoughts.
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.
BoxWorks 2015 ran from September 28th to September 30th in San Francisco. Day 1 was for us analyst types and for CIO’s; the general conference ran on the 29th and 30th. Attendance numbers that I heard ranged from 6,000 to 9,000 – I have no clue how accurate these numbers are. Anyways, here’s my thoughts on some of the key announcements / moments, from my perspective … Oh, this Box post has all the goods from the event …
Aaron Levie’s fireside chats with Tim Cook, John Chambers, Ed Catmull – The Tim Cook chat was, I think, one of the most anticipated events of the conference for many people. It was good, nothing special for me. The chat with John Chambers, however, was the one that I found resonated most with me. I missed all but the last 5 minutes of the chat with Ed Catmull.
Best comment at the afterparty – “Is that One Direction?” For what it’s worth, One Republic is way better live than I thought they’d be. Too bad I only got to see them for about 30 of their 90 minute show.
Realization on the way home – Over the last 18 months or so I’ve met a lot of people from Box, either in person or on the phone. There’s not one where I’ve come away from meeting them thinking “what a dick.” That’s pretty impressive.
Jeetu Patel actually categorized Box as ECM during the analyst summit. He’s the first Box exec (I think) that actually made that statement.
I reminded Whitney Bouck that earlier this year I referred to Box as being part of the information governance landscape and that she wasn’t thrilled when I said that. She just smiled at me.
Proof that some people still don’t get it –
That some people (analysts, even) are still including Box in the same category as Dropbox, OneDrive, Google Drive, Egnyte, etc. is, I dunno, stupid, I guess.
Box Capture – see my quick review here.
Better image / video support in previewer – Box announced enhancements for interacting with 3D, video, and DICOM images directly within the Box previewer. The DICOM bit doesn’t interest me much, but it is impressive. The 3D and video (up to 4K, adapts to bandwidth issues) enhancements are going to be a big deal for the clients I deal with. Training, safety, and technical content will benefit hugely. Marketing, sales, media & entertainment, … any use case that relies on rich content and the ability to collaborate on it is going to benefit. Oh, and all this is delivered in HTML5.
Box Platform – In my opinion, the announcements about Box Platform and its separation from Box’s product group are huge. I know I got excited when Box made their original platform announcement (last year?), but now I think we’re really going to see the fruits of that decision.
Platform’s going to allow app developers, including Box, to focus on providing functionality to their users without having to worry about all the content services and security stuff (i.e.: pesky infrastructure stuff) in the back end. Jeetu Patel (SVP Platform & Chief Strategy Officer) estimates that folks building content apps spend about 80% of their time buggering about with infrastructure related stuff and only about 20% building the core functionality that users want/need. Now, I don’t think app developers will ever get to spend 100% of their time on only the core functionality, but even a 20% increase (very conservative, IMO) would yield significant benefits. Time to delivery, innovation, creativity, and quality would all improve.
The impact to corporate IT is going to be significant as well. To all you CIO’s and IT execs hesitant about cloud because in reality you’re worried about being marginalized or losing power / relevance: get over yourselves. The opportunity is there for you to shift from fixing printers and patching outdated systems that are barely able to stand up anyways to actually becoming MORE relevant by adding value to your organization and delivering functionality (apps) that add business value. And I strongly urge you to check out what John Chambers had to say. Read it however many times you need to to get it (this goes for the couple analysts that claimed Box is not a platform, as well).
This tweet from Jeetu Patel sums up nicely what the impact will be to users and developers:
Something else that makes Platform such a compelling story is that users won’t even know that they’re interacting with Box. They’ll simply use an app to get their work done, and all the content services will be in the back end. In many (most?) cases there won’t even be a need for users to have a Box account. IMO, this path leads to delivering on the original promise of Enterprise Content Management.
Content Management & Collaboration – There’s a lot in this bunch of stuff announced by Whitney Bouck (GM, Enterprise & SVP, Global Marketing), so I’m just going to focus on the stuff that really stands out to me.
The whole Box/IBM thing is “f**king brilliant”, as I said to a couple of Box and IBM execs at some high falutin’ gathering. Remember when I said that a hybrid approach was needed? Well, the Box/IBM partnership provides EXACTLY that. Box+Content Navigator and Box+StoredIQ (is it pronounced stored ick?) provide a unified view into Box and on-premises content, along with the ability to do some analysis, tagging, discovery, and classification. It’s boring stuff from an apps point of view, but for being able to put together an information governance strategy it’s absolutely critical and kinda sexy.
Box and IBM are working together on further integrations, including Datacap and Case Manager. There’s going to be a whole bunch more use cases that open up to them with these integrations. It’s not that Box couldn’t participate in these use cases previously, it just couldn’t be done end-to-end. Now, to the users’ benefit, there’s really no reason to jump into another tool to execute any portion. Human resources, mortgage & lending, claims management, incident investigations, etc. will all be able to be executed from within a single UI, regardless of whether the content is on-prem or in the cloud. That’s friggin’ cool. Oh, and the IBM MobileFirst for iOS is gonna have a pretty big impact on the whole Box partnership thing, too.
Hmm, I wonder if there’s any plan to hook Datacap to Box Capture. If not, THERE SHOULD BE. At the very least there should be some plans on the roadmap to provide similar capabilities.
Storage & Security – Perhaps some of the most significant announcements at the conference relate to changes in security and storage options.
Box’s Enterprise Key Management (EKM) announcement earlier this year was key (no pun intended) in eliminating some security concerns about moving content to the cloud. However, it turns out that EKM is expensive and a bit of a chore to configure and manage. In order to alleviate those concerns Box announced that, next year, customers will be able to use Amazon’s AWS Key Management System. This changes things from a hardware appliance based approach to a software based approach, without sacrificing security. It ought to make things less expensive and cumbersome for customers.
The one thing I don’t like about the whole key management thing is that customers lose the benefit of full text search. The partial solution to that is to rely on metadata for searching.
In the coming quarters customers are going to be able to choose from among three storage partners for storing their Box content (I think we can all guess who they are). In addition to storage provider flexibility, this will eventually afford customers the option of where (think data residency) to store their Box content. There are some details still to be worked out, but this could be massive for organizations that have operations across multiple jurisdictions and have to deal with a myriad of data residency issues. I fully expect that as time marches on there will be more choices for customers.
Between the EKM changes and the storage flexibility, I foresee the day when customers will be able to choose what gets stored where, and what portion of their content gets secured via the key management solution (it’s currently an all or nothing proposition).
The Crystal Ball – This was one of my favourite sessions. A bunch of folks from Box’s product team presented a bunch of stuff that: 1) will be delivered this year; 2) will be delivered next year; 3) may not even get on the roadmap (exploratory stuff, you know). All I’ll say is that there’s nothing I saw that shouldn’t make it into the product at some point, with one exception. But, it’s all about priorities, babies.
Metadata – Much of the good stuff that was announced is going to rely on having really solid metadata. Regardless of the release of Metadata Template Editor earlier this year (my thoughts about that), applying metadata to content in Box is still a huge pain and needs to be automated. I know Box is thinking about this and I hope that they deal with it sooner rather than later.
Services – Box is going to need to beef up their services organization. Even a year ago I think they could get away with having a roster of consultants that are almost exclusively technical in nature; that’s all changed. Between the IBM partnership and stepping out of EFSS into ECM, they’re going to need a services group that includes ECM and information governance SME’s, business solutions folks, and some other non-technical skill sets. Will they do this via partnerships or by bringing the skills in-house? I don’t know and I don’t think it makes a huge difference. All I know is that they need to do it fast.
As I said during the conference:
Box is going to need a services organization to support that.
Anti-Big Blue – The Box/IBM partnership has accelerated Box’s ability to provide ECM and information governance capabilities. However, for whatever reasons some organizations simply will not have anything to do with IBM (I know, weird, huh?). However, these organizations are still going to need the same capabilities. Will Box take steps to provide these capabilities or forego the opportunities?