The failure of IT organizations to respond to this demand on account of resource limitations or security concerns can cause wireless backlash, encouraging workers to set up unsanctioned wireless systems in their departments or offices, which don't have central IT support or security. Also, it can set back your organization: If you wait five years to implement your first WLAN, you'll be hopelessly behind the technology learning curve and ill-equipped to implement secure and reliable systems.
WLAN standards, from security to QoS (Quality of Service), are evolving rapidly. If your plan is to wait for the perfect time to deploy wireless, you may miss the boat entirely. It's often better to at least get started with tactical deployments that yield immediate benefits, like installing wireless in heavily used conference rooms.
7. Confusing data rate with system throughput
When the 802.11b wireless standard was ratified in 1998, it was a breakthrough mainly because it was the first WLAN standard to topple the 10-Mbps barrier set by wired Ethernet LANs. Although bits did in fact move across the medium 11 million times every second, the actual application throughput after accounting for MAC (Media Access Control)-layer overhead was only about 50 percent of the data rate. And that was under ideal test-lab conditions. Ethernet, by comparison, is typically about 90 percent efficient.
Aside from MAC efficiency, interference from external sources (microwave ovens, cordless phones) and other WLANs can also stifle throughput.