Microsoft’s 7 Essential E2.0 Truths

Seven Truths:
  • Focus on the need, not the technology
  • Be a silo buster
  • The solution belongs to the users – it doesn’t work in a command-and-control way. If it is done top-down, you have to compel participation. If it’s bottom up, people self-select and much more effective
  • What’s in a name? The platform/program should have a distinct name, look and personality. (If it had been just another SharePoint site, it would not have achieved the same level of visibility and interest.)
  • Start small, grow fast. They just wanted to help a few communicate and connect. They didn’t intend to create a video backbone.
  • Bring in everybody. Make sure you give ways for various types of participants  – contributors, commenters, raters, etc.
  • Value? They actually didn’t make a hard ROI business case before launching the program.  However, they have since be able to establish lots of business value.  It speaks for itself.
  • Mileage will vary – not every E2.0 effort will have the same impact.  You need to really calibrate your methods and branding to your goals.

Excellent advice, Liveblogged from #e2conf by @VMaryAbraham at Above and Beyond KM

My key points? Focus on the needs, start bottom up, and bring everyone in.

J. Boye | What does the intranet look like in a social business?

With a byzantine user experience and long implementation times (think Interwoven, Microsoft SharePoint, Oracle Portal or SAP), social businesses have taken alternative approaches. Blogs and wikis may have lost some of their sexiness, but are being deployed massively, also beyond technology-happy IT users. Social businesses tend to find the right tool for the job and are not afraid to put more than one tool in place.

We're going SP2010, and with a fairly rapid timescale; my fear is the command and control creeping in...

MPs' expenses

Yes, there was abuse. Yes, some MPs are crooks.

The pendulum has swung too far, surely? Do you want your MP reading your letter about your child, your parent standing in the walkway, or with your your neighbour sitting reading over his shoulder? Let them travel - and work- in privacy.

They will be able to claim rent for a one bed flat. So, we don't want them to be able to have their children/friends visit them in London? Do we really think that will make them *more* connected with normal folk and less with the Establishment?

I think this is a step too far.

How does your Community of Practice or Professional Community work?

For the last wee while, I've been thinking about how we should be using our Professional Communities to share knowledge within the company; that brought me to thinking about how effectively our Communities function.

BT has an Open Source arm  called Osmosoft; this is a bit of a departure for BT, and it's managed differently and does things in different ways. The guy who runs Osmosoft is Jeremy Ruston (@Jermolene), and he tried to explain "What is the point of Osmosoft".

A couple of things came out from that, the first being:
  • exploring the central question of how innovation occurs in communities
Since I was thinking about communities, I took the opportunity for a chat with one of their guys who helps look after the community -  @FND - and explored how their community worked.

I asked him to talk a bit about their community; he described the 2 main reasons for joining communities as being
  • Self interest
  • Gaining respect - from others [or even yourself]

The community he deals with have a small number of developers for the core; more plugin developers,  rather more folk who will contribute tips & tricks, and a much larger number of users/help seekers.

Leadership within the community really comes via self selection; leaders have to have credibility within the community and not just be "this guy who's telling me what to do". The leaders have to effectively establish what's going to be best practice, and a general direction for the community.

Leaders can be direct Subject matter Experts (SME); the "go-to guys" for technical issues; they'll often get a personal kick out of being able to do a tailored solution; other leaders can be the codifiers, or knowledge gardeners - they'll maintain FAQ lists to make everyone's life easier - keep an eye on what questions are being asked.

This community is a developers/open/external community; I asked @FND about his Professional Community within the company. I liked his answer so much I tweeted it "The internet is my professional community". That had resonance with @Jermolene 's other phrase
  • Communicate with our colleagues across BT using the public internet to ensure the widest audience
@FND indicated that one of the strengths of their community was the ecosystem they worked in - "Redside", or outside the corporate firewall; Google Groups host their End-user discussions   and Developers Group. Discussions regularly took place as to whether they should work with other larger communities - for example, the jQuery teams who do many clever javascript things, like the TiddlyWiki team do. That would give them more people to work with - but communities are fluid.

Communities of this nature have very diverse populations by age, occupation, geography, background; managing a group like this requires differing approaches. The concern for the core architecture vs. the never ending quest for features causes discussion; fortunately there appears to be little/no trolling. The approach taken to discussion is to embrace difference and discuss patiently. It seems to work for them.

There are, of course other places to go to for support - StackOverflow hosts a lot of Q&A on Tiddlywiki; another community where people answer questions and get pretty rapid feedback on their answers

