I, like many of my peers, went through various crisis as I matured professionally. First existential, wondering what my purpose and value were. Doing that while a discipline is starting to established itself is both a privilege and a curse. A privilege because you are both defining yourself and your broader collective without the shackles of traditions and ingrained habits, making progress easy and fast; a curse because when the vast majority of people “like you” are questioning what you are at the same time, it is hard to find the comfort and support that gives you the confidence to advance.

Peter Morville and Lou Rosenfeld wrote a book that described what the IA practice meant for a particular context. That provided enough confidence for five or six years of truly amazing development in the practice of information architecture. I am happy I was around. However, I have not been happy about my community of practice in the past several years. The level of energy, enthusiasm and possibility I felt and experienced in the first half of the 2000′s became marred by attempts to find a solution to a problem that was not ever really articulated.

Known as “defining the damn thing”, we talked ourselves into a circle trying to describe information architecture and its place in the world. In that process, I watched information architecture erode as a discipline. The forward momento became stagnant. When DTDT is described as naval-gazing, it’s because it accurately portrays information architecture’s adolescence. Our struggle with DTDT is because we were in effect, telling IA to grow up, “be a man”, when it was still a child verging on adolescence. That’s the second crisis, a crisis of identity. Unlike the existential crisis, value was not the core question: we learned our worth and felt (mostly) confident about it.

Identity crisis is the failure to achieve ego identity during adolescence. Psychology research (Erikson) has found that peers have a strong impact on the development of ego identity during adolescence. I, in retrospect unfortunately, spent most of my energy trying to figure out my identity and grow professionally while our collective identity crisis was taking place. I would have been a really happy diplomat. Or engineer. Or software developer. All of which I considered seriously at different points, but because I pursued this path, I needed to push myself in ways I could have never imagined and watched others do the same – and I spent several years frustrated with the lack of progress.

Information Architecture’s crisis of identity reflects our inability to change our self-image. I find it funny that the stage of psychosocial development in which identity crisis occurs, according to psych theory, is called the Identity Cohesion versus Role Confusion stage. Defining Information Architecture and being an Information Architect are different things. We spent years conflating the two. Since our daily reality is the work we do, this work exists in a setting that requires role definition. We thought that role was “information architect” and in trying to make progress figuring that out, we stopped making progress on what information architecture was becoming.

Many smart people have repeated over and over that these are separate issues, but to this day I see people not making the distinction. This is when User Experience Design won the battle. At the same time all this was progressing, User Experience emerged as a term to describe the intent of these efforts we were trying to figure out. User Experience seemed to me like a way to refocus from the dogma of User-Centered Design to a more meaningful overarching understanding that imbues various disciplines with meaning and purpose. I feel this has been wildly successful. But what of the IA discipline?

That’s when our poor framing of the question came back to haunt us. “What is information architecture and where does it belong” was now being asked in this larger User Experience context. And Peter and Lou’s definition for the context in which it was defined was not enough. Also, the same question was being asked of other disciplines. This is where Design with its deep and rich traditions emerged as a great foundation – as a practice – to form the identity that could deliver on this promise.

By declaring and accepting we are all User Experience Designers we embraced User Experience and left Information Architecture behind. Apples and Oranges. But – I hope it’s obvious now – taking the identity of user experience designers could/should have simply broadened the identity of information architect, not dismiss information architecture as a practice. Unfortunately for information architects, this amazing progress of the field (UX) happened while we were having a major identity crisis and extremely ill equipped to distinguish the two.

There is no conclusion to this. I see seedlings of the right sentiment starting to re-emerge in information architecture from people who are not interested in what we call ourselves. That problem will always get in the way and I have come to terms with it. I am an information architect because that’s a meaningful descriptor of my identity – TO ME. I don’t care if I need to describe that meaning as User Experience Designer so I can be understood, but I no longer struggle with the identity. The label is just a translation of meaning into different contexts. I absolutely embrace User Experience as the field in which I practice my work and I draw from a few different disciplines to achieve what I need to achieve. But information architecture is still the principal discipline that guides me. It took me a long time to realize I didn’t have to move away from information architecture to get to where I wanted to go. It is nice to know this instead of wondering about it.

