Search This Blog

May 20, 2011

The think week

The undergraduate  Commencement is tomorrow, and the weather seems to be cooperating, knock on wood. Spring is the best time in education, like fall is in farming, I imagine. The fruits of our labor are over there, happy, naïve, proud and so young. I am still cleaning up the paperwork hills accumulated from the NCATE era, but we are thinking about the next year and beyond.
The Economist, my favorite magazine, has just published “What do bosses do all day,?” a review of the new Harvard study. The study indicates that bosses may “spend only 3-4% of their day thinking about long-term strategy.”  That is probably true for college administrators as well. I’d say it is much less than 3% during the busy time; hopefully a little more in the Summer. We crave summer, love summer, because it is the only time to think.  Another quote: “Bill Gates took regular “think weeks”, when he would sit alone in a cabin for 18 hours a day reading and contemplating.” This is great, except I would prefer to do it not alone, but with a small group of people. The article also does not mention that many major innovative companies have something like this not just for the bosses, but for everybody. We all need some think weeks.  
The challenges on the horizon are both new and somewhat unpredictable. For example, if things continue to go wrong, we may lose a significant part of our graduate enrollments. We should be responding creatively, not just with defense. Please think how we can stop this particular absurdity from becoming the law. I am trying everything possible through all available channels, but perhaps there is something I am missing. If things just continue to go as they go, we face an increasing pressure to modernize, to improve our programs smartly and be able to prove it. What we need is not just good honest work, but a real break-trough to question the very essence of education, of colleges, of educator preparation. That’s one item of homework for you all – come up with a brilliant idea to change the name of the game for us.
We have a number of other priorities; these are just a few:
  1. State-wide collaboration for teacher preparation: the vision, common placement policies, PR.
  2. Complete modernization of operations: Feinstein admissions, program information, student advising, digital 
  3. Update and modernize faculty processes: applications, annual reports, evaluations, asking for funds, etc.
  4. Make Chalk and Wire work for us to the maximum extent. This is not a technological challenge only: we need to get all programs to undertake a critical review of their assessment systems, make sure the Unit-wide assessments are used to the maximum, extent, stop collecting data no one can use, and in general, reduce the number of hoops for faculty and students to jump through.
  5. We need to make sure curriculum is discussed routinely, frequently, and with actionable outcomes. We should have no lose ends, no gaps, no redundancies; with every course in each program tightly fit in a way every student can explain.
  6. Need to review and update the fundamental documents: governance, conceptual framework, mission, etc.

This is just a brief list of things right off the top of my head. The next step would be to make a detailed list from what we started and di not complete this year, from the Strategic Plan, from what we know is coming next year. Then we need to see what we can actually accomplish, and how and how would do it. If we cannot do it all, what is the priority, and what should be put off.

May 13, 2011

The non-linear text

The institutional report we just turned in (enjoy) is a particular case of the non-linear text. It is designed, produced, and read differently than a linear document. NCATE has been long encouraging the so-called “electronic exhibit rooms.” Those were meant to save time and space, and make all documents available online. However, as M. Turner (2007) notices, experts often “offer learners a ‘flat’ body of text on screen that imitates the presentation of a paper document. But what is on screen is not a ‘page’ of text. It appears that a ‘page’ of text on screen is more difficult to make sense of than the same information presented on a printed page […] Linear content fails both to engage with the medium and, to use its unique expressive resources.” She claims that
[T]he starting point for writing online media needs to acknowledgment and embrace the medium’s different structure that is distributed rather than linear; and for the content to be constructed and presented to take advantage of that difference. The structure of the Internet, as an example of this type of media, is an ephemeral network of distributed nodes in potentially continuous connection. In this network there is no centre, no beginning or end and no certain direction—just islands of stored information; hosted it is true, on real hardware housed in a multitude of real buildings across the world, but the Internet itself is not a ‘thing’, in the way a book is a thing. (Turner 2007)
We all are only beginning to learn how to deal with the non-linearity of the information. There are no conventions, only the gut feeling on when to link and when not to link. We still tend to write in long sentences, and cannot produce website-friendly chunks of text. Those habits of mind that professional web masters learned perhaps a decade ago, are elusive to most of us, who do not build websites every day.

Several issues came up at different stages of production:        

1. Architecture. The website we produced has 1935 files in 122 folders. Of course, a couple hundred of them are not text – they are pictures, backgrounds, bullets, logs, style definitions, and other machinery that makes any website work. Several hundred are student work samples and course syllabi that all our programs graciously submitted. But the rest are text or data files. There is a limit to human ability to keep track of only so many documents. This makes possible the errors of redundancy – when text is re-produced, and in some cases versions of the same text may contradict each other. Every web designer knows to avoid redundant information, for it creates challenges for maintenance. To manage that, one can use a flat structure, where all files are in the same directory, or a hierarchical architecture, where everything is in folders and subfolders (Say, /Standard 1/St1Evidence/data). The hierarchy is much easier to navigate in production, because files can easily be found. It makes no difference to the reader. However, the flat structure encourages reusing of the same documents for multiple purposes. We ended up using a mixed design – documents of a similar kind – program reports, syllabi, student work samples – were in separate folders, while the main body of the report, documents and supplementary reports were flatly positioned in the main directory. Looking back, we should have used just a little more hierarchy (even though we had naming conventions, it was hard to remember what each file was called). For example, we should have a folder called assessment instruments, and samples of activities, etc. We did not have money to hire a professional web designer; learning curve is to be expected.
The challenge is to produce the most information-rich environment which requires the least amount of reading. I know our Reading faculty will object me saying this, but the new literacy is all about how to read less, and learn more. The non-linear text allows to write very briefly, and put most of text and data n the contingency pockets – in case the reader wants to learn more, or needs help understanding, or simply wishes to check the accuracy of information the writer provides. Skillful readers have always known how to scan and skip; the non-linear text allows all to do what only the best were able to do before. This is really the architectural challenge for the non-linear web-based text. Of course, NCATE does not know any of this, so they still expect a 30 page narrative. This confuses and discourages the writers from taking advantage of the non-linear writing. Even in fiction writing, only the most sophisticated of readers could read the allusions to the earlier parts of the story, and to larger cultural references. This is an important part of enjoying fiction – figuring out the allusions. But it also alienates children and less educated people. It makes serious writing an exclusive experience, a marker of class. But it does not have to be that way. If you are well-read, and encounter, say Ulysses as referring to the novel in your book, you just keep on reading. But someone else can digress, learn about it, and keep reading. All writing in all ages is already hyper-texted. It is just the case that many of these links are hidden – some on purpose, and some out of pride and arrogance.

