Something on my mind

For the last week or so we’ve been working on scheduling our first data-gathering adventures in July and August, which are going to be jam-packed with observations and intercepts for the whole team. We’ve also been working on planning for a couple of new programs and projects and how to evaluate them.

We’re a creative bunch, so the ideas keep rolling in and I’ve been thinking quite a bit about grouping, staging, and prioritizing. Meanwhile, the seasonal shift in the sunrise and sunset has been wrecking a bit of havoc on the homefront recently–our cats are now quite convinced that 4:15 am is breakfast time. The [only] positive thing about being awake then is that it is does build a quiet moment into the day when I can focus on something that I might otherwise not have the time to do (or that I would probably put off to another time). My what-on-earth-am-I-doing-up-now project this weeks has been a little mindmapping.


I keep thinking about the question Why do we do it?, and the connected question What makes this fulfilling? For me, reaching goals is part of what makes the work fulfilling, so I thought I’d start with goals I’d like to work on this year. This isn’t meant to represent what I intend to achieve in the year, but is a way to start thinking about directions and planning paths. Although I started with the idea of goals for this year, built into the map are the places I’d like to reach next year, the year after, and in a few cases some year in the future.


I think there are more than a couple of 4:30am mindmapping exercises in my future, with more refining and a few more concrete descriptions. Many of the bubbles feel like they need to be unpacked a bit. Sometimes it was hard to figure out where things were connected because it felt like they were connected to everything. Which reminded me of a tweet from Bethany at AAM this year:

I think this ties into a theme that I think has been woven through many of the planning and projecting exercises of the last couple of months, whether it’s applying some of the design thinking strategies, mindmapping, or creating personas. A lot of the focus of our discussions has been on visitor-centered-ness. It was a phrase that I heard over and over again at AAM, and it sounds like what we are trying to do, but since coming back from Seattle I’ve been thinking a lot about what we mean when we talk about visitor-centered practice or visitor-centered design. I heard a lot of examples of how that is conceptualized in panels (as well as informal discussions). How we define it in our team and in our work is going to be an important point to articulate in our planning.

For today, I included my own definition of visitor-centered-ness in my first meeting of the day, talking with the fabulous protection services staff about our collection app.

guardsand artlens

It was like giving a tour with the most engaged group ever, which was awesome. They are among the staff members who spend the most time with visitors (and the art), and they have a ton of experience and knowledge about how visitors experience the galleries, the app, the art, and the organization. I learned a lot from them this morning, and I’m excited to be talking to them again next week, when I plan to pluck their brains for even more information.

Calm Before the Storm

This week has felt like the dip between waves. After a series of clustered deadlines there are a few moments to think before the next cluster of deadlines arrives. Often the troughs are great moments to start stirring up new notions, and it has been a week of exciting ideas and a great team meeting. Each time we meet we refine and clarify a bit more, and every day we get closer to filling this up with our plan for the year:


There is little as exciting as a blank slate.

Planning and Projects

We’ve had an incredibly busy couple of years in our department (and in the institution), and it is just recently that the manic pace has started to slow a bit. There are still a lot of balls in the air, but we seem to be past the point where we regularly forget what day of the week it is (or on at least a handful of occasions, what month it is). So we’re taking the moment to, in the immortal words of Vanilla Ice, stop, collaborate, and listen.

We thought about making a music video, but opted for planning with post-it notes instead.

BC and the planning board

We had an incredibly productive discussion, and I’m really excited to see what directions the process takes us. I work with amazingly creative, perceptive, empathetic people, and I see fantastic things on the horizon. Including a panoply of new and interesting projects (more on that soon).

Thinking about (Design) Thinking, Part 1

For the last year or so design thinking has been stalking me. (There are lots of images showing the design thinking process. I found this one here).


I keep ending up in meetings and discussions where someone says we should try using it for a project. I hear it talked about at conferences, and recently saw a presentation in which graduate students showed proposed museum projects devised through a design thinking process. In the last few months I’ve been involved in two attempts to actually use design thinking. In the first case it seemed like a process with quite a bit of potential, but because of the circumstances it ended up being rather truncated. It was an all day workshop and we got to the Ideate stage and then the day ended. Taking it beyond that stage wasn’t part of the plan for the day, but there also wasn’t a plan for taking the imagined projects back into our regular work. Talking through the process was exciting in the day, but as weeks and then months passed and the ideas stayed in the corner, rolled up on giant post it notes, the process began to feel a lot less magical than it did when we were idea-ating months earlier.

The second experience was more recent and was disappointing, even frustrating. Like the first experience, we didn’t get past the ideate stage. Unlike the first time around, those of us who participated had the distinct impression that the organizers had scheduled the day with the ideas that would be going to the prototype stage already identified before the rest of us had begun. We split into groups, and each group came up with a slate of ideas, which were presented to the somewhat glazed over expressions of the organizers. They complimented everyone on how fantastic and creative the day had been, but when the project moved to the prototype stage it incorporated none of the ideas any of the groups had come up with.*

Although one of these encounters with design thinking felt exciting and full of potential, while the other one felt disingenuous, the two experiences were, ultimately, surprisingly similar. In neither case did we get past coming up with ideas. In neither case was there a plan for bringing ideas to the prototyping or testing stages. In neither case was the problem design thinking as a process itself, but instead perhaps an incomplete commitment to the process. And so in both cases a lot of energy was spent on coming up with ideas that never had a chance at being more than ideas. Ideas will only get you so far.


Ideas that aren’t taken out for a test drive are pretty easy to come by (at least I find them to be thick on the ground in my work), and some of them you realize (perhaps even as you’re coming up with them) don’t really deserve a second look in the cold light of day. But some (or many) of them just might work. There’s only a couple of ways to find out if they do: 1) try them out and see if it works; 2) wait for someone else to come up with the idea and try it out to see if it works for them.

I’m pretty sure one of these is more satisfying than the other.

*Since then the idea one group had come up with appeared as a major component of another organization’s project. It’s been very popular (for them).