Explaining our discipline succinctly in a context-agnostic fashion seems to be the holy grail for most – I feel ‘making the complex clear’ already did that over 30 years ago. Explaining the discipline in context-sensitive terms, well, that I can’t do and I don’t feel I need to. Describing information architecture (as in DTDT) is the top down way to answer our identity question. As an information architecture practitioner I know damn well that the most meaningful structures emerge from the content, so my base assumption is to continue expanding the boundaries of our practice by DOING THINGS and then calling them something when we need a name for them. That name may be information architecture. Or not. I don’t care – as long as we don’t conflate the practice development and our identity we can start growing again.

Jeff was nice enough to send me the source images so I created the widget library for us dynamic prototyping fans. You can still download the original OmniGraffle stencils.

To use it, download the UX People Widget Library for Axure file (3.2 MB), run Axure RP, then, on the Widget pane (located on the left side of the screen) click “Load Library….”. Locate the file you just downloaded (UX People.rplib). The library should load up and look something like this:

Related and of interest:

• People in Pictures: 8 Techniques for Humanizing Diagrams by Dan Brown
• Other Axure Widget Libraries
• If you have no idea what’s with the thing about the banana… #ias10

After the presentation I actually started asking myself why the hell is it that I so rarely have to design for search behaviors. The reality is that oftentimes I’m designing for existing services where search is an existing capability and iterating it is never in scope.

One of the problems with that, which became more apparent to me after the presentation, is that treating search as a separate behavior from browse is really misguided. I thought about this problem before but could not quite articulate it very well until today.

Historically I had been taught and understood search and browse as distinct elements – which they are visually and from a UI elements standpoint – but from a behavioral perspective, they really are not, rather, they are part of a continuum. A spectrum of discovery behaviors if you will.

If we think, for example, about how faceted classification emerges in search interfaces and in browsing interfaces it becomes really clear how intertwined they are.

One of my questions to Peter during the presentation (which unfortunately did not get addressed but hopefully will be part of the UIE follow-up podcast) was if he had identified patterns of use of faceted search and if there were any emergent patterns that could help answer if faceted search is more appropriate for a particular kind of content or context — and when it might not be appropriate.

Faceted browse/search is a hot topic at work and I feel like it’s been historically a random requirement that ends up on a project brief because of process inertia. Someone saw it somewhere and thought it was cool so decided that it should be applied to the kind of content we are surfacing for our audience.

I have no good evidence to substantiate my hypothesis at this point (unless lack of examples in the wild is enough), but I suspect that for our content – namely video content, generally in the entertainment realm, frequently movies, series and other TV programs – having faceted search as a primary tool for discovery is really inappropriate.

I have definitely seen and appreciated the application in e-commerce and feel like there is a prevalent pattern there for its use. But on the content I design for, I just don’t know. If I am to rely on what I know from user behavior learned observing people try and get to the video content they want (across different platforms in a number of distinct scenarios of use) the attributes they need to make decisions are frequently few. The variation in behavior is little in terms of user motivation, and greater in content type (i.e.: people look for movies differently from how they look for series).

How can I make a compelling argument that this particular pattern is not the right fit when I am not sure what is? I’ve seen it fail in usability tests but that only makes people try to fix it and improve it, not to try a completely alternate solution that might be appropriate. Any ideas out there?

Also, I’m not on a crusade against faceted search, I am just looking for ways to 1) articulate that there might be a problem picking this particular pattern 2) explore other ways to do it (both in the context of use and content I described). Any ideas are welcome.

Regardless, I think it will help me in the future to frame the scope of what I need to design for when dealing with content discovery behaviors by thinking about them in the browse-search spectrum. At least I expect that to give me a better argument to combat feature requirements void of context.

“Hi, everyone. If you decided you were interested in IA/UX but you didn’t know much about it…and you wanted to find out more…where would you go? What books would you read? What blogs would you add to your feed reader? What seminars would you attend? What tutorials would you take? What tweeters would you follow?”

Having no context I took 5 minutes are made this recommendation. I am sure I would tweak and change this significantly if I had any other inputs, but this was my 5 minute recommendation and I thought I’d share:

The starter book is Information Architecture: Blueprints for the Web. After that, The Elements of User Experience followed by Don’t Make Me Think. All other books people recommend are wonderful, but not to start with.

Become a member of The Information Architecture Institute and find yourself a mentor; it’s the most valuable investment anyone can make when starting out.

I don’t follow blogs. I let the community curate content for me instead. Following the right people on twitter means they send me all the good blog posts. Also, you come across the relevant blogs via the discussion lists (specially the one you get access to when you join the IA Institute). Connect with people first, content second. It’s helpful to connect to the UX/IA/IxD groups on LinkedIn, Facebook, Slideshare – it will help attract good content to you. You’ll immediately have access to all kinds of people you’ll become interested in connecting with.

