Hello, guest. Welcome!
EllisLab

News and thoughts from the people at EllisLab.

Company Intranet

Posted by Rick Ellis on March 25, 2008

One of the byproducts of having started out as a company with one employee (me!), and allowing our growth to happen organically, is that until recently we didn’t need much in the way of employee documentation, or even internal policies and such.

Over our first five years, until 2006, we had only grown to four full-time employees including me, plus a couple part-timers.  We didn’t need internal documentation for a group that small.  Everyone communicated constantly. 

All we had was a simple employee handbook that covered the basics, the rest we filled in by talking amongst ourselves.  We discussed all important issues, and often made decisions as a group.  It was a good dynamic.

From then until now we’ve more doubled our staff size, and this year we’re on pace to add three or four more team members.  Unfortunately, we can no longer expect new employees to learn our process, goals, policies, history, and culture through osmosis and direct discussion anymore.  As much as I enjoyed the more personal approach of the past, it doesn’t scale.

The solution we’ve decided upon is to create a staff intranet, as a series of blogs, containing everything that an employee might need to know.  The book on EllisLab, if you will. 

The intranet will also help us, perhaps most importantly, continue to integrate new people onto our team and into our culture.  It’s critical that as we grow we continue to maintain our values, and help new employees adopt them.  This is an area where so many small companies screw up as they grow.

Part of me thinks it would be interesting to make our intranet, at least in part, publicly accessible.  Why not share with the world how and why we do the things we do?  Why not be totally transparent?  It could be a refreshing approach…

Comments

I think that’s a great idea. As a developer, it could potentially be another selling point when convincing clients of the benefits of EE, both from the perspective of transparency, as well as its being another example of the possibilities of EE.

Plus, I’m personally always curious about the internal workings of companies that I respect. I think that making portions of it public would be a great move.

Posted by Nat from Chicago on  Monday, March 31, 2008

Curious if the intranet utilizes ExpressionEngine or not?
If it is another solution it would be interesting to know.
Thanks for any insights into the workings of the EL intranet.

Posted by ty from Ohio, USA on  Monday, April 07, 2008

This part of the reason I continue to stick with Dreamhost for my web hosting. They have had some issues over the past couple of years, but they are refreshingly transparent about all of the issues that come up. I suspect other companies have similar problems, they just don’t share them with their customers. What it reveals is just how much they care about their customers, even if they make some mistakes.

I think you are heading down the right road with being transparent.

Posted by Schwebbie on  Friday, April 11, 2008

Yes, yes, yes…
And the #1 reason for having a partially accessible intranet…
to glean some bits of knowledge about the otherwise Top Secret v.2 ExpressionEngine smile

Posted by ty from Ohio, USA on  Friday, April 11, 2008

Commenting is not available in this weblog entry.
EllisLab Products and Services

Copyright 2002-2008 · EllisLab, Inc. · All rights Reserved

Powered by ExpressionEngine, of course!