A friend-of-a-friend (”SJ”) and I were talking about Web 2.0 as part of his research for a major London based VC. He asked me, “Why Web 2.0? And Why now?” In large part for Silicon Valley geeks, Web 2.0 is nothing new and it’s an old topic. Guess what, rest of the world and the enterprise are waking up to Web 2.0 now.
Here’s a summary of what I explained to him:
1. Web 2.0 is an attempt to fulfill the promises made during the Web 1.0 days. Office on the web, online calendar, utility Computing for the masses, content sharing, collaboration, anywhere/anytime on-demand storage, one-click publishing, etc. are some of the examples, where we heard lot of chatter during the late 90s but we are seeing real applications only now.
2. Growth of user-created content. Simply put, blogs and wikis are allowing non-geek crowd to participate in the 2-way web. The surge of tools, commoditization of CMS, 1-click publishing and new methods of monetization are pushing the limits and expectations of both consumers and innovative startups.
3. Money is no longer just waiting on the sidelines (it has started talking lately). Web 1.0 bust is now digested and pooped from our intestines. At a recent New Tech Meetup in Palo Alto, I overheard couple of angel investors introducing themselves to the companies demoing over there.
4. Browser as a platform has matured. I gave him a very simple example, of rectangles with smooth/rounded edges rendered on web pages. During the 1.0 days it was quite a hack doing that using tables and images. In 2.0, it is done by a few lines of CSS. And then there is AJAX, which has made the browser a much more mature platform.
All of the 4 are the necessary ingredients in that order of decreasing priority, for making Web 2.0 happen. More than that and contrary to a popular notion, Web 2.0 is not just about the advancements of browser as a platform, or social networking at large, or raw bandwidth/storage for video at cheap prices, or just the sheer volume of user-created content, but it’s the ideas around simple applications which are now being done right (of course, technology has helped). It’s the simple applications which everybody wanted to reduce their drudgery while working with computing devices. That’s why it’s happening now and has a new version number.
Tags:Web 2.0 Expo Web 2.0 Writable Intranet Enterprise 2.0
Archive for the ‘Enterprise 2.0’ Category
Why Web 2.0? Why now?
Sunday, April 15th, 2007Enterprise Tagging: How Sales & Marketing can exchange information
Friday, November 24th, 2006Tagging on the internet has allowed discovery of information from individual blog posts, to stories, to stock tickers, to photos, all of which has given rise to Folksonomy. Large corporations have Marketing departments spend millions of dollars in marketing material which never get shared with the sales department — event if they do, it’s after spending tonnes of money in building/buying some proprietary software to automate the process.
The reality is:
* Marketing is global, so are sales
* Marketing material is produced by different teams viz. marcom, product marketing, channel marketing, event people, etc. etc.
* Sales department sits in their own silo — esp. in large organization, Marketing material never reaches sales, even if it does, either it’s not timely or not in it’s entirety or maybe after spending thousands of dollars for a software to properly tag the proprietary meta-data
* Meta-data is a moving target — If a system is used for storing the attributes in an RDBMS — any change in meta-data either renders the content undiscoverable or leaves it with incorrect attributes.
Come tagging to the rescue, being flexible, tags can be defined on the go — however good idea to have some high-level tags; as in product names, business units, etc. The second level tags could be platforms, customer names, companies, etc. How the information can be exchanged? Marketing runs a blog with the single objective of exchanging information with sales (in this case say marketing collateral). Every post is tagged with the product the collateral belongs to, the second level tags being platform, industry vertical, target audience, etc. etc. Sales can receive this information by either subscribing to the feeds or by searching for the tags on the blogs. WordPress supports category level feeds.
Tags: Writable Intranet, Enterprise 2.0
Enterprise Tagging: How Sales & Marketing can exchange information
Friday, November 24th, 2006Tagging on the internet has allowed discovery of information from individual blog posts, to stories, to stock tickers, to photos, all of which has given rise to Folksonomy. Large corporations have Marketing departments spend millions of dollars in marketing material which never get shared with the sales department — event if they do, it’s after spending tonnes of money in building/buying some proprietary software to automate the process.
The reality is:
* Marketing is global, so are sales
* Marketing material is produced by different teams viz. marcom, product marketing, channel marketing, event people, etc. etc.
* Sales department sits in their own silo — esp. in large organization, Marketing material never reaches sales, even if it does, either it’s not timely or not in it’s entirety or maybe after spending thousands of dollars for a software to properly tag the proprietary meta-data
* Meta-data is a moving target — If a system is used for storing the attributes in an RDBMS — any change in meta-data either renders the content undiscoverable or leaves it with incorrect attributes.
Come tagging to the rescue, being flexible, tags can be defined on the go — however good idea to have some high-level tags; as in product names, business units, etc. The second level tags could be platforms, customer names, companies, etc. How the information can be exchanged? Marketing runs a blog with the single objective of exchanging information with sales (in this case say marketing collateral). Every post is tagged with the product the collateral belongs to, the second level tags being platform, industry vertical, target audience, etc. etc. Sales can receive this information by either subscribing to the feeds or by searching for the tags on the blogs. WordPress supports category level feeds.
Tags: Writable Intranet, Enterprise 2.0
Why the Hiring Process sucks and How Writable Intranet can fix it
Friday, August 4th, 2006One of the biggest roadblocks in hiring process is (absence of) collaboration. Again, email and word documents are used for accepting resumes, screening, providing feedback and managing the queue, prioritization, etc. There are multiple parties involved for a single job opening viz. Hiring Manager, Recruiter, HR Manager, HR Specialist (the lady who schedules the interviews!), the interview team, Hiring Manager’s boss, etc.
All the parties involved use e-mail and word documents buried in e-mail to gather feedback and collect data points, which sucks big time. It’s a pain managing the approval process, why a candidate is good on resume, who was phone-screened and rejected/approved. This whole workflow is a mess in most large and small companies. There are vendors however who have software/services for automating this; some are focused on resume management, others are geared towards candidate management, while others specialize in managing the job descriptions. A good software costs at least $200K-$500K in TCO, including license fees, software costs, hardware costs, people costs, training, etc. On top of that, in my experience, HR is last in the queue to get IT support to create an infrastructure to manage the workflow.
What’s needed bare minimum is a collaboration tool for the Hiring Managers where they can track resumes, annotate them as needed and capture feedback from the interview team. I think the Writable Intranet in the form of Wikis could be a great platform. Here are some ideas:
- Create a centralized Wiki run/managed by the HR department.
- Each page on the Wiki corresponds to a an open position within an organization. As the pool of resumes comes in, the resumes are attached as a file and an entry is made as a section for each candidate. The interview team provides individual feedback by entering their feedback directly into the Wiki under the candidate’s section. Thus all the data gets collected in one single place and is visible to everybody
- Security issues? The major thing is reducing visibilty to other people who are not part of the hiring process for a job; depends on the policy as well. Turning off “special pages” and features like “Random Pages” would prevent people from accidentally jumping onto a page.
Easy?