Saturday, October 3, 2009

Creating A Tangible Asset From An Intangible One


As I contemplated studying for the CRM, I picked up a copy of Kaplan and Norton's "Strategy Maps" (ISBN: 1-59139-134-2). With inspiration from one of its graphic designs, I pieced together my thought process for becoming one. Hope this helps.

Wednesday, September 2, 2009

SP Rec Ctr, Cont'd.

Never, ever underestimate the pros and cons of an Information Rights Management server.

Monday, August 17, 2009

The THG

The Telecommunications History Group is just what it sounds like: a local archival repository which houses the material history of the telecommunications industry. I help its (wonderful) director, Jody L. Georgeson, with the repository's documentation, lookout for potential collections, and process indexes on Saturdays; in turn, she helps me with my continuing education credits for my Certified Archivist (CA) designation. The archives has a cheery volunteer staff and encourages long-distance researchers. You can find the archives here.

SP Rec Ctr, Cont'd.

Have you seen this yet?

Wednesday, August 5, 2009

A List of To-Dos

Quite frankly, I have so much going on I don't know what to share with you first!

The day job: SharePoint Records Center pilot, of course, plus all the additional responsibilities like travel, training, records center ops, etc. But I'm also priviledged to be a member of a corporate committee and an internal think tank.

For ARMA's Standards Development Committee, my white paper proposal was accepted. It will address the line of custody between Document Control and Records Management. You can find the application to apply here.

Also, ARMA's Higher Education Task Force: I'm working on the non-proprietary contact information for major (RIM) educational institutions. We hope to reach as many programs as we can in the next two months to confirm program offerings.

I'm the Program Director for the ARMA Mile High chapter and I will begin a regular contribution to its newsletter. An ICRM article is due every month.

The ICRM: my term as Exam Administration Regent begins January 2010. You can find the press release here.

I'm working on another article for publication with Adele, of course.

I continue to design a new program for Mimi Dionne Consulting. It's coming along nicely. I'm proud of it. The website should be up soon.

I have a daily regimen of IT studies. I'm promoting the idea of The 2.0 Advisory Council. Founded by the impressive Susan Scrupski of SoCo Partners, you can find more information about it here.

I tweet (@MimiDionne) and I Facebook, of course, keeping tabs on all the people I admire. By the way, ARMA Mile High's trying a Twibe experiment. Check it out here.

I attend the Rocky Mountain SharePoint User Group meetings once a month. Find them here.

I've got a couple of presentations lined up in the Fall, of course.

And that's just the top of the list. Well, back to work.

Thursday, July 16, 2009

Herding Technomads, Cont'd.

The Records world looks very different to me now that I've begun to study programming. I begin to understand, where I did not before, that business units and end users have need to create sense out of something that has small sense. Bits and bytes...little more. So much freedom to be had--as I delve deeper into the limited structure of that which creates information from nothing, I regret (almost!) my tenured fascination with the life cycle of the record. Except that it is still the basis of all. Now, to bridge the two worlds. Yes, I can do that.

SP Rec Ctr, Cont'd.

You cannot use a separate Shared Services Provider (SSP) for a Records Center, can you?

Also, requirements gathering for business units.

Friday, June 19, 2009

SP Rec Ctr, Cont'd.

Name resolution.

Monday, June 1, 2009

SharePoint Records Center

