Fresh & New(er)

discussion of issues around digital media and museums by Seb Chan

Fresh & New(er) header image 4

Museums and making the ‘digital shift’

March 11th, 2012 by Seb Chan
Respond

I’m mid-way through writing a number of articles that explore the challenges for museums in pulling ‘digital’ into their core operations. As a result I’ve started to formulate this idea –

museums will not be able to properly understand and integrate ‘digital’ into their organisational DNA until they have substantial born-digital collections.

Libraries have had a significant head start, I’m beginning to think, because of their ever increasing digital holdings. Not to mention the acceleration of their shift to being ‘service-oriented’ which had its seeds in the 1980s.

Discuss.

(Regular readers will know that I’ve discussed digital experiences, augmenting physical objects, visitor engagement etc, as well as the organisational change aspects at length before. This idea is additive to those pre-existing conversations. If you are new to this then have a read of my summative post from Web Directions a few months ago).

Tags:   · · 27 Comments

The museum as a text adventure – Inform7 and TourML/TAP

March 2nd, 2012 by Seb Chan
Respond

Today I was sitting at WebWise 2012 listening to Rob Stein talk about TAP/TourML and he started talking about games and stories referencing Marc Reidl’s work.

It reminded me a lot of the world of interactive fiction and it got me thinking about whether it would be possible to use TourML to generate text adventures.

And then, whether long established interactive fiction authoring tools like Inform7 (used as the system behind PlayFic) could be used to author gallery tours.

Being of a generation that has fond memories of playing Infocom adventures (I vividly remember my dad buying Zork II for our Commodore 64) – there’s definitely a lot to learn about how this narrative genre works that could equally be applied to the creation and support of visitor narratives.

So I took 20 minutes to whip up a very very basic ‘playable’ text advennture rendering of the conference experience.

Go play it on PlayFic! (It obviously isn’t finished)

Here’s the source code. (contains spoilers!)

The story headline is "Adventures at WebWise". 

The story description is "A quick journey into interactive fiction inspired by Rob Stein's introduction to TAP presentation and his referencing of Marc Reidl. It raised, in my mind, that there are already robust frameworks for quickly generating interactive fiction of the sort that makes the foundation of a mobile tour - so, could TAP use the Inform7 language for advanced authoring?"

The Main Conference Room is a room. "Rows of tables, each with their own powerstrip stretch endlessly toward the speaker podium. Two projection screens show the wifi login details whilst unfashionably out of date pop music plays softly over the speaker system.

On the table nearest you is a conference pack and an abandoned Samsung Galaxy.

The foyer is to the South."

Projection screens are scenery in the Main Conference Room. Speaker system is scenery in the Main Conference Room.

Samsing Galaxy is a thing. The Samsung Galaxy is in the Main Conference Room. The description is "The Samsung Galaxy is turned off. You cannot figure out how to turn it on, and, turning it over, you realise that the battery has been removed. Helpful isn't it?"

Conference Pack is a thing. Conference pack is in the Main Conference Room. The description is  "The conference pack, like all conference packs, is looking for the recycling bin. You notice that the conference schedule has already been removed, leaving only  the wad of promotional materials."

South of the Main Conference Room is the Foyer. 

The Foyer is a room."The foyer is empty.

Lukewarm coffee drips from a boiler but there are no cups nearby. The crumbs of food that used to be here litter the floor. Obviously these places don't pay their venue staff very well. A faint waft of perfume comes from the East."

East of the Foyer is the Lifts.

Lifts is a room. "As you enter the lift lobby you notice the furthest-most door has just closed.

The whirring of motors comes from behind closed lift doors. 

Strangely, there are no lift buttons and the concierge must have gone on a break."

That doesn’t look like source code does it?

Doesn’t it look exactly like the sort of language that museum educators and curators coud quickly learn and write?

Tags:   · · 7 Comments

Metadata as ‘cultural source code’

March 1st, 2012 by Seb Chan
Respond

A quick thought.

Last week I wrote about collection data being ‘cultural source code’ in the context of the upload of the Cooper-Hewitt collection to GitHub.

As I wrote over there,

Philosophically, too, the public release of collection metadata asserts, clearly, that such metadata is the raw material on which interpretation through exhibitions, catalogues, public programmes, and experiences are built. On its own, unrefined, it is of minimal ‘value’ except as a tool for discovery. It also helps remind us that collection metadata is not the collection itself.