Attending seminars: Go to all the free stuff happening locally. In Philly there’s PhillyCHI and Refresh Philly to start with. Online, spend your money wisely and pick the topics that seem more interesting to from UIE Virtual Seminars and Rosenfeld Media Webinar Series. Make sure you keep track of The UX Workshop for free broadcast of local events in other cities.

For community and education, attend the IA Summit. If you are starting out, that’s the first conference to go to. And Interactions. For more focused training, UIE’s User Interface Events and Adaptive Path’s UX Week and UX Intensive.

On Twitter, there are too many interesting people to follow and big names in the field. They don’t necessarily share any relevant information or advice relevant to starting out. These people do: @jmspool, @whitneyhess, @halvorson, @sladner, @mmilan, @austingovella, @leisa, @mediajunkie, @emalone, @stephenanderson, @billder (I share a lot of stuff too: @livlab)

Lastly, start a blog. You learn significantly more by sharing and capturing your own thoughts than countless dollars spent in training.

And if you are going to start on all this after lunch, print this to read during lunch: http://www.jjg.net/ia/recon/

Who is the Information Architecture community of practice? The practice of information architecture has evolved significantly since I started working on the User Experience Design world. There was a time when being a practitioner equaled to being an information architect. That is not the case anymore as evidenced by the popularity of different job titles. There was also no formal training of any kind that would equip someone with the skills necessary to practice information architecture – self-teaching was the only path – today we see a number of institutions offering educational opportunities. There are many other changes, including how sister disciplines have evolved and grown, how the market demands shape different kinds of professionals to fulfill the needs of companies (further emphasized in moments of economic stability), etc.

With all this, how can we as a community do a good job at investing resources to continue to create valuable services that support the development of the practice of information architecture? I don’t have one answer nor do I hear a prevalent answer from anyone else in the community. I think I need to do some user research to get a better grasp of the problem. I’m trying to re-educate myself on who the practitioners are so I can offer a better and non biased answer, and do a better job at the kinds of things we are doing today (specifically through the IA Institute in my case).

I’ve talked to practitioners directly, I’ve read everything I could that comes to the IA Institute as requests or comments and I’ve tried to engage with as diverse a group of people within the practice as I can. Though I wasn’t doing that with the explicit intent of understanding this audience, I feel like I have a lot of information, but I’m unsure if it’s enough to help me understand our community better. In thinking about the IA community of practice in terms of “audience” to whom services can be provided to (as well as the community who powers these services), I was trying to identify a model to help me articulate the various dimensions that reflect different people’s expectations, needs and attitudes about their practice and career; and how the IA Institute could best support them. Here are a few:

Novice <--------------> Experienced
(how much qualification under the belt one has)

Specialist <--------------> Generalist
(how much of their personal practice focuses on a particular aspect of UXD)

Practitioner <--------------> Collaborator
(is this person interested in the practice itself or knowing just enough to work with someone who is)

Innies <--------------> Outties
(is this person working independently or with a firm helping companies with their UX or are they part of an org working on their own UX)

Member <--------------> Non-Member
(are they a member of the IA Institute – this is only really relevant as I think about things offered through iainstitute.org)

This is might be the start of a way to think about who the IA Institute is supporting. Knowing that everyone changes as they progress in their career, how can we offer different services that are relevant to people in the different points where they might be? I think I could plot every practitioner I speak to in some end of these spectrum and have a map of what “profile” they might fit.

There are some specific needs (which the IAI could fullfill) that are most relevant to people only when they align to certain characteristics. For example, a very experienced practitioners who is generalist in UXD (maybe a manager), working inside an organization and member of the IA Institute since the beginning, does not have a great overlap in needs with someone who is fresh out of library school, interested in pursuing a career in UXD, very focused in the core IA practice (likely to specialize) and who just learned about the IA institute last month because they attended the IA Summit for the first time.

Granted these are probably the most distant profiles but you get the idea. I think identifying the main profiles (who knows, maybe if I have enough relevant information I could build some useful personas out of that), would be really helpful in directing our future efforts, rather than trying to stretch the usefulness and relevance of everything we do to an audience so broadly defined as “information architecture practitioners”.

Anyway, this is my first draft. What is missing? What seems off? How do you think this could be helpful?

