Fred Brooks: Building Student Projects That Work For Us, For Them and For Their Clients

In the Thursday keynote, Professor Brooks discussed a couple of project approaches that he thought were useful, based on his extensive experience. Once again, if you’re not in ICT, don’t switch off – I’m sure that there’s something that you can use if you want to put projects into your courses. Long-term group projects are very challenging and, while you find them everywhere, that’s no guarantee that they’re being managed properly. I’ll introduce Professor Brooks points and then finish with a brief discussion on the use of projects in the curriculum.

Firstly, Brooks described a course that you might find in a computer architecture course. The key aspect of this project is that modern computer architecture is very complex and, in many ways, fully realistic general purpose machines are well beyond the scope of time and ability that we have until very late undergraduate study. Brooks works with a special-purpose unit but this drives other requirements, as we’ll see. Fred’s guidelines for this kind of project are:

  1. Have milestones with early delivery.

    Application Description
    Students must provide a detailed application description which is the most precise statement that the students can manage. A precise guess is considered better here than a vague fact, because the explicit assumption can be questioned and corrected, where handwaving may leave holes in the specification that will need to be fixed later. Students should be aware of how sensitive the application is to each assumption – this allows people to invest effort accordingly. The special-purpose nature of the architecture that they’re constructing means that the application description has to be very, very accurate or you risk building the wrong machine.

    Programming Manual (End of the first month as a draft)
    Another early deliverable is a programming manual – for a piece of software that hasn’t been written yet. Students are encouraged to put something specific down because, even if it’s wrong, it encourages thought and an early precision of thought.

  2. Then the manual is intensely critiqued – students get the chance to re-do it.
  3. The actual project is then handed in well before the final days of semester.
  4. Once again the complete project goes through a very intense critique.
  5. Students get the chance to incorporate the changes from the critique. Students will pay attention to the critique because it is criticism on a live document where they can act to improve their performance.

The next project described is a classic Software Engineering project – team-based software production using strong SE principles. This is a typical project found in CS at the University level but is time-intensive to manage and easy to get wrong. Fred shared his ideas on how it could be done well, based on running it over 22 years since 1966. Here are his thoughts:

  1. You should have real projects for real clients.

    Advertise on the web for software that can be achieved by 3-5 people during a single semester, which would be useful BUT (and it’s an important BUT) you can live without. There must be the possibility that the students can fail, which means that clients have to be ready to get nothing, after having invested meeting time throughout the project.

  2. Teams should be 3-5, ideally 4.

    With 3 people you tend to get two against one. With five, things can get too diffuse in terms of role allocation. Four is, according to Fred, just right.

  3. There should be lots of project choices, to allow teams choice and they can provide a selection of those that they want.
  4.  Teams must be allowed to fail.

    Not every team will fail, or needs to fail, but students need to know that it’s possible.

  5. Roles should be separated.

    Get clear role separations and stick to them. One will look after the schedule, using the pitchfork of motivation, obtaining resources and handling management one level up. One will be chief designer of technical content. Other jobs will be split out but it should be considered a full-time job.

  6. Get the client requirements and get them right.

    The client generally doesn’t really know what they want. You need to talk to them and refine their requirements over time. Build a prototype because it allows someone to say “That’s not what I want!” Invest time early to get these requirements right!

  7. Meet the teams weekly.

    Weekly coaching is labour intensive and is mostly made up of listening, coaching and offering suggestions – but it takes time. Meeting each week makes something happen each week. When a student explains – they are going to have to think.

  8. Early deliverable to clients, with feedback.

    Deadlines make things happen.

  9.  Get something (anything) running early.

    The joy of getting anything running is a spur to further success. It boosts morale and increases effort. Whatever you build can be simple but it should have built-in stubs or points where the extension to complexity can easily occur . You don’t want to have to completely reengineer at every iteration!

  10. Make the students present publicly.

    Software Engineers have to be able to communicate what they are doing, what they have done and what they are planning to do – to their bosses, to their clients, to their staff. It’s a vital skill in the industry.

  11. Final grade is composed of a Team Grade (relatively easy to assess) AND an Individual Grade (harder)

    Don’t multiple one by the other! If effort has been expended, some sort of mark should result. The Team Grade can come from the documentation, the presentation and an assessment of functionality – time consuming but relatively easy. The Individual Grade has to be fair to everyone and either you or the group may give a false indication of a person’s value. Have an idea of how you think everyone is going and then compare that to the group’s impression – they’ll often be the same. Fred suggested giving everyone 10 points that they allocated to everyone ELSE in the group. In his experience, these tallies usually agreed with his impression – except on the rare occasion when he had been fooled by a “mighty fast talker”