A community like this has a lot of competent people who work within it; they all need literacy in their subject matter, but they have differing skills and seem willing to share.

I asked for views as to how this could be applied to our Professional Communities; it seemed likely the best way would be under the radar, doing it via a piecemeal approach. If it works, we'd see a change in the way people were working.

While I was documenting this, my attention was drawn to an excellent  Communities Manifesto piece by @stangarfield - the Osmosoft guys do a lot of that; I think maybe I need to audit my Professional Community!

Corollaries of Knowledge sharing

Just read some more Steve Denning

Middle-management resists...
 Middle managers have often built their lives and careers on mastering the hierarchical pathways of organizations. They can feel threatened by the emergence of new non-hierarchical work flows which no longer require command-and-control management behaviors.  Communities of practice are indeed less orderly than hierarchies and it takes time for middle-managers to understand that maintaining order can advantageously be replaced by facilitating and cheer-leading knowledge sharing initiatives.

I love this. End Command and Control... 

What do you do with knowledge? Find it? Share it?

I've just read a really excellent - though lengthy - blog post from Mark Gould (@markgould13)  entitled What do we do with Knowledge?
This was bought to my attention by a tweet from @VMaryAbraham

Two bits stood out

 much of what we call KM is, in fact, merely manipulation of information. What social tools bring us ... are really interesting ways of exposing people’s working processes... there is little better for learning and development of knowledge than close observation of people at work

This aligns quite strongly with some of the bits I've been mulling over relating to a Systems Thinking approach. Seddon, in Freedom from Command and Control says "The principles for the development of knowledge are: integrating measures with work, focusing on purpose, designing work in flow rather than function, and assuming knowledge is associated with work"

Put people in an environment when they are making their own life/job/process better - and the process rather than the people are measured... I wonder if they'll feel an incentive to share then?

what we think is information overload is actually filter failure. Where we rely solely on controlled vocabularies and classification systems, our capability to filter and search effectively runs out much sooner than it does when we can add personalised tags, comments, trackbacks, knowledge about the author from other sources, and so on. Whereas repositories usually strip context from the information they contain, blogs and other social tools bring their context with them. And, crucially, that context keeps growing.

and the context is not something the system brings... they are part of the conversation.

I commend the post and thank  Mark for writing it and Mary for sharing

30 years with an employer

Vanishingly rare these days, but in 31 days time - February 19, 2010 I will have worked for my employer for 30 years.
I work for BT, who followed British Telecom, who followed Post Office Telecommunications.

I've worked dealing with customer complaints; done customer research and analytics; managed phone book deliveries; worked in marketing; database analytics; internal communications; sales reporting and payplan; project management; IT systems support; high level design consultancy; indirect sales management; IT Service management; Process consultancy; Service design.

I'm now a solution designer, dabbling in Knowledge Management for interest - and learning about the Security space, aiming for CISSP.

It's a privilege to work for a company with the breadth we have - that continues to strive for excellence. I'm looking forward to the next 15 years. 

Five Minute Management Course

I liked it, although it is old, and trite!

Lesson 1:

A man has just gotten into the shower as his wife is stepping out of the shower, when the doorbell rings. The wife quickly wraps herself in a towel and runs downstairs. When she opens the door, there stands Bob, their next-door neighbor. Before she says a word, Bob says, 'I'll give you $800 to drop that towel.' After thinking for a moment, the woman drops her towel and stands naked in front of Bob, after a few seconds, Bob hands her $800 and leaves. The woman wraps back up in the towel and goes back upstairs. When she gets to the bathroom, her husband asks, 'Who was that?' 'It was Bob, from next door.' she replies. 'Great,' the husband says, 'did he say anything about the $800 he owes me?'

Moral of the story: If you share critical information pertaining to credit and risk with your shareholders in time, you may be in a position to prevent avoidable exposure.

Lesson 2:

A priest offered a nun a lift. She got in and crossed her legs, forcing her habit to reveal a leg. The priest nearly had an accident. After controlling the car, he stealthily slid his hand up her leg. The nun said, 'Father, remember Psalm 129?' The priest removed his hand. But, changing gears, he let his hand slide up her leg again. The nun once again said, 'Father, remember Psalm 129?' The priest apologized 'Sorry sister, but the flesh is weak..' Arriving at the convent, the nun sighed heavily and went on her way. On his arrival at the church, the priest rushed to look up Psalm 129. It said, 'Go forth and seek, further up, you will find glory.'