If you look at the software development world, you’ll see plenty of examples of tools for ‘collaborative coding’ and some very robust platforms for supporting communities of practice like Stack Overflow.

Yet where are their equivalents in collection management? Or in our exhibition and publishing management systems?

(I’ll be cross-posting a few ideas over the next little while as I try to figure out ‘what goes where’. But if you haven’t already signed up to the Cooper-Hewitt Labs blog, here’s another reminder to do so).

Tags:   · 2 Comments

Three months in. Be a summer intern!

February 27th, 2012 by Seb Chan
Respond

Three months in now.

And if you’ve been keeping an eye on the Cooper-Hewitt Labs blog you’ll know that email marketing and event ticketing has been overhauled, we’ve optimised our hosting platforms, a new monthly newsletter has been started, and last week we released our collection dataset to the public domain on Github under a Creative Commons Zero dedication.

My team has also been busying with webcast events and getting the volume of posts on the Design Blog increased, as well as experimenting with different social media tactics elsewhere. Behind the scenes, there’s plenty of long term planning going on with the Mansion rebuild under way, and embedding digital infrastructure into it.

There’s a fair bit more on the near horizon – an entirely new ecommerce presence for the Cooper-Hewitt Shop, a CMS migration – and quite a bit more.

But, for readers of Fresh & New(er) who happen to be students, you might be interested know that we’re taking on summer interns!

The deadline for applications is March 1 so hurry!

Tags: No Comments.

Back to reality. Returning from the Horizon Retreat.

February 1st, 2012 by Seb Chan
Respond

Last week I was at the Horizon New Media Consortium 10 Year Retreat – The Future of Education. It was a fascinating glimpse into the world of bright-eyed educators and a few museum people who want the future of education to be something far better than it is now. If that sounds a little utopian, it should.

The Horizon Reports have always made for good reading. I contributed to some of the Horizon.Au reports in and have had a fair number of my projects included over the years as ‘examples’. These reports have more-or-less predicted most of the technology trends over the last decade, even if their timeframes are too optimistic. Their methodology – a wiki-made document compiled by hand selected specialists works especially well and avoids a lot of the traps of most futurist predictions. What is especially useful is that these wikis remain available after the reports are published – so it is possible to read the internal discussions that informed the creation of the report.

Summing up the predictions of the Horizon reports over the past decade was this great chart from Ruben Puentedura. You’ll notice recurring themes and the emergence of the social web, then mobile, then open content in the reports over the last decade.

The retreat, set outside of a stormy Austin, Texas, locked 100 people from several continents in a room with huge sheets of butcher’s paper and some great facilitation. Over two days meta-trends were identified and ideas shared. Thousands of tweets were tweeted on the #NMCHz hashtag, and many productive discussions were had.

Ed Rodley sums up the event nicely – day one and day two – over on his blog. Ed and I spent a fair bit of time throwing around ideas around the role of science museums in the modern world (from his experience at Boston and mine at Powerhouse) which should become the topic of a future blogpost.

But gnawing away at me during the Horizon Retreat was this article from the New York Times on Apple and its supply chains, and a broader follow up opinion piece in The Economist.

For all the talk of digital literacy, educating for megatrends, and the role that museums can play in fostering creativity – all this talk of open content and collaborative learning – these words continue to concern me.

The most valuable aspects of an iPhone, for instance, are its initial design and engineering, which are done in America. Now, one problem with this dynamic is that as one scales up production of Apple products, there are vastly different employment needs across the supply chain. So, it doesn’t take lots more designers and programmers to sell 50m iPhones than it does to sell 10m. You have roughly the same number of brains involved, and much more profit per brain. On the manufacturing side, by contrast, employment soars as scale grows. So as the iPhone becomes more popular, you get huge returns to the ideas produced in Cupertino, and small returns but hundreds of thousands of jobs in China.

Maybe it is just pessimism brought about by having two consecutive winters creeping in.

You can grab the summary ‘communique’ from the Retreat from the Horizon site.

Tags:   · · · 2 Comments

Call for submissions: Epic Fail at Museums & the Web 2012, San Diego

January 25th, 2012 by Seb Chan
Respond

Jane Finnis (Culture24) and I are hosting the closing plenary at Museums & the Web in San Diego this year. We’ve called it Epic Fail and we’re going to be shining a light on the failures that we individually and we collectively have had as project teams, institutions, and maybe even the sector as a whole.