This is a pretty demanding list. How do you do tasks for people at the risk of wasting their time for six months? If failure is possible, then failure is inevitable at some stage and it’s always going to hurt to some extent. A project is going to be a deep drilling exercise and, by its nature, cannot be the only thing that students do because they’ll miss out on essential breadth. But the above suggestions will help to make sure that, when the students do go drilling, they have a reasonable chance of striking oil.


Another Airport Land Speed Record: Can My Students Make Their Connections?

As I was running through San Francisco Airport last week, I was thinking many things. Among them were:

  1. Why am I running through yet another airport?
  2. How long will it be before my bad knee gives out? (Surgery last November)
  3. Is my wife still behind me?
  4. Do I ever do this to my students?

Two people running through an airport.

The reason that I was, once again, running through an airport was that delightfully evil concept – the legal connection. This is the minimum connection time estimated for your incoming and outgoing flights, through a given airport. When your travel organiser goes to make flights, they plug all of your destinations and restrictions into their computer, add some seriously manual machinations, and then receive a set of results that all meet the legal connection limits. These are connections that the airlines say are legitimate and, if you miss a flight, they will assist you in making another one. There’s only one problem with the so-called legal connection. Any variances to the schedules, caused by weather, delay in customs, late arrival of other planes, maintenance or unexpected construction in the airport, can make it hard to impossible to make your (so-called) legal connection. Hence, I run a lot in airports. I very rarely miss planes but I run past a lot of people who do – people who don’t know that there’s only one bus every 40 minutes between the international and domestic terminals. People who don’t know where the bus is or that it’s more reliable to catch a cab. People who don’t know which way to go and there isn’t enough signage to assist – Frankfurt Airport, with your sign that says ‘Terminal X this way” and a sign that points in both directions, I’m looking at you.

On this occasion, my knee held out and my wife WAS behind me, which is just as well as the hotel is booked in her name. But it really made me think about the layout and structure of STEM curricula. We set up pathways through our courses that are designed to develop knowledge and produce a graduate with the right combination of skill and knowledge. But what else do we assume? If we have provided bridging to bypass a pre-requisite, are we secretly assuming that the student will have aced the bridging or just passed the bridging? Do we introduce Boolean algebra in second year because “almost every student will have enrolled in Logic I” even though it’s not formally part of our course progression?

We can look at our programs as being legal connections, but with that comes all of the darker aspects that this entails. We’ve recently redesigned our curriculum, just in time for curriculum 2013, and part of this was removing some of the implicit assumptions and making them explicit. Providing pathways for the less-experienced. Matching expectations so that a Pass in a pre-req was sufficient for the next course – you didn’t need 60. We build giant pyramids of knowledge throughout our courses but, of course, a pyramid only works one way up and is far less stable if we don’t have all of the supports. If too many of these building blocks are assumed, and not explicit, then our legal connection is next to impossible to make. And we all know what the cost of that is.

I don’t want to run through anymore airports, and I strongly suspect that when we ask our students to do so, we lose a fair few of them on wrong turns or leave them stranded somewhere along the way, without ever making their destination.


Consistency: Doing the Same Thing Can Be Useful!

Another day, another design post, but this post is not going to be that huge because I’ve already shown you several examples of what I’m talking about today. Systems are more usable when similar parts are expressed in similar ways – that’s why OS X’s steady convergence with iOS is probably going to bring more people to both platforms than lose grumpy people who don’t like the ‘new’ interface. If one Apple platform allows you the familiarity to use any other, the consistency will make people happy.