Moral of the story: If you are not well informed in your job, you might miss a great opportunity.

Lesson 3:

A sales rep, an administration clerk, and their manager are walking to lunch when they find an antique oil lamp. They rub it and a Genie comes out. The Genie says, 'I'll give each of you just one wish.' 'Me first! Me first!' says the admin clerk. 'I want to be in the Bahamas , driving a speedboat, without a care in the world.' Puff! She's gone. 'Me next! Me next!' says the sales rep. 'I want to be in Hawaii , relaxing on the beach with my personal masseuse, an endless supply of Pina Coladas and the love of my life.' Puff! He's gone. 'OK, you're up,' the Genie says to the manager. The manager says, 'I want those two back in the office after lunch.'

Moral of the story: Always let your boss have the first say.

Lesson 4

An eagle was sitting on a tree resting, doing nothing. A small rabbit saw the eagle and asked him, 'Can I also sit like you and do nothing?' The eagle answered: 'Sure, why not.' So, the rabbit sat on the ground below the eagle and rested. All of a sudden, a fox appeared, jumped on the rabbit and ate it..

Moral of the story: To be sitting and doing nothing, you must be sitting very, very high up...

Lesson 5:

A turkey was chatting with a bull. 'I would love to be able to get to the top of that tree' sighed the turkey, 'but I haven't got the energy.' 'Well, why don't you nibble on some of my droppings?' replied the bull. They're packed with nutrients.' The turkey pecked at a lump of dung, and found it actually gave him enough strength to reach the lowest branch of the tree. The next day, after eating some more dung, he reached the second branch. Finally after a fourth night, the turkey was proudly perched at the top of the tree. He was promptly spotted by a farmer, who shot him out of the tree.

Moral of the story: Bull shit might get you to the top, but it won't keep you there...

Lesson 6:

A little bird was flying south for the winter. It was so cold the bird froze and fell to the ground in a large field. While he was lying there, a cow came by and dropped some dung on him. As the frozen bird lay there in the pile of cow dung, he began to realize how warm he was. The dung was actually thawing him out! He lay there all warm and happy, and soon began to sing for joy. A passing cat heard the bird singing and came to investigate. Following the sound, the cat discovered the bird under the pile of cow dung, and promptly dug him out and ate him.

Morals of the story: (1) Not everyone who shits on you is your enemy. (2) Not everyone who gets you out of shit is your friend. (3) And when you're in deep shit, it's best to keep your mouth shut!

 

THUS ENDS THE FIVE MINUTE MANAGEMENT COURSE

Backup & Restore in Knoppix

Everyone has nightmares about losing their machines. If the worst happens, you should be OK if you took a backup.

A colleague of mine, Colin Markwell, compiled a helpful little guide to doing just this with Knoppix. (I liked this, as Knoppix once saved me from a very difficult situation!). He pointed out to me:

note the links at the bottom of the file where most of the info came from.  My notes are pretty-much just a compilation of info from them Still helpful, Colin!

Heres the guide, not prettily formatted, but easy to follow.

------------------------------------------------------------------------------

BACKUP AND RESTORE USING KNOPPIX

------------------------------------------------------------------------------

-----------

ENVIRONMENT

-----------

Source: The first partition of the first hard drive (/dev/hda1), which is

10Gb and formatted with the FAT32 file system.

Destination: A ext3 partition on an external hard disk (/mnt/sda2).

----------

BACKING UP

----------

Boot into Knoppix and mount "sda2" (destination drive we're backing up to)

by right-clicking on the icon and selecting "mount", then make it writable

by right-clicking the icon again and selecting Actions > Change read/write

mode.  Open a root shell (KDE Menu > Knoppix > Root shell).

Back up the Master Boot Record - MBR - (this contains code to boot first

partition and the partition table for up to 4 primary partitions):

  dd if=/dev/hda of=/mnt/sda2/hda-mbr-20041124 count=1 bs=512

Note: bs = block size (in bytes) - the MBR is 512 bytes long.

Back up the partition:

  dd if=/dev/hda1 bs=1k conv=sync,noerror | gzip >/mnt/sda2/hda1-20041124.gz

Note: gzip compression used to backup faster and reduce the file size.

sync,noerror ensures that if there's a problem reading the source drive, dd

still writes the correct number of bytes so that later data isn't incorrectly

offset.  Using a block size of 1k minimises the amount of data lost if a block

can't be read.

Make a note of the partition sizes:

  fdisk -l /dev/hda >/mnt/sda2/hda-partition-info.txt

 

To back up the extended partition table (Not used this in the restore, as I

was restoring to a smaller drive and only wanted to restore the first

primary partition):

  sfdisk -d /dev/hda | dd of=/mnt/sda2/hda-partition-table-20041124

 

---------

RESTORING

---------

Boot into Knoppix and mount "sda2" (drive that contains the backup)

by right-clicking on the icon, DON'T make it writable (prevents accidently

overwriting the backup).  Open a root shell (KDE Menu > Knoppix > Root shell).

