Skip to main content

Collegiate Stadiums Projecting Pro Brands

My son and I throughly enjoyed watching The Ohio State University Buckeyes shred the Miami of Ohio Redhawks on a recent Saturday afternoon. Following an early afternoon downpour, the humidity and recently-cleared skies brought a healthy glimmer to everyone's skin. It was hot. Which makes folks thirsty.
A few years back, Ohio State, like many other universities, began selling beer during football games. As a college student and later as an alumni, I experienced some of the greatest tailgating in the country--frequently enjoying a beverage or two. Why not bring it inside and further line the pockets of the university? The argument at the time centered less around the fiscal and more around alleviating the need for ticketholders to drink intensely immediately before the game knowing they would need to last through a 4 hour contest. The university claimed people would enter the stadium less intoxicated knowing they could get their fill inside. I would love it if the Sociology department performed a study to judge the efficacy of this hypothesis.
Rather than debate the merits or transgressions of alcohol, I would invite Ohio State (and any other public institution) to further scruitinize and debate their position in choosing to sell alcohol at stadiums--as it relates to their brand. We enjoyed great seats from a friend right on the north goal line. They were right on the aisle. Despite these amazing seats with an incredible view, I missed a good chunk of the game. Was my view obstructed by a support pillar? Did my son suddenly take ill? No, the constant stream of fans exiting and entering our row as well as walking up and down the nearby steps disrupted our viewing frequently if not near-consistently. Hey, I get it. It's a venue with 103,000+ other fans. We need to be accommodating and graceful. Everyone needing into or out of the row exhibited politeness and cordiality. It was the fact that in all of these interruptions, almost everyone returned holding a beer or two in their hands. As a fan and an alumni, I love going to Ohio State games. There's nothing like the excitement, energy, and antics. And maybe as I age, different things are important to me. I think Ohio State needs to think deeper about what sort of brand image all these people constantly wandering around getting beer (and relieving themselves) projects. Personally, I want to watch the game. I don't want to watch massive groups of people filling the aisles. If it becomes a better experience to watch at home or to even tailgate without buying tickets, how does that impact Ohio State's brand? Maybe Ohio State doesn't care--but I think it should. I always tell my kids, "pay for experiences--not stuff" but if that experience is poor, folks are unlikely to return. The NCAA continues to try to preserve the mystique and innocence of college athletics. They're fighting the pay-the-players argument more fervently now--especially with pending legislation in California. Professional sports has long embraced alcohol and now looks certain to leverage gambling to increase the business vibrancy and lucrative opportunities. Professional sports is business though. Amateur athletics is not. For many universities, sports creates an incredible and vibrant revenue source--hundreds of millions of dollars annually. It won't be easy while treating amateur athletes fairly and providing a great in-person fan experience all while competing with everything vying for our attention. Both the NCAA and collegiate athletic programs must constantly strive to preserve their brand. I think that brand revolves around team spirit and connect, amateurism, and academics. Perhaps it's too late to turn back but we must remember the sport is the entertainment--not the alcohol, gambling, or revenue structure. And the sport only exists because of the academic institutions.

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 worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i