Ok, I'm setting up a SharePoint Records Center, complete with customized information policies and routers and integrating with several well-known...applications/platforms. However, I don't feel comfortable posting the screen shots (again, I'm being careful of copyright infringement); therefore, I'm creating documentation that diaries the adventure for future presentations. I've decided to hint keywords that will appear within the presos as I accrue the slides. Think of it as a kind of scavenger hunt.

Today's list:

DNS
C#=.net
Visual Studio
Content types
E-Whiteboard application
Screencast
Test environment
Production
Site collection segregation
Load balancer
Information policies
Mapping content types
Stylesheets

Two blogs of note on the subject:

I've had the pleasure of speaking with him several times already on our favorite topic. A dapper blogger, you can find Don Leuders here.

This gentleman is a wealth of information. John Holliday's work is featured in several SharePoint Developer texts as well as online. I hope to catch up with him soon. You can find his blog here.

Saturday, May 30, 2009

What I Should Have Said...Tweet! Tweet!

Ahhh, Twitter. Darwinian. Now that I've been on for six months, I'm more aware of the subtleties of tweets like hashmarks and alternate desktop applications such as Seesmic and TweetDeck. They're particularly helpful in managing the @ tweets. I hate to miss one and I have in the past. Embarrassing but true, because I'm on/off alot due to the work load.

My retroactive exploration includes my tweet count and my use of language. The Marine had a great tweet this morning: if you're wondering why you have a small amount of followers, analyze your past forty tweets. So I did, objectivity being close to godliness in twitterverse and the key to success. Since I am my harshest critic, of course mine need finessing. For the purposes of public comment, I chose five tweets to share here:

Tweet No 1: "Morning! Puttering about today."
Verdict: Good lord. Really? That's the best I could come up with? I needed more caffeine before I posted. What I should have said was "Morning twitterverse! Pencil, pad of paper, and color wheel in hand to design personal, new clip art for blog and presos." Then I could have followed that with the tools I was using to create 'em.

Tweet No 2: "Interesting commentary in this week's Time on "The Future of Work", esp. Silicon Valley. "Is the next big thing cloud computing?"
Verdict: Why am I commenting on a comment regarding cloud computing derived from a print medium? That doesn't even make sense.

Tweet No 3: "Webinar: Strategic information Management: Beyond Personal Information. Sponsored by IAPP. Focus on GE."
Verdict: I could have expanded further to include real-time details, but unfortunately I was interrupted several times (as usual!) and heard about 20% of it. I almost deleted the tweet above because I couldn't contribute anything from it in real time, which is the usual expectation.

Tweet No 4: "Admiring one of the Met's newer exhibits: Period Rooms in the New American Wing http://bit.ly/WdlsN"
Verdict: Nerd alert: the above tweet was a guilty pleasure just for me. I was a historian first. Also, I'd love to go to New York soon, so I've been scoping out sites to visit.

Tweet No 5: "Ha! Adele misses me. That's sweet."
Verdict: About three of my followers know who Adele is. Ridiculous, self-absorbed tweet. Not at all in the spirit of those who I admire so much and follow.

ANYWAY, you can see the above needs some work. After calculations, I discerned I like about 15% of my tweets.

At the end of this six month period, I'm most surprised at my sense of possessiveness over my group of followers. I don't know if it's the subconscious influence of reality tv, but I find myself sometimes writing for my audience to keep them. For example, I follow a ballerina in San Francisco; therefore, I tweet occasionally that I'm watching a certain performance or that I'm picking up tickets to the Colorado Ballet. She sometimes posts in Russian, which I find fascinating, so I continue to follow her. Conversely, I fear tweeting any remarks on certain subjects, based on that old nugget, "Never discuss religion or politics with a friend". For example, I attend daily Mass, but that's not a tweet I ever send for fear of ostracizing those who I think of as professional colleagues. I wouldn't mention it to a colleague at work every day I attend; why would I post it in twitterverse?

In fact, if I had to graph it, I would probably design an end user's comfort with Twitter similar to an end user's comfort with an ERMS: two bell curves. First trough: you've signed on, you're anxious, you want to tweet well. Moving up the bell curve: you're making mistakes, you're anxious, you don't get it. First crest: you say, ahh, I don't get it...I'm out. Ride the crest to the second trough because you don't tweet; your account is static for a lengthy period of time (mine was about two months, I think). Second trough to second crest: you're back...you have a better understanding. You delicately use hashmarks, the FollowFriday thing, still making mistakes but it's better and you may be using one of the other platforms or may link Twitter and FaceBook. You feel more connected; besides, your list of followers expands...you've got to keep tweeting now! Second crest to third trough: that feeling of anxiousness is gone and you're completely comfortable. You ask the same as your followers: what's life beyond Twitter like? What's next? Anyone found it yet?

Remember, thanking your followers in twitterverse is a delicate objective. You run a serious risk of sounding "like a boor" as one of my followers tweeted, no matter how altruistic the intent. Twitter requires greater finesse than a verbal conversation. Be delicate, sharp, expert, and fascinating and you keep your group. You have only 140 characters to make a first impression every time you tweet, not just when someone decides to follow you; they could leave you anytime. Twitter is the most extraordinary real time experiment in what I've always suspected: we all have a real estate value. For better or for worse, Twitter counts that value in the number of followers.