Skip to main content

You've Been Marketed!

My office "won" a free lunch yesterday at a local eatery. Unsuspecting, naive professionals that we are, we all figured, how fortuitous of us--we won! Wrong. We were about to be 'marketed'.

Gathering at the front door of the restaurant, one of our crowd didn't belong. Who's this guy, I thought. Oops, I'm out of the loop again...new employee. Nope, that's not it. Why is he wearing a suit?

"Hi, I'm Ron. I'm hosting your lunch today. I have a table ready over here for us." Ok, so this guy is with the restaurant. He's milking the opportunity to show off the restaurant. Fine. Although, what's up with the suit?

After we sit down, Ron goes on to explain he's a financial advisor with Ameriprise. Huh? Where'd you come from pal? Then it hits me: he's "purchased" our time. Brilliant! Now I'm really into this. I start reviewing the marketing:
  • captive audience
  • getting something in exchange for listening to a pitch
  • targeted marketing (I doubt it was a coincidence our firm was picked...and Ron could have performed reconnaissance ahead of time)
  • folks who actually might need financial services
  • all in a comfortable, neutral setting
Ron let everyone order (requesting to keep it around $10/person) and then while we were waiting for our food, Ron gave his 5 minute pitch. Afterward, he had us complete a survey with contact information and financial needs (he said it was a NASD requirement...I need to look that one up). And then he left--left us to contemplate what just happened! I think most of us already had financial plans in place but I saw a few folks putting thought into Ron's survey.

Overall, I was impressed. Impressed that someone had punched through my marketing firewall without leaving me feeling like I'd just encountered Slimer. I received something in exchange for my time. It was a bit misleading but I'm willing to let that go. I also admired the initiative. It had to take guts to pull off the presentation. I really hope this pays off for Ron--I'd love to know conversion rates on this approach.

Comments

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)]

I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent!

I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around.

Thanks in advance!

Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario...
I'm workin…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…