November 10th, 2008

Reflections on Writing

As a writing tutor, I tried to be as honest and straightforward about my assessments of student writing as I could while supporting the art and act of writing and helping writers to see where they had room to improve.  This made me a very polar writing tutor: people either loved sessions with me or they hated it and never returned.  If I got lucky, students who hated it realized that they needed the level of candid feedback that I provided and returned for more sessions with different pieces of work.  If I got extremely lucky, the writers that I absolutely reveled in working with returned time and time again.  That is not to say that I did not enjoy each and every single session I had (there were bad ones, but 90% of them were enjoyable).  But the quality of the writing and the talent of the writer allowed me to engage on a much deeper philosophical level with several students over time, getting past mechanics into more complicated issues like flow, thesis development, voice, and assertiveness.

I have not offered to read many of my classmate’s papers in the MSIM program, partly because it was no longer my job, but partly because my group work and the quality of the writing that resulted from that work discouraged me.  It is not that I am dealing with more English as a World Language speakers (some of whom have a better grasp of the mechanics of English composition than I do!), but that I am left unimpressed by the devotion to the art.  I recognize in many of my classmates the same tendencies that I wrestled with as a writing tutor: an aversion to the skill of written communication in general, a lack of interest in complete development of ideas, and no realization of the power that the written word holds.  Again, I do not imply that these are bad writers — there is no such thing - underdeveloped, perhaps, where skill can be improved, but never bad — only that they seem detached.

The problem is this: the MSIM program is a professional program, and a core competency for professionals is to be able to write.  By this, I do not mean the ability to string words together to make a coherent sentence - it is a much higher level than that.  It is the ability to use words to convince, to argue, to assert, to discuss, and to realize.  I do not demand that they enjoy the act, that they pine for the days when they can pick up the pen or sit down at the keyboard and write.  I do not even demand that they do so frequently (the program does, but I don’t).  Instead, I demand that they respect the process and that they devote themselves to nothing less than the best they can achieve.  Half-hearted is not sufficient.  I prefer no complaints, but I will tolerate those within reason, for not everyone is as interested in writing as I am.  If I am to hear whining the entire quarter about how we have to write a paper, I am unlikely to be interested in working with that individual again, for such reactions are uninspiring and indicative of more than they might think.

This is not a complaint post - far from it.  I am not bemoaning my peers, nor am I taking any stance in particular as to the technical quality of their work.  I have merely realized that my skills in writing have influenced my perception of my peers.  I have also realized that perhaps I have failed at something small but nonetheless significant: it was not simply my job to promote the art and act of writing as a writing tutor, but to carry this effort on.  I owe this in part to Kevin Desouza, associate professor at the Information School, who tirelessly offers on a weekly basis to both his Change Management and Finance classes to read any writing sent his way so long as it is mechanically correct.  His devotion to his students and to supporting them is above and beyond some of the other classes I have taken here.  This is neither good nor bad from a program perspective, but from the perspective of a tutor who has, perhaps, let the art slip, is inspiring nonetheless.

March 27th, 2008

Internships

I went down to Olympia yesterday to interview for an internship with the Washington State Department of Information Services. This position would essentially be working with DIS to help them roll out services from their development to production environments; most notably, this would involve work with SharePoint and allow me to have fairly decent exposure to a lot of different projects across state agencies. I wouldn’t be dealing with “end users” per se - at least not in the traditional sense of “non-technical everyday people”. The work would support system administrators and developers in their efforts to use the offerings put forth by DIS.

The interview went about as perfectly as I could hope - after getting signed into the building and getting a visitor badge, I was shown upstairs and talked with the group about my previous experience in SharePoint and answered a few questions about what I thought the internship might entail. As it turns out, one of the people I would be working with in that position was actually an MSIM student in the past, so there was also a smaller conversation about the program itself. The next step is figuring out who I would report to, since there’s some deliberation as to who would be most effective. After the interview, I was given a brief walkaround to meet a couple of other individuals in the office.

On this one, I’m optimistic.

There is, however, still my original discussion with the Washington State Department of Ecology, which has turned into something of a hassle. While Ecology’s project is fascinating - involving working directly with the state’s sustainability initiatives - there are a couple major problems that are causing red flags to pop up in my head left and right:

  1. Communication. I get very random e-mails from Ecology, and not just from a single person - from multiple people, and it’s often fairly clear that they’re not talking to each other internally at all. While I was very comfortably dealing with multiple people at DIS, I have always had a primary contact at each step of the way, which moved from their HR department to a high-level supervisor to a supervisor closer to the work that I would actually be doing. I know at this moment exactly who to talk to and who to work with within DIS to make an internship happen. With Ecology, I have no idea who’s in charge of coordination or who I’d be reporting to. On top of that, they can’t seem to figure out the difference between a capstone project and an internship.
  2. Vetting. Whereas DIS put me through a state application process, the usual requests for references, and an in-person interview, Ecology has done nothing of the sort (and in fact, unless I’ve been misreading the last couple e-mails, seem to be assuming that they’ve already brought me on as an intern!). As important as the vetting process is for an employer, it’s actually almost as important for an employee - it tells me that DIS is taking this seriously and putting me through a standard process for hiring. Ecology hasn’t even so much as requested a resume, to my current recollection.

In short, regardless of what happens with DIS, I’m likely to withdraw my interest in an internship with Ecology - it doesn’t matter how great the project is if the planning process itself isn’t executed well, and at this point, it doesn’t feel well-executed in the least. I’ve had a couple e-mail conversations with people within the MSIM program who have both recommended talking to Ecology either over the phone or in person, but with the DIS interview having gone well (and, quite frankly, sounding like it’ll offer many more opportunities to get involved in different areas), I’m not sure it’s worth the effort.

February 24th, 2008

Résumé Updated

My résumé has been updated. I’m starting to wonder whether I need to trim the damned thing, since it does seem like there’s a lot on there, and some of it may stop being entirely relevant after a certain period of time. I’m still very proud of being Eastside Journal’s Most Inspirational Graduate of 2001, but how long does a high school graduation award actually matter? This is a bit of a trickier question, since I’m still in school. I’ve had people look at that document and think it way too long, while others think it proves that I have a vast array of experience (let’s ignore my personal reaction to that last opinion for the moment).

February 24th, 2008

iA SUMMIT 2008 - Miami, FL

Hmm, if it weren’t in the middle of the second or third week of Spring, this would be freaking awesome. Registration would be fairly cheap, since I happen to have recently become a student member of The Information Architecture Institute.

January 31st, 2008

The Definition of an Information Professional

information professional: someone who has the ability to make decisions with regards to information.

Joseph Tennis, IMT530, January 31, 2008

January 29th, 2008

Career Goals

Even though this is posted on my internal wiki, I figured I’d post it here for posterity.

This document outlines my personal career goals as they currently stand, as well as related academic goals that inform these goals.

General Goals

  1. Apply my personal mantra, “everything is interconnected”, to information management and sustainability and understand how these fields infiltrate and influence everyday decisions.
  2. Work in a collaborative rather than an isolated environment.
  3. When possible, incite change. When impossible, make possible.

Academic Goals

  1. Serve as teaching assistant for an undergraduate course.
  2. Assist in the learning process of my fellow students; learning is not competition.

Topic-Specific Goals: Information Management

  1. Understand how information is ethically and professionally handled and embody these standards in my own work.
  2. Understand the paradigms behind information organization.
  3. Actively consider issues of information fragmentation, information overload, and information sustainability.
  4. Place human use of information first.
  5. Promote information accessibility.
  6. Participate in relevant national professional associations.

Topic-Specific Goals: Environmental Sustainability

  1. Significantly contribute to thinking and dialog about environmental sustainability and environmental policy.
  2. Understand the relationship between information and sustainable action.
  3. Promote corporate and public environmental stewardship.
  4. Recognize that sustainability is not achieved in a void. Promote cross-political and interdisciplinary sustainable initiatives.

    “I never saw a Democratic mountain or a Republican glacier.” - Daniel J. Evans

  5. Influence organizational thinking and action around sustainable ideals.
January 29th, 2008

A Shift in Philosophy

People may or may not be aware that my work at Evergreen made one thing abundantly obvious: everything is interconnected. I’ve been living by this mantra for quite some time (indeed, since somewhere around my freshman year at Evergreen), but lately, I’ve come to realize that, while it’s certainly sufficient to recognize this, there’s an extra layer to this idea that I hadn’t quite recognized. There are two ways that I can state this, and I haven’t quite decided which one I prefer yet, since they are two distinct expressions of the same set of ideas:

Everything is interconnected, given a particular context.

Or:

Everything is interconnected; context is king.

The word “context” is something that is repeated almost ad nauseam in a lot of the work that I’ve done so far in the MSIM program. A lot of user interaction design work depends on the context in which a solution will be used. How things are categorized depends on the context of that information in relation to other facets. The context in which a question is asked can affect the results of that question. Management styles differ depending upon how managers choose to contextualize different information in their environments.

There is one major thing missing at this point as well that I’ve actually chosen not to attempt to integrate: the centrality of the user (or, less technically, of people) in information management. The reason for this is that it’s already recognized in my personal statement of my career goals (which has not been posted to this blog - it exists on my personal wiki).

So what’s the difference between these two potential statements? “given a particular context” implies restrictions or limitations on what connections can be formed, and suggests to me that those limitations may not be surmountable. On the other hand, “context is king” recognizes the original spirit of the mantra of “everything is interconnected” - that everything, somehow, connects to something else, context or not. It also recognizes that context plays a central role in our accumulation of knowledge and information.

Which one I end up choosing will depend heavily on which of these interpretations I feel is more central to my work.

November 26th, 2007

Intranet Planning

Zach Hale sent along this short article on planning intranet architecture using information architecture practices.  Quite useful.

November 23rd, 2007

Résumé Updated

Somehow, the last update to my résumé omitted my ACM membership details, which I’ve now rectified. As always, the most recent version is available from this site’s navigation bar.

August 27th, 2007

Résumé Updated!

My résumé has finally been updated with my most recent information. Check out the link on this site’s navigation bar.