And that’s today’s principle for discussion: consistency. Again, it’s from Universal Principles of Design, Lidwell et al, Revised, 2010. People will learn new things more quickly, focus on the right things and be able to transfer their knowledge more easily if the system is consistent. There are four basic considerations and I’m going to show them to you in exactly the same format that I’ve been using for all of these posts. Well, I’ve been trying to be consistent. It’s possibly been similar enough that when you see bold italic you think ‘design principle’ and when you see a bulleted list with leading bolds you think ‘aspect’ or ‘facet’. Sorry for the priming but I’m trying to make a point here 🙂 Anyway, here are the four kinds of consistency.

  1. Aesthetic consistency: Is everything similar or the same in terms of style and appearance? I adopted a standard template for my lectures in one course, with strong visual indicators of transitions to different modes. As a result, students always knew which lecture they were in and what was expected of them in terms of participation and activity.
  2. Functional consistency: This is consistency in what things mean and how they’re used. How do students hand-in their work – do they always do the same things to make a hand-in work? Does button X always produce result Y? We can also use pre-existing knowledge of function to our benefit and save ourselves the effort of having to teach someone how to approach our work, from scratch. Use existing knowledge of functional actions, and their associated symbols, to make your work easier. (Here’s a thinking point: the save Icon for many systems is an image of a 3.5″ floppy disk. I polled my students and over 70% of them had only seen the disk in this context. What does ‘save’ look like in a cloud-based context?)
  3. Internal consistency: The elements inside your system or set of materials should be consistent with each other. Once you’ve learned one part of the system, the others won’t surprise you by being completely different. This also makes people believe that you have actually bothered to design a system, rather than stitch it together out of other, inconsistent, parts.
  4. External consistency: How do your objects, materials or systems work inside the overall environment of your students? This is a tricky one because innovation sometimes means that you’re out of step (let’s say ahead of step) with other people. Just because nobody else uses lecture recordings and you do isn’t a violation of external consistency. However, there will be core design standards across most areas (to at least a degree) and adherence to these is important or it’s easy for students to get confused. If you are diverging from this standard, you must take the additional effort to address the inconsistency to reduce confusion.

As Lidwell notes, aesthetic and functional consistency should be considered in almost everything we do – aesthetic consistency allows us to produce a distinct idea, and functional consistency makes it easier for people to learn. The other requirements drive the need for internal and external specifications that work and are observed. All we’re really doing here is trying to make it easier for people to learn, and that should never really be that controversial.

(Wait, what was that about priming? And haven’t you mentioned that before? Yes, I have. Further discussion is coming soon.)


If you’ve got five thinking hats, I’ve got five hat racks for you!

This isn’t actually a post about Edward de Bono’s Five Thinking Hats, although that’s a fascinating book to describe adopting different modes for different cognitive activities. Once we get out of design week, I hope to come back to this. Part of designing any materials or object is to ensure that the information it represents or makes available is organised in a way that people can use. No textbook of any value is organised along Dadaist principles – semi-random and deliberately nonsensical organisation – they all use well-established idioms like chapters, headings and indexes (indices?) to organise the information and make it more accessible. One of the things I like about the reference I’m using (Universal Principles of Design, Lidwell et all, Revised, 2010) is that all of the design principles are organised alphabetically but, wherever you start, there is a see also section down the bottom that takes you to a conceptually linked entry. You can then, of course, use alphabetical search or the index to then locate it.

