Tag: Yammer

Social SharePoint and Yammer Evolution
Social SharePoint and Yammer Evolution
Presentations

Take a look at Social SharePoint and Yammer Evolution Microsoft has purchased Yammer for 1.2 Billion USD and the face of enterprise social networking will never be the same. In this session we’ll look at the new business productivity of enterprise social networks and dig into how our world has changed. We’ll dig into SharePoint integration,… READ MORE

Socialised and Mobilised: How the Most Successful Businesses are Using SharePoint and Yammer
Socialised and Mobilised: How the Most Successful Businesses are Using SharePoint and Yammer
Webinars

Using SharePoint and Yammer to get Socialised and Mobilised Most companies today realise the importance of connecting with their customers, employees, and partners through social technologies, such as SharePoint and Yammer. For corporations to successfully transform into social business enterprises, they must learn how to leverage these technologies to create a more adaptable organisation. Mark… READ MORE

Yammer Feedback… The New Inbox Hell
Yammer Feedback… The New Inbox Hell
Blog Posts

I promised a constructive blog, and that’s what I plan to provide, but I do need to share what I’ve seen happen over the last couple of days. Yammer doesn’t suck. The inbox definitely pushes buttons on fundamental functionality and that’s why it’s so important that they get this right.

10 Reasons Why SharePoint and Yammer Really Make Sense
10 Reasons Why SharePoint and Yammer Really Make Sense
Blog Posts

Have you heard the news? Microsoft to Aquire Yammer – How could Steve Ballmer, CEO, Microsoft say: “Yammer adds a best-in-class enterprise social networking service to Microsoft’s growing portfolio of complementary cloud services.”
When Yammer was announced as a possible acquisition for Microsoft, I smiled and giggled inside. I’ve known for over a year that Yammer was more than a few SharePoint web parts, it has real enterprise momentum and a social community that reminds me of what happened with SharePoint Team Services in the first version.