Inspired by the valuable lessons we’ve learned personally from over-sharing our own failures on our blogs, and the growing trend in the non-profit and social enterprise sectors to share analyse, and learn from failures – we think the time has come for Museums and the Web to recognise the important role that documenting failures plays in making our community stronger.

Failure?

Well, taking a cue from FailFaire, there are many common reasons for failure in the non-profit sector –

1. The project wasn’t right for the organisation (or the organisation wasn’t right for the project)
2. Tech is search of a problem
3. Must-be-invented-here syndrome
4. Know thy end-users
5. Trying to please donors rather than beneficiaries (and chasing small pots of money)
6. Forgetting people
7. Feature creep
8. Lack of a backup plan
9. Not connecting with local needs
10. Not knowing when to say goodbye

Sound familiar? I thought so.

So . . .

We’re doing a call out for ‘failures’ to be featured in our closed door session (that means no tweeting, no live blogging).

Each Fail will present a short 7-10 minute slot followed by 10 minutes panel and open-mic discussion. Each Fail needs to be presented by someone who worked on the project – this isn’t a crit-room – and we want you to feel comfortable enough to be honest and open. We want you to explore the reasons why you thought the project was a failure, diagnose where it went wrong, what would you do differently, and then collectively discuss the key lessons for future projects of a similar nature or targeting similar people.

Maybe, like me, you did an early project with QR codes that didn’t take into account the lighting situation in your exhibition, not to mention the lack of wifi? Or maybe a mobile App that you forgot to negotiate signage for the exhibition space? Or an amazing content management system that failed to address the internal culture and workflow for content production and ended up not being used?

In fact in my career, I can’t think of any project that hasn’t had its own share of failure. But in most cases I’ve been able to address the problem and iterate, or, if necessary, as they say in the startup game, ‘pivot‘.

The more significant the failure, the better is its potential to be an agent of change.

So, if you are coming to Museums and the Web in San Diego in April this year, get in touch to nominate your project for a spot! We promise to create a safe environment for sharing these important lessons and end this year’s conference on a high.

Get in touch with the Fail Team – epicfail [at] freshandnew [dot] org

Tags: 1 Comment

Six weeks in and Cooper-Hewitt Labs launches

January 24th, 2012 by Seb Chan
Respond

The last six weeks have been a bit of a blur – settling into a new city, a new job, trying to find proper coffee nearby (still unsuccessful!). As you do in a new job, my first weeks have been spent looking at the lie of the land and analysing the data available about the land itself (and configuring better data collection tools if the data you have isn’t suitably illuminating).

The Cooper-Hewitt has just closed its last exhibition for a little while and the focus is firmly on the museum’s re-building and getting all the back of house digital infrastructure up to date and in order.

The question that underpins most of what comes after that is clearly – “how can a museum make the most of online and digital operations when its buildings are closed?”.

So . . .

Today we launched a new blog over at the Cooper-Hewitt – Cooper-Hewitt Labs. This one focusses on the work my team is doing – and the challenges that lie ahead. Being the Labs, we’re going to be undertaking a range of experiments that we’re going to need your help with, as well as offering some opportunities to intern with us (hint! hint!).

Go check out the Cooper-Hewitt Labs. (And don’t forget to leave a little offering for the tanuki while you are there.)

(awesome animated gif by Fealoki!)

Tags: No Comments.

The museum website as a newspaper – an interview with Walker Art Center

December 3rd, 2011 by Seb Chan
Respond

There’s been a lot of talk following Koven Smith’s (Denver Art Museum) provocation in April – “what’s the use of the museum website?”. Part driven by the rapid uptake of mobile and part driven by the existential crisis brought on Koven, many in the community have been thinking about how to transform the digital presence of our institutions and clients.

At the same time Tim Sherratt has been on a roll with a series of presentations and experiments that are challenging our collections and datasets to be more than just ‘information’ on the web. He calls for collecting institutions “to put the collections themselves squarely at the centre of our thoughts and actions. Instead of concentrating on the relationship between the institution and the public, we can can focus on the relationship we both have with the collections”.

Travelling back in time to 2006 at the Powerhouse we made a site called Design Hub. Later the name was reduced to D’Hub, but the concept remained the same. D’Hub was intended to be a design magazine website, curated and edited by the museum and, drawing upon the collection, engaging and documenting design events, people and news from that unique perspective. For the first two years it was one of the Powerhouse’s most successful sites – traffic was regularly 100K+ visits per month – and the content was as continuous as it could be given the resourcing. After that, however, with editorial changes the site began to slip. It has just relaunched with a redesign and new backend (now WordPress). Nicolaas Earnshaw at the Powerhouse gives a great ‘behind the scenes’ teardown of the recent rebuild process on their new Open House blog.