According to the Five Thinking Hats principle, there are a limited number of organisational strategies that you can use to organise information. These can be used for just about any application.

  1. Category: We can organise things by their similarity or relatedness. In teaching materials for Computer Science, we often group similar programming concepts together – loops with loops, conditionals with conditionals. Most texts are going to use categorisation to minimise the cognitive load of context switching from one area to another, and having to remember what you read before. Will your students try to search out things by category? Probably – that’s how their access to your college’s web site handles their enrolment details, most likely, by grouping all relevant courses into a common category. But why not tag all materials relevant to Assignment 2 under a search item ‘stuff for Assignment 2’? That’s an easy use of categorisation.
  2. Time: Lecture recordings are a natural fit for time-based organisation because they present a set of events that are dependent upon each other and evolve over time. Yes, you could put them into a folder sorted by lecture name but, unless your lectures are really not connected at all, no-one is going to thank you for that. Schedules and historical timelines are also fairly obvious candidates for temporal strategies.
  3. Location: Grouping things by their geographical or spatial reference helps people successfully orient themselves to work with your materials. While it may seem that this is of little use to people who aren’t teaching geography, what about making a clear distinction between things that students need for lectures and those that they need for tutorials or practicals? Wherever your students are – what do they need when they get there? Is it clearly identified wherever your materials are or do they need to search through everything to find out what they need?
  4. Alphabet:  You didn’t think I’d leave this one out did you? The alphabet is always a good fallback when people will be using your work as a reference and not reading it sequentially, or you want to be able to leap around the work efficiently. If you can’t think of any other way – go for the alphabet. Of course, this assumes that whoever reading your work is familiar with your alphabet. This must be a consideration if you’re working with people who have your language as their second, or third, language.
  5. Continuum: Some things can be grouped by their magnitude – students are all familiar with this if you’ve ever posted a list of grades from top to bottom, rather than by ID. Best to worst, highest to lowest, largest to smallest. This kind of organisation can be handy for electronic materials where you have a variety of recording types and some produce larger files. Providing a list to students can be organised by type or by size. If you know that students prefer the smaller, faster to download, ones, sort to put them up there first. If you’re comparing things across one key measure, think about how you could group along that measure to make the information easier to access.

Now, this may explain why I try to put these blog posts into some sort of context by talking about ‘opinion’ and ‘design’ as weekly themes. The posts are already ordered by time but I add a categorical overview because the actual categories and tags are used for people finding these posts, not necessarily for people who are already reading my blog. This loose organisation, that I usually make at least an oblique reference to at the start of each post, helps you to categorise the information in the post. How do you group your ideas and materials?


Give your students a nudge (and the Woman in Red effect)

The Woman in Red effect is a strange one. Woman in red appear more attractive, men in red appear more dominant. (This is a gross simplification and doesn’t take into account gender orientation.) I’ll talk about this more later on in this post but, first, I’d like to talk about encouraging people to adopt behaviour that will allow them to learn better and engage more with your teaching.

A picture of a woman in a red dress, sitting in a chair.Picture of a man wearing a red tie.

One of the most common problems I face is getting my students to engage with my courses, and the materials I’ve spent time preparing. I’m not teaching at an Army base so I can’t order people to attend my lectures or read the book, and I can’t offer every student $1000 if they demonstrate sufficient knowledge. I have to try and get them to adopt the ‘correct’ behaviour without the ability to restrict their options to force adoption or changing the incentives that are in play.

This is where nudging can be very useful. Nudging is a method for making the behavioural changes that you want, in a predictable way, without overly constraining people or resorting to outright bribery. We’re all exposed to nudging on a day-to-day basis but it’s not always obvious – which, to be honest, is good. There are always going to be certain students who actively resist any form on behavioural modification or suggestion that their adaptation can be predicted in any way. We’re not trying to brainwash people – we’re trying to gently encourage them onto a path where they will get more out of our courses.

