Here goes:

1 Developer
The developer should be a PHP Harry Potter, with a mastery of Wordpress and/or Drupal. It’d also be nice if this person had some Python chops and had some experience building web applications on Django. They should also have some experience using and managing databases. Some JavaScript skills wouldn’t hurt either. You won’t need a server administrator starting off, but the developer should also have some experience managing a hosting environment. Taped glasses would be optional, but some sort of geeky paraphernalia would be preferred.

1 Bad-Mother Designer
Far too many non-profit and community news startups suck in terms of presenting their content. You need to have a brand and it needs to look professional or hip or both. This person understands web usability and how to build a Web site that’s easy to navigate. This person is also experienced in theming in Wordpress and/or Drupal, having a scary-deep knowledge of XTHML and CSS. The designer should have a lot of experience with the Adobe Creative Suite and be able to produce graphics and ads for print and web. Experience using Flash services and plugins is a big plus.

3 Reporters
Each reporter should first and foremost be a solid journalist and have a hunger for practicing the craft. Second, they should be obsessive compulsive about learning. Part of being an inquisitive journalist is learning new techniques for documenting a story. I would worry more about getting extremely motivated people than candidates with specific technical skills. At the same time, I would try and get a least one candidate who has a really solid base taking video, photos and audio.

1 Editor/Customer Service Representative/Accountant/Evangelist/Cheerleader
The editor will work the most and set a high morale for the organization on a daily basis. It would not be an easy job, but it would sure be one hell of an exciting challenge.

This person would:

• Listen and respond to customer questions, problems and suggestions
• Edit and fact-check stories
• Serve as the spokesperson for the organization
• Organize coverage of planned events and stories
• Update and manage social networking sites
• Track expenses and revenues
• Keep an eye on the web/newswires
• What else??

The First Two Weeks
I would spend the first two weeks running a team and skill-building boot camp. Each person would lead sessions in their area of expertise. This would help build solidarity on the team and a good understanding of roles and workflow. How can we compliment each other? What are our strengths and weaknesses?

And I would do what every good solider does before heading into battle: field exercises. Take your team out on photo-walks, video-walks, audio-walks and get them familiar with how the equipment operates in the field. Better they make mistakes when the cost of screwing up is negligible.

I’d also incorporate social events (e.g. share a brewskie or two) and print team t-shirts. Do not underestimate the power of the t-shirt.

I would take at least one entire day a month to schedule a day for training, brainstorming and relaxing.

Why Start So Small?
It’s easier to find 6 really talented people than it is to find 12 right off the bat. Come on, you don’t even have a reputation to help attract people yet.

Start small and farm out what you can. There are a lot of free or cheap web services that can help boost your team’s productivity and save valuable hours. Start with a big staff (10 or more) and you’ve essentially tied yourself to the tracks already. There’s no need to accumulate that kind of debt and it’s important to keep your overhead low. All you really need is cheap office space with reliable Internet service.

A large media organization could easily adopt this model to form an internal startup. In fact, I wish they would do this more often. Generally, big news organizations that rely on centralized IT fail to utilize emerging technologies fast enough. The “guys at HQ” tend to be barriers, not an empowering force.

It’s extremely difficult to deploy and troubleshoot technologies across multiple TV stations or newspapers. Not only that, but it’s nearly impossible to keep up with the dozens, if not hundreds, of differing feature requests coming from each market. “We need this to do that.” The response sure as hell better not be “Get in line.” There’s simply no time to wait.

Questions I Have
One thing I’m unsure about is whether it makes sense to establish the focus/niche of the startup before making the first hires, or involving them in the process? Does anyone have any thoughts?

What would you do to build momentum in the first 6 months?

Would you pay everyone equally? I would tend to pay the developer and designer more, but I’m definitely biased.

What about creating a rotating Editorship between 4 reporters (e.g. a 1-week term)? This might help prevent people from burning out and also spread power and responsibility.

Disclaimer: I own stock in Netflix.

Netflix is doing a great job of opening up lines of communication with its customers. It’s simple and it needs to be a standard for all businesses.

They’ve set up a community using Ning.

They’ve also got a blog. Oh, and did I mention their Facebook page?

Why every business doesn’t have a blog and community (and sometimes wiki) set up is lamebrained. You could literally have all two or three up and running in under an hour using Blogger, Wordpress, PBWiki, Ning or a host of other free/cheap service providers.

It’s especially useful when customers have a complaint or question about your product. In the case of Netflix, it’s been especially useful during the past year in explaining to customers the stopping block for instant viewing on Macs and on Firefox.

It won’t necessarily make the problem go away, but as a customer, knowing someone is listening and working to fix the problem is more than half the battle.

We live in a culture of change and the fast flow of information. The worst thing you can do is forget to lay the plumbing down.

You certainly don’t want to end up here.