It is clear that the biggest challenge with these sorts of endeavours is the editorial resourcing – anything that isn’t directly museum-related is very easily rationalised away and into the vortex, especially when overall resources are scarce.

So with all that comes the new Walker Art Center website. Launched yesterday it represents a potential paradigm shift for institutional websites.

I spoke to Nate Solas, Paul Schmelzer and Eric Price at the Walker Art Center about the process and thinking behind it.

F&N: This is a really impressive redesign and the shift to a newspaper format makes it so much more. Given that this is now an ‘art/s newspaper’, what is the editorial and staffing model behind it? Who selects and curates the content for it? Does this now mean ‘the whole of Walker Art Center’ is responsible for the website content?

Paul Schmelzer (PS): The Walker has long had a robust editorial team: two copy editors, plus a managing editor for the magazine, but with the content-rich new site, an additional dedicated staffer was necessary, so they hired me. I was the editor of the magazine and the blogs at the Walker from 1998 until 2007, when I left to become managing editor of an online-only national political news network. Coming back to the Walker, it’s kind of the perfect gig for me, as the new focus is to be both in the realm of journalism — we’ll run interviews, thinkpieces and reportage on Walker events and the universe we exist in — and contemporary art. While content can come from “the whole of the Walker Art Center,” I’ll be doing a lot of the content generation and all of the wrangling of content that’ll be repurposed from elsewhere (catalogue essays, the blogs, etc) or written by others. I strongly feel like this project wouldn’t fly without a dedicated staffer to work full-time on shaping the presentation of content on the home page.

F&N: The visual design is full of subtle little newspaper-y touches – the weather etc. What were the newspaper sites the design team was drawing upon as inspiration for the look and feel?

Nate Solas (NS): One idea for the homepage was to split it into “local, onsite” and “the world”. A lot of the inspiration started there, playing with the idea that we’re a physical museum in the frozen north, but online we’re “floating content”. We wanted to ground people who care (local love) but not require that you know where/who we are. “On the internet, nobody knows you’re a dog”.

The “excerpts” of articles was another hurdle we had to solve to make it feel more “news-y”. I built a system to generate nice excerpts automatically (aware of formatting, word endings, etc), but it wasn’t working to “sell the story” in most cases. So almost everything that goes on the homepage is touched by Paul, but we use the excerpt system for old content we haven’t manually edited.

PS: Yeah, the subtle touches like the weather, the date that changes each day, and the changing hours/events based on what day it is all serve as subtle reminders that we’re a contemporary art center, that is, in the now. The churn of top stories (3-5 new ones a week) and Art News from Elsewhere items (5-10 a day, ideally) reinforces this aspect of our identity. The design team looked at a wide range of news sites and online magazines, from the New York Times to Tablet Magazine to GOOD.

Eric Price (EP): Yeah, NYTimes, Tablet, and Good are all good. I’d add Monocle maybe. Even Gawker/Huffington Post for some of the more irreverent details. We were also taking cues from print – we’re probably closest in design to an actual printed newspaper.

F&N: I love the little JS tweaks – the way the article recommendations slide out at the base of an article when you scroll that far – the little ‘delighters’. What are you aiming for in terms of reader comments and ‘stickiness’? What are your metrics of success? Are you looking at any newspaper metrics to combine with museum-y ones?

NS: It’s a tricky question, because one of the driving factors in this content-centric approach is that it’s ok (good even) to send people away from our site if that’s where the story is. We don’t have a fully loaded backlog of external articles yet (Art News from Eleswhere), but as that populates it should start to show up more heavily in the Recommendation sections. So the measure of success isn’t just time on site or pageviews, but things like – did they make it to the bottom of the article? Did they stay on the page for more than 30 seconds (actually read it)? Did they find something else interesting to read?

My dream is of the site to be both the start and also links in a chain of Wikipedia-like surfing that leads from discovery to discovery, and suddenly an hour’s gone by. (We need more in-article links to get there, but that’s the idea.)

So, metrics. I think repeat visitors will matter more. We want people to be coming back often for fresh & new content. We’ll also be looking for a bump in our non-local users, since our page is no longer devoted to what you can do at the physical space. I’m also more interested in deep entrance pages and exit pages now, to see if we can start to infer the Wikipedia chain of reading and discovery. Ongoing.

