Body language essentials for teachers

Amy Cuddy teaches at the Harvard Business School and studies, among other things, the effect of body language – not just on others, but on ourselves. In this TED video, she demonstrates the effect of consciously using body language to change your own mindset:

I occasionally teach teachers how to teach, especially case teaching or discussion-based teaching. A recurring problem for many teachers – particularly the younger ones, when they start out – is a feeling of nervousness, sometimes quite severe. This nervousness makes them want to take control in the classroom, to script their presentations, to make sure that they have every angle covered – precisely the behavior that is most detrimental to running a good discussion-based class, where the teacher trusts the class and relies on the students to provide drive and perspective, facilitating rather than driving the discussion.

Overcoming nervousness is not easy, but I have found that the techniques mentioned by Cuddy work. For instance, I tell teachers to check out the classroom, lecture hall, meeting room, whatever, ahead of time – and make a change to something. When I am giving a speech or teaching a class, I will almost always change something in the room when I come it: I’ll set the boards just so, adjust the lighting, get rid of the “protection table” that so many teachers put between themselves and the students, grab a stack of books or a soda crate to build a stand for my laptop. These changes I do because I want them, but also because they are my way of asserting power in the room – telling myself that I own this room for the duration.

The two-minute power stances advocated by Cuddy work well and should be used by any teacher – go to the bathroom before class, lock the door and stand tall by yourself for a little. The difference can be quite dramatic – and the students will notice it. This is especially important if it is the first time they see you – research has found that the first 30 seconds students see a teacher are extremely important for their opinion about him or her.

Stand tall, that you may teach well. Just a little will go a long way.

The Death Of Blogs? Or Of Magazines?

Reblogged from The Dish:

Click to visit the original post

As part of his "eulogy for the blog", Marc Tracy touches upon the evolution of the Dish - which he praises as "a soap opera pegged to the news cycle":

[T]oday, Google Reader is dying, Media Decoder is dead, and Andrew Sullivan's The Daily Dish is alive in new form. This year, Sullivan decided that he was a big enough brand, commanding enough attention and traffic, to strike out on his own.

Read more… 841 more words

According to Andrew Sullivan, it isn't blogs that are dying, but magazines with titles such as "the death of blogs." I agree - like the Internet now reflects a whole society rather than the thinking of the early pioneers, the blogosphere has evolved into many distinct segments. It is natural, things take time, and we are still at the beginning. (Incidentally, this is a reblogging test )

Boston Marathon Bombing

This hits home – it is very bad. Boston is our family’s second home town, where our youngest was born and the other two had formative years (as did we all.) Boylston street certainly is familiar and so is every Boston reference and place name now being repeated on CNN.

I am impressed by the police and various spectators and marathon officials – they immediately run to help the wounded, acting very sensibly, quickly coordinating to gain access to the bomb site and get to the wounded.

Let’s hope the aftermath of this event is characterized by the same calmness, relevance and restraint. The bombings in Oslo and shootings at Utøya two years ago gave rise to very solemn reactions and a surprisingly thorough and measured debate about immigration, extremism and the role of religion in Norway – as well as a thorough examination of security routines and the response of the police (which, unfortunately, was not as quick and coordinated as in Boston.

Let’s hope this can be an event to learn from, whoever the perpetrators may be. The Boston Marathon is very much an outdoor celebration – people happily cheering the runners along the route and everyone having a great time. It would just be too sad to have it changed and locked down by the insanities of people who think violence will gain them anything at all.

MOOC and me: Reflections on a Coursera course

On April 10, I signed up for a course on network theory and analysis with professor Matthew Jackson of Stanford University. That was about one week into the course, which started April 1, so I will have to hurry to finish some of the assignments. The course is both a test in online coursing for me – not that I think I am at a stage where I should create on, but it could be interesting to try – and I chose this particular one because it is a field in which I have brushing knowledge (I have read Burt’s Structural Holes: The Social Structure of Competition, for instance) but never have systematically undertaken any training or done any math.

Signing up was very easy: Name, email address and a password, no cost, off we go. The web site is very simple, well, here we go. Estimated work 3-6 hours per week. Will see if I can make that, especially if I am blogging on the side…

image

The course (at least the intro) is delivered with a set of slides and the instructor superimposed over them, using on-screen drawing (using a tablet pen, it looks like) drawing lines around or between concepts. The ability to speed up the presentation is useful – I can still follow it at 1.5x normal speed, and used that to rush through some of the examples I had heard before and some of the more self-explanatory slides. There are some problems with the transmission – occasionally, the screen will be garbled (especially when there is movement on the screen, such as the instructor drawing on the slides, which means that I will have to print out the slides for the next week’s lectures, when the formulas become more complicated. i will also have to start taking notes by hand, since my typed comments can’t keep up with the presentation when it comes to creating formulas and drawing diagrams.

The course uses open-source network software (Pajek) and the first homework assignment dealt with basic network attributes such as diameter, density, and average paths. Not too hard so far, but i have a graduate education from an English-speaking university and some intuitive understanding of the topic (plus experience in fiddling with software until it works, including screwing up the Pajek configuration and fixing it by simply erasing the config file and starting over.)

On the positive side, I might be just in the right market segment: Someone who is interested in the topic but does not have the time to sign up for a course in it. Wonder how many other academics there are out there who see MOOCs as a great way to update themselves on a related field…

I’ll be back with more observations in a few weeks, assuming I haven’t dropped out – which many students tend to do in these courses.

Newsblur–an alternative to Google Reader

The best way to find new tools and work tips is to see what other people are doing – which is why I spend time writing up experiences with various tools. It is even better when you can read the experiences and work tips of someone you admire – such as this Lifehacker interview with the frighteningly articulate and productive Cory Doctorow.

From this interview I noted that Cory, like many of us, has to leave Google Reader – as he says, probably for Newsblur. I promptly went there, plonked down $20 for a year’s subscription, choose “import Google Reader subscriptions”, and wondered why I hadn’t heard of this gem before. In addition to RSS feeds, Doubt if I will ever open Google Reader again…. Newsblur seems more elegant, gives me the option of reading the blog in original format, and has a great interface for adding and deleting blogs. And it is trainable – i.e., it observes what you read and asks your opinion – though I haven’t used it long enough to see how this works.

Highly recommended – and the fact that a) this is fee-supported, hence not subject to arbitrary facing-out decisions that leave a loyal following with no tools, and b) recommended by Cory and now – gasp – me, should make this a very viable tool in the future. The creator, Samuel Clay, is a bit overwhelmed with demand right now (hence no free test subscriptions), but that will change as the site firms up its infrastructure and gets more optimized, I am sure.

