The Microsoft connection clarified
Yesterday, we posted an explanation of what happened to Skype on August 16. Some reactions to the explanation, however, have reminded us of one of the basic tenets of communication: It's not what you say. It's what they hear.
Context & Ripple Effects
Three days after posting its August 18 account of what happened to the network on August 16, Skype found that readers had heard something different from what it wrote: a version in which Microsoft was the culprit. Heartbeat's new post corrects the reception, not the record — 'It's not what you say. It's what they hear,' as the blog itself concedes.
The story has also travelled well beyond Skype's own channel: InfoWorld ran it twice the same day under a 'perfect storm' banner, which means Skype's framing of the failure is now competing with the trade press's framing for the audience that matters most to it — the IT readers evaluating whether Skype belongs anywhere near their organisations.
First-order effects
- Skype's own explanation became the story: the clarification pushes responsibility for the August 16 failure back onto Skype's engineering account and away from the Microsoft-caused reading spreading among commenters.
- InfoWorld's same-day double pickup places the outage narrative squarely in front of enterprise and IT readers, forcing Skype into a defensive posture over its own incident report.
Second-order effects
- Business evaluators now have a documented large-scale failure, amplified by trade coverage, to weigh against Skype's price advantages — sharpening the reliability-versus-cost calculus for any organisation considering it alongside paid conferencing alternatives.
- Microsoft gains nothing from the association either way: even a clarified non-culpability leaves its update machinery publicly entangled with a rival communication service's worst day.
Third-order effects
- If a mass-market communication service's failure can be plausibly attributed to behaviour in someone else's software ecosystem, operators face a structural accountability problem: customers expect carrier-grade answers while the actual causes sit outside the operator's control.
- Public, iterative self-post-mortems — explain, get misread, clarify — look set to become the standard playbook for consumer-platform incidents, replacing single official statements.
The trend: Consumer VoIP platforms are discovering that incident response is a communications discipline as much as an engineering one, with every explanation subject to reinterpretation by press and public.