• Home
  • About
  • RSS Feed
  •  

    Watch that stream become a wave

    May 19th, 2010

    Hello everyone!

    We are excited to be working to support the Google Wave Federation Protocol in SAP StreamWork to let tools – collaboration or business – work seamlessly between any wave server, including Google Wave!  With SAP StreamWork, we help business be more productive by letting people drive decisions together.  Since our first BETA announcement a number of months ago we have been constantly compared to Google Wave, due to the real-time characteristics of the collaboration patterns we use. While products each have a  different focus, they are also naturally complementary, and from the moment we saw Google Wave we were excited about the possibilities of connecting the two. This year’s Google I/O is our first opportunity to tell the story of how we plan to work collaboratively with Google, the Wave Federation Protocol, and OpenSocial.

    For those of you who are not familiar with SAP StreamWork, it is aimed at transforming the way people work. When Google developed Google Wave it asked the question, “What would e-mail, instant messenger, and collaborative document creation look like if it were invented in the 21st century?” Similarly, SAP asked the question, “How can people solve important business decisions in a natural, fluid way, making every day more effective and fun?”. SAP StreamWork is a new on-demand, collaborative decision-making application that brings together people inside or outside your organization with information for fact-based decision-making and interactive business tools for collecting feedback, strategizing, and brainstorming, and is available today in a free version for anyone.  It is also fully extensible by developers using open REST APIs. in a business context

    Many of you make decisions every day, using a range of tools, from e-mail, to white boards, to shouting matches, to business applications and business intelligence.  We get the work done, but it often becomes chaotic and hard to follow and can hinder clear decisions.  Wave is modernizing collaborative communication; SAP is modernizing business. SAP StreamWork brings together people, information and proven business methodologies to help teams naturally and fluidly work toward goals and outcomes. Teams can assess situations together, develop strategies and make clear decisions, with a full record of what transpired. What better idea than to include anyone with a wave account?

    So this is how we see you rolling in the near future: A supplier just notified you they couldn’t deliver materials that you need tomorrow to continue production.  Crap!  You bring that context fluidly into SAP StreamWork and assemble a team, bringing experts in that industry to see who might have capacity.  Some of the people you know are registered as Google Wave users – instead of having to enter a different system, the business discussion complete with analytical and business tools show up in their wave inbox.  It no longer matters where people are, or what tools they prefer – they can safely make decisions, in real-time, and directly drive the business applications that run the largest companies in the world.  Now that feels like an improvement, yeah?

    At this year’s Google I/O we will show the beginnings of this.  But, what exactly, are we talking about?

    Passing the Wave (Wave Federation):

    At I/O we plan to show how SAP StreamWork has added a Wave Server to the platform to enable conversations between SAP StreamWork and other Wave servers. In SAP StreamWork a user starts an Activity where in they invite other participants to collaborate with them on a work activity like making a business decision. The group can then add the data and tools to guide them through the decision process. When an activity is created, StreamWork creates a new wave and federates the content of that Activity to the Wave server of any Wave users that may have been invited to that activity. With this integration Wave users will be able to seamlessly collaborate with SAP StreamWork users to work on the important decisions they need to make every day.

    Go Go Gadget! (Gadget / Method Interoperability):

    In order to ensure that content from an Activity or wave is properly federated between each other, we had to ensure that the content found in both systems was compatible with each other, and this included Wave Gadgets and StreamWork Methods. Wave Gadgets are shared programs that run inside waves, and are very comparable to StreamWork Methods which are business tools that run inside StreamWork Activities. Theproof of concept will show the compatibility between a StreamWork business method being federated over to  Google Wave. We intend to create a generic compatibility between StreamWork Methods, and Wave and OpenSocial Gadgets so that developers will be able to ensure that gadgets or methods built for one system will work in the other.

    These are the early days with our Wave Federation Protocol support and we are still in proof of concept stage, but we are excited to discover together with you how Wave, OpenSocial and StreamWork naturally extend each other, and we intend to deliver value to our customers, based on this work, within the next year. So please let us know your ideas, and we can figure out how the make the world a little more productive every day.

    -David Meyer, SAP


    Peak production, peak waste, social media and Must Ignore

    December 23rd, 2008

    I enjoyed Tim O’Reilly’s post today, Waking up from the ‘Nightmare on Tech Street’, itself a response to Om Malik’s recent piece. Finally, I felt, someone was touching on the upside of oil demands finally declining, or celebrating the slowdown in our culture of excessive consumerism.

    As he notes, peak production usually equals peak waste:

    In a recent conversation with my daughter Arwen and son-in-law Saul Griffith, Matt Webb remarked that he’d like 2008 to be remembered as the year of “peak consumption.” Saul pointed out, though, that the term “peak waste” is perhaps more accurate. In an analogy to peak oil, he suggested that maybe we’ve reached the pinnacle of waste in our consumer culture. I do wonder if we will look back at the past few decades as a kind of sick aberration rather than a golden age, with good times we want to get back to. Like Saul, I’m hopeful that we can get rid of the waste, and get back to creating things of lasting value.

    I’ve heard the term waste applied in another way lately, in regard to people spending time in social sites, such as Facebook and Twitter. These pundits usually follow such comments with an aside like, “I don’t need to be talking to people about what I just ate for lunch.” And then, of course, people laugh, thinking, Oh, those silly, wasteful twitterers.

    Those of us that actually use Twitter may have another perspective: perhaps this is a lean, efficient mode of communication. Perhaps a glance at it a few times a day can lead to unexpected insights and help build better relationships. And maybe even be a little bit fun.
    Read the rest of this entry »


    Whoever killed the Dinosaurs, please stand up.

    December 18th, 2008

    So it turns out that, perhaps, Dinosaurs were felled not by a gigantic asteroid, but by tons of sulfur polluting the atmosphere. Think of the smell!

    Whichever theory will prove true remains to be seen, but we see this again and again: sufficient evidence over sufficient time leads us to a worldview which feels more and more like fact. Facts that we make decisions on. Facts that that lend concreteness to our lives.

    How many arguments have been made for asteroid research and defense techniques that cite the extinction of dinasaurs?  Many. If Volcanoes turn out to be the true culprit, do we know which policies or government programs should be revisited to see if they are still valid?

    Read the rest of this entry »


    OpenSocial is making progress; the world spins faster

    November 18th, 2008

    Jason Kincaid wrote a nice piece on TechCrunch about the progress of OpenSocial (a standard interface for plugging your social application into a social network), with a rather attractive and impressive chart:

    Open Social just turned 1

    So what does this have to do with decision making? Not much, but it is such a pretty chart, so I thought I’d post it.

    Actually, it is a bit relevant. We’ve talked about how the workplace is being transformed, and this is part of the reason… the increasing social aspects of applications. While OpenSocial is usually talked about in context of the popular consumer Social Networks (which gives them the ridiculous and oft-misleading numbers above), a growing number of enterprise applications are starting to utilize it, for a simple reason: it is not that hard, and it gives you wide reach.

    Read the rest of this entry »


    Cars on Demand, College Laziness and Modern Efficiency

    November 12th, 2008

    I’m a big fan of Zipcar, as those around me know.  I just reserved one for tomorrow, and since I waited so long, I had to choose a pickup waiting at a local McDonalds, instead of my usual Prius down the street.  But I didn’t mind since it took me only about 25 seconds to find it, book it, and have a car ready for me tomorrow at 5:30 AM.

    As I did this I was thinking about speed.  Satisfying the speed of business is not about perfection  — it is about things being good enough, provided they are fast enough.

    Read the rest of this entry »


    Five Ingredients of Good Decision-Making

    November 7th, 2008

    The report’s authors state that good decision-making needs:

    1. High-quality data
    2. Access to advanced systems and training
    3. Sound judgment
    4. Trust
    5. Flexibility

    My colleague Timo also blogged on this some time ago - here.

    Read the rest of this entry »


    People People People People People

    November 7th, 2008

    I work at a large company.  My nature is to move quickly, which often feels impossible.  In the past few weeks, a lot of the impossibility has involved not knowing the right people.

    A lot of smart people think about this, for example the labcoats behind Organization Network Analysis.  Looking at how people work together in a network can often yield surprising insights into whether the organization can move fast or slowly.

    A lot of the rest of us do this everyday without thinking about it, with LinkedIn, Facebook, Twitter, Yammer and the rest, leveraging each other to speed ourselves up (I didn’t list MySpace, since that slows people down).

    But it comes down to one thing… the degree to which you can communicate effectively, quickly, and trustfully with the people you need to get things done.  If you couldn’t conceivably get agreement with someone over IM then you don’t have the right relationship with them to decide things in business time.  The last guy I hired I negotiated purely over SMS while I was on the tarmac, otherwise I would have lost him.

    Fast Fast Fast Fast requires People People People People.


    Anatomy of a Decision

    November 6th, 2008

    What are the elements of a decision, what is the basic structure that every decision can encompass.

    Access to information

    Most decisions will require some information, especially if we want to make an informed decision. Information comes in many forms of course. Ideally we have direct access to all the information to make our decision immediately. In reality we will likely have access to some, have to hunt for some, and have to rely on experience or guesswork when we cannot expend the time to collect or discover the gaps.

    And of course, before we worry about the quality of that information, we have to be able to get to it. This remains the biggest blockage for user - actually getting access to information. Most information workers - 60% in recent survey by the economist - continue to lack access to the information they need to complete their tasks:

    image 

    Source: “Enterprise Knowledge Workers: Understanding Risks and Opportunities” - available here 

    Read the rest of this entry »


    FACT BASED DECISION MAKING

    November 2nd, 2008

    How often have you heard someone say “We need to be making fact-based decisions” as apposed to “Gut-feel based decisions”

    Timo Elliott a colleague of mine has this to say:

    It’s one of our core beliefs that decisions made on data are better, of course Scott Adams has a slightly alternate take on that…

    Dilbert.com

    Before we can really start to assess whether facts assist us in making decisions, we need to be able to achieve a few other things. The very first thing is we need to find the facts. And given that Butler Group state:

    “a number of surveys have concluded that an information-based worker is spending between one and 20 hours each week searching for information”

    It appears were spending a lot of time collecting information. Anything we can do to reduce the time spent looking for information and increase the time spent looking at information would seem to be important to getting better decisions faster.

    And that is the project I have been working on for a while - BUSINESSSOBJECTS POLESTAR. How to get from “I have a question” to “Here is some useful data” as fast as possible - and to make that accessible and usable by anyone.

    “Polestar combines the simplicity of search with the power of BI to offer an iTunes-like interface that will appeal to a currently under-served segment of BI users.” - Cindi Howson, Founder BI Scorecard