Highly recommended!

Collaborative online writing–some personal experience notes

I am currently spending a lot of my time in a collaborative writing project with my friend and colleague Bill Schiano – the details are not important at this point, but it is a book-length, somewhat complicated piece of text, and involves an editor. Bill is in Boston and I am in Oslo, usually a six-hour time difference. A relatively short deadline has necessitated finding a way to work together which is faster than the time-honored method of e-mailing drafts back and forth. Shouldn’t be hard in this day an age, with cloud-based software and 60-megabit Internet connections, right?

Well, it is. We started out with Google Docs, which is great for quickly setting up shared documents fast and handles multiple concurrent editors (you can actually see the other person writing almost in real time.) However, it turns out it lacks some of the nicer interface details of good old Word, such as comments in bubbles and a lot of the keyboard shortcuts. It also quickly gets very unwieldy as the document gets longer.

We then tried out Scrivener, an authoring (as opposed to word processing) tool which recently has become available for Windows and is touted as the best thing since sliced bread by a number of authors. We found it to be fantastic for authoring – if you are a single author. For two or more people working together (over a DropBox-shared directory) it lacks the version tracking and commenting features, meaning that we would have to be very disciplined about who wrote what where and have lots of supporting documents a la “Unifinished issues”. After a few screw-ups, we decided to try something else.

We then came up a with solution that really works, which we have been using for a few months now and gives us nearly everything we want: The venerable and much-maligned Microsoft Word. The difference is that the document we work with (which currently stands at 157 pages, nearly 63000 words, just over a megabyte storage) is stored on Microsoft Skydrive, and we can both edit it using Word on our computers. I will leave the actual setup of this as an exercise for the reader, but the short version is that you set up a Skydrive account at skydrive.live.com, open a new document in Word (must be at least the 2010 version) and save it to the Skydrive. You then share by sending a link to your co-author, who opens the link and can then choose to edit it online (i.e., through a browser (not Google Chrome) or in Word on his or her own machine.

This gives us the best of both worlds. We can edit the document on our own machines, see the changes the other has made and accept them, write comments in the text that the other person can respond to. We do Skype meetings (with Skype Premium, so we can share screens) about twice per week to discuss things we cannot fix simply by shared editing, and the whole thing is progressing quite nicely.

As usual when you start using an old tool for something new, you learn a few tricks you hadn’t thought about – the best way to learn new tricks is always to watch someone else using the software: I learned that you can control-click on an item in the TOC to go directly to it by seeing Bill do it, and he learned that you can grab selected text pieces and drag them to new places (without doing Ctrl-x Ctrl-v.) That’s why I think every group working together should have an occasional “Tips and tricks swap meet.”

We have found that working with a large (at least 27”) screen as your primary tool is immensely useful. That allows a full-page view with two full pages and a navigation pane, like this:

image

If you are disciplined about heading styles (i.e., chapter headings being “Heading 1” etc.,) then the navigation pane works more or less like the outline or slide sorter in PowerPoint, allowing you to drag and drop chapters and sub-chapters around and promote or demote them, which is extremely useful when your work approach is to bung in a lot of text in sub-chapters and then sort out the structure later. (Word is a bit irritating in its use of styles, though – it should be easier to enforce a standard style set, unchanged when text is clipped in from other sources.)

Another useful trick is to go to the File>Recent screen, locate the shared draft, and press the little push-pin to the left of it. This places the document permanently at the top of your Recent files list – making it very easy to open without having to go to Skydrive etc.

When working together like this, you also need to come up with a shared notation for work – how to you mark some text as tentative, for instance. The standard comment and track changes settings are OK (but change the standard for Track Changes so it does not track changes in formatting) but you need more than that. We have defaulted to marking spurious text with {curly brackets} and reference points with “zzzz”. (I have heard other writers, such as Cory Doctorow, use “tk” because that particular letter combination does not appear often in the English language, unless you write about the Atkins diet.) The idea is that even with a large document, you can search through it until you have fixed all issues, i.e., gotten rid of all the curlies and zzzz’s.

There are, of course, a few issues you need to deal with. That a document is shared does not mean it is backed up, so we both do local, dated backups every now and then, just to stay on the safe side. The more users are editing the document, the slower it updates, so we try to be disciplined about a) saving often, and b) exiting the document when we are not editing it. If not (as Bill found when Espen had done a lot of small edits and then, in Norway, gone off to bed while leaving the unsaved document on his workstation,) the edited paragraphs become inaccessible to the other author. So, save and exit whenever you can.