If you need to create the partition (not necessary if restoring the partition

table as part of backing up the mbr, or if the partition already exists):

  fdisk /dev/hda

 

  n [new partition]

  p [primary]

  1 [1st partition]

  <accept default first cylinder>

  1275 [end cylinder - obtained from hda-partition-info.txt]

 

  Note: The partition can be larger than the source partition if necessary

 

  p [print table - confirm size matches the source partition]

 

  t [change partition's system ID - use l to list]

  c ["Win95 FAT32 (LBA)"] - NTFS is 7 I think

 

  a [toggle bootable flag on]

  1 [1st partition]

 

  w [write and quit]

 

  Reboot Knoppix so everything's aware of the new partition layout.

Restore the MBR (without the partition table):

  dd of=/dev/hda if=/mnt/sda2/hda-mbr-20041124 bs=446 count=1

 

Note: The partition table is at the end, bs=446 ensures we don't overwrite it.

To restore the partition table too, leave off the "bs" and "count" arguments.

Restore the partition:

  gunzip -c /mnt/sda2/hda1-20041124.gz | dd of=/dev/hda1 bs=1k conv=sync,noerror

To restore the extended partition table (Not used this in the restore, as I

was restoring to a smaller drive and only wanted to restore the first primary

partition):

  sfdisk /dev/hda </mnt/sda2/hda-partition-table-20041124

  Reboot Knoppix so everything's aware of the new partition layout.

----------------

SPLITTING BACKUP

----------------

Splits into 1Gb files, named as follows:

hda1-20041124.gz.00

hda1-20041124.gz.01

hda1-20041124.gz.02  ...and so on.

  dd if=/dev/hda1 bs=1k conv=sync,noerror | gzip -c | split -b 1024m -d - /mnt/sda2/hda1-20041124.gz.

Note the dot at the end of the command

------------------

JOINING TO RESTORE

------------------

cat hda1-20041124.gz.* | gunzip -c | dd of=/dev/hda1

--------------------------

FORMATTING A NEW PARTITION

--------------------------

Format a partition with the FAT32 file system:

  mkfs.vfat -F 32 /dev/whatever

 

Note that this is useful as Windows XP doesn't allow you to format partitions

larger than 32Gb with FAT32.

-----------------------------------

BACKING UP OVER A NETWORK USING SSH

-----------------------------------

Preparation

-----------

On the machine containing the backup destination:

  Open a root shell (KDE menu > Knoppix > Root shell)

  Change the root password: (Enter this when prompted by ssh on the client)

    passwd

  Start the ssh daemon:

    /etc/init.d/ssh start

Backing up partitions

---------------------

On the machine that is to be backed up:   

  Backup MBR:

    dd if=/dev/hda count=1 bs=512 | ssh -c blowfish root@192.168.7.11 "dd of=/mnt/sda2/oldpc-mbr-20041127"

  Backup /dev/hda1

    Method 1: Compress on source machine and send over network compressed to a file:

    dd if=/dev/hda1 bs=1k conv=sync,noerror | gzip -c | ssh -c blowfish root@192.168.7.11 "dd of=/mnt/sda2/oldpc-hda1-20041127.gz"

    Method 2: Send over the network uncompressed and compress on the

    destination machine.   Use this if you're backing up a slow machine to a

    quick machine over a quick network:

    dd if=/dev/hda1 bs=1k conv=sync,noerror | ssh -c blowfish root@192.168.7.11 "dd bs=1 | gzip >/mnt/sda2/oldpc-hda1-20041127.gz"

    Method 3: Don't compress.  Use if backing up slow machines over a quick

    network:

    dd if=/dev/hda1 bs=1k conv=sync,noerror | ssh -c blowfish root@192.168.7.11 "dd of=/mnt/sda2/oldpc-hda1-20041127"

    (replace filename with device (e.g. /dev/hda1) if restoring partition, rather than backing up to a file)

    Method 4: Compress, send over network, uncompress.  Use if backing up

    over a slow network.   

    [NOT TESTED]

    dd if=/dev/hda1 bs=1k conv=sync,noerror | gzip -c | ssh -c blowfish root@192.168.7.11 "gzip -d -c | dd of=/mnt/sda2/oldpc-hda1-20041127"

    (replace filename with device (e.g. /dev/hda1) if restoring partition, rather than backing up to a file)

  Copy across partition table information

    fdisk -l /dev/hda | ssh -c blowfish root@192.168.7.11 "cat >/mnt/sda2/oldpc-partitions.txt"

Use "top" to monitor CPU performance (gzip + ssh bottlenecks) and KDE System

Guard to monitor network usage (KDE menu > System > KDE System Guard, look

under Network > Interfaces > eth0 > Receiver > Data, drag+drop onto graph

grid thing as "Multimeter" type).

   

Backing up files

----------------

On the source machine:

  Mount relevant partition (for example):

    mount /mnt/hda1

 

  Copy files:

 

    cd /mnt/hda1

    tar cv . | ssh -c blowfish root@192.168.7.11 "cd /mnt/sda1/OldPC-C ; tar x"

To compress files using gzip, use the z flag:

    tar zcv . | ssh -c blowfish root@192.168.7.11 "cd /mnt/sda1/OldPC-C ; tar zx"

   

Note that a list of files being copied will be output to the screen on the

source machine (due to the tar "v" flag).

--------------------------------------

BACKING UP OVER A NETWORK USING NETCAT

--------------------------------------

This doesn't use encryption, so may be faster than ssh if CPU resources

are limited.

Backing up partitions

---------------------

Backup MBR:

On the destination machine, enter the following:

  netcat -l -p 10000 | dd of=/mnt/sda2/hda-mbr-20060326

 

  "-l" = listen for incoming connection

  "-p 10000" = listen on port 10000 - change if required.

On the source machine, enter the following:

  dd if=/dev/hda count=1 bs=512 | netcat -w 5 192.168.7.11 10000

Backup /dev/hda1:

Destination machine:

  netcat -l -p 10000 | dd of=hda1-20060326.bin

 

Source machine:

  dd if=/dev/hda1 bs=1k conv=sync,noerror | netcat -w 5 192.168.7.11 10000

Compressing on source machine (sent over network compressed):

  dd if=/dev/hda1 bs=1k conv=sync,noerror | gzip -c | netcat -w 5 192.168.7.11 10000

Compressing on destination machine (sent over network uncompressed):

  netcat -l -p 10000 | gzip -c | dd of=hda1-20060326.gz

Copying across partition table info:

  Destination machine:

    netcat -l -p 10000 >hda-partition-info.txt 

  Source machine:

    fdisk -l /dev/hda | netcat -w 5 192.168.7.11 10000

Backing up files

----------------

On the destination server, go to the directory you want the files to be

copied to and enter the following:

  netcat -l -p 10000 | tar x

If you want to see a list of files on the destination server as they're

copied, add the "v" switch to tar:

  netcat -l -p 10000 | tar xv

Ensure the destination server is running before running the command

on the source machine.

 

On the source machine, go to the directory you want the files to be copied

from and enter the following:

  tar c . | netcat -w 5 192.168.7.11 10000

  "-w 5" = wait 5 seconds for input before closing connection and ending.

If you want to see a list of files on the source machine as they're copied,

add a "v" option to tar:

  tar cv . | netcat -w 5 192.168.7.11 10000

If you want to gzip compress the files as they go over the network, add

the "z" option to tar:

Destination:

 

  netcat -l -p 10000 | tar zx

Source:

  tar zc . | netcat -w 5 192.168.7.11 10000

-----------------------------------------------------

BACKUP/RESTORE TO A SHARED DRIVE ON A WINDOWS MACHINE

-----------------------------------------------------

Mount the shared drive:

  mkdir /mnt/win_share

  smbmount //192.168.0.1/shared /mnt/win_share -o username=colin,password=secret

Then backup/restore as you would do locally.

[ From: http://www.okmoore.com/imagedrive.html ]

-------------------

INFORMATION SOURCES

-------------------

http://www.inference.phy.cam.ac.uk/saw27/notes/backup-hard-disk-partitions.html

http://www.rajeevnet.com/hacks_hints/os_clone/os_cloning.html

http://wiki.linuxquestions.org/wiki/Dd