Let's describe the deliverable

[Phil Wolff]

What are the minimum necessary and sufficient conditions for the
vision statement?

What do we want in a great vision? Talking points? Stories of people?
Charts, graphs? Beginning-middle-end, or another structure?

In which formats should we present it? Text, pictures, comic strip,
video?

Is the vision document about data portability (the idea) or
DataPortability.org (the community organization)?

What time frames should we consider? 2010, 2015, 2020, 2030?

What possible future scenarios should we consider?

- AllMyDataBelongToMicroGoogle where user rights are hard (if not
futile)?

- Klepto World where identity thieves mine social networks and
security/privacy are of personal and national concern?

- ItsAsmallWorldAfterAll where nearly all services are social, from
banking to brothels?

- SocialWorkForce where a trillion euros of virtual work is organized
by virtual labor markets (eBays for bringing work to workers)?

- MyBabyIsFamous where everyone is born with a thousand "friends", we
never lose contact with anyone we meet, and social graph overload is
well managed?

- FriendThing where objects want to befriend you and you can friend
your stuff, sharing "life" and "thing" streams

- Mobilized where PCs are secondary to mobile devices, the descendants
of the iPhone and Kindle Garmin and heads-up Ray-Bans.

What benefits do we hope the vision statement will bring?

Is this a perishable statement (best if used by 2010) or an enduring
one?

[Elias Bizannes]

Whoops, let's start again.

 

I think a fair bet is that we design a vision for now. Current technologies, current issues - what do we want NOW in our lives. And if there are aps with what we can't do, that's where we focus our attention to align that.

 

We want a clear vision so that we have

- direction: we now where to focus our efforts as I mention above to align things with that view

- a framework: we can evaluate things (ie, company announcements), with respects to our vision

- Consistency: We can be more consistent with what we say, and things like our missions to our branding can be derived from the common document. It will be the central node for everything we do.

 

In terms of format, this is a report to the steering group. It should be formally addressed as a document. Other media can be used subsequently if we want to communicate this to the outside world perhaps, but we shouldn't let art distract us given the tight timeline unless it helps commnuicate the point.

 

The vision is to help the idea - it essentially encapsulates what it is in a measureable way. This will then allow the organisation to execute on its purpose.
 

In terms of scenarios, amusing but also good points you raise. This is like the policy group, but with a deliverable. In future, I hope to create off another task force that creates other deliverables (like terms) but ultimately that is derived from the vision. This is a building block for all our work I believe.

 

Anyone else got any ideas? I will try to create some structure for how we proceed, but I a most productive during the weekend when I don't have that annoying thing called "work: distracting me.

 

On 7/23/08, Elias Bizannes <elias.b...@gmail.com> wrote:

Thanks Phil,

I think its

Sent from my iPhone

[Christian Scholz / Tao Takashi (SL)]

Hi!

> We want a clear vision so that we have
> - direction: we now where to focus our efforts as I mention above to align
> things with that view
> - a framework: we can evaluate things (ie, company announcements), with
> respects to our vision
> - Consistency: We can be more consistent with what we say, and things like
> our missions to our branding can be derived from the common document. It
> will be the central node for everything we do.

+1

I think little bits of such a framework started in the technology
group when we were searching for criteria for which standards to adopt
and which not. I would here go one step back again though and start
with some general principles in terms of policy and see if some
announcement meets these.

> In terms of format, this is a report to the steering group. It should be
> formally addressed as a document. Other media can be used subsequently if we
> want to communicate this to the outside world perhaps, but we shouldn't let
> art distract us given the tight timeline unless it helps commnuicate the
> point.
>
> The vision is to help the idea - it essentially encapsulates what it is in a
> measureable way. This will then allow the organisation to execute on its
> purpose.
>
> In terms of scenarios, amusing but also good points you raise. This is like
> the policy group, but with a deliverable. In future, I hope to create off
> another task force that creates other deliverables (like terms) but
> ultimately that is derived from the vision. This is a building block for all
> our work I believe.

I hope the policy group will also deliver something :) But I agree, we
should not be too specific here but maybe define things like we want
to define criteria for evalutating technologies, processes,
announcements and so on.

> Anyone else got any ideas? I will try to create some structure for how we
> proceed, but I a most productive during the weekend when I don't have that
> annoying thing called "work: distracting me.

Looking forward to it :-)

cheers,

Christian

--
Christian Scholz
Tao Takashi (Second Life name)
taota...@gmail.com
Blog/Podcast: http://mrtopf.de/blog
Planet: http://worldofsl.com

Company: http://comlounge.net
Tech Video Blog: http://comlounge.tv
IRC: MrTopf/Tao_T

[Elias Bizannes]

Christian - as you aware of those "criteria's" from the technical
group, could you look into that and post a summary to the list of what
you guys developed. That could be extremely useful.

I also think this vision task force is like a part of the original
policy group. Unde the new governance framework, the policy action
group doesn't exist (...yet) - and instead of a broad group, these
task forces are replacing the work with specific items.

[Phil Wolff]

Let me put this another way:
What is the table of contents for the vision report?

--
Phil Wolff
managing editor, Skype Journal
http://SkypeJournal.com
pwo...@skypejournal.com
skype:evanwolf
+1-510-455-4384 SkypeIn
+1-510-444-8234 San Francisco
+1-646-461-6123 New York
+44 020 8816 8780 London
+852 8175 8107 Hong Kong
http://www.linkedin.com/in/philwolff
http://www.facebook.com/profile.php?id=724232370
http://twitter.com/evanwolf
http://wiki.dataportability.org

[Elias Bizannes]

Thanks Phil, good idea.

How about this:
1. Executive summary
2. History of DataPortability
3. Research findings:
- DataPortability forums
- blogosphere
4. Task force recomendations

On Jul 26, 7:23 pm, "Phil Wolff" <pwo...@gmail.com> wrote:
> Let me put this another way:
> What is the table of contents for the vision report?
>

> managing editor, Skype Journalhttp://SkypeJournal.com

[Christian Scholz / Tao Takashi (SL)]

Hi!

On Sat, Jul 26, 2008 at 10:42 AM, Elias Bizannes
<elias.b...@gmail.com> wrote:
>
> Christian - as you aware of those "criteria's" from the technical
> group, could you look into that and post a summary to the list of what
> you guys developed. That could be extremely useful.

Well, there was no such thing what "we" developed yet, I just made a
proposal which you
can find here:

http://wiki.dataportability.org/display/dpmain/Process+-+How+to+select+standards

It's not much there really and we maybe should think more about other
criteria, like

- is developed in the open
- is owned by some open org (e.g. not owned by a company)
- has a certain level of adoption (whatever that means)
- fits the principles defined in policy

-- Christian