And that’s it so far – just sharing experiences here, but this approach really works. Our next challenge is bringing our editor on board – so far we have been sending him chapters as they have become ready. I am now going to set this up for collaboratively writing with a couple of other colleagues, on shorter pieces, and we’ll see how that goes.

Keep you posted – and tips and tricks are appreciated!

A day in the life of a Computer Expert

(Julie linked to this article, which made me remember that I actually wrote something similar in 1989 or thereabouts, when I was running user support for the Norwegian Business School)

Report from the trenches: Scenes from the life of a computer expert

The onslaught of user-friendly personal computers, where the user points and clicks his or her way to computational satisfaction, is hailed by many as the beginning to the end of the in-house computer expert (also known as the Local Guru). As this field report will show, there is no reason to look at the classifieds yet. Relax, guys.

The dominant source of computer problems is finger trouble. Finger trouble is the term computer experts (loosely defined as anyone who knows the approximate location of the power switch) have coined for problems inexperienced users get themselves into by way of the keyboard. While this source of job security and discretionary income may be reduced due to graphical user interfaces, there are still plenty of hardware errors to keep us occupied. Hardware errors are part of the everyday life of all computer experts, and show no sign of abating.

Let us examine a typical case, in order to gain an appreciation of the current state of things: The setting is a medium-sized company with high ambitions, a ubiquity of PCs and a Computer Expert (hereafter called E.). E. is sitting in his office, consumed with the difficulty of reaching level 42 in the 486 version of the “The Hitch-Hikers Guide to the Galaxy” when the telephone rings. Having recently cleared his office, E. manages to find the telephone before the caller gives up. The voice in the other end informs him, with audible consternation, how that darned printer, again, won’t do what it’s supposed to. Can E., with his long-standing reputation as a technical wizard, do something about it? The Voice (hereafter dubbed V.) assures E. that the matter isn’t pressing – but if he has the time…. (Somehow V. manages to convey a message of great need, sort of “you just take your time, we don’t mind sitting here rolling our thumbs and wasting the company’s money etc.”). E., when airing a suspicion that the equipment in question probably isn’t switched on, is informed by V. (with audible consternation) that they have in fact been using computers for several years now etc.

The setting 10 minutes later: E. arrives in the manner and style of a 20th century doctor making a house call on a farm far away from civilization (or like a veterinarian in Yorkshire). From every nook and cranny the office personnel come running to witness an Expert’s modus operandi (please bear with me if I’m carried away a bit here). E. eyes the printer and sees that the cable between it and the PC is present – and that the switch, indeed, is turned to ON. Still, the thing is as dead as a post- Format C: hard disk.

With a supreme air of confidence E. grasps the power cord and begins to pull. A veritable birds’ nest of cables appears (the premises were constructed long before information technology made its cheerful appearance in organizational life). Dangling inside the cable web is a power plug, its prongs conspicuously devoid of physical contact with anything electric. E., with an air of quiet achievement, lifts it high in the air for examination in a gesture reminiscent of a surgeon in a 1950′s war movie (the scene where the bullet has just been removed from the young soldier’s chest).

The reaction of V. and colleagues at this point depends on a number of variables, chief among them their rank in the organizational hierarchy. The range of reactions varies from “how could I be so stupid (again)” to “who the hell loosened that plug”. Suddenly the preferred topic of conversation is anything but office automation – frantic discussion of the quality of the local cafeteria coffee ensues, accompanied with a noticeable rise in body temperature above the 6th vertebrae.

E.’s reaction depends mainly on the tone of the initial telephone conversation, the distance covered in order to reach the culprit, and what he could have done instead. (The number of times this has happened before might also have some effect, but as V. normally has a choice between several E.s it is not likely that the scene will repeat itself with the same E. very often.).

If E. is a really experienced technical wizard, he will refrain from sarcastic comments, quietly lay down the power plug, and disappear into the sunset. The lonely hero has done it again. He has for the nth time shown who is the boss – who is in command of this omnipresent technology, incomprehensible to mere mortals.

But he knows this cannot last. There will come a day when the users will check for loose power plugs – a day when no carefully choreographed searches beneath desks will be enough to sustain his reputation as a technological superhero.

That will be the day he will have to learn how to change printer paper.