Skip to main content

To the Vendors, to Make Much of Time

Vendors: if you are investing in the sponsorship of a conference, then you must want to market to these customers, right? So when you get a “sponsor slot” to speak to the attendees, don’t waste it!  

Disclaimer: All of the ideas expressed in this article are my personal statements and opinions, and do not reflect the opinions/statements of the City of Urbana.

I attended a conference recently of IT Directors from cities, counties, and villages around Illinois.  What did we hear about (from a vendor who I won’t name here?): mining social media posts, augmented reality, and NASCAR performance measurement.   None of which mean anything to our problems.   For that you paid several thousand dollars?  (Plus travel costs for your representative?)

We appreciate the sponsorships, we really do.  And I’m absolutely fine with the quid pro quo of listening to your sales pitch.  Just make it relevant, that’s all I ask.  Send someone who knows the market, and knows the audience – and can speak to them to properly tell your story.

And if you don’t have someone to send who can be meaningful, how about getting creative?  You could donate the time back to the conference for an impromptu session.   Or invite a local person to come and speak on a topic that resonates.  (Even if there’s a speaker fee, that’s GOT to cost less than sending someone, right?)  You can still brand the session – and don’t you think that we’ll appreciate it ten times more than a standard boring pitch?

And now I'll climb down from my soapbox.

I feel that I need to explain the title and image of this post.  The title is from a poem that I remember from 11th grade, and the image is both a reference to the poem’s first line (“Gather ye rosebuds while ye may”) and my peace offering to the vendors.

Popular posts from this blog

The Tectonic Speed of Government, Part 1: Procurement

This post is my reaction to conversations about how hard it is to create change in government, and how government projects (and IT projects in particular) take so long from genesis to completion. This is part 1, about procurement; part 2 will address project implementations . PS - there was a surprise Part 3 of this series later! Warning : what follows is an “inside baseball” discussion of government IT procurement. I’m not trying to dissuade you from reading it, but if you’re not enmeshed in this world you might want to consider reading my articles on lighter topics like organizing your electronic life , the greatness of Abbey Road , or the story behind The Room . If you ARE enmeshed in this topic, then please don’t overlook my call to action at the end! Changing the process will take a group effort, and I’m hoping to get feedback on my scheme to create a library of reusable software specifications. By the way, this post’s first title was “The Glacial Speed of Government” bu

How To Videos: Lucity Queries with Microsoft SQL Server and Excel

What follows is not a blog, but some suggestions on using Microsoft SQL Server "Views" to query your Lucity data using Excel.   This information is intended to assist Lucity software users, and not for any nefarious purposes. I recommend watching the videos in Full Screen view and with HD resolution.  They're not as blurry as they look on this page!!  Each of these about two minutes long, but the original actions only took 50 seconds each.  (After recording them, I decided to slow them down to make them more watchable.) 1. How to create a SQL Server "View".   The video shows how to create a new View from the core Work Order table.  (WKORDER - see the data dictionary here .)  The video first shows the simple method of creating a view with all fields, then shows the more effective method of including only needed fields, and re-labeling them with their on-screen names. Music: "A View to a Kill" - Duran Duran 2. How to Connect to the Vi

Why the Tectonic Speed of Government?

The original name ("Glacial Speed of Government”) is both cliché and inaccurate, as it implies a faster pace than it used to. I decided that “Tectonic Speed” is more accurate because change in government shows tremendous resistance and moves slowly, but when it happens progress can occur in significant outbursts - and in those moments, there is great opportunity!     Click on "Read the Whole Thing" to access these links: Part 1 |  Part 2   |  Part 3  | Part 4 | Wait there's a Video?!  

The Tectonic Speed of Government, Part 3: It’s Never Over

Recently, I wrote two posts discussing why IT Projects take a long time: one on the Procurement Process and one about Project Implementations .  They were written during a time of three simultaneous projects, and they were therapy for me to exorcise some complaints... and make suggestions for others. From the start, I planned those as two topics – and I thought they'd finish the series. But this third part was a surprise, and the greatest lesson I learned from those projects. ********************************************************************************************* Disclaimer: All of the ideas expressed in this article are my personal statements and opinions, and do not reflect the opinions/statements of the City of Urbana. ********************************************************************************************* “It ain’t over till it’s over” - Yogi Berra on baseball, not IT projects. Trick Question : When is a software project over? Answer : Never

Tectonic Speed of Government, Part 2: Why do Government IT Projects Take So Long?

This is part two of my series on why government IT projects take so long. Part one complained that the Purchasing process is tough to navigate because methodically describing what you want to buy - and documenting your decision making - takes effort. That blog helped me vent some frustrations about parts of my job, although I admit that it was a little dry. (But please, this is Government Procurement.) With part two I’m on my home turf: the process that starts with the purchase of an IT tool and ends with its everyday use by people. If the process was successful, users are doing their jobs better than they did before. (A less successful outcome that also occurs: it’s harder to do their jobs, but at least their managers have better data.) This process, which I’ll refer to as the “Implementation” or “Project,” can take months or years for any organization - let alone a government. My first section explains why government IT projects take a long time, while the other three suggest