2. Collaborative production. Different parts of the report were written by different people, some of it directly on the web. We had to limit the number of authors to avoid a complete chaos on the site. But then dozens of other people contributed to the report – they had to send us the information, we would then edit, format, and position on the site, link, etc. That is a tremendous waste of time and energy (thank God for low cost/high expertise labor of graduate assistants). In the next generation of report writing, all people would be able to submit their pieces directly onto the site, with a few people editing and linking these resources. That is the Wikipedia approach to text production. I wish it occurred to me eight months ago when we started; otherwise we would have done the report as a wiki book.  It would not look as fancy, but would be a lot more efficient in terms of labor. The budget office and the library director could just paste something on pages we created for them, or create their own pages. It is ironic, because I actually have an experience producing a wiki book with my students, and should have considered that option. The other advantage – my co-authors would not have to learn the Dreamweaver, which is actually a professional tool, not for amateurs like us. If you never use it again, it is a waste of time. Of course, we made a number of technical mistakes that all cost time to fix. Another lesson – I should have been the editor, and not write any parts of the report myself. There is a different mindset for each role, and it is a conflict to be both. We should have planned for much more editing time to avoid burning midnight oil, and develop an explicit set of instructions in what to look for.

3. Reading. The author used to have most of the power by structuring the text in a linear fashion, with a beginning and the end. Even if one wanted to skip a portion of the text, the rules of such skipping were laid out by the author who supplied a table of contents and the index page to guide the reader through the experience. Now the power balance has shifted radically toward the reader. She can move in any direction, including leaving the author’s text entirely, and going somewhere else. The boundaries between the author-produced and external text are almost completely obliterated. The color of your banner is the only thing that reminds the reader where he is. How any author does still manage to say what one wants to say? Who is responsible for accuracy of the information? It is even more important for the genre we were engaged in, the report writing. The non-linear text needs a test reader, someone who would examine it, and talk about one’s experiences, critique, and help organize the site. In linear text writing, most of us can easily imagine a reader, because we all have had much experience as readers. We cannot yet imagine a reader of non-linear text, who skips most of the text, hops around, comes back, scans rather then reads, and needs help staying focused on  the message we want to get across.

These are my linear thoughts on the non-linearity of the new written media. 

May 6, 2011

Notes from the underground

My email is on auto-reply: “I am going partially underground until May 13 …” I had to clear some time to finish putting together the NCATE report. We are doing it as a website, http://RICreport.org, rather than one long text, for a couple of reasons: first, it is easier to use the same documents for different sections of the report; and second, it allows us to include resources already on the web. The disadvantages are mainly technical: several people had to learn how to use Dreamweaver, which is neither easy nor very intuitive. There is also an organizational challenge: it comes to the point – within the next week or so, when one or two people only can edit, make sure there are no contradictions, gaps, or weird things. While the main body of the report is not that large, perhaps 50 pages, building the architecture of the report’s web site is a challenge. The site already contains 1827 files in 113 folders, more are coming online. The site was put together by about dozen different people, each able to edit the site directly. Faculty members, chairs, and many offices on campus have been exceptionally helpful in providing many different bits of information. The challenge is: we sometimes don’t know which of us has what data. With that many files, we can lose track of which is the most recent, and which is an older version. We can link wrong files, and override each other’s writing. Different sections may develop inconsistencies, redundancies, or gaps. That’s what really takes time, and only so much of it can be done by many people.
It is actually fun, believe it or not. Organizing information is an interesting challenge, like putting together a puzzle; except you get to design pieces. I especially enjoy finding bits of data that allow our programs shine. Did you know, for example, that 74% of our classes are taught by full time faculty? This is much better than in any number of peer institutions. Did you know that 97.5% of our FT faculty members have doctoral degrees? I am sure my co-authors experience the same thrill of a good find. You should take a look at the description of our assessment system put together by Susan, our field experiences (Eileen), and our  Diversity section and a number of different key pieces, including the monumental Curriculum and Assessment Chart nurtured by Karen. The site is still under construction, of course. I am fully aware this admission of having fun is somewhat contradictory to all my misgivings about NCATE. But putting all this together is actually an enjoyable exercise; it has an element of game in it. I also enjoy the crisis mode; sorry to admit it. When time runs out, and things happen fast, it is exciting to try to direct all the flying pieces to the same goal. Not that it always works, of course. Thanks to  the NCATE leadership team, working on the final stages of the project: Susan, Karen BR and Karen C, Eileen, Patrick, and Monica, and to our assistants Melissa, Erica (a.k.a. the queen of Dreamweaver), Paula, Kim, Dottie and Rose.
My former colleague and partner in crime Carolyn Edwards just reminded me yesterday how we had to miss the undergraduate commencement last year to put some finishing touches on the NCATE report. Yes, we did; perhaps the only commencement I missed in my career. But isn’t she a beauty? http://www.unco.edu/ncate.