Since 2004 the IA Summit has been my favorite conference to attend for a number of reasons (it’s been going since 2000 though, I just had not had the opportunity to attend before then). The quality of the content always meets my needs, the diversity of people I meet is just the right mix of new contacts and familiar faces and the atmosphere is consistently welcoming and conducive of great conversations and ideas.

This year is particularly exciting for many reasons, chiefly because it is the 10 year anniversary of the IA Summit! What a great landmark for our practice that we have been going strong for a decade. This makes me proud about our past and excited about our future.

I am also involved in so much stuff that I know I won’t have a minute to rest; I’ll probably need a day off to recuperate after Memphis. Here are a few things I am looking forward to (that I hope I get to see you involved in):

1. I’m giving a workshop on behalf of the IA Institute – The workshop is titled Beyond Findability: Reframing IA Practice & Strategy for Turbulent Times. I am really looking forward to it and I know it will be a blast presenting with with Andrew Hinton, Matt Milan and Joe Lamantia. We will focus on practical advice to help peers elevate their IA practice and expand the boundaries of how IA is applied today. There are still a few spots left if you want to come; Wednesday 3/18 from 9:00am to 5:00pm.

2. I’m presenting a new tool: The UX Health Check – After almost two years of working with a new approach originated by the fantastic Austin Govella, we are finally going to expose it to a broader audience. Initially we proposed a workshop but given the novelty, we are doing a presentation and a poster. Come check it out Friday (3/20) at 5:45 in the Tennessee Exhibit Hall during the Poster Session and Sunday (3/22) at 11:45 in the Grand Salon A.

3. The Wall of Deliverables is back! – After a successful prototype in 2008, Jacco, Nathan and I decided to do it again and up the stakes one more time. This year people can submit online at http://www.wallofdeliverables.com and we have some amazing prizes lined up for the best of the best!

4. I’ll get to talk to everyone about the great things the IA Institute has been doing – Though my 2008 contribution in the IA Institute board of directors only started in October, I’ll have the opportunity to report on all the great stuff the IAI accomplished last year and have a conversation with our membership about where we are going next. Please join us Saturday 3/21 at 6:00pm (location TBD)!

5. We are doing a fun Board Game Night! – We have been discussing this since forever so I am excited we are making it happen! Come have fun with us Saturday evening (3/21), in the Skyway Room.

I really enjoyed reviewing submissions this year and feel like the program is very strong. This will also be my first time in Memphis so I am looking forward to visiting Graceland and the Civil Rights Museum.

There is so much I’m looking forward to (all the items I listed above don’t do justice to the amount of stuff that is actually going to take place – I was even promised knitting lessons from some master knitters!), so I hope you are feeling as energized and ready to rock as I am. See you in Memphis!

I procrastinated for 2 weeks to write it because I was trying to understand a problem and it was just not happening. I think I finally came to terms with it.

Hello fellow practitioners!

In the past 60 days I had the opportunity to take a closer look at the IA Institute and observe how it operates, recognize where some opportunities are and identify some of the challenges that we need to vercome.

It was a very edifying process, but a gruesome activity. Did you know our websites and service run on 26 different Movable Type blogs (version 2.6.6.1 from 2004)? Me neither. It’s magic what our volunteers were able to accomplish by hacking and patching that system; mad mad skills, I tell you.

Apart from technical marvels, that discovery process allowed me to think about what the Institute means to me and what it can mean to us in the future.

In recent years I had become more distant from the Institute and also noticed that many of my peers become more detached and less involved with the activities associated with it. I wondered what that meant.

This November was the 6th anniversary of the IAI. I was disappointed that we as a community didn’t remember or see the need to celebrate. That’s when I understood why I had drifted away myself: I just didn’t recognize the Institute as the face of our community of practice anymore.

Thinking about this I re-visited http://info-arch.org and was immediately reminded of where we came from. That was a time when our community was blooming with energy and we were screaming for action. Very talented and dedicated people came together, and out of that desire to evolve our practice, to raise awareness and understanding for what we do and to help move our profession forward, created a thriving international organization that brought our community together.

There was a strong vision from the get-go and progress was palpable. At any time I was involved, whether it was translating an article, mentoring a new professional or helping out during a local event, I knew I was making a difference in our community. It was a pleasure to spend the time and see others contributing as well.

