One of the first things someone asked me when they found out I’d gotten the New Media Women Entrepreneur grant was what I was going to call it. “Do you have a URL yet?” she asked.
I remain evasive on that question, because I know the trap that I can fall into searching for a domain name first, compromising based on what is available, THEN trying to fit the business model to what the name may suggest. Sounds backward, but oftentimes searching for a domain name is the first activity because it looks like a legitimate business activity.
But what are you branding? Words have meaning and domain names have meanings (or not, if the word is a neologism) associated with them. Is the name representative of what you are delivering?
And so I’ve pushed back, focusing my energies on finding a platform/technologies that will nurture the types of online connections and conversations that I’d like to see in my model…and letting the name evolve from that.
I’ve been asking myself:
- What do you want people to be able to do?
- What are the uses you expect people to have of the technology? How is it better/different than what is currently in use?
- How will I know when I am successful? What activity demonstrates that the technology is working?
I know these don’t sound like questions of a journalist trying to reinvent the business. They’re not. They are questions designed to focus my attention on the larger purposes of the journalistic/community building enterprise…beyond delivering data and information to building the knowledge and capacity for action of the community.
And a choice of a platform affects the larger architecture of the franchise model. Do I use a blog-type software that perhaps embodies ease of use for the franchisees but feels like a push model (traditional content delivery model) to my community? Is the software representative of the collaborative writing space that I’m hoping to model in the community’s actions? Does an open-source solution philosophically match the contributory nature of the environment I want to simulate? Or would a proprietary solution help ensure that there’s motivation by *someone* to continue to build out the software? Each of these questions has consequences and compromises as to whom the tool best serves.
So I’m a philosophy in search of a platform. I’m looking for an architecture like the franchise model that embodies independence, yet collaboration, collective development, yet independent practice. The ultimate solution lies in the in between, the spaces between the either/or models I’ve seen to date.