F&N: How did you migrate all the legacy content? How long did this take? What were the killer content types that were hardest to force into their new holes?

NS: Content migration was huge, and is ongoing. We have various microsites and wikis that are currently pretty invisible on the new site. We worked hard to build reliable “harvesting” systems that basically pulled content from the old system every day, but was aware of and respected local changes. That worked primarily for events and articles.

A huge piece of the puzzle is solved by what we’re calling “Proxy” records – a native object that represents pretty much anything on the web. We are using the Goose Article Extractor to scrape pages (our own legacy stuff, mostly) and extract indexable text and images, but the actual content still lives in its original home. We obviously customized the scraper a bit for our blogs and collections, but by having this “wrapper” around any content (and the ability to tag and categorize it locally) we can really expand the apparent reach of the site.

F&N: How do you deal with the ‘elsewhere’ content? Do you have content sharing agreements?

NS: [I am not a lawyer and this is just my personal opinion, but] I feel pretty strongly that this is fair use and actually sort of a perfect “use case” for the internet. Someone wrote a good thing. We liked it, we talked about it, and we linked right to it. That’s really the key – we’re going beyond attribution and actually sending readers to the source. We do scrape the content but only for our search index and to seed “more like this” searches, we never display the whole article.

That said, if a particular issue comes up we’ll address it responsibly. We want to be a good netizen, but part of that is convincing people this is a good solution for everyone.

F&N: What backend does the new site run on? Tech specs?

Ubuntu 11.04 VMs
LibVirt running KVM/QEMU hypervisor
Django 1.3 with a few patches, Python 2.7.
Nginx serving static content and proxying dynamic stuff to Gunicorn (Python WSGI).
Postgres 8.4.9
Solr 3.4.0 (Sunburnt Python-Solr interface)
Memcache
Fabric (deployment tool)
ImageMagick (scaling, cropping, gamma)

F&N: What are you using to enable search across so many content types from events to collections? How did you categorise everything? Which vocabularies?

NS: Under the hood it’s Apache Solr with a fairly broad schema. See above for the trick to index multiple content-types: basically reduce to a common core and index centrally, no need to actually move everything. A really solid cross-site search was important to me, and I think we’re pretty close.

We went back and forth forever on the top-level taxonomy, and finally ended with two public-facing categories: Genre and Type. Genre applies to content site-wide (anything can be in the “Visual Arts” Genre), but Type is specific to kind of content (Events can be of type “Screenings”, but Articles can’t). The intent was to have a few ways to drill down into content in cross-site manner, but also keep some finer resolution in the various sections.

We also internally divide things by “Program”, programming department, and this is used to feed their sections of the site and inform the “VA”, “PA”, etc tags that float on content. So I guess this is also public-facing, but it’s more of a visual cue than a browsable taxonomy.

Vocabularies are pretty ad-hoc at this point: we kept what seemed to work from the old site and adjusted to fit the new presentation of content.

The two hardest fights: keeping the list short and public-facing. This is why we opted to do away with “programming department” as a category: we think of things that way, no one else does.

F&N: Obviously this is phase one and there’s affair bit of legacy material to bring over into the new format – collections especially. How do you see the site catering for objects and their metadata in the future?

NS: Hot on the heels of this launch is our work on the Online Scholarly Catalogue Initiative from the Getty. We’re in the process of implementing CollectionSpace for our collections and sorting out a new DAMS, and will very soon turn our attention to building a new collections site.

An exciting part of the OSCI project for me is to really opening up our data and connecting it to other online collections and resources. This goes back to the Wikipedia surfing wormhole: we don’t want to be the dead-end! Offer our chapter of the story and give them more things to explore. (The Stedelijk Museum is doing some awesome work here, but I don’t think it’s live yet.)

F&N: When’s the mobile version due?

NS: It just barely didn’t make the cut for launch. We’re trying to keep the core the same and do a responsive design (inspired by but not as good as Boston Globe). We don’t have plans at the moment for a different version of the site, just a different way to present it. So: soon.

Go and check out the new Walker Art Center site.

Tags:   · 14 Comments

Chickens, eggs & QR codes

November 21st, 2011 by Seb Chan
Respond

Adam Greenfield at Urbanscale just posted some interesting research his team has been doing in NYC on the citizen familiarity of QR codes.