Over the years, we have collectively established ourselves as practitioners and, along with our careers and the paths we have chosen, our needs have evolved. Many have drifted apart because they don’t feel the Institute is supporting their individual needs anymore. Others still feel great affinity for what the Institute represents to (and for) this community and continue to be involved and volunteer.

Today we have a great opportunity and an even bigger challenge. We can turn this organization into exactly what we need it to be. And not only for our current set of circumstances, but also for the future. We have matured along with our practice and we need an organization that can continue to support a mature and growing practice while helping a new generation of practitioners join the job market.

Let’s make the Information Architecture Institute the place that connects the legacy of our community and our professional future. Speak out now: What do you need? What do you want? How can you help? How can you be helped?

We must understand what our collective needs are in order to continue to build an organization that is relevant and sustainable. The Institute exists to provide infrastructure and build bridges across and beyond our community. Use those assets; tell the Institute what you need that isn’t there today. Let’s ensure the energy and resources from the Institute are used towards the things that really matter to you.

You can use the discussion list (1), our website (2), Twitter (3), our Get Satisfaction engine (4), Facebook (5), LinkedIn (6), talk to your peers and colleagues, your friends and family. Let’s have this conversation and figure it out together.

I am very excited about what we will accomplish in the next year and I most certainly expect you to participate and make the IA Institute work for you.

Happy holidays,

Livia Labate
Director of Getting Things Done
The Information Architecture Institute

(1) http://lists.iainstitute.org/listinfo.cgi/iai-members-iainstitute.org
(2) http://iainstitute.org
(3) http://twitter.com/iainstitute
(4) http://getsatisfaction.com/iai
(5) http://is.gd/4Iz
(6) http://is.gd/bUps

Check out more photos from the Wall of Deliverables.

We had a great crowd viewing and discussing the displayed deliverables all through the summit, thanks to a bunch of people who took the time to submit an entry. We were very satisfied with the results and received a lot of valuable feedback, so of course, we are doing it again!

To give you a sense of what it takes to make it happen, we’ve had two planning meetings so far where we discuss lessons learned and reviewed all feedback in detail, then started planning what steps need to be taken to set it up next Summit.

We have to figure out what kind of space we are dealing with (determined by the IA Summit organizers) so we can design the best walk-through flow and allow for people to hang out and discuss. We learned from last years that having to squat and squint was not the best thing for the deliverables that were hanging low on the wall, so we’re trying to get more horizontal space to ensure easy access and allow the deliverables to be more spread out.

We also learned that our entry form was taking more space than it needed and not helping convey as much as we wanted, so we’re picking more appropriate fields and designing is so that it’s legible and so that you can see the submission number from space.

The voting process was pretty smooth last year and the feedback indicated people were very satisfied with the prizes, but we’re looking into new options to make things fresh. If you’d like to sponsor, drop me a note!

One of the most effort intensive aspects of this initiative is to spend time hanging out around the Wall, helping contributors include their deliverables and answer questions from the crowd. Last year we conveniently placed a printer right there, but we really want to encourage people to submit and print in advance next time. It still is a lot of effort so if you would like to volunteer 30 minutes of your time to help facilitate, let me know!

We are toying around with some other very exciting ideas that I was planning on writing down on this post but that I just realize it will be much more fun if they are a surprise, so I’ll just leave it at that!

Nathan, Jacco and I will start broadcasting to the various UX outlets that you can submit deliverables as soon as we have our first to-dos out of the way, particularly coordinating with the IA Summit committee about how the Wall of Deliverables will be part of the program and how we’ll make people aware of what’s going on throughout the event.

If you have ideas, suggestions and comments, please let us know!

The list software we use is Mailman, which is extremely popular and very good at one thing: delivering mail. I guess they chose a pretty appropriate name for it. Other than that, it’s pretty sucky.

My intention when I started to take a look at our discussion lists was to understand how extensible our technology was to support any future plans (indexing archives, subscribing to threads, integration list subscription with membership profile, RSS subscription, etc). What I’ve found is a messy legacy that needs to be at least normalized before we can think of expanding its capabilities.

Here’s a list of all the discussion lists we have:

From this list it should be easy to tell that we (the IA Institute) have not been big on naming conventions. I created some of these lists at one point or another as I volunteered in different initiatives, but I didn’t even know all of them were out there. I would love to be able to go to the IAI website and just know what’s available (right now the site shows a partial list).

Some of these lists, I am sure, are dead. But somebody forgot to pull the plug. Also, between managing subscribers and moderating discussions, there is this horrible thing called the discussion list interface. Mailman as I said before is good at one thing and that’s not its user interface. It’s impressively adequate in terms of multi-lingual support and is flexible enough that you can customize presentation to fit your website (We have tried before), but if you don’t have a standard way to to do in an organization with such high volume, this mess is inevitable.

If it’s not clear from the rant above, many lists still have our old organization name (Asilomar Institute for Information Architecture) and are hosted at ibiblio.org, which provides free discussion lists. Another issue: We host our site and systems on Dreamhost. Their Mailman implementation doesn’t allow me to go directly and finagle with the lists directly (like merge archives or modify the code) so I have to ask them to do it, which means any changes may take a while.

Now that I’ve bitched about the current situation, here’s what I believe needs to happen:

Do you have experience with discussion lists? Drop me a note if you have any advice or suggestions. I’m particularly interested in systems that have discussion lists associated with member/profile management associated with other services. Anyone has experience with Drupal; any Drupal modules for discussion lists?

When we first started discussing roles, my main desire was to become the IAI Ombudsman. Having ran for the board on a platform of transparency, I thought the Ombudsman role would be a good way to introduce an initiative-agnostic role that remained 100% accessible to the membership and was able to directly respond to their needs.

Regardless of my desire to play the role of an open channel of communication that helps things get addressed, someone needed to take on the oversight of the Institute’s IT and Membership (which is corresponds to customer service, tech ops, and all systems). I volunteered to take these on because they seemed to be the most related to the things I wanted to do as an Ombudsman.

A problem became apparent to me right away: an Ombudsman, by definition, is supposed to be independent, neutral and impartial to do their job well. From the IAO Standards of Practice:

1.1 The Ombudsman Office and the Ombudsman are independent from other organizational entities.
1.2 The Ombudsman holds no other position within the organization which might compromise independence.

I have been trying to reconcile how I could play the Ombudsman role while being the director responsible for infrastructure oversight and the reality is that it’s just incompatible. Having spent the past few weeks learning about how the Institute runs, what the various systems are, who does what and what is currently understood as needs of the membership, it was not a big leap to figure out I needed to re-frame my role.

I thought lots about whether I should withdraw from the board so I could become the Ombudsman, but seeing where the current infrastructure is today, I think being the director of infrastructure is a better match for me and for the Institute *right now*. To address my concerns on the Institute’s transparency and foster a culture of openness, communication and accountability, we need systems and tools that support people working that way.

I know I have the right skills to lead that charge (as I design systems for a living) and I am interested in the kinds of infrastructure issues the Institute has today (more on that in a future post). There is plenty of work to do so I decided to write a job description to help me focus the time and energy I’m volunteering and so anyone knows how to use that time and energy. Please help me refine!

Director of Infrastructure

The director of infrastructure is responsible for overseeing the planning and development of systems and technologies needed to support and maintain the services and initiatives associated with the Information Architecture Institute.

Key responsibilities

Evaluate the short and long-term value and impact of technology decisions.

(When someone chooses to deploy a CMS, create a new feature or tweak existing services, I should be able to assess how this affects our overall infrastructure in terms of technology, cost and effort, and help them make the right choices).

Ensure infrastructure projects are properly managed and executed

(When we need to do something that contributes to the Institute’s infrastructure, I need to make sure projects have a clear purpose and sufficient resources to succeed, in addition to support and encourage contributors to move things along).

Keep the Institute and members abreast of infrastructure improvement plans

(During my time in this role, I need to involve institute members and keep them informed about what’s going on and set expectations about the direction things are going to ensure it’s in line with what everyone needs.)

Assess the infrastructure wants and needs of new initiatives

(When a new project comes around, I should offer advice and guidance so project champions are aware of what’s available to them and what they can build on)

Direct the Institute’s resources towards the highest value opportunities

(To get things done, I need to be mindful of the cost and benefit of utilizing our staff versus reaching out to the community for help and support)

Assess the organization’s ability to maintain core systems operational

(Evaluate, on an ongoing basis, how well the Institute can maintain it’s various services and advise the board of directors on areas of opportunity and risk)

Ensure a smooth role transition to the next director of infrastructure in office

(By the time I’m done with my term on the board of directors, I will have a transition plan for the next person who will take this role to ensure quality knowledge transfer and continuity of permanent efforts)

My goal is that my platform of transparency, vision and empowerment is well translated in the openness, communication and accountability of this role. Any thoughts, edits and additions much appreciated.