Here are some useful nudging techniques. Once again, the primary source here is “Universal Principles of Design”, Lidwell et al, Revised, 2010.

  1. Use sensible defaults. If you have a default option that will do the most good for your participants, then they will have to expend more effort to do themselves less good. Do you have an automated electronic forum enrolment system? Are all students added to it automatically as they enrol? Once on, are they automatically subscribed to all key news feeds? Can they cut themselves off the feed easily (probably undesirable)? Opt-in and opt-out can be important concepts here.
  2. Provide good feedback. Let people know when the’ve done something with perceptible and immediate feedback. “Thank you for your submission.” “Your question has been sent.” “That’s a good question, let’s look at the answer.” If people haven’t done something, then provide them with a visible indicator that it’s not done. A colleague told me about a countdown clock that they put on the course web page showing the time remaining until hand-in closed. Students handed in at a much higher rate – yes, in feedback they said that they didn’t like it but they noticed it! A student hasn’t handed in any drafts of their work for this assignment and there are still 12 hours left? Why not send them a reminder?
  3. Provide properly-aligned incentives. What do you want students to do? Hand in early or hand in their best work? If you give a bonus for handing in early, but don’t tie it to quality of work, then all you do is encourage hastiness. If you only accept ‘early work’ if it meets quality and acceptance criteria, then you are encouraging students to start and finish their work earlier – bringing the point of understanding further forward. Similarly, rewarding attendance is a slippery slope to sleeping students. Rewarding participation subsumes an attendance requirement and reduces the sleeping cohort. (We hope!)
  4. Simplify the choices people have to make by structuring them well. Complex decision processes take time to navigate and, at each stage, there are more places for things to go wrong. If students have choices in your course, is it easy for them to choose or is it a matter of “navigate three web-pages, make an appointment, follow-up e-mail and, at each stage, make a good decision”? Sometimes processes do have to be this complex but, particularly for good teaching materials, if you make it easy to work out what your choices are and which one to take – students will make better choices. Even if things do need to be complex, laying them out clearly and making the process easier is going to help everyone.
  5. Provide visible goals. People like to measure progress. If you have visible goals, and a clear indication of progress, then your students can work out how far they’ve come and how they’re tracking against their own performance metrics. Unless students are totally disengaged, every student will have a meter in their head to tell them how well they’re doing. The ‘more than 50% is a waste’ crowd are tracking how little work they can do in Assignment 3 to still scrape a pass. The ‘99% is 1 mark lost’ crowd are carefully watching to see if they’re holding to their mission. If you provide measures and goals that the students can tie in to, then you may be able to combine this with a nudge that encourages good behaviour.

Now, some people think of this as molly-coddling or pandering. Urm, no. If these students were independent knowledge framework assemblers and fully mature before they came to us then college would take about 3 months as we handed over the books, some tests and told them to come back at the end of the year. The majority of our students need our help to nudge them in the right direction and to keep them on the right track. That way, when they finish, they are mature and independent – but that’s the culmination of a long and complex process.

Now, I haven’t forgotten about the Woman in Red effect. It’s also called, with less gender orientation, “The Red Effect” and you see it in nature as well, with those monkeys with comically exaggerated colouring and protrusion of their sexual organs. I didn’t actually want to focus on this – it’s interesting but it’s not really useful as a teaching technique. It is, however, a nudge because people will see the title and there are a group of people who will click on this blog because they want to read about the effect, or maybe they’re fans of the movie, or the Chris de Burgh song (which is actually Lady in Red). Some people will click through to this because I primed them on my Facebook page with a very brief discussion of the effect and they might want to read more. I was able to legimately use a picture of a woman in a red dress, which will also nudge some people to read this article when they otherwise wouldn’t. Of course, being me, I used Gauguin because it’s an image of a woman in red that has no sexual or culturally inappropriate overtones. (Believe me when I tell you that searching for ‘images woman in red’ gets you a lot of search hits, only some of which you can use.)

Many of you are here anyway and have not been nudged. Except that, if you’ve read this far, I’ve already established an incentive mechanism that says “reading 1000 words of Nick won’t kill you”. I’ve set the feed up so you don’t have to take any action to see that I’ve posted. You’re near the end of the post so it’s not that much further to go and I am about to talk about the Red Effect some more – so please stick around. We’re nearly done.

So, because you’ve read this far, here’s some more information on the Red Effect. In mandrill species, the red colouring of the snout indicates testosterone levels – an attractive trait in a monkey mate. There is a cultural aspect to the effect in that the red clothing worn should be culturally appropriate – a man wearing a red dress and lipstick is potentially not going to be seen as dominant but a man wearing a red tie probably will be. Or is sending a message that he wishes to be seen to be.