This is especially timely as QR codes are getting a lot of interest (finally) from the cultural sector. The Powerhouse Museum in Sydney has been doing QR codes for a few years – first failing – but now perhaps getting good traction with them now that the code scanner is built into the exhibition catalogue App. Shelley Bernstein’s team at the Brooklyn Museum have also been rolling them out. And Wikipedia’s been promoting the nifty language ‘auto-detect’ QR codes that Derby Museum & Art Gallery have developed (QRpedia).

But there are still very valid concerns about the appropriateness of them – especially now that visual recognition is coming along rapidly (see Google Goggles at the Getty) and maybe even NFC might gain traction (see Museum of London’s Nokia trial). QR codes feel very much like a short term intermediate solution that isn’t quite right.

Here’s Greenfield:

While general awareness of the codes was frankly rather higher than we’d expected, and a majority of our respondents knew more or less what they were for, very few … were successfully able to use QR codes to resolve a URL, even when coached by a knowledgeable researcher.

A strong theme that emerged — which we certainly found entirely unsurprising, but which ought to give genuine pause to the cleverer sort of marketers — is that, even where respondents displayed sufficient awareness and understanding of QR codes to make use of them, virtually no one expressed any interest in actually doing so. As one of our respondents put it, “I’ve already seen the ad, and now I’m going to spend my data plan on watching your commercial? No thanks.”

These findings mirror the anecdotal experience most of us have had with QRs ourselves. The value proposition just isn’t obvious – and the amount of scaffolding required to encourage scanning can, in museums, sometimes take up as much visual space as the content that ends up being displayed (especially for object labels).

Is this just a chicken and egg situation? I’m not sure.

Greenfield’s initial findings do show that even when there is awareness there isn’t interest. And, I’d add, even when there is interest, museums need to be especially careful to consider what visitors actually want/expect to see when they scan vs what museums are able to show/tell. This is a crucial distinction that is often missed in discussions of in-gallery content delivery.

Tags:   · 5 Comments

Farewell Powerhouse, Hello Cooper-Hewitt National Design Museum

November 15th, 2011 by Seb Chan
Respond

It is official now.

Today I’m leaving the Powerhouse after a long stint to take up a new role as Director of Digital & Emerging Media at the Cooper-Hewitt National Design Museum in New York. I’ll be starting at the Cooper-Hewitt on November 28 (2011).

I’m looking forward to the new challenges and also the opportunities that I hope will flow from being part of the larger Smithsonian Institution whilst being in the cultural epicentre that is New York. I’m especially excited to be working for the Cooper-Hewitt with its high calibre exhibitions, and well established national education projects.

I’m continuing to write Fresh & New so don’t fret about any loss of signal. It will just be from a different timezone – and possibly, over time, a slightly different set of spelling conventions.

I’d like to thank the support of the Powerhouse over many years – the teams I’ve managed and my colleagues are all kinds of awesome. My digital colleagues have made the workplace one where ideas have flourished and everyone has been committed to trying out new things fueled by coffee, sugary treats, and a sense of mirth. I’ve been extraordinarily lucky to have worked with such people.

Of course none of the work that’s been done would have been possible without the rest of the Powerhouse, especially the curatorial, registration, and education staff who’ve been at the frontline of how the ‘new museum’ has adapted to rapid technological change. The IT team at the Powerhouse, where I first began as an employee, has also been instrumental in providing a flexible technology environment in which to test and trial new ideas, and they embody the notion that a real IT department should be ‘enablers’, not just ‘fixers’.

I also need to thank my series of supervisors over the years each of whom has supported experimentation and encouraged the prototyping of many wild ideas. I hope my own management style has learned from them.

Most of all I’ve made some (hopefully) lifelong friendships working at the Powerhouse and I’m going to miss hanging out and making stuff with such great people.

It also needs to be said that the Powerhouse, as a workplace, provided a rare luxury – a job that provided great creative stimulation and opportunity, flexible working hours and work/life balance, even within the constraints of a shrinking public service. The opportunity to do ‘purposeful work’ – not just a job – is a luxury not afforded to many and one that needs to be seized.

And of course, “done is the engine of more”.

Now let’s see how it turns out in “the city that is a goal”.

Fresh and New readers should also keep an eye on a new technology and museology blog from the Powerhouse being coordinated by Paula Bray called Open House. It is going to be broader in focus and draw in contributions form across the Powerhouse so make sure you add it to your RSS reader.

Tags: 23 Comments