Strategic Technology Analytics

Firefox's Enterprise Hangups

While Firefox offers scads of benefits there are lots of reasons why enterprises might think twice before deploying the platform. Here are some problems pointed out by  Mike Kaply, Yuriy Krylov, and friends. See the posts for suggestions as to how to address some of those issues. Much of this content will become a sort of working plan for the Enterprise Working Group

1. Release lifecycle is too short. Mozilla only supports previous Firefox version for six months after the next release is too short for many large enterprises. Most large organizations  only deploy new software once or twice a year, so half the support period could well be wasted if deployed at the wrong time of year. One year support after the release of the new version is critical.

2. Enterprise level phone support is missing

3. The business case for switching to Firefox is far from obvious.

4. Compatibility with many third-party applications remains a problem.

5. Intranet application  compatibility is its own challenge. Often internally developed applications will take years to write and then are incompatible with new  browsers.

6. Better Active Directory and Microsoft installer support is needed.

7. Better forms support. Mozilla this week was rumored to have cut off support for Xforms. (Can anybody verify?) 

8. No easy way to enforce corporate restrictions around information sharing between departments and yet share bookmarks.

9. No easy way to synchronizing bookmarks across multiple browsers.

And two others from a great post by Yuriy:

10. Enterprise Settings Management -

• How do we flip a setting on every Desktop in the event of a vulnerability?
• How do we prevent users from altering settings that are deemed risky?
• How can we enable and lock Security Zone-like implementation in Firefox

11. Granular Addon Management -

• How can we prevent a user from installing or uninstalling an extension without having to compile extensions into the browser itself?
• How do we internalize extension repositories so we can "Bless" extensions before our users get to them?
• How can we disable an extension or plugin on all desktops in the event of an emergency?

Group Adjusts Firefox for the Enterprise

Kudos to Michael Kaply and Yury Krylov for organizing the Enterprise Working Group. The first meeting will occur next week  The group goals to develop enterprise management and security for the Firefox. More specifically:

• To establish a unified governance body around Enterprise Firefox.
• To drive Enterprise requirements for the benefit of all Enterprise-scale firms and institutions
• To help each other succeed in deploying Firefox within our environments
• To recruit like-minded firms
• To share risk and cost
• To use industry influence to "raise the bar" on Web Browsers and push for WebDev best practices and open standards
• To offer perscriptive guidelines around Firefox to peers

The group's first phone call will take place on July 25th at 10:00am Pacific, 1:00pm Eastern. The meeting details are as follows:

• 650-903-0800 or 650-215-1282 x91 Conf# 280 (US/INTL)
• 1-800-707-2533 (pin 369) Conf# 280 (US)

Each call will be organized around a series of themes. The first call will be about "Experience" and Mike hopes to get folk talking about their experiences around Firefox and the importance to the organization.  Two weeks later the second call will be about "Wishlist"  where folk will have the opportunity to fill in what they think is missing from Firefox for enterprise deployment. Anonymous participation is possible and even encouraged.

'Eweek' and Enterprise 2.0

Next month, the good folks at eWEEK will run a feature of mine on enterprise bookmarking and tagging platforms.

it's very much a work in progress and would look forward to input you might have. Right now we'll examine the use cases for these platforms and share insights from major organizations who're in various stages of deploying them.

Got a use case, favorite vendor, or feature that you'd like to see covered? Drop me a line here or at dave@stanalytics.com and let me know.
Dave

Long Live the Uber-User

Stowe Boyd builds on a post in January, pointing out yet again that work is evolving away from groups and toward the individual:

First of all, I believe that because of the way that we live and work the individual is the new group [see my original post on this from January]. Stated differently, apps that purport to help us order our work should start by solving the problems of the individual, realizing that one of the issues involved in work is sharing with others.

So, I am amazed to see how many apps continue the old, old ways, where membership in groups is the primary (if not only) notion at work. All of these apps that support projects as a collection of folders into which we move documents and people get access to them through group membership.

All of which is a why you see startups -- such as JackBe, Coghead, and LongJump, and more recently BEA and IBM -- delivering mashups for the rest of us. These products assume that users, not traditional developers, will create the applications -- and business -- of tomorrow. The collective brain trust that is the user community is IT's greatest asset.

I made this point last year in an April 11th post in CMP's VoIPLine newsletter. By embracing -- even encouraging -- the uber-user, IT gets a homegrown SWAT team that can respond far faster to the business than traditional ITers because the members of that team are part of the business:

....Yet precisely those uber-users constituting the brain trust will help IT translate business requirements into technology imperatives. Group and department managers understand the needs of their respective business units, but they're vision may be myopic. In some instances, they may fail to grasp the working realities of their people. In other cases, they may lack the know-how to pinpoint what problems might be solved with today's technology.

Uber-users, on the other hand, are often pondering or grappling with the problems IT will look to solve in the future. "Power users are the bleeding edge of technology usage. By understanding the challenges and success of the power users, IT can develop the best practices and lessons learned before the technology is deployed companywide," says Zeus Kerravala, vice president of the Yankee Group.

By filtering technology suggestions and insights from this bleeding-edge group through its management, IT can received an in-depth, sanity-checked view of organizations' requirements from the folks in the field.

IT could then bring these early technology adopters into an extended 'first-strike team.'  This team would become the beta group for the enterprise, ultimately the organic support crew throughout the organization, and the watchdogs on potential security threats....

Off on My Own

Life changes are a bit nerve-racking but also incredibly exciting. Starting up Strategic Technology Analytics has been a dream of mine for years, but one thing or another got in my way. Now that I've finally left the mothership of Network Computing to launch this gig, I'm finding it awesomely exciting. New projects, new contacts... it's a blast! Tune in a bit later for details on what lies ahead.