Daily Archive: June 12, 2010

the endless pursuit of…complacency

This is a post about differing perspectives on technology and support of student learning here at SCU, so I must preface things a bit.  Any administrator at any academic institution, especially in “these tough economic times” (a phrase that I am so sick of…yet I use here in this post) has to make tough decisions about how to invest one’s money.  Especially if expenses have trended and gone generally in one direction for many years, it’s hard to suddenly say “let’s spend more money, in a different way!”  I know this, even as I put together initiatives for new projects and programs that either change my budget or require additional funds.  So I can empathize with the mentality that I’m describing below.

Doesn’t mean I agree with it, though.

Santa Clara has a great program that supports innovation in technology.  The Tech Steering Committee offers up grants to those that are pushing forward with technology in the use of teaching, learning, and/or research.  It’s meant, at the least, as seed money to see if something will be useful.  Ideally, it’s to get a project off the ground that will, with proven success, turn into an ongoing operation.

I have applied for a grant each year I’ve been at SCU with the latter goal in mind – I want to start something that will last for years into the future.  As part of a larger roadmap of where I think the law school should be headed.  And I have received 2 grants in 2 tries, totally over $24,000.  I applaud SCU for this program, which was offered even during the especially lean 2009-2010 budget year.

(more…)

tips for Capstone

In my recent review of Michael Fern, my professor in the final course in the MBA program (known as Capstone), I mentioned a few tips on surviving the class.  I thought they might merit a post on their own.  So here they are…

6 person teams – The most important part of the entire class, IMO, is finding the right team.  Find the right people, the right mix of skills, and the right set of personalities to be as productive as you can be.  If that’s 4 people, great.

Having said that, you’ll want to try to get to 6 people if you can find the right ones.  Just think about the roles that are needed and/or the sections to be covered:

  1. Integrator (and make sure you have 1-2 others that will look over things at the end, too)
  2. External Analysis (this might be 2 people easily)
  3. Financial Analysis (need a 2nd set of eyes here, too)
  4. Corporate Strategy (linked to Business Level)
  5. Business Level Strategy (linked to Corporate)
  6. Exhibits (collecting, making them look consistent, etc, which requires a single person at the end)

So I indicate 6 people there, but note that some areas will need more people and help.  Imagine doing all of that with fewer than 6.  Also, this doesn’t even consider the Intro section, the Synthesis or Recommendations.  The last part really needs to be done as a team, then written up by 1 person.

Collaboration tools – One of the biggest issues I’ve had with the Leavey School of Business over the last 3 years is that the school doesn’t really provide anything that aids collaboration.

During Capstone, you will be going through financial statements and making exhibits(documents), articles (often web pages), and communicating every which way (e-mail, phone, real-time screen-sharing).  You’ll want ways of keeping all files in one location, being able to have multiple people edit a single file, communicate with the group, and probably doing a kind of real-time, video/phone conference session with shared documents.

We utilized the following:

  1. Mailing list – we used google, but whatever will work.  This was used just for e-mails.
  2. Dropbox.com – We kept all of our relatively static documents here.  Financial statements and various other electronic sources, plus our drafts of each section.  The 2GB you get here and unlimited file size were the key factors here (Google Lists’ files section has a file size and capacity limit).
  3. Google Docs – for the few documents that we wanted to truly quickly collaborate on.  The best example is the Bibliography, which we just kept adding to as we found and entered citations.
  4. vyew.com – This was the best free tool we found where we could all talk together (they offer a conference call number for free), look at documents simultaneously, and mark them up as needed.  For instance, if we felt that an exhibit posted should look differently, then any one of us could use the pen tool and just draw on it.  The person in charge of that area could then make the real changes, share them again, etc.

Ground Rules – Set these early.  Good ones are:

  1. Citation style – MLA is probably the easiest.  Don’t let anyone cite anything without using the style, or it’ll likely slip by in the final edit.
  2. Receptivity to changes – you can discuss changes that the integrator made to a section, but you can’t be arguing about it and no one can go about feeling hurt because a paragraph was edited out or whatever.
  3. When and how often you’ll be meeting – we agreed early on that we would meet “as often as we needed, for as long as we needed” and acknowledged that during the quarter we would meet more often and for longer periods of time.
  4. What you will do in case of writer’s block, lack of data, help needed on something, etc.  How will you respond, as a team, to obstacles?