The am workshop I attended today (actually already yesterday now). A more detailed description can be found here.
What's PFFAP...
Presence, Flow, Feeds, Activity and Peripheral Awareness (and Getting Things Done).
And what about the tool?
Trying to use the tools that are "out there on the net" (see further below for review of prior art) for use in a work environment
Kick-off
Lee Bryant, from Headshift, kicks off with his introduction presening his teams knowledge pyramid (the social "stack", see a detailed description of the social stack here) and the six goals that the tool (or an integrated solution combining several tools) might help to achieve:
Picture taken from the Headshift website.
1. "How do we break the inbox addiction"
2 ."More flow, less sequential processing"
3. "More human scale, informal sharing"
4. "A better personal radar"
5. "Negotiating shared meaning and language"
6. "Use attention feedback to drive relevance"
Review of prior art: Tom Taylor & Colin Schlüter give an overview on different tools that are currently being used (Twitter, Tumblr, iGTD, NetNewsWire, E-mail).
Discussion then moves on to the topic of "How the decision making process is affected when we use social tools and when we don not use social tools". This is just an unsorted list of thoughts people uttered.
With social tools:
includes marketing noise,
synchrony of discoveries (e.g. digg),
group think,
possibility to discuss in an asynchronous way,
good for information gathering and backing up the decision,
logged conversations allow others to be involved
Without social tools:
using personal criteria makes it easier (faster),
involves more perceived risk,
is based on trust.
Several groups agreed on the following: Decisions are influenced most by the person who's "there" the longest (especially in corporate context), although there might be people using social tools who could (and try to) add relevant information to the decision process. In the end the decision however is often taken on a gut level. Complexity of the decision process and time constraints play a big role as well.
Talking about complex situations and the related analysis:
Recognition Primed Decision Model
- Situation analysis: The decision maker interpretes cues from the environment.
Currently forms that are used by social tools to gather information restrict the input of much of the side information (that however is really important to understand the situation) gets lost.
- Pattern recognition: The decision maker analyses the cues from the environment and compares them against stored cues.
Cognitive abilities are not supported by the tools at the moment. - Idea generation: The decision maker generates workable solutions to the problem at hand
- Solution selection: The first workable solution is selected. The solution is defined, as being workable if the simulation generated poses no problems.
- Simulation generation: The decision maker constructs a mental scenario of the proposed solution. Any problems are then addressed.
- One more point that I unfortunately missed.
Developing a feature list (that we can derive from the goals for social tools in the enterprise)
4 questions and 4 groups:
- What do we want to pipe through?
- How do we wan to access and transform this info?
- What sort of global actions do we need to support?
- What are the key features of the tool?
ad 1. "Work / play" switch or master switch (on/off)
"Context" switch"
ad 2. "Ranking by peers" (not digg style but implict, by reacting on it)
"Emerging peer groups": people who have read this item also subscribe to this RSS Feed
ad 3. Collect, process, organise by priorities, postpone, delete, relate, delegate, involve, follow the info.
ad 4. Resilient and agile
Context specific
Multiple interfaces ... and some more
Design brief and wrap-up
Several propositions on the how the tool could look like:
- just a search box. Searching lenses around topics, created by discussions by people you know, in the background. Those lenses can be made up of feeds, discussions via Skype, documents, twitter updates, social bookmarks, e-mails. Basically everything that is currently used for searching and organising information,
- "workstream"(in comparison to lifestream, timeline)
- flexibility of formats - converting e.g. e-mail to SMS
- leverage e-mail as de facto standard for conversations
A couple of good posts over at Ewan's Edublogger: