We’ve all had one of those days when you think that your job has no meaning. And I’m sure some people look from the outside at someone working in technology consortia and think “Wow…that’s pretty arcane.” But I need to look no further than Black Friday and Cyber Monday to realize that the work we do here at Virtual has a pretty significant impact on the world.
You’ve just spent months navigating the formalities of incorporating a new consortium and all the associated legalities and growing pains that will allow you to work with industry peers.
Now it’s time to begin the real work of identifying annual goals and objectives. Your chances for success will be much higher if you build a strong foundation. Here is a handy checklist you should have before you begin to operate. Most of this checklist is also relevant for other associations seeking a blueprint for operational success.
starting a consortia,
Launching an Association,
After more than nine feet of snow in Boston, I saw something I haven’t seen a while this week. My lawn. And it wasn’t a pretty sight. All that snow brought gravel, matted leaves, trash and who knows what else on to my property.
For a technology consortium that plans to create any type of deliverables -- particularly specifications -- an intellectual property rights (IPR) policy is absolutely essential. Not having one will almost certainly discourage some or all participants from actively contributing to such efforts. Worse, adoption of your organization's specifications will almost certainly be limited if implementers are not sure what licensing rights they have or need. Consortia do themselves a big favor, then, by defining and making readily available IPR Policies as early into the organization’s life cycle as possible. What's more, associations are generally encouraged to develop such policies before any work on deliverables has begun. While all IPR Policy negotiations among members of a technical consortia can expect to get contentious at some point -- and why not, given the potential financial stakes involved -- the process only gets thornier when a late-to-bloom IPR Policy is the only thing standing in the way of technical progress.