<!--DEBUG:--><!--DEBUG:dc3-united-states-software-in-english-pdf-2--><!--DEBUG:--><!--DEBUG:dc3-united-states-software-in-english-pdf-2--><!--DEBUG-spv-->{"id":2025629,"date":"2021-11-03T21:52:00","date_gmt":"2021-11-03T19:52:00","guid":{"rendered":"http:\/\/nhub.news\/?p=2025629"},"modified":"2021-11-04T00:04:08","modified_gmt":"2021-11-03T22:04:08","slug":"teams-and-webex-what-if-microsoft-and-cisco-merged-their-platforms","status":"publish","type":"post","link":"http:\/\/nhub.news\/ru\/2021\/11\/teams-and-webex-what-if-microsoft-and-cisco-merged-their-platforms\/","title":{"rendered":"Teams and Webex: What if Microsoft and Cisco merged their platforms?"},"content":{"rendered":"<p style=\"text-align: justify;\"><b>Rather than competing in the collaboration market, Microsoft and Cisco could join forces and deliver even more for the customers.<\/b><br \/>\nWhen Cisco had its big Webex unveiling last week, I was impressed. This week, Microsoft Ignite is under way, and Microsoft is treating collaboration like it once treated. Net. As I write, Cisco is at the event, talking about how the two companies are collaborating on development tools and collaboration\u2019s significant impact on Cisco customers using Azure and App Dynamics. Microsoft and Cisco aren\u2019t natural competitors and have partnered in the past with Unified Communications. That got me thinking: what if they collaborated on the future of communications? What if they worked together and either blended Teams and Webex or shared technology to a degree that both products could be equally enhanced and interoperated more seamlessly with the other? The core differentiators Microsoft is showcasing this week with Teams include things like deep application integration across their development and productivity tools and the use of avatars and holograms. Last week with Webex, Cisco exhibited its deep integration with telephony, the use of employee monitoring while preserving privacy (for management), and the use of holograms. (Both products use Hololens.) So which one should you choose? You\u2019d pick Teams if you\u2019re wedded to Microsoft\u2019s toolset, and you\u2019d use Webex if you wanted to integrate your communications methods (phone + video conferencing) and if you needed to assure your remote employees aren\u2019t at risk. Your choice is between maximizing your productivity process or maximizing your employee effectiveness. And your new problem is that the \u201cor\u201d doesn\u2019t make sense \u2014 I can\u2019t think of a business that doesn\u2019t want to do both. You could use Teams specifically for IT and software development (if you do software development), and you\u2019d use Webex for staff meetings. Depending on the nature of collaboration needed, you could use either to connect the customer, vendor, or partner \u2014 Teams for software, Webex for everything else. Collaboration tools are a force multiplier for the companies that make them. Microsoft Teams would likely have a more significant economic impact as a tool Microsoft uses than a product Microsoft sells because it makes Microsoft more efficient. The same is true for Webex and Cisco, which makes the competition between the platforms a lower priority than both platforms\u2019 capabilities for their respective vendors or users. Selling these tools is incremental revenue; using these tools enhances everything these companies do internally and externally. Car companies often collaborate on cars and engines; Toyota and Suburu, for instance, partnered on the FR-S and GT86. They shared the development cost and created a pair of sports cars that each could sell with a unique flavor, increasing the overall volume sharply and potentially reducing costs due to increased economies of scale. In the case of Microsoft and Cisco, a collaboration would create a substantial competitive advantage against other existing and emerging products that wouldn\u2019t match on features or interoperability. (Hardware, like this offering from Poly, would more easily work with both than with a non-aligned competitive offering.) Rather than both Teams and Webex going down separate and redundant paths, Microsoft and Cisco could develop the same core features for each while optimizing for their individual customers\u2019 needs. They could divide the work, with Cisco more focused on increasing network performance and integration with Cisco tools. In contrast, Microsoft would focus on better Hololens integration and their tools \u2014 and both could advance avatar capabilities that need to be far more realistic. Both Microsoft Teams and Cisco Webex lead the collaboration market with unique features and capabilities. But they each have unique advantages. Teams is more integrated with Microsoft\u2019s tools and should increase productivity within that product set. Webex is more integrated with existing telephony tools and does a better job assuring work\/life balance and department\/team dynamics (potentially improving employee loyalty and retention.) I can\u2019t think of a single company that wouldn\u2019t want both sets of features. In addition, both Microsoft and Cisco would use their respective tools to improve each company\u2019s own performance. By joining forces, they would set a new bar for the market, nearly impossible for any rival to match. By sharing the effort to advance their respective products, innovation would accelerate, too, making the combined effort almost impossible to catch. Stranger things have happened.<\/p>\n<script>jQuery(function(){jQuery(\".vc_icon_element-icon\").css(\"top\", \"0px\");});<\/script><script>jQuery(function(){jQuery(\"#td_post_ranks\").css(\"height\", \"10px\");});<\/script><script>jQuery(function(){jQuery(\".td-post-content\").find(\"p\").find(\"img\").hide();});<\/script>","protected":false},"excerpt":{"rendered":"<p>Rather than competing in the collaboration market, Microsoft and Cisco could join forces and deliver even more for the customers. When Cisco had its big Webex unveiling last week, I was impressed. This week, Microsoft Ignite is under way, and Microsoft is treating collaboration like it once treated. Net. As I write, Cisco is at [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2025628,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[93],"tags":[],"_links":{"self":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts\/2025629"}],"collection":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/comments?post=2025629"}],"version-history":[{"count":1,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts\/2025629\/revisions"}],"predecessor-version":[{"id":2025630,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/posts\/2025629\/revisions\/2025630"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/media\/2025628"}],"wp:attachment":[{"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/media?parent=2025629"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/categories?post=2025629"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nhub.news\/ru\/wp-json\/wp\/v2\/tags?post=2025629"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}