Ultimately, my very lightweight discussion ignores the variety of sexual orientations and relationships around. I don’t have firm data to hand on how this plays out in other combinations – but I’m certainly now looking because it interests me! If I wear red, will my wife pay up to twice as much when she takes me out to dinner?

Now something that surprised me is that, in the 2004 Olympics, where red and blue outfits were assigned randomly in boxing, Greco-roman wrestling and tae kwan do, the red outfits won significantly more often. This is cross-gender – dominance in red appears to transcend boundaries. Similar effects occur in English football – red teams win more often.

What’s going on here? Is it that their opponents are being intimidated? Is the referee more likely to favour the red? I would be interested to see what happens on the basketball court, where aggressive behaviour will attract fouls. The next time that you think that your team is getting too many fouls – what colour are they wearing? Are they still winning?

Articles that might be worth reading include “Red Enhances Human Performance in Contests”, Hill and Barton, Nature, May 19, 2005. Hill also produced “Red shirt colour is associated with long-term team success in English Football” (Attrill, Gresty, Hill et al), Journal of Sports Sciences, April 2008, 26(6). If anyone has any good articles on the effect outside of hetero-normative sources, please put them in the comments!


Access All Areas: Getting Your Knowledge Into Everyone’s Head

This is another design post, as that’s this week’s (loose) theme. Again, the reference is “Universal Principles of Design”, Lidwell et al, Revised edition, 2010.

If you’ve used a modern lift (you might call it an elevator) recently, you may have noticed that lifts now have larger buttons than they used to, have Braille on the buttons, provide audible feedback when you press buttons and, on a lot of occasions, as they move – and they’re bigger, with wider doors.

What’s happened? Legislation across many states and countries now require that any public environments be as widely accessible as possible – that disabled and able-bodied alike can use the lift, that people with prams can get in, that those who are larger don’t have a problem.

If you’ve looked at older lifts, in converted European hotels or pensiones, you’ll find tiny little boxes, with hard to read or unmarked buttons, zero feedback and an experience that is akin to travelling in a shoebox on a string. These were barely usable for the able-bodied and, despite the additional space consumed and the extra cost involved, it appears that the accessible elevator/lift is now with us for the foreseeable future.

When we consider accessibility, we think about how can we design our materials and teaching spaces so that the greatest number of people can use them – without any additional modification. This is the secret of the new lifts. A very large number of accessibility options are now standard in lifts so that they can be installed and used without further modification. Now this is certainly not a disabled/able-bodied divide because many of our teaching spaces are hard to work in at the best of times! As we’ll see, you might be surprised how often these issues can affect any or all of your students.

There are four fundamental principles of accessibility, which I’ll touch on here, and draw into teaching examples.

  1. Perceptibility: Everyone can perceive your content or design, regardless of their abilities. For teaching purposes, this means having redundant delivery methods such as ALT tags on HTML images, audio recordings for visually impaired students, full text version for text-to-speech synthesis and so on. This, to me, also includes the colour blindness checks that I’ve mentioned before. From a delivery point of view, can everyone in your lecture theatre see what you’re doing?
  2. Operability: Everyone can use what you’ve produced. In the knowledge area, perception and operation are closely aligned, but think about things like scratch-off cards. Do you have an alternative for someone without fine motor control – or a broken wrist? Do you require your class to rearrange themselves for group work? How will that work with a wheelchair or crutches? I once ran an exercise that required students to flip coins – which turned out to be really, really dumb on my part. This was a set of repetitive actions, with a high probability of dropping the coin. This was almost inoperable for people with no issues because of the confined space in the lecture theatre. (Another teaching application is the open book exam – have you given the students enough desk space to open books?)
  3. Simplicity: Make it easy to understand and use what you’ve done, whether students have seen either your work or an example of this type of work before. If you’re using a commonly used format – think carefully before you make subtle changes to it or people will get confused with the new complexity. Be clear, consistent and remove as much unnecessary complexity as possible. Don’t throw everything on to the screen at once but consider the use of staged delivery to provide simple blocks that go together to form a more complex whole.
  4. Forgiveness: Reduce the impact if students do something wrong while working with your material and, from a design perspective, put things together so that it’s hard to go wrong in the first place. Designing your materials so that there is only one obvious way to use them (using good affordances) will mean that students will find it harder to go wrong in the first place. Being able to recover easily reduces the impact of accidental error – which can negatively reinforce behaviour and encourage students to disengage. Scratch-off cards have simple use and easily recovered error conditions, depending upon whether they give instant feedback or not. These can be high affordance/high forgiveness materials and, because of that, very, very useful.

I’ve given you a number of examples but I want to give you an example of bad accessibility, from a recent hotel stay. I went to grab the shampoo and conditioner mini-bottles to put into the shower and I realised that the text on the front was identical for both bottles. I wasn’t sure which was which. I turned the bottles around and, in type so small that I had to squint, I could just make out the text. Turning the bottles around, I had noticed that there was Braille on the bottles – which seemed a bit odd, given that they’d done such bad design on the back. I realised that the Braille was the same on both bottles and all it said was the brand name.

This is, possibly, one of the most irritating things they could have done. Assume that you’re blind. You’ve made your way to the bathroom, finally found the sink, located the bottles, picked them up and (hooray!) they have Braille. Annnnnd,  it’s completely useless. You ask your sighted companion to help you but he or she are long-sighted. Together, angrily, you mix all the bottles up and make Shamditioner. More seriously, this fails Perceptibility (you can’t see which one is which), Operability (the bottles were hard to open as it happened) and Forgiveness (as it was easy to use the wrong product). I’ll give it a pass on Simplicity, only because you don’t really need instructions for Shampoo – putting it in a bottle is sufficiently simple. I may be being generous.

I’m working on a checklist for myself, because I try and consider all this but doing it from a list this long isn’t actually following the rules themselves! When I get the checklist finished, I’ll post it up on the blog.

 


Design, design everywhere – nor any drop of ink!

The upcoming week of posts, from Monday (Australian time) onwards is going to talk about interesting principles of design and how I believe they can be applied to teaching. I’m working from a set of books in my design library but the main one is “Universal Principles of Design”‘ Lidwell, Holden and Butler; Revised edition, 2010. I will try to put that in as a reference throughout, as these posts shouldn’t force you to search backwards and forwards, but I may forget so here it is as a basis.

I will be on the road for a while and I may have to load the queue to deal with the fact that WiFi doesn’t reach into the middle of the pacific at 30,000 feet. Yet. This may also slow down my comment response and clearance. Please hang in there, I’ll deal with everything as and when my network access improves.

The final post in the week of opinion is going to be published shortly and it’s more of an encouragement to look at other people who are more experienced in this education area – so go and read their opinions as well!

The title of this post is a reference to a fragment of The Rime of the Ancient Mariner by Samuel Taylor Coleridge.

Water, waterevery where, And all the boards did shrink; Water, waterevery where, Nor any drop to drink.

My use of this is supposed to do three things:

  1. Tap into the familiar pattern established by Coleridge with this well-known quotation – because it’s familiar to some of you, you may remember my message more easily. (Don’t make me force you to remember the “1 2 3 4 5, 6 7 8 9 10, 11 12” song from Sesame Street to prove my point about familiarity.)
  2. Identify that design is actually everywhere but that, in many regards, digital design has become the dominant form. The advantage of digital design, for us as teachers, is that we can be producers and distributors of digital design work without having to involve or pay for printers. Modern tools and production facilities allow us to make our good design, and well-designed materials, available anywhere, anytime.
  3. Remind you that, because good design is everywhere, we don’t want our teaching materials to be the worst designed thing that students see on a given day. No, you don’t have to be a professional designer, as I’ve said before, but consideration of basic principles can help to lift the valuable educational message that we’re all trying to give, and put it into a frame that will make it easier to use and actually be valued.

My secret final aim is to interest you all in running off to read Coleridge, because the language is beautiful and he’s one heck of a poet. It’s ok, I’ll still be here when you get back.