This morning I attended a session at the World Summit on the Information Society entitled "Creativity, Culture and Capacity", organized by Prof. Mike Best of Georgia Institute of Technology (Georgia Tech, or gatech.edu). I had first met him in 2003 when he was at the Media Lab and he was researching the kinds of systems I was building for Laos. He later went on to manage the Media Lab India, left MIT and is now editing "Information Technology and International Development", a journal published by MIT press. I will have to subscribe now.
The session was not well publicized and Best had invited certain people, myself among them, to attend. At four hours' duration, it would not draw many casual onlookers, especially with a bland title. Originally, Nick Negroponte had been scheduled for a panel, along with Alan Kay, for whom I have the highest respect. Another panel member was an acquaintance of mine, and I hoped there would be a good round debate on the OLPC.
But Negroponte had canceled a few weeks before, so instead we had a pretty good discussion on the whole issue of creativity on the internet. I particularly want to quote a comment by Alan Kay, the only one he made that was even tangential to the OLPC.
He said, "There's a hierarchy of elements, each of which is harder than the other. There's the hardware and that's easy - that's just engineering (I don't take that wrong - LF). Then there's software, and that's harder. Then user interface, and that's even harder. Then there's courseware, which is harder still. And finally there's mentoring, which is really, really hard."
I think this is an important taxonomy, and in a later session (Alan had to leave to be part of the OLPC road show) I realized how important it was. Clotilde Fonseca of Costa Rica said that "the digital divide doesn't exist. The use of the term implies there were no divides before the digital one, and there were many... the digital divide is just the old divide in a new area."
That got me thinking about how the digital divide was in fact a design failure. We should have been able to design computers and their software so that everyone could use them. Then Alan set out his hierarchy, and I was thrilled. "He's made my case," I whispered to Bob Marsh, sitting next to me.
Because you need to design from the right end of the hierarchy. PCs were designed from the bottom up, in the order Alan Kay listed, and he was a major player in areas like user interface. But we should have designed them from the top down, taking on the hardest first (hindsight is great!). So now, if we're going to redesign things (or put forward an initiative intended to change everything, as OLPC is represented), we have the ability (and responsibility) to make use of hindsight and structure our efforts the right way.
Mentoring (the human interactions which are both necessary for successful use of the technology and which constitute an important outcome) is the key. Exactly how you design them and design for them is not obvious to me, but you have to start somewhere. Then courseware, then user interface, then software and finally hardware. Each step reveals the requirements for the next.
And, of course, starting from a different set of assumptions about mentoring yields an entirely different path through the hierarchy and results in a different system. Taxonomies provide structure for thought, and the rest is mostly just hard mental work punctuated by insights.
So let's all remember Kay's Hierarchy and try to apply it in designing the next generation of everything. It won't be easy, admittedly, but we've been doing it the hard way until now.
And I rest my case (for now) about the OLPC. It's being designed as a piece of hardware, with all the other hierarchy elements pushed out into the future. You'd think we'd learn.
Lee Felsenstein
OK, wise guy...
So what would I do instead, if it were up to me? I've got plenty to say on the topic, since it's been my focus for a few years now.
I must admit I've fantasized about being offered the position of project engineer, but there seems to be no possibility of realizing that particular fantasy.
That's because I'd set as a condition the complete re-evaluation and re-planning of the project, not to mention subtitling it "but first make sure it's going to work". That means a simultaneous focus on 1) research, and 2) provision of infrastructure.
Research would consist of 1) ethnographic field investigation, gathering new data among the intended usership communities, 2) review of pertinent literature on education with computers, along with 3) analysis of data fro, both of the above, and 4) experimentation to develop appropriate system specifications and scenarios of use.
The part about infrastructure provision should be the focus of the balls-to-the-wall crash development effort. Fortunately not much research is needed here - there is a body of experience with telecentres (I use the British spelling advisedly here in recognition of the leading role played by practitioners in India) that shows the need for a nice, solid, reliable PC in a box that will operate in telecentre service with a minimum of setup and maintenance.
Telecentre operation involves the following capabilities:
1) IP telephony, both
a) through the Internet for international calling, and
b) through a gateway to the local switched telephone (POTS - Plain Old Telephone Service)
2) World wide web browsing
3) Spread sheet operations
4) email
5) simple word processing, in the character set of the local language(s)
6) a simple paint program (for training as well as drawing)
7) a simple database program
8) printing capability with the least cost of operation and greatest possible reliability.
An essential part of the package would be a source of electrical power. My approach is a 100 Watt system that keeps a 12 V lead-acid battery charged from a variety of sources, with pedal power as the backup. In addition to a robust pedal frame and an optimizing switching regulator, it needs enough microprocessor brains to run a little database system for keeping energy accounts. My experience shows that the people where it's installed will want to use it to charge other batteries as well, so the technology can't forbid that. Think of it as a small village power utility.
And finally there's the real eye-roller, connectivity. Felsenstein's Ninth Law states that every wire has two ends (and wireless has more), so just putting a WiFi transceiver and a directional antenna there isn't enough. We'd need to craft arrangements with satellite providers for low-cost VSAT time and work out the system structure to enable optimum use of the channel. Then we'd have to specify a low-cost earth station and negotiate a bulk deal on its production. Wifi and just plain wireline modems are the backup here.
It would be a real project - not just something to be dashed off and abandoned to its fate. When it's been shipping for six months and working stably we can then begin to bring in the laptops and be sure they'd work.
Along the way there would be a lot of unglamorous arrangements to be made with indigenous partner organizations and governments, not the high-visibility schmoozing with heads of state and the cream of the business establishment that make the OLPC effort look so appealing (and inevitable).
This one would be the steak, not the sizzle, and that's why it's fantasy to think that the OLPC project could be re-directed toward this methodology.
Lee Felsenstein
November 19, 2005 at 04:00 AM